I did that as well, didn't work. I said I deactivated hald which was introduced with SL 12.0 (??).

Nope, no choice with udev.

There was a guy sometime back, here, who was talking about going back to an earlier release (10 I think) to see how things were done there in order to see whether he could do the same with the current release - haven't heard any more. Anyone else remember that?

What does automounting devices have to do with running CUPS or Apache?

You mean: what should they have to do with Cups, Apache, etc.
They should be optional. Automounting something isn't a big deal. A daemon?

I used that too, at the time (but we used another platform, because my fella at work is a debian guy, so we used that and the just-born knoppix): FYI, it's still active (we even tried it again a few years ago, to have lot of cores available) and got also nice new features but now it's commercial only (with some facilities for academic use)...
well, variables are an awful lot, not to count the knowledge involved, so I think yes, also to do that can still count as computer science.
...for more than one normal person, I'd say.
to have chances to be pushed, also those should be maintained (and they should probably follow the coding standards of Slackware's SlackBuilds, but this is another matter...): FYI (as I think there has been a misunderstanding), Vincent Batts is maintaining his scripts, advertised repeatedly here and elsewhere (they are not secret at all), since Slackware 13...

also, rocket science isn't that hard: one of our students made one a few years ago.

Perhaps it's art. And like art at least half the trick is to be blessed with the intuition to know what work should not be done. This is Slackware's strength, in my not so humble or informed opinion, having not used it all that long. You know, there are guitar solos like the hair metal bands had with many notes per second and then there are Kenny Burrell's guitar solos.

So someone in the non-bsd section of a bsd forum recently pointed out Morpheus, which uses a lot of the suckless software and is partly inspired by plan 9. It looks interesting, but is it art?

Seems like the init system that shall not be named has maybe spurred quite a few malcontents to try creating new minimal distros lately. Or maybe they had this idea for awhile. One weird thing to me with the minimalists is they seem to like a statically linked libc. If you do that how manageable are security updates to libc? Okay folks, update your libc and these 300 programs and libraries.

This person got rid of udev:
http://www.linuxquestions.org/questi...7/#post5044071

2 members found this post helpful.

A very provocative remark.

No. They were the ones who were quite contented. We were and are contented. We still have the slackware init system. :D

A few malcontents decided to replace the init systems of all distros. They are not content until they achieve their aim and - even then - they are still not contented as they are now changing other things.

They are the malcontents.

We were otherwise content until they turned up on our doorstep.

6 members found this post helpful.

Thanks - that's very interesting indeed - for me at least - since I use Ratpoison and even if I used something else it wouldn't be KDE or Xfce.

Thanks again.

1 members found this post helpful.

My tone isn't translating into text. I meant the word malcontent in an affectionate way.

You could have specified this before. After our discussion about automounting on production desktops in earlier Slackware versions, I feel now like the guy who tried to discuss the appropriate spicing of raw T-Bone steak with a vegan.

Sorry :)

1 members found this post helpful.

Yeah a fellow Slack-Ratpoisonner !

This is a quite good WM for a coder, I felt in love with it.

Garry.

1 members found this post helpful.

MtoolsFM would have suited your (and their) needs perfectly: http://mtoolsfm.sourceforge.net/.

I wonder if this stuff is usable and maintained why someone who is willing to deploy Slackware commercially is forced to stick with NIS. I took a look at the /source and it is barely usable.

I am not trying to be pushed. I was just willing to share my spare time and skills and to provide a working example how the things could be done. I stated in the beginning that I can't provide maintenance for the simple reason that I can't guarantee my availability. My life doesn't revolve around computers since long ago.

If Slackware is to be dumbed down to the bare minimum I couldn't care less. I am perfectly able to solve my computer problems myself. Its not "rocket science" (or whatever the English idiom for something not so complicated is).

There was a time when the word Linux meant Slackware. It is not the case anymore.

I wish you all the best of luck.

Cheers

If you are using Slackware in a commercial environment that is already using NIS, there is no real reason to bring PAM into the equation.

I did that ~8 years when Nortel was still operational; admittedly, that was a while ago.