devil-linux-develop — developer discussions

[Devil-linux-develop] [Patch] network script

[Thomas E. <tho...@bu...>]

the /etc/sysconfig/nic/ifcfg-vlanXXX doesn't work without this patch:

--- config/etc/init.d/network.old       2004-02-11 00:09:57.000000000 +0100
+++ config/etc/init.d/network   2004-02-11 00:10:25.000000000 +0100
@@ -275,9 +275,9 @@
         start)

                 #
-               # if vlan tools are installed set vlan naming shema
+               # set vlan naming shema
                 #
-               test -x $VLAN && $VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> /dev/null
+               $VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> /dev/null

                 #
                 # physical interfaces are brought up first


-- 
thomas

Re: [Devil-linux-develop] squid redirector ?

[Friedrich L. <fl...@fl...>]

*REAL NAME missing!*

Touch13 wrote on 10.02.2004 16:10 MET:
> 
> I work on the stable release (1.0.4)...

Version 1.0.x is a stable release that only gets bug fixes!

Maybe some stuff is back-ported from 1.1.x but all development of new 
features should be done on 1.1.x.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

[Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Friedrich L. <fl...@fl...>]

Hi Bruce!

You might have read that Arnaud Gomes-do-Vale is working on IPv6 support 
for DL. But this implies that he has to modify the syntax for the routing 
entries in /etc/sysconfig/nic/ifcfg-ethX and replace the : with a | as the 
: is used in IPv6 addresses.

Now to have consistent syntax in the routing syntax - it makes the 
documentation much less confusing to the users and saves us a lot of 
possible troubles - I want to change the syntax for IPv4 too when 
integrating Arnauds changes for IPv6.

Not much fuzz about that _but_ the crux is that it would introduce troubles 
during upgrading. So could you possible prepare the update script to take 
this into account, but not checking in those changes till I've got the 
contributions of Arnaud applied?

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] squid redirector ?

[<hzu...@ra...>]

On 02/10/2004 10:10:28 AM Touch13 wrote:

You got a name?

>Le Mardi 10 F=E9vrier 2004 15:01, Heiko Zuerker a =E9crit :
>> > I planned to add a squid redirector (squidguard) in DL and i ask m=
e
>if
>> > this is
>> > not allready planned ?
>>
>> Not that I know.
>>
>> > I have make squidgard pakage for DL, This application need an old
>version
>> > of
>> > berkley db and i have make this package too. but i dont found how
>modify
>> > the
>> > file 'ld.so.conf' in build process and how this change is apply fo=
r
>the
>> > rest
>> > of the build process
>>
>> You should not need to modify this file, what's the change you want
>to do?
>> If you just have to add a line, use something like this:
>> echo "my new line" >> $ETCDIR/etc/ld.so.conf
>Yes, i just want add a line.
>>
>> > ps; sorry for my poor english, i'm french ;-)
>>
>> Excuses ;-)
>> (for most of us English is a second language...)
>>
>> And don't forgett to send us the patch later, so we can include it.
>;-)
>Of course ;-)

Cool !

>I work on the stable release (1.0.4) and for my test i have rebuild
>entierly
>DL (with XFS support) and when the build process try to apply XFS patc=
h
>it
>stop and saw this patch is allready apply.
>Any idea ?

The XFS part is currently not supported/maintained, I would suggest you=
 use
another filesystem like reiserfs. Or.... you can fix it for us, but it
wont' work together with grsecurity.
The next major DL release will have XFS support, since the kernel has i=
t by
then as standard FS and it won't conflict with grsecurity anymore.

Heiko
=

Re: [Devil-linux-develop] squid redirector ?

[Touch13 <to...@fr...>]

Le Mardi 10 F=E9vrier 2004 15:01, Heiko Zuerker a =E9crit :
> > I planned to add a squid redirector (squidguard) in DL and i ask me if
> > this is
> > not allready planned ?
>
> Not that I know.
>
> > I have make squidgard pakage for DL, This application need an old versi=
on
> > of
> > berkley db and i have make this package too. but i dont found how modify
> > the
> > file 'ld.so.conf' in build process and how this change is apply for the
> > rest
> > of the build process
>
> You should not need to modify this file, what's the change you want to do?
> If you just have to add a line, use something like this:
> echo "my new line" >> $ETCDIR/etc/ld.so.conf
Yes, i just want add a line.=20
>
> > ps; sorry for my poor english, i'm french ;-)
>
> Excuses ;-)
> (for most of us English is a second language...)
>
> And don't forgett to send us the patch later, so we can include it. ;-)
Of course ;-)

