This whole thing has me puzzled from both directions.

On the one hand, the geek in me wants to make it all work just because.

Then there's the part of me that really does not get it and gets more perplexed the more I "learn".

Then there's the lazy f###-wit in me that says, "If I can configure digikam to automagically download my pictures from my digital camera when I start the program, and I can create an icon that opens Konqueror and mounts my thumbdrive at the same time, why do I care if all this BS works or not? What more will I achieve having udev and hal?"

Shrug

Plus, if PV and his loose collective of brain power can't get it right, what friggin' hope do I have

Do I understand correctly that when Patrick is ready to release Slackware 11, he will tar the slackware-current directory over to slackware-11.0?

I would have thought that there was a "dump" directory, where stable packages are put. The summary directory would be slackware-11.0 and tested for... "system wholeness." (or whatever. I hate it when I can't think of the correct words!)

--vonSt
Today in Bremen, Germany

he'll copy the dir's contents to a slackware-11.0 dir...

and he'll make a bootable ISO of it... no tar involved...

huh??

So I see Slackware 11.0 RC2 showed up on the front page at distrowatch today with a link to an unofficial iso.

could this have been caused by the export memchr() change which was just reverted in 2.4.33.2?? just curious...

yeah, i'd like to remind folks that use unofficial ISOs that it's a good idea to run an md5sum on each and every file using patrick's CHECKSUMS.md5 file... if there's any FAILED tests, then either something has already been updated in -current or has been tampered/corrupted by the unofficial ISO maker... in both cases, creating a new bootable ISO by replacing the weird file(s) with proper ones from -current would be the best course of action...

CHECKSUMS.md5 is the ONLY file I download directly from slackware.com (apart from the odd Changelog.txt... ). Everything else comes from various mirrors.

Too easy!!

@win32sux :

I think Pat should put that on the "get slack" part of his site to be honest with you. When I downloaded slackware I was an "oober uber noober" and was paranoid and downloaded from his site all of the cd's not realizing that I only needed 2. Believe me when I tell you I had no idea to verify stuff times change; and now I'm comfortable having learned that command and now do what rkelson does so as not to beat up Pat's connection.

I'm using one I compiled from Alien Bob's repository.
It appends a kernel version in the script, but is not kernel specific.
I have edited the script. Eric probably will in the future.

Yeah expect a new upload tomorrow, I have already reworked the SlackBuild script to split out the kernel modules in a separate lm_sensors_kmod package (only a build against a 2.4 kernel will produce kernel modules) and leave the kernel version number out of the lm_sensors version number.

Just need to check if the new script works well, but my build box is at home (and I am not).

Eric

Btw, if you want to be kept informed of updates to my package repository, subscribe to this RSS feed: http://www.slackware.com/~alien/slac.../ChangeLog.rss

when will Slack 11.0 be released?

seriously, if you pre-order a disc set, does it ship at the same time as the ISO is posted to the mirrors? or do you get it a little bit earlier?

I would assume the same time as Pat has to send the ISO's to whoever makes all those CDs, so why not upload them at the same time since he has them?

I am guessing though .

I think the new slackware will be released soon as the changelog has been pretty quiet. No changes in two days...

Yup, if no higly importance updates appear then I predict we'll have 11 officialy declared before 1 September.

I agree, I think that is likely.