sm-commit AT lists.ibiblio.org
Subject: Source Mage code commit list
List archive
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc)
- From: Jaka Kranjc <lynx AT mages.ath.cx>
- To: sm-commit AT lists.ibiblio.org
- Subject: Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc)
- Date: Sun, 10 Feb 2008 10:02:48 +0100
On Sunday 10 of February 2008 00:08:00 flux wrote:
> Jaka Kranjc (lynx AT mages.ath.cx) wrote [08.02.09 14:06]:
> > On Thursday 07 of February 2008 23:41:48 flux wrote:
> > > What concerns me is whether or not lilo will need to write to /boot,
> > > and if so then simply running lilo -b /dev/hda -C
> > > /mnt/root/etc/lilo.conf is out, because it would mean lilo will try to
> > > write to /boot on the ISO and not the installed hard drive. If it
> > > doesn't need to write to /boot, then I think this will be ok.
> >
> > -b can accept a partition too.
> >
> > The -r was just a honorary mention, it indeed seems simplistic from the
> > description.
>
> The issue is not which partition lilo gets loaded to (-b specifies
> things like /dev/hda for example), but rather where lilo stores/writes
> it's config data (separate from the user-created config file that lives
> in /etc). When lilo writes to the boot sector, it stores a backup of
> what was previously in that boot sector as a file in /boot so that if
> something goes wrong you can easily restore the previous boot sector
> configuration. If specifying /mnt/root/boot as the location it should be
> writing to rather than /boot is not trivial, this would actually be a
> problem. I'll be testing this very soon though, as I am currently
> testing the ISO in VM boots ;-).
-s then, heh. But things are getting complicated. :/
--
We cannot command nature except by obeying her. --Sir Francis Bacon
Have a sourcerous day! www.sourcemage.org
Attachment:
signature.asc
Description: This is a digitally signed message part.
-
[SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
Justin Boffemmyer, 02/07/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
Jaka Kranjc, 02/07/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
flux, 02/07/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
Jaka Kranjc, 02/07/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
flux, 02/07/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
Jaka Kranjc, 02/09/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
flux, 02/09/2008
- Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc), Jaka Kranjc, 02/10/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
flux, 02/09/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
Jaka Kranjc, 02/09/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
flux, 02/07/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
Jaka Kranjc, 02/07/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
flux, 02/07/2008
-
Re: [SM-Commit] GIT changes to master cauldron by Justin Boffemmyer (13e277555c0fbe15b61e691f3ce55288daaa10bc),
Jaka Kranjc, 02/07/2008
Archive powered by MHonArc 2.6.24.