I work on the stable release (1.0.4) and for my test i have rebuild entierl=
y=20
DL (with XFS support) and when the build process try to apply XFS patch it=
=20
stop and saw this patch is allready apply.
Any idea ?
 =20
Regards.

Re: [Devil-linux-develop] kernel 2.6.2

[Heiko Z. <he...@zu...>]

> Hi heiko.. can you put the kernel 2.6.2 image to the src distribution
> and remove the patch for the gettime problem

I did that already (years ago)... ;-)

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

[Devil-linux-develop] kernel 2.6.2

[Oliver J. <oli...@mo...>]

Hi heiko.. can you put the kernel 2.6.2 image to the src distribution
and remove the patch for the gettime problem

thanx

oliver

Re: [Devil-linux-develop] squid redirector ?

[Heiko Z. <he...@zu...>]

> I planned to add a squid redirector (squidguard) in DL and i ask me if
> this is
> not allready planned ?

Not that I know.

> I have make squidgard pakage for DL, This application need an old version
> of
> berkley db and i have make this package too. but i dont found how modify
> the
> file 'ld.so.conf' in build process and how this change is apply for the
> rest
> of the build process

You should not need to modify this file, what's the change you want to do?
If you just have to add a line, use something like this:
echo "my new line" >> $ETCDIR/etc/ld.so.conf

> ps; sorry for my poor english, i'm french ;-)

Excuses ;-)
(for most of us English is a second language...)

And don't forgett to send us the patch later, so we can include it. ;-)

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-linux-develop] [PATCH] IPv6 support

[Heiko Z. <he...@zu...>]

> Friedrich Lobenstock <fl...@fl...> writes:
>
>> For new features please work with 1.1.x as 1.0.x is the "stable"
>> branch. If something works within 1.1.x we might back-port it -
>> similar to the linux kernel, but don't count on it.
>
> That's what I am doing, actually. :-) I still need some getting used
> to the build system, though.

The docs are (of course) out-dated.
The main difference is, that you don't need to create the "links" in
scripts/build anymore, it's all done with the insserv utility.

Take a look at the top part of the other scripts, you see there all you
need to add to the new ones.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-linux-develop] [PATCH] IPv6 support

[Arnaud Gomes-do-V. <Arn...@ir...>]

Friedrich Lobenstock <fl...@fl...> writes:

> For new features please work with 1.1.x as 1.0.x is the "stable"
> branch. If something works within 1.1.x we might back-port it -
> similar to the linux kernel, but don't count on it.

That's what I am doing, actually. :-) I still need some getting used
to the build system, though.

> The documentation for that can be _currently_ found at
>    http://www-test.devil-linux.org/documentation/1.1.x/

Thanks.

-- 
Arnaud

Re: [Devil-linux-develop] [PATCH] IPv6 support

[Friedrich L. <fl...@fl...>]

Arnaud Gomes-do-Vale wrote on 10.02.2004 11:22 MET:
> Friedrich Lobenstock <fl...@fl...> writes:
> 
> 
>>I have reworked your patch for 1.1.x. Can you please test it
>>since I have no IPv6 network up and running.
> 
> 
> I am currently rebuilding the CVS version. I would like to include
> radvd as well, since it is often needed on IPv6 routers; is there any
> up-to-date documentation about the build system? I am not sure which
> parts of the 1.0.x documentation are still valid.

For new features please work with 1.1.x as 1.0.x is the "stable" branch. If 
something works within 1.1.x we might back-port it - similar to the linux 
kernel, but don't count on it.


The documentation for that can be _currently_ found at
   http://www-test.devil-linux.org/documentation/1.1.x/

PS: The page above will change when we get the design from our new web 
designers, so don't count on it that the link will be stable all time. If I 
don't forget I will add the appropriate redirects, so you might have to 
remind me if I'd forget.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

[Devil-linux-develop] squid redirector ?

[Touch13 <to...@fr...>]

Hello,

I planned to add a squid redirector (squidguard) in DL and i ask me if this is 
not allready planned ?

