XFS has served my purposes well for big files (>500MB), but I will give DragonFly a bloody try, out of curiosity. ReiserFS on the other hand is better optimized for small files (<5MB).

As far as ExtFS is concerned, I don't really think that it's that bad of a filesystem - it's well tested, and obviously the FS of choice on Linux.

I always use Ext3/4 for the root partition, for a very simple fact: if you mess around with your /etc/fstab and for some reason the system doesn´t boot anymore, you have to use some Live CD in order to amend the config files you've been playing with.

Well, if the root filesystem uses Reiser, JFS or XFS, you won't be able to mount those partitions from a Live CD to /mnt or whatever in order to fix the problem - at least I couldn't manage (similar experiences on the web).

That's a very basic reason why one should stick to ExtFS on Linux, at least for the / partition.

It really comes down to what you need it for. We don't have a proper Visio clone in OpenOffice, or something similar to QuickBooks (well, there's efforts like the Dia or GNUCash projects), so that might be one reason to stick with it. (Wikipedia turned to Ubuntu for their servers not long ago, but they still use a Windows machine for financial stuff).

On the other hand, Mac OS X is also a great platform as a desktop. It is true UNIX under the hood (Mach & BSD foundation) and, as Bill Joy stated in an interview, it is rock solid and beautifully designed. Mostly used in editing (text, video, audio - publishing houses, recording studios etc.)

Windows 7 is not that bad either, if you think about it, and yet I for one run almost exclusively Linux on my machines. To quote Bill Joy again, Windows is of no technical interest to me. They took a system designed for desktop use in an isolated environment and put it on the web, without thinking about evildoers, as the former US president would say.

(Well, they're trying to come to terms with all of that stuff now, but it's mostly patchwork anyway. Once you start on the wrong foot, it's pretty darn difficult going back and fixing some of the earlier, low-level, design mistakes.)

Lets get this thread back on topic, RC2! Release is near.

But how soon is soon? Seriously, that's cruel. Do you guys think it's going to be released
in August?

only pat knows, and I trust him: when he will think it's ready it will be released

dates don't matter much for me: I started installing my servers with 64-current since some weeks already, for the services I use it it's already rock solid.

My guess is as soon as the docs are ready. The sooner 13.0 is released, the sooner KDE4.3 would be in -current ;D

QUOTO! Oh, well, QUOTE!

Only Pat knows when... I trust him, too, he always makes the right choice, the release date this time should be later than the other versions for(for me) two new components:

-Slackware64
-New X

Now, thank to rworkman X got stabler, slackware64 is very stable and works perfectly(even better than the 32bit version...Obviously!), I'm gonna install it as soon as possible We're on RC2 version, slackware 13.0 is near!

http://www.linuxquestions.org/questi...24#post3631024

The above link is where I had posted about `kdesu konqueror &` in Slack64-current not working, and being really tricky to get working.

I *just* upgraded to RC2 via rsync, and the first thing I checked after reinstalling the new nvidia driver and logging in, was `kdesu` -- I am happy to report that it works as expected.

Sasha!

I'm using slackware64-curent. After the latest updates, glxgears seems to be broken.

I suspect the problem occur after the mesa-7.5-x86_64-1 package upgrade

it has been added glew as a dependency of mesa, as for changelog.

if you use slackpkg, use
to sync with added packages

UPDATE: Unfortunately, I must retract that post. I booted up this morning, and it's back -- kdesu doesn't work (no, it isn't only konqueror, it's ANYTHING kdesu) but over on the post I linked to, I'll try the 'strace' suggestion and post results.

it works for me (kernel 2.6.30-zen3), tried konqueror, dolphin and xterm.

I know there's some debate about newer 2.6.31-rc kernels breaking kdesu on lkml, dunno if related.
EDIT: reading the other topic I've seen you're running 2.6.30.x? have you tried with stock huge?

No, haven't tried stock huge kernel. Haven't run that since I installed. Currently running 2.6.30.2, but based on the strace output HERE it doesn't look like a kernel issue (to my untrained eye..)

Sasha

kdesu has no problem with the stock generic kernel

Phooooey! Heh, ok, I'll try the stock kernel today and post results.

Sasha

EDIT: As of 11 Aug 2009 I still have not tried a stock kernel.