LINBO & italc-rlp integration (Re: Gosa vs. CipUX)
On Fri, Jan 07, 2011 at 04:57:44PM +0100, Mike Gabriel wrote:
> Hi Petter, hi Klaus,
> On Fr 07 Jan 2011 11:01:34 CET Petter Reinholdtsen wrote:
> >[Klaus Knopper]
> >>Hi Petter,
> >>Ok, here I am, at least for LINBO and italc-rlp. What do I need to
> >>do now?
> >I would suggest showing up on IRC to coordinate, to a test
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I'm an occasional
visitor of #debian-edu, and will ping Petter when I get a chance. :-)
> >installation of the squeeze-test ISOs and figure out what need to
> >change on the installed system to integrate the two tools to work out
> >of the box (which I have no idea what is doing). When you know what
> >need to change, see if this configuration / setup can be done using
> >preseeding ( -> add preseeding settings to debian-edu-install),
For LINBO, we probably don't need to change anything in Skolelinux.
LINBO consists of a kernel and an initial ramdisk für PXE booting a
graphical imaging and direct boot console that handles various operating
systems. It can be installed on any machine acting as DHCP-Server.
Only if we want to install LINBO on Tjener in order to easily
install and repair workstations in the same subnet, we could provide
scripts that change the DHCP servers configuration. But I believe this
can also be done manually. LINBO really just needs the two files in a
new directory that should be accessible for tftpd.
italc-rlp uses the same mecahnism and packaging as italc. So, this is
probably also no big deal, though the key installation mechanism could
be more elaborated.
> >editing of existing files ( -> create cfengine rules in
> >debian-edu-config cf/) or by adding extra files ( -> add them to
> >debian-edu-config). If some script need to run during installation to
> >dynamically adjust the setup at install time, a combination of these
> >might be needed.
> >When changes are done to the packages in svn, one of us with upload
> >right can upload it into our test repository to get new ISOs for
> as far as I know, LINBO is not in Debian at all and italc-rlp sounds
> like a modification of the original italc software (which is already
> packaged for Debian).
> Thus, as far as I understand,
> (1) some effort has to be put in filing an Debian ITP (intent to
> package for Debian) for LINBO and
Creating a Debian package for the LINBO binaries with documentation and
examples is easy. Creating a single source package from the 1.2 GB of
sources is near to impossible. I don't know if this is a requirement.
We have LINBO packages on http://rp.skolelinux.de/packages/linbo/, and
italc-rlp at http://rp.skolelinux.de/packages/italc/ .
Wait... One thing missing in LINBO is automatic localisation yet, since
it is quite monolithic, but this is not difficult to change.
> (2) the Debian italc package and italc-rlp have to checked against
> each other (I do not known about the differences of italc and
> italc-rlp and their development history).
Since the original italc in Debian is kind of abandoned and italc2 is,
as far as I know, not near to be usable, we made a fork of italc that
contains our addons, which are examination mode and observer
notifications plus a "loose interface" with cipux for internet access
and examinee account management. Our package contains the necessary
Conflicts: fields in order to just replace italc by italc-rpl cleanly,
and works fine with Skolelinux as well as plain Debian. We also have a
source patch of italc-rlp vs. italc, so it's quite easy to create
italc-rlp from italc using a diff.
> There probably is some
> more communication needed between upstream italc, italc-rlp and the
> package maintainer (if these are three differnt parties)...
Martin Öhler who has been working on italc-rlp and its packaging, has
discussed the issues with the italc authors, but these now seem to be
busy developing italc2, which is not useful as development base for us
We have an add-on CD containing LINBO and italc-rlp, which we use for
> I would love to see iTalc and LINBO move into Skolelinux...
Me, too. It would be great if some people who have the power to make it
happen, could attend our developer meeting in February in
Zweibrücken/Germany. More about this later.