I have make squidgard pakage for DL, This application need an old version of 
berkley db and i have make this package too. but i dont found how modify the 
file 'ld.so.conf' in build process and how this change is apply for the rest 
of the build process  

regards

touch13

ps; sorry for my poor english, i'm french ;-)

Re: [Devil-linux-develop] [PATCH] IPv6 support

[Arnaud Gomes-do-V. <Arn...@ir...>]

Friedrich Lobenstock <fl...@fl...> writes:

> I have reworked your patch for 1.1.x. Can you please test it
> since I have no IPv6 network up and running.

I am currently rebuilding the CVS version. I would like to include
radvd as well, since it is often needed on IPv6 routers; is there any
up-to-date documentation about the build system? I am not sure which
parts of the 1.0.x documentation are still valid.

-- 
Arnaud

Re: [Devil-linux-develop] remote update

[Heiko Z. <he...@zu...>]

> hzu...@ra... wrote on 09.02.2004 19:54 MET:
>> On 02/09/2004 03:12:42 AM Friedrich Lobenstock wrote:
>>
>>>Heiko Zuerker wrote on 09.02.2004 02:20 MET:
>>>
>>>>Friedrich Lobenstock wrote:
>>>>
>>>>
>>>>>It has to be done in the initrd anyway and you are not changing those
>>>>>libraries when doing the update. And yes this might be a problem of
>>>>>its own, we can not change the initrd anymore. Hmmmmm.....then initrd
>>>>>needs some fixed parts (does not change across stable version) which
>>>>>loads the varibale ones, taking into account to update those if an
>>>>>"update CD" exists. Then the rest of the system is updated. Now this
>>>>>might also be a good idea to include the update script _from_ CD.
>>>
>>>This
>>>
>>>>>way we can provide for a more complicated if we did not think about a
>>>>>specific update problem later and as this script is tamper proof (on
>>>>>CD!) it can check all the signatures against a provided signature
>>>
>>>file
>>>
>>>>>(is that really needed?).
>>>>
>>>>
>>>>Since all update functions are on the CD anyway (pre_init script), the
>>>>existance of this script would be the only requirement.
>>>>
>>>>This would be the procedure:
>>>>1. initrd loads
>>>>2. initrd replaces bootcd.iso with bootcd.iso.new (after verifying it)
>>>>3. initrd continues as usual
>>>>4. pre_init sees the CD version is different to the config version and
>>>>performs an update (interactive part already implemented).
>>>
>>>What do you do if initrd has to be updated?
>>
>>
>> I would suggest that the pre_init script takes care of this. The correct
>> initrd.gz is on the ISO image and just needs to be copied over onto the
>> usb
>> stick or whatever is used.
>
> Then direct after the upgrade a reboot has to be forced to activate the
> new
> initrd, I think. Or would you give the initrd's a version number so you
> can
> distinguish if a forced reboot is needed or not?

Hmmm.....
I think we should force a boot whenever we updated the initrd.
This would be the easy way. ;-)

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-linux-develop] remote update

[Friedrich L. <fl...@fl...>]

hzu...@ra... wrote on 09.02.2004 19:54 MET:
> On 02/09/2004 03:12:42 AM Friedrich Lobenstock wrote:
> 
>>Heiko Zuerker wrote on 09.02.2004 02:20 MET:
>>
>>>Friedrich Lobenstock wrote:
>>>
>>>
>>>>It has to be done in the initrd anyway and you are not changing those
>>>>libraries when doing the update. And yes this might be a problem of
>>>>its own, we can not change the initrd anymore. Hmmmmm.....then initrd
>>>>needs some fixed parts (does not change across stable version) which
>>>>loads the varibale ones, taking into account to update those if an
>>>>"update CD" exists. Then the rest of the system is updated. Now this
>>>>might also be a good idea to include the update script _from_ CD.
>>
>>This
>>
>>>>way we can provide for a more complicated if we did not think about a
>>>>specific update problem later and as this script is tamper proof (on
>>>>CD!) it can check all the signatures against a provided signature
>>
>>file
>>
>>>>(is that really needed?).
>>>
>>>
>>>Since all update functions are on the CD anyway (pre_init script), the
>>>existance of this script would be the only requirement.
>>>
>>>This would be the procedure:
>>>1. initrd loads
>>>2. initrd replaces bootcd.iso with bootcd.iso.new (after verifying it)
>>>3. initrd continues as usual
>>>4. pre_init sees the CD version is different to the config version and
>>>performs an update (interactive part already implemented).
>>
>>What do you do if initrd has to be updated?
> 
> 
> I would suggest that the pre_init script takes care of this. The correct
> initrd.gz is on the ISO image and just needs to be copied over onto the usb
> stick or whatever is used.

