SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
now this comes
Configuration NOT ok. LILO said:
LILO version 22.4.1 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2002 John Coffman
Released 27-Jan-2003 and compiled at 19:45:45 on Mar 9 2003.
Warning: LBA32 addressing assumed
Reading boot sector from /dev/hda
Using MENU secondary loader
Calling map_insert_data
Boot image: /boot/vmlinuz
Added vmlinuz *
Boot image: /boot/vmlinuz-ide-2.4.20
Added 2.4.20
Boot other: /dev/hda1, on /dev/hda, loader CHAIN
Added NT
Boot other: /dev/hdb1, on /dev/hdb, loader CHAIN
Fatal: Duplicate label "NT"
when i type lsmod (as super user)
ide-scsi is listed
but the brop now is mounting
and i dont now if the cdrom is hdc or hdb i think it is /dev/cdrom but i cant mount that beacause when i do
the message about its not a valid boot device
Its this hdc which needs to be in the append (as Excalibur and I have both said) and then it should all be working. Once that's done, you'll need to alter where the /dev/cdrom link points since the kernel will no longer think of the cdrom being at /dev/hdc, it will think of it as being at /dev/scd0 instead. Don't alter the append line, its this which causes the renaming as is needed, but you will need to alter the /dev/cdrom link and /etc/fstab possibly.
when i wrote the code you sendt me webtoe it was hdc1
and i changed from cdrom hdc1 but when i try to mount i get
the message that hdc1 is not in fstab should i
switch from cdrom to hdc1 in fstab
???
Killi, the correct name is hdc, the numbers are only for partitions on hard drives. Once you have a correct lilo.conf (don't forget to run lilo after changing lilo.conf), reboot and login, then do "dmesg | grep scsi", and look for something like the following,
Make note of the last line, /dev/sr0 is my cdrw.
The next step is to link your scsi emulated cdrw to /dev/cdrom, first we remove the cdrom entry "rm /dev/cdrom", then we link the new device (sr0 in my case) with "ln -s /dev/sr0 /dev/cdrom".
You should now be able to mount your cds.
but about fstab
/dev/cdrom /mnt/cdrom iso9660 noauto,pico,ro 0 0 thats my cdrom shall i change the pico after noauto beacause befor it was owner but if i change it to
user could every one mount cds then
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.