Hello Rial,
When you have many image sections in your /etc/lilo.conf, do you have to
type in a specific command?
That is, do you have to type anything other than Linux at your boot
prompt? Or. is their another switch to use for another image?
I assume that you do all of your changes at ' root '...
Roman
Rial Juan wrote:
>
> On May 16 Romanator wrote:
>
> > Hi,
> >
> > How do you access 'Console Mode' from within X windows?
>
> You don't have to be in real console mode; an xterm will do just fine. If you
> really want console mode, press CTRL-ALT-F1 for the first console (CTRL-ALT-2
> for the second and so on...)
>
> > In addition, can I review and make modifications from the desktop i.e.
> > checking my RAM. I think the command line is: /sbin/lilo.conf
>
> If you want to check your ram, type the following line in console or xterm
> free
> To modify lilo options, edit the file /etc/lilo.conf with an ascii-editor. To
> activate the changes, in console or xterm type "lilo", as root.
>
> > Should this be done from ' root ' ?
>
> Due to file permissions only root can edit /etc/lilo.conf, and only root can
> activate lilo options.
>
> > I have an IDE drive. Should I type in:
> > append=hda=ide_scsi mem=128M
>
> If it's a harddisk, I don't think it's necessary. The only reason you want to
> use ide-scsi mode would be to be able to write on a cdr or cdrw drive, and
> perhaps it's nice to have your regular cdrom work in ide-scsi mode as well, if
> some application demands it. the only app I ever encountered that didn't want to
> read from atapi-cdroms was xcdroast.
>
> Anyway, the line you were looking for is:
> append="hda=ide-scsi mem=128M"
> ^ ^ ^
>
> But I'd drop the 'hda=ide-scsi' part. Not necessary, and probably even
> dangerous.
>
> If you're smart, you add another image-section to your /etc/lilo.conf, and leave
> the old one alone. This way you can test new settings on the new kernel image,
> without modifying your old config, and thus making it impossible to boot if you
> screw up. As an example, I'll paste my /etc/lilo.conf below. Notice how I test
> all new kernels, and all new lilo settings on the "test" image.
>
> **************************************************
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> vga=0x030C
> default=test
> keytable=/boot/be-latin1.klt
> prompt
> timeout=50
> message=/boot/message
>
> image=/boot/vmlinuz-test
> label=test
> root=/dev/hda6
> append="mem=128M hdb=ide-scsi hdc=ide-scsi"
> read-only
> image=/boot/vmlinuz-2.2.14
> label=linux
> root=/dev/hda6
> append="mem=128M hdb=ide-scsi hdc=ide-scsi"
> read-only
> image=/boot/vmlinuz-2.2.14-15mdksecure
> label=secure
> root=/dev/hda6
> append="mem=128M hdb=ide-scsi hdc=ide-scsi"
> read-only
> image=/boot/vmlinuz
> label=linux-up
> root=/dev/hda6
> append="mem=128M hdb=ide-scsi hdc=ide-scsi"
> read-only
> other=/dev/hda2
> label=dos
> table=/dev/hda
> other=/dev/fd0
> label=floppy
> unsafe
>
> **************************************************
>
> --
>
> Rial Juan <http://nighty.ulyssis.org>
> e-mail: [EMAIL PROTECTED]
> Belgium tel: (++32) 89/856533
> ulyssis system admininstrator <http://www.ulyssis.org>
>
> The little critters in nature; they don't know they're ugly.
> That's very funny... A fly marying a bumble-bee...
>
> ------------------------------------------------------------
>
> Sign the petition at http://www.libranet.com/petition.html
> Help bring us more Linux Drivers
