flashboot - Jun 2007 - New backup and network configuration tools

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi
A few hours ago Jakob committed a some diffs from me.
It includes a new backup tool (backupconfig) and a network
configuration tool (createconfig).
Here is the short description of what it does.

Createconfig is checking for existing backups and presents a (very
short) list of devices containing backups. It should detect if a usb
memory is inserted and contains a /conf/etc folder.
It then presents 4 options which should be self-explainatory.

0. Use existing config
1. Manual setup
2. DHCP
3. Do not run createconfig


Backupconfig uses /etc/backup.conf and mtree to decide what files to
backup. backup.conf is for directories to look for changes and mtree
for files different then the version in bsd.gz. The backup is then
copied to /flash/conf/.
A mtree of the initial filesystem is stored in /root/flashboot.mtree.
Flashboot.mtree is created at the end of list.

Regards

Niclas Rosell
Department for Domain Product and DNS Operation
.SE (The Internet Infrastructure Foundation)
PO Box 7399, SE-103 91 Stockholm, Sweden
Phone +46 8 452 35 00/25, Mobile +46 73 270 86 84
E-mail: niclas.rosell at iis.se
www.iis.se 

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBRnKgbQXDAg/A+7GOEQLVjQCeKHwKFMR1/gPlMRmI+5q4HqL9a8cAoJQ+
sRx5WjQGGEYl9q024wgShzYG
=eRPm
-----END PGP SIGNATURE-----

On Fri, 15 Jun 2007, Niclas Rosell wrote:
>  
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi
> A few hours ago Jakob committed a some diffs from me.
> It includes a new backup tool (backupconfig) and a network
> configuration tool (createconfig).
> Here is the short description of what it does.
> 
> Createconfig is checking for existing backups and presents a (very
> short) list of devices containing backups. It should detect if a usb
> memory is inserted and contains a /conf/etc folder.
> It then presents 4 options which should be self-explainatory.
> 
> 0. Use existing config
> 1. Manual setup
> 2. DHCP
> 3. Do not run createconfig
> 
> 
> Backupconfig uses /etc/backup.conf and mtree to decide what files to
> backup. backup.conf is for directories to look for changes and mtree
> for files different then the version in bsd.gz. The backup is then
> copied to /flash/conf/.
> A mtree of the initial filesystem is stored in /root/flashboot.mtree.
> Flashboot.mtree is created at the end of list.
Thanks, I''m sure a lot of people will find these useful.

Are there any caveats for people who are running flashboot systems
who upgrade the a new image that incorporates these changes? It
seems that their systems may not come back properly from a reboot if
the "config" variable is not set in rc.conf.

-d

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello

The changes i have made does not change the bootup behavior unless
config=YES is in rc.conf.
The "restoration" process (in rc.initial) of backup files on the
flash card is left untouched. When running a system with config=YES
(or by running createconfig manually) you are asked if you want to
make a backup of your changes. If the answer is yes then the changed
files will be copied to /flash/conf/ and will be restored by rc at
next reboot.
Any changes made at any time can be backed up by running the command
backupconfig. By default it only looks in /etc but you can change
this by editing /etc/backup.conf. Take a look in /flash/conf/ after
running backupconfig to verify.
Good to know is that if a USB memory stick is plugged in then that
will be used as /flash instead of the flash disk.

At first I did not use config=NO/YES but instead i checked if there
was a backup on flash and used that instead of going into
createconfig (no questions asked), but that was before I was thinking
of backing up to a USB memory.

I was thinking of renaming createconfig/backupconfig to
flashboot-autoconf/flashboot-backup. (thanks to Jakob for helping out
with the names)

Niclas

> -----Ursprungligt meddelande-----
> Fr?n: Damien Miller [mailto:djm at mindrot.org] 
> Skickat: den 20 juni 2007 06:43
> Till: Niclas Rosell
> Kopia: flashboot at mindrot.org
> ?mne: Re: [flashboot] New backup and network configuration tools
> 
> On Fri, 15 Jun 2007, Niclas Rosell wrote:
> 
> >  
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > Hi
> > A few hours ago Jakob committed a some diffs from me.
> > It includes a new backup tool (backupconfig) and a network 
> > configuration tool (createconfig).
> > Here is the short description of what it does.
> > 
> > Createconfig is checking for existing backups and presents a
> > (very short) list of devices containing backups. It should detect
> if a usb 
> > memory is inserted and contains a /conf/etc folder.
> > It then presents 4 options which should be self-explainatory.
> > 
> > 0. Use existing config
> > 1. Manual setup
> > 2. DHCP
> > 3. Do not run createconfig
> > 
> > 
> > Backupconfig uses /etc/backup.conf and mtree to decide what 
> files to 
> > backup. backup.conf is for directories to look for changes 
> and mtree 
> > for files different then the version in bsd.gz. The backup is
> > then  copied to /flash/conf/.
> > A mtree of the initial filesystem is stored in 
> /root/flashboot.mtree.
> > Flashboot.mtree is created at the end of list.
> 
> Thanks, I''m sure a lot of people will find these useful.
> 
> Are there any caveats for people who are running flashboot 
> systems who upgrade the a new image that incorporates these 
> changes? It seems that their systems may not come back 
> properly from a reboot if the "config" variable is not set in
> rc.conf.  
> 
> -d
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBRnjjqwXDAg/A+7GOEQLlvACfVWsnSBGHthalS6K0shdzkWj/EcEAoNY1
n7WuKjG/HxkDrO7eTMc2IL6k
=iKMM
-----END PGP SIGNATURE-----