Then direct after the upgrade a reboot has to be forced to activate the new 
initrd, I think. Or would you give the initrd's a version number so you can 
distinguish if a forced reboot is needed or not?

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] remote update

[<hzu...@ra...>]

On 02/09/2004 03:12:42 AM Friedrich Lobenstock wrote:
>Heiko Zuerker wrote on 09.02.2004 02:20 MET:
>> Friedrich Lobenstock wrote:
>>
>>> It has to be done in the initrd anyway and you are not changing those
>>> libraries when doing the update. And yes this might be a problem of
>>> its own, we can not change the initrd anymore. Hmmmmm.....then initrd
>>> needs some fixed parts (does not change across stable version) which
>>> loads the varibale ones, taking into account to update those if an
>>> "update CD" exists. Then the rest of the system is updated. Now this
>>> might also be a good idea to include the update script _from_ CD.
>This
>>> way we can provide for a more complicated if we did not think about a
>>> specific update problem later and as this script is tamper proof (on
>>> CD!) it can check all the signatures against a provided signature
>file
>>> (is that really needed?).
>>
>>
>> Since all update functions are on the CD anyway (pre_init script), the
>> existance of this script would be the only requirement.
>>
>> This would be the procedure:
>> 1. initrd loads
>> 2. initrd replaces bootcd.iso with bootcd.iso.new (after verifying it)
>> 3. initrd continues as usual
>> 4. pre_init sees the CD version is different to the config version and
>> performs an update (interactive part already implemented).
>
>What do you do if initrd has to be updated?

I would suggest that the pre_init script takes care of this. The correct
initrd.gz is on the ISO image and just needs to be copied over onto the usb
stick or whatever is used.

Heiko

Re: [Devil-linux-develop] remote update

[<hzu...@ra...>]

On 02/09/2004 01:34:21 PM Diego Torres wrote:
>On Sun, Feb 08, 2004 at 08:10:10PM -0500, Heiko Zuerker wrote:
>
>> >I mean how do you check the signature if the user did run custom-cd?
>> >How do we support security against tempering that way?
>>
>> Actually the user has to provide his own key pair. It's like the
>signing
>> of the etc.tar.bz2, the user has to burn his own public key onto the
>ISO
>> with custom-cd.
>
>i've been very busy and out for a while. is this gpg stuff configurable
>(with other words, can i take this feature off a custom build? :)

Do you mean to turn it off ?
It's only active when you custom-cd you ISO image and put your public key
onto the CD.

Heiko

[Devil-linux-develop] [fmII] Linux-VServer 1.3.7 released (Development branch)

[<no...@fr...>]

This email is to inform you about the release of version '1.3.7' of
'Linux-VServer' through freshmeat.net. All URLs and other useful
information can be found at

    http://freshmeat.net/projects/vserver/

The changes in this release are as follows:
A minor memory limit issue was resolved. XFS IUNLINK and BARRIER
support was added. The network source address selection was enhanced.
 

Project description:
Linux-VServer allows you to create virtual private servers and
security contexts which operate like a normal Linux server, but allow
many independent servers to be run simultaneously in one box at full
speed. All services, such as ssh, mail, Web, and databases, can be
started on such a VPS, without modification, just like on any real
server. Each virtual server has its own user account database and
root password and doesn't interfere with other virtual servers.  

Trove categories:
[Development Status  ] 5 - Production/Stable
[Intended Audience   ] System Administrators
[License             ] OSI Approved, OSI Approved :: GNU General Public
License (GPL)
[Operating System    ] POSIX :: Linux
[Topic               ] Security, System :: Operating System Kernels ::
Linux 

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects and
categories you're subscribed to in the right column, which you may cancel
by highlighting the project or category in question and clicking the
'delete' button.

Sincerely,
freshmeat.net 

Re: [Devil-linux-develop] remote update

