Very Computer

My LILO doesn't read the settings I have put in it.  Is there something
else LILO is paying attention to?
Here is my /etc/lilo.conf --

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/dev/hda1
        label=Win
        table=/dev/hda
other=/boot/vmlinuz-2.0.35-1
 label=RH
 root=/dev/hda5
 read-only

Im Dual booting RH5.2 and Windows95.

Q1: Shouldn't this lilo.conf cause a default boot to Windows95?  It does
not, rather it insists on booting to
RH by default.

Q2: When I hit <tab> at the "boot" prompt, shouldn't I see the options
(labels) of "Win" and "RH"?  I
don't, rather I get "Windows95" and "Redhat".

I have searched my Linux partition for lilo.* and *.conf and for all
files containing "Windows95" and
Redhat.  I get hits, of course, but can't find anything that would might
be an "alternate" lilo.conf" that
LILO is reading.

Thanks for any insight!

nospams.

Sent via Deja.com http://www.deja.com/
Before you buy.

Quote:>boot=/dev/hda
>map=/boot/map
>install=/boot/boot.b
>prompt
>timeout=50
>image=/dev/hda1
>        label=Win
>        table=/dev/hda
>other=/boot/vmlinuz-2.0.35-1
> label=RH
> root=/dev/hda5
> read-only

[...]

--
Hal B

--
            Linux helps those who help themselves

--

Trinity College, Cambridge, and Computer Science         [riva.ucam.org]
"Oh Danny Boy, the pipes, the pipes are calling,
 From glen to glen, and down the mountainside ..."

The lilo command reads the config file and stores the information into
/boot/map and stores a pointer to that file with the boot code itself
that is loaded into the boot sector.  At boot time nothing is ever
reading /etc/lilo.conf.

When you understand this you will never forget to re-run the lilo
command after anything has changed in the boot directory or the
config file.

Villy

Thanks very much for your help and explanations.  I got LILO working
the way I want it to.

I went back to the LILO howto I've been poring over, looking for
Colin's tip to run lilo -v to activate changes.   Guess what....this
critical item isn't in there.

LILO -v did say I had a problem around line 8 which corresponded to
Hal's observation of having "image" and "other" out of order.  I
changed it, reran -v (verify?) no error.

So, what would be the correct way to specify the default boot OS?

Now, would either of you want to take a swing at a problem I'm having
with Samba?  From my Linux box I can list browse list and workgroup
members, but none of the share on my PDC.  Everything lists on my
BDC's and standalone servers. (using SMBCLIENT -L)  Already scoured
Deja, how-to's and posted my quandry to comp.protocols.smb, but no
solution yet.

Thanks again on LILO!

best regards,

Greg

Quote:>So, what would be the correct way to specify the default boot OS?

Quote:

>Now, would either of you want to take a swing at a problem I'm having
>with Samba?  From my Linux box I can list browse list and workgroup
>members, but none of the share on my PDC.  Everything lists on my BDC's
>and standalone servers. (using SMBCLIENT -L)  Already scoured Deja,
>how-to's and posted my quandry to comp.protocols.smb, but no solution
>yet.

--
Hal B

--
            Linux helps those who help themselves

       default=name
              Uses the specified image as the default boot image.
              If  `default' is omitted, the image appearing first
              in the configuration file is used.

Quote:>Now, would either of you want to take a swing at a problem I'm having
>with Samba?  From my Linux box I can list browse list and workgroup
>members, but none of the share on my PDC.  Everything lists on my
>BDC's and standalone servers. (using SMBCLIENT -L)  Already scoured
>Deja, how-to's and posted my quandry to comp.protocols.smb, but no
>solution yet.

Villy