Hi

I have made som changes to resolv a issue with the config variable in
rc.conf. Thanks Damien for pointing this out, I didnt read your question
properly at first.
I also renamed the config variable to initial_config in rc.conf, I think
this is a better name.
Now createconfig will only run from rc if initial_config exists and is
set to YES. Upgrading from older releases that does not have
initial_config variable should now be safe.

/Niclas


ons 2007-06-20 klockan 10:22 +0200 skrev Niclas Rosell:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello
> 
> The changes i have made does not change the bootup behavior unless
> config=YES is in rc.conf.
> The "restoration" process (in rc.initial) of backup files on the
> flash card is left untouched. When running a system with config=YES
> (or by running createconfig manually) you are asked if you want to
> make a backup of your changes. If the answer is yes then the changed
> files will be copied to /flash/conf/ and will be restored by rc at
> next reboot.
> Any changes made at any time can be backed up by running the command
> backupconfig. By default it only looks in /etc but you can change
> this by editing /etc/backup.conf. Take a look in /flash/conf/ after
> running backupconfig to verify.
> Good to know is that if a USB memory stick is plugged in then that
> will be used as /flash instead of the flash disk.
> 
> At first I did not use config=NO/YES but instead i checked if there
> was a backup on flash and used that instead of going into
> createconfig (no questions asked), but that was before I was thinking
> of backing up to a USB memory.
> 
> I was thinking of renaming createconfig/backupconfig to
> flashboot-autoconf/flashboot-backup. (thanks to Jakob for helping out
> with the names)
> 
> Niclas
> 
> 
> > -----Ursprungligt meddelande-----
> > Fr?n: Damien Miller [mailto:djm at mindrot.org]
> > Skickat: den 20 juni 2007 06:43
> > Till: Niclas Rosell
> > Kopia: flashboot at mindrot.org
> > ?mne: Re: [flashboot] New backup and network configuration tools
> >
> > On Fri, 15 Jun 2007, Niclas Rosell wrote:
> >
> > > 
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Hi
> > > A few hours ago Jakob committed a some diffs from me.
> > > It includes a new backup tool (backupconfig) and a network
> > > configuration tool (createconfig).
> > > Here is the short description of what it does.
> > >
> > > Createconfig is checking for existing backups and presents a
> > > (very short) list of devices containing backups. It should detect
> > if a usb
> > > memory is inserted and contains a /conf/etc folder.
> > > It then presents 4 options which should be self-explainatory.
> > >
> > > 0. Use existing config
> > > 1. Manual setup
> > > 2. DHCP
> > > 3. Do not run createconfig
> > >
> > >
> > > Backupconfig uses /etc/backup.conf and mtree to decide what
> > files to
> > > backup. backup.conf is for directories to look for changes
> > and mtree
> > > for files different then the version in bsd.gz. The backup is
> > > then  copied to /flash/conf/.
> > > A mtree of the initial filesystem is stored in
> > /root/flashboot.mtree.
> > > Flashboot.mtree is created at the end of list.
> >
> > Thanks, I''m sure a lot of people will find these useful.
> >
> > Are there any caveats for people who are running flashboot
> > systems who upgrade the a new image that incorporates these
> > changes? It seems that their systems may not come back
> > properly from a reboot if the "config" variable is not set
in
> > rc.conf. 
> >
> > -d
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.1
> 
> iQA/AwUBRnjjqwXDAg/A+7GOEQLlvACfVWsnSBGHthalS6K0shdzkWj/EcEAoNY1
> n7WuKjG/HxkDrO7eTMc2IL6k
> =iKMM
> -----END PGP SIGNATURE-----
> _______________________________________________
> flashboot mailing list
> flashboot at mindrot.org
> http://lists.mindrot.org/mailman/listinfo/flashboot
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad
	meddelandedel
Url :
http://lists.mindrot.org/pipermail/flashboot/attachments/20070713/0bf8abae/attachment.bin

What do you say, are we ready to start deploying binary-version of this??

