before i boot this one...

I secured /tmp with script a few ago..

I upgraded kernal last night.

kernal upgrade went as perfect as i can tell w/o boot.

But:

df shows

/dev/hda2 ext3 54G 3.7G 47G 8% /


fstab now shows SWAP as /dev/hda3


lilo.conf has root as hda3

SHOULD I CHANGE THE ROOT IN LILO TO:

hda2 ?


-----------------------------------
-----------------------------------
df:

Filesystem Type Size Used Avail Use% Mounted on
/dev/hda2 ext3 54G 3.7G 47G 8% /
/dev/hda1 ext3 99M 5.1M 88M 6% /boot
none tmpfs 247M 0 247M 0% /dev/shm
/usr/tmpDSK ext3 242M 4.1M 225M 2% /tmp
/tmp none 242M 4.1M 225M 2% /var/tmp


----------------------------------
fstab:

/dev/hda2 / ext3 defaults,usrquota 1 1
/dev/hda1 /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda3 swap swap defaults 0 0


----------------------------------
LILO CONF

prompt
timeout=50
default=linuxnew
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.20-20.7
label=linux
initrd=/boot/initrd-2.4.20-20.7.img
read-only
root=/dev/hda3

image=/boot/vmlinuz-2.4.20-28.7
label=linuxnew
initrd=/boot/initrd-2.4.20-28.7.img
read-only
root=/dev/hda3


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


lilo -v -v

Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Message: 46 sectors.
Boot image: /boot/vmlinuz-2.4.20-20.7
Setup length is 10 sectors.
Mapped 2097 sectors.
Mapping RAM disk /boot/initrd-2.4.20-20.7.img
RAM disk: 253 sectors.
Added linux
Boot image: /boot/vmlinuz-2.4.20-28.7
Setup length is 10 sectors.
Mapped 2097 sectors.
Mapping RAM disk /boot/initrd-2.4.20-28.7.img
RAM disk: 239 sectors.
Added linuxnew *
/boot/boot.0300 exists - no backup copy made.
Map file size: 29696 bytes.
Writing boot sector.


thanks

rock

no you shouldnt change the root.... its perfectly fine dont touch it.

Well, we sometimes learn the hard way...

FOR ALL THOSE who use script ./securetmp and select YES for reboot...

a restore was in order, why?

cause you MUST CHANGE THE LILO.CONF

NOTICE THE HDA3 as SWAP and the HDA2 as the main ROOT directory


/dev/hda2 / ext3 defaults,usrquota 1 1
/dev/hda1 /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda3 swap swap defaults 0 0



AND LILO CONF HAS ROOT AS HDA3 --it should be changed to HDA2
----------------------------------
LILO CONF

image=/boot/vmlinuz-2.4.20-28.7
label=linuxnew
initrd=/boot/initrd-2.4.20-28.7.img
read-only
root=/dev/hda3

If you know the exact option a restore is not necesarrily needed. Though I cannot think of it off the top of my head you can use a command in lilo to force a different root partition.