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