Rickard.

Niclas Rosell wrote:
> Hi
>
> I have made som changes to resolv a issue with the config variable in
> rc.conf. Thanks Damien for pointing this out, I didnt read your question
> properly at first.
> I also renamed the config variable to initial_config in rc.conf, I think
> this is a better name.
> Now createconfig will only run from rc if initial_config exists and is
> set to YES. Upgrading from older releases that does not have
> initial_config variable should now be safe.
>
> /Niclas
>
>
> ons 2007-06-20 klockan 10:22 +0200 skrev Niclas Rosell:
> Hello
>
> The changes i have made does not change the bootup behavior unless
> config=YES is in rc.conf.
> The "restoration" process (in rc.initial) of backup files on the
> flash card is left untouched. When running a system with config=YES
> (or by running createconfig manually) you are asked if you want to
> make a backup of your changes. If the answer is yes then the changed
> files will be copied to /flash/conf/ and will be restored by rc at
> next reboot.
> Any changes made at any time can be backed up by running the command
> backupconfig. By default it only looks in /etc but you can change
> this by editing /etc/backup.conf. Take a look in /flash/conf/ after
> running backupconfig to verify.
> Good to know is that if a USB memory stick is plugged in then that
> will be used as /flash instead of the flash disk.
>
> At first I did not use config=NO/YES but instead i checked if there
> was a backup on flash and used that instead of going into
> createconfig (no questions asked), but that was before I was thinking
> of backing up to a USB memory.
>
> I was thinking of renaming createconfig/backupconfig to
> flashboot-autoconf/flashboot-backup. (thanks to Jakob for helping out
> with the names)
>
> Niclas
>
>
> >>> -----Ursprungligt meddelande-----
> >>> Fr?n: Damien Miller [mailto:djm at mindrot.org]
> >>> Skickat: den 20 juni 2007 06:43
> >>> Till: Niclas Rosell
> >>> Kopia: flashboot at mindrot.org
> >>> ?mne: Re: [flashboot] New backup and network configuration
tools
> >>>
> >>> On Fri, 15 Jun 2007, Niclas Rosell wrote:
> >>>
> >>>> -----BEGIN PGP SIGNED MESSAGE-----
> >>>> Hash: SHA1
> >>>>
> >>>> Hi
> >>>> A few hours ago Jakob committed a some diffs from me.
> >>>> It includes a new backup tool (backupconfig) and a network
> >>>> configuration tool (createconfig).
> >>>> Here is the short description of what it does.
> >>>>
> >>>> Createconfig is checking for existing backups and presents
a
> >>>> (very short) list of devices containing backups. It should
detect
> >>> if a usb
> >>>> memory is inserted and contains a /conf/etc folder.
> >>>> It then presents 4 options which should be
self-explainatory.
> >>>>
> >>>> 0. Use existing config
> >>>> 1. Manual setup
> >>>> 2. DHCP
> >>>> 3. Do not run createconfig
> >>>>
> >>>>
> >>>> Backupconfig uses /etc/backup.conf and mtree to decide
what
> >>> files to
> >>>> backup. backup.conf is for directories to look for changes
> >>> and mtree
> >>>> for files different then the version in bsd.gz. The backup
is
> >>>> then  copied to /flash/conf/.
> >>>> A mtree of the initial filesystem is stored in
> >>> /root/flashboot.mtree.
> >>>> Flashboot.mtree is created at the end of list.
> >>> Thanks, I''m sure a lot of people will find these
useful.
> >>>
> >>> Are there any caveats for people who are running flashboot
> >>> systems who upgrade the a new image that incorporates these
> >>> changes? It seems that their systems may not come back
> >>> properly from a reboot if the "config" variable is
not set in
> >>> rc.conf.
> >>>
> >>> -d
_______________________________________________
flashboot mailing list
flashboot at mindrot.org
http://lists.mindrot.org/mailman/listinfo/flashboot
>>
>>
>>
-------------------------
>>
_______________________________________________
flashboot mailing list
flashboot at mindrot.org
https://lists.mindrot.org/mailman/listinfo/flashboot

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.mindrot.org/pipermail/flashboot/attachments/20070719/7cd40cd6/attachment-0001.html

On 19 jul 2007, at 15.14, Rickard Dahlstrand wrote:
> What do you say, are we ready to start deploying binary-version of  
> this??
why binary?

	jakob

Jakob Schlyter wrote:
> On 19 jul 2007, at 15.14, Rickard Dahlstrand wrote:
>
>> What do you say, are we ready to start deploying binary-version of
>> this??
>
> why binary?
kernels and diskimages..

On 19 jul 2007, at 18.17, Rickard Dahlstrand wrote:
>> why binary?
> kernels and diskimages..
sure, but why isn''t the shell-script enough?

	jakob