[Diego T. <dt...@co...>]

On Sun, Feb 08, 2004 at 08:10:10PM -0500, Heiko Zuerker wrote:

> >I mean how do you check the signature if the user did run custom-cd?
> >How do we support security against tempering that way?
> 
> Actually the user has to provide his own key pair. It's like the signing 
> of the etc.tar.bz2, the user has to burn his own public key onto the ISO 
> with custom-cd.

i've been very busy and out for a while. is this gpg stuff configurable (with other words, can i take this feature off a custom build? :)

-- 
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC  2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.  
Diego Torres - dtorres at anthalia dot org - Madrid / España

[Devil-linux-develop] [fmII] ALSA driver 1.0.2c released (Stable branch)

[<no...@fr...>]

This email is to inform you about the release of version '1.0.2c' of 'ALSA
driver' through freshmeat.net. All URLs and other useful information can
be found at

    http://freshmeat.net/projects/alsadriver/

The changes in this release are as follows:
This release adds a driver for RME HDSP MADI (hdspm) and fixes a few
compilation problems with kernel 2.6.  

Project description:
The Advanced Linux Sound Architecture is composed of several parts.
The first is a fully modularized sound driver which supports module
autoloading, devfs, isapnp autoconfiguration, and gives complete
access to analog audio, digital audio, control, mixer, synthesizer,
DSP, MIDI, and timer components of audio hardware. It also includes a
fully-featured kernel-level sequencer, a full compatibility layer for
OSS/Free applications, an object-oriented C library which covers and
enhances the ALSA kernel driver functionality for applications
(client/server, plugins, PCM sharing/multiplexing, PCM metering,
etc.), an interactive configuration program for the driver, and some
simple utilities for basic management.  

Trove categories:
[Development Status  ] 4 - Beta
[Environment         ] Console (Text Based)
[Intended Audience   ] Developers, End Users/Desktop
[License             ] OSI Approved :: GNU General Public License (GPL),
OSI Approved :: GNU Lesser General Public License (LGPL)
[Operating System    ] POSIX :: Linux
[Programming Language] C
[Topic               ] Multimedia :: Sound/Audio, Multimedia ::
Sound/Audio :: Capture/Recording, Multimedia :: Sound/Audio :: CD Audio,
Multimedia :: Sound/Audio :: Conversion, Multimedia :: Sound/Audio ::
MIDI, Multimedia :: Sound/Audio :: Mixers, Multimedia :: Sound/Audio ::
Players, Multimedia :: Sound/Audio :: Sound Synthesis, Software
Development :: Libraries, System :: Hardware, System :: Networking ::
Monitoring :: Hardware Watchdog, System :: Operating System Kernels ::
Linux 

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects and
categories you're subscribed to in the right column, which you may cancel
by highlighting the project or category in question and clicking the
'delete' button.

Sincerely,
freshmeat.net 

Re: [Devil-linux-develop] remote update

[Friedrich L. <fl...@fl...>]

Heiko Zuerker wrote on 09.02.2004 02:20 MET:
> Friedrich Lobenstock wrote:
> 
>> It has to be done in the initrd anyway and you are not changing those 
>> libraries when doing the update. And yes this might be a problem of 
>> its own, we can not change the initrd anymore. Hmmmmm.....then initrd 
>> needs some fixed parts (does not change across stable version) which 
>> loads the varibale ones, taking into account to update those if an 
>> "update CD" exists. Then the rest of the system is updated. Now this 
>> might also be a good idea to include the update script _from_ CD. This 
>> way we can provide for a more complicated if we did not think about a 
>> specific update problem later and as this script is tamper proof (on 
>> CD!) it can check all the signatures against a provided signature file 
>> (is that really needed?).
> 
> 
> Since all update functions are on the CD anyway (pre_init script), the 
> existance of this script would be the only requirement.
> 
> This would be the procedure:
> 1. initrd loads
> 2. initrd replaces bootcd.iso with bootcd.iso.new (after verifying it)
> 3. initrd continues as usual
> 4. pre_init sees the CD version is different to the config version and 
> performs an update (interactive part already implemented).

What do you do if initrd has to be updated?

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] Postfix milters?

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:

>>... but take a look at http://mailtools.anomy.net/
> 
> 
> Has anyone tried anomy on DL?  Does DL come with all the perl modules
> required?

