Although I prefer to hand mount drives, loop devices, etc, by hand, from my experience with HAL, it looks for /media for a starting mount point for temp devices like CD's, DVD's, USB drives, etc.

I am not sure if Pat added /mount but meant to add /media according to the FHS standards, which try to standardize Linux file system setups to an industry/agreed standard, so emailed Pat to ask this question.

If you'll look 10 posts back you'll see that it's /media, not /mount. He just got it wrong in the changelog.

Yeah, I saw that. Just wasn't sure if it was a typo, or a brain fart, as I often have! :P

Just got a reply from Pat:

Jamie Rubinstein wrote:
> Hi Pat,
>
> My name is Jamie Rubinstein, and I have been a slackware user/admin for
> over 10 years. I have been folowing the /current/ChanngeLog.txt and the
> ""When Will The Next Slackware Release Arrive" MegaThread on
> linuxquestions.org, which I am newbie on, and noticed the latest changelog
> states that you added the /mount directory in the a/aaa_base, however
> according to the FHS, it's supposed to be /media. Is this a typo, or just
> what we would prefer(you and me both)? From my experience with HAL, it
> looks for /media for a mount point start. Just my two cents.

He's right, too. Calling it /media really is redundant.

The FHS is a very good guideline, but unfortunately misses enough things that it should be only considered a guideline, not a law.

For example, it completely overlooks the concept of /usr/libexec (which is something I've emailed the author about to no avail) which is the directory where executeable user-space files are put (originally by BSD I b'lieve) that are not meant to be executed by users, and therefore have no reason to ever be in the search path.

Isn't that what /sbin is for?

When's the next Slackware release??

Soon? Since our BDFL has already updated the "Welcome to Slackware" email, we must be really close.

Agreed. I'd say in a day or two:-)

/sbin is for statically linked programs IIRC - ie the programs you need to get a bare system up and running before ldconfig and mounting of shared drives that might hold the actual libraries..

-Y1

i thought /sbin was for binaries that only root was supposed to run, related to maintaining the system (hence, "s" bin ).

I agree, we "mount" a file system in linux, we do not "mount" a device.

I think maybe this is the difference between /sbin and /usr/sbin? Just by judging by the directory contents, /sbin seems like all the lowlevel system utilities, and /usr/sbin contains all the extra administration utilities.

I hate to take the easy way out, but it appears you are both correct in a way.

regards,
...drkstr

PS: I wonder who will be the first person to post in this thread when 11 is released. Maybe Pat will do it himself? heh, wouldn't that take the cake!

I want Slackware 11.0 so bad I can taste it! MythTV 0.20 has been released and I am waiting for Slack 11 before upgrading everything - so for me the wait it doubly painful :-)

Don't get me wrong though, this isn't a complaint but rather just a display of the excitement I am feeling - I check the page *a lot* during the course of the day.

Hmmm I just read that back, how sad I am :-)

The changelog is the first thing I see in the morning and the last thing I see at night... maybe a few checks in between.

It's not so bad really. It's one of those things you just come to accept. I've taken the opportunity to mess around and break things now so I don't break them on a fresh system... a system guaranteed to be stable, reliable, and just plain awesome.

I think everyone has a point in their life where something just doesn't come fast enough. I'm glad to have purged that already with this release. [EDIT: Maybe not completely purged... but much better than I was... ] Yes I have blank CDs prelabeled sitting on the table... yes I have things set aside and ready to settle into a new release. For now I'm finishing up my tinkering so when it's finally released I can have it up and running by the end of that day... hopefully...

The wait was very much worth it. We're getting an awesome product here... even the KDE bug was fixed. Sure I can't wait and I'm pouncing on sight because I essentially have a dirty install right now that needs a lot of work and I'm starting to miss things. But I'd rather have the "perfect" compilation than install now and then be waiting for 11.1 as impatiently as I was earlier for 11.