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.
Pat has added a new boot script in rc.d that I believe is suppose to add usb/firewire based devices at boot and it has executable permission right off the bat at install. For me it just scans for new devices and since I don't have any it does not create any new devices.
Quote:
#!/bin/sh
#
# rc.scanluns (Wed Jul 26 16:55:51 CDT 2006) pjv
#
# This script simply runs "rescan-scsi-bus -l" to look for devices
# that have been plugged into a USB or IEEE1394 (Firewire) port that
# might not have been detected because they use a LUN (Logical Unit
# Number) other than 0.
#
# You might need to run this script again (or just use
# rescan-scsi-bus directly at the command line) after plugging
# in new devices such as USB cameras, music players, external
# storage, and similar items.
# Run this only if "noscanluns" was NOT given as a kernel option.
if ! grep -qw noscanluns /proc/cmdline ; then
if [ -x /sbin/rescan-scsi-bus ]; then
echo "Scanning all LUNs for additional hardware: /sbin/rescan-scsi-bus -l"
/sbin/rescan-scsi-bus -l
fi
fi
I added the noscanluns kernel boot option to decrease my boot time (worked) but I wonder why it one just doesn't chmod 644 rc.scanluns as is done for all the other boot scripts?
Originally posted by shepper:
Have you removed executable permissions for rc.scanluns and if so are you having any problems?
I have had not problems with passing the noscanluns option at boot.
I did try "chmod -x /etc/rc.d/rc.scanluns" and it doesn't probe
for luns while booting.
However, Alien Bob explained to me why you don't just change the perms:
Quote:
You should not "chmod -x" that script. If you do, the issue of "noscanluns" boot option becomes non-existent. The problem you don't yet see is when someone boots the computer and something breaks because of the rc.scanluns. Instead of getting a Knoppix CD and fixing the X bit of rc.scanluns, you can simply pass "noscanluns" on the lilo prompt. Just like you can pass "nousb" or "nohotplug". It is meant to help computers boot that otherwise wouldn't - without having to resort to rescue CD's.
I haven't had problems with it probing luns. And fwiw, I had 3 USB
devices plugged in when I installed -current, and let it create
mount points for them.
The issue I did have is that "mount -a" is passed during bootstrapping
before "hotplug" or "rcscanluns" so they don't get mounted. Pat said:
Quote:
We're looking into ways to make that happen automatically, but that involves some additional components that won't make it into Slackware 11.0.
Last edited by Bruce Hill; 08-30-2006 at 10:50 AM.
Reason: Alien Bob explained it to me...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.