I didn't try it.

Check out the src/perl-ext folder and the contents of perl-2*/ext/ if 
you find 'em in there.

Heiko

[Devil-linux-develop] [ devil-linux-Bugs-893146 ] add init script for adsl-start/stop

[SourceForge.net <no...@so...>]

Bugs item #893146, was opened at 2004-02-08 20:25
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=893146&group_id=34096

Category: Configuration / Scripts
Group: v1.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Heiko Zuerker (smiley73)
Assigned to: Nobody/Anonymous (nobody)
Summary: add init script for adsl-start/stop

Initial Comment:
>>2. How should I go about starting the ADSL connection
using
>>rp-pppoe?
> 
> 
> It's quite easy adding a script to DL to start it.
(It must be easy because
> I managed to do it *g) If you speak german, it helps
a lot to read the T_DSL
> Howto that is linked in the helpfile. I'm planning to
wirte a new howto for
> that stuff but I have not enough time at the moment.
Anyways it would be
> good to include the DSL_autostart-script in DL once
it is done, so you can
> switch it on and of conveniently via Setup menu :)

Basically you copy the script /etc/init.d/skeleton to
/etc/init.d/adsl and edit it.
Add to the start part adsl-stop and to the stop part
adsl-stop
Then insert the script into the init system with
insserv /etc/init.d/adsl .

I document this thing as a bug, so we include a init
script in the next DL release.

Heiko


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=893146&group_id=34096

Re: [Devil-linux-develop] remote update

[Heiko Z. <he...@zu...>]

Friedrich Lobenstock wrote:

> Bruce Smith wrote on 09.02.2004 01:28 MET:
> 
>>>> What about automatically updating the stick from CD?  Burn the new 
>>>> image
>>>> on CD, boot from CD, and it copies itself to the USB stick.  It could
>>>> also be used to initially create a bootable stick (blank).
>>>>
>>>> Just a thought, CD drives are a LOT cheaper than big memory sticks.
>>>
>>>
>>> What if it boots of off the USB stick, checks for an "update-CD" 
>>> (just a normal CD, but created from a newer ISO), does an update if 
>>> necessary and then moves one?
>>
>>
>>
>> Sure, if that can be done.  I was worried about problems updating a
>> running system (replacing libraries in use, etc.), which is why I
>> suggested booting off CD.
> 
> 
> It has to be done in the initrd anyway and you are not changing those 
> libraries when doing the update. And yes this might be a problem of its 
> own, we can not change the initrd anymore. Hmmmmm.....then initrd needs 
> some fixed parts (does not change across stable version) which loads the 
> varibale ones, taking into account to update those if an "update CD" 
> exists. Then the rest of the system is updated. Now this might also be a 
> good idea to include the update script _from_ CD. This way we can 
> provide for a more complicated if we did not think about a specific 
> update problem later and as this script is tamper proof (on CD!) it can 
> check all the signatures against a provided signature file (is that 
> really needed?).

Since all update functions are on the CD anyway (pre_init script), the 
existance of this script would be the only requirement.

This would be the procedure:
1. initrd loads
2. initrd replaces bootcd.iso with bootcd.iso.new (after verifying it)
3. initrd continues as usual
4. pre_init sees the CD version is different to the config version and 
performs an update (interactive part already implemented).

I didn't think to much about the upgrade script yet, but that's a 
separate issue.

Heiko

Re: [Devil-linux-develop] remote update

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:

>>>>My original idea was to add the iso image as boot.cd.new to the root of 
>>>>the media and then just check for it's existence, verify it, rename it 
>>>>to bootcd.iso and continue.
>>>
>>>So, the USB stick has to be large enough to hold TWO copies of the ISO?
>>
>>Yes correct.
> 
> 
> Is anyone ever going to use the feature?  1GB sticks are EXPENSIVE!!!

I know somebody who wants to use it.
Don't forgett that with the zisofs the size of DL decreased quite a bit.

> What about automatically updating the stick from CD?  Burn the new image
> on CD, boot from CD, and it copies itself to the USB stick.  It could
> also be used to initially create a bootable stick (blank).
> 
> Just a thought, CD drives are a LOT cheaper than big memory sticks.

It needs to be done remotely, there are no moving parts in the computers 
and nobody available to actually do the task.

Heiko