nice .. ;D
try to edit lilo.conf to mount your root partition read-write so the filesystem can be restored upon a failure .. i had this problem once with my comp.
At last! Finally managed to install Sid on A Reiser FS partition. So far so good!
nice .. ;D
try to edit lilo.conf to mount your root partition read-write so the filesystem can be restored upon a failure .. i had this problem once with my comp.
Thanks for the tip. Here is my lilo.confnice .. ;D
try to edit lilo.conf to mount your root partition read-write so the filesystem can be restored upon a failure .. i had this problem once with my comp.
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
compact
prompt
timeout=60
image=/boot/vmlinuz-2.2.19-reiserfs
label=linux
root=/dev/hdb3
append="hdc=ide-scsi hdd=ide-scsi"
read-only
other=/dev/hda1
label=win
The only thing was that my startup scripts now had a problem, cause they thought that the fs was ext2 and was mounted read-write and this shouldnt be done ..
Thanks for the tip. Here is my lilo.conf
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
compact
prompt
timeout=60
image=/boot/vmlinuz-2.2.19-reiserfs
label=linux
root=/dev/hdb3
append="hdc=ide-scsi hdd=ide-scsi"
read-write <-- change this to write instead of only
other=/dev/hda1
label=win
I solved this with editing the scripts .. but this was in slack I dont know debian .. so any one here can tell me if this problem exist in debian ?
Finally made the modifications (work has kept me busy) and no problems on boot-up. I should mention that the install disks I used were from a third party developer.
The only thing *was that my startup scripts now had a problem, cause they thought that the fs was ext2 and was *mounted read-write and this shouldnt be done *..
I solved this with editing the scripts .. but this was in slack I dont know debian .. so any one here can tell me if this problem exist in debian ?
Bookmarks