If you have 1G of ram, 800M of swap is way to much, try 512M or even 128M. Your root should probably be about 5-10G anywhere in there should be plenty, especially for slack. The rest looks good though!

Ok ty POW. PS I liked your blog.

I just spent the last half hour paging thru 11 pages of LQ Slack forum "subject lines" looking for any hint of a new Slackware release.

<<<edit: For all just now reading this thread, LQ does NOT have the kind of posters who know the latest Slackware rumours. This thread has (at best) everybody's Slackware 11 wishlists.>>>

What an adventure!!!

What great information!!!

Unfortunately, nobody posted any rumours in the last month or two about a new release. Does anybody have some goodies to post?

Prior to this, I spent 10 minutes reading thru the Changelog.txt in Slackware-current. No info, just TONS AND TONS AND TONS OF UPDATES!!!! Since the new year Patrick has been kicking some serious hiney, getting those updates out. And didn't he just get in the family way not too long ago? (Maybe he has an extra set of hands helping him program???)

I could really use the next Slack, as it's time to get my new machine running and Slack 10.2 isn't doing it for me. I'm going to go back to a thread I found on page 6 or 7 and get Alien Bob's "make a slack-current ISO" and try to use that for install, but of course I realize that slack-current has that big *** WARNING: NOT NECESSARILY STABLE *** disclaimer on it.

In the meantime... rumours, anyone? Rumours?

--vonSt

Slack-current seems pretty stable to me.

If you would do a forum search, you would see that:

When it comes out, it comes out.

This subject has been beat to death...Many,many,many,many,many,many,
many,many,many,many,many,many,many,many,many,many,many,many,many,many,many,many,
many,many,many,many,many,many,many,many,many,many,many,many,many,many,many,many,
many,many,many,many,many,many,many,many,many,many,many,many,many,many,many,many,
many,many,many,many,many,many,many,many,many,many,many,many,many,many,many,many,
many,many,many,many,many,many,many,many,many,many,many,many,many,many,many,many
times.

My bad. I tried using the LQ search function once before and nothing happened, so I thought I froze Mozilla. I killed it and did something else. This time, I took your advice, searched for "Slack 11", went to the bathroom, watched a little TV, came back, and indeed it gave me several pages to look at. I did indeed find 2 threads near the top that (at least first... you know how threads are) talked about the possibilities of a Slack 11.

For the other new LQ posters:

http://www.linuxquestions.org/questi...light=slack+11

http://www.linuxquestions.org/questi...light=slack+11

Of course, these threads give you zero in satisfaction. As cwwilson says, Patrick will post Slack 10.3 or Slack 11.0 whenever he feels like it. Businesses are taking pre-orders for it, supposedly, but that's just marketing.

I thought in the past, I'd seen, like maybe on the Changelog, that there was a good month's notice before a distro came out. Maybe I was hallucinating.

--vonSt

Slack is Pat's project, and it's entirely his call as to when he determines a new release is warranted. Random speculation about the timing of a new release might be fun, but the bottom line is that it will come out when Patrick decides it's ready to come out

Yea, great.... so when do you guys think it will be out? 1 month...2 months?

Since http://store.slackware.com/ is taking pre-orders for "Slackware 11" I guess there will be no Slackware 10.3. Looking at the ChangeLog.txt for Slackware-current, there is no indication that the release is imminent. Usually before a release, there are messages about -current entering beta stage. With all the frantic development that the changelog shows, I would say it won't take many months to see the light of a new release.
I am curious about Pat's plans to have a 2.6 as the default for Slackware 11. If that is indeed going to be the case, we have a lot of changes yet to come. Especially problems with udev is something that seems to keep the 2.6 kernels in the "testing" directory.

Eric

it'll come out just keep reading the changelog thats all you can really do

The latest 2.6.16.18 kernel is very good on a variety of my machines - even sped up an old PII 266 nicely. The udev version we have seems a older than recommended but seems to work.
The major issue I forsee with a switch to 2.6 is a need to rebuild just about everything with the 2.6 kernel headers. Is that correct or is it just kernel modules?

Just kernel modules, you should use the kernel headers that libc was compiled against, in Slackware those are 2.4 kernel headers.

And place a preorder for Slackware 11.0!

Dennisk

I have a subscription, I don't have to place pre-orders :-)

Eric

Here, here!

Subscriptions are the best. Not to mention cheaper, too.