Does someone know of a well written guide for making udev work in Slackware such as the two excellent stickies at the top of this forum?

echo /sbin/udevsend > /proc/sys/kernel/hotplug

You could put that in your rc.udev script. Towards the bottom above 'udevstart'. Not on a slack box at the moment. That's how it's supposed to work really. Pat doesn't do it because he's still using a 2.4 kernel. That and he probably wouldn't feel comfortable giving such an unstable/in-flux program so much control. If your running a 2.6 and want to give the reins to udev then thats the way to go.

Works with no problems. I've frozen at 072 because it's like playing russian roulete when it comes to udev. I get tired of things breaking on every new release... ;-)

just wondering...

how are you "frozen" at 072
when -current is at 064???

I don't normally run Slackware as per my sig... :-) It's something I made myself and I know why Pat is so conservative with upgrades. It's a full time job keeping a distro up to date. Especially when you use packages that are in flux like udev...

so....
you don't run slack,
but you pretend to?

jong357,
Thanks for the input. My multicard reader now is detected. However the system still isn't recognizing my usb scanner when I connect it. Another thing, not sure if it is related, but since trying your solution my network connection keeps shutting off periodically I have to run /etc/rc.d/rc.inet1 start to restart my DHPC server.

Yes, Kodon... I run Slackware. I have been since 8.1 or so. I tri-boot between Jaguar, Slack and Windows and spend most of my time in Jaguar. My favorite color is green, I have 3 cat's and an annoying downstairs neighbor. ?

Dannyl, not sure about that stuff. Try running "tail -f /var/log/messages" and leave the terminal open. Wait for your network to go down and see what was reported. Check 'lsmod', 'ifconfig' and whatever else you can think of to see what might be the problem. Is it a wireless or LAN connection?

Maybe your multicard reader is interfering somehow tho I'm not sure how. Try rolling back to your original udev script to see if the problem goes away. Then start using it again to see if it returns.

Not too sure what to tell ya.. You could also tell udev to log in /etc/udev/udev.conf... Maybe you could spot some conflicts or something fishy by looking at the logs. That's where I would start. At square one....

Maybe i am wrong but i believe that it is not needed to put udevsend as the hotplug program.
(At least in my case it isn't)

/sbin/hotplug which is the default hotplugger will run the appropriate script from /etc/hotplug.d
If you have the udev package installed there is a symlink in the hotplug.d directory to udevsend.
So, hotplug will run it.

If you don't have the hotplug package installed and you have all the drivers needed compiled in your
kernel then you need to specify udevsend as the hotplugger as jong357 mentioned.

the latest is 79 now and it has completly taken over hotplug's job

I appreciate all the input. Maybe I will get this sorted out yet. Thats why I asked if anyone had a good guide that would walk a person through the entire process. I haven't made any scripts, I'm just running whatever the defaults are in a complete install. (version 10.2 with 2.6.13 kernel and modules from disk two.) Udev is about the only thing I haven't figured out yet. I'm seriously considering changing my computer over to Ubuntu simply because udev works in ubuntu. There are some things I don't like about Ubuntu, but so far it has been much easier to either fix or work around those than it is getting udev to work in Slackware.

It might be worthwhile to have a look see at how Ubuntu handles Udev and then make Slackware do the same thing. That's pretty much why I rolled my own distro. A little bit of this... A little bit of that... You can have your cake and eat it too...

Interesting news on udev-079.... I stopped reading the changelog at 072.... Maybe in another year it'll calm down.

Much easier to get working? I compiled my own 2.6.x kernel, and udev works by default

Me too.
It worked from day 1 with my compiled 2.6.X kernel
Just after 2.6.14 some things are symlinks in /sys so it didn't work correctly, so i compiled
udev-079 . Newer udev - kernel doesn't need hotplug so i just run udevd from an initscript and
everything works correctly. Slackware rules work perfectly. The only thing i added is a rule
to symlink /dev/usbflash to any usb device that has the "USB mass storage" model name.

errrrr. I just did
as root. while using a 2.6.14.4 kernel, and it magically started working.

all on slackware 10.2, hell I dunno if I did something stupid...

Udev-0.64 has worked out of the box for me without any tinkering. I have heard nightmarish stories with udev so I'll stick with what I have for now

oooh, sounds interesting. I think I'll wait for things to calm down before upgrading though.