I've been following the development of Dragonfly for some time...
 

I have been especially interested in their dedication to the delivery of a native clustering kernel. If Hammer can be delivered to Linux without dependency on the Dragonfly kernel it runs on, Hammer would indeed be a fantastic asset. But I see problems with the porting of Hammer to Linux.
1.) Linux is not yet native cluster capable.
2.) There is too much conflict between different sources as to what clustering should be on Linux.
3.) Much of that conflict is due to the economic considerations of "corporate distributions: Redhat, Suse, Mandriva. And while Debian is not corporate by definition, they have their own set of aspirations which are not conducive to negotiation.

And then, there's one more issue that can't be dismissed regarding Slackware. There would likely be resistance from the majority of Slackware users (being seen as unnecessary), since most of them only run desktops and not servers for enterprise installations. Trying to convince them that Hammer should be included would take more effort than it's worth. Look instead to third parties like the "Access Grid" project to deliver the necessary tools for things not currently included in Slackware as standard features. That project is well defined, and already devoted to such services as would benefit from Hammer. So in the future, we might well see Hammer delivered by Access Grid.

I guess I (we) could chat with Christoph Willing about this.
EDIT: I just emailed him about this. I'll let you know what he has to say about it.

Shingoshi

Well said Shingoshi:

I suppose the few of us who would really like to see this FS make its way into our realm will just have to do what we can to get it there, since it is pretty likely that getting distro support on it won't happen anytime soon. Can't wait to hear what Mr. Willing has to say tho...

That's the sort of thing that I've NEVER been able to get my head around. From my perspective, Slackware IS the Enterprise Linux distro of choice. Or you can roll your own Gentoo and there's a couple of others.

Although rpm -ivh *appears* to be as easy as installpkg, the reality is that you then you find yourself hunting down all these dependencies on rpmfind.net (sometimes for hours, and one package dependency requires three more packages, etc...)

Not to mention that you have to spend more time DISabling holes in say, RHEL, than you do ENabling features you want in Slack LOL!

This whole, "Hire a Linux n00b who has his MCSE", and... Heck! You can't even do a quick kernel compile in RH w/o voiding your support agreement. You have to ask RH to do it for you, telling them exactly what you want, and pay them to do it!

I came from a BSD bacground coz we couldn't get IP to run on ARPAnet with AT&T UNIX. I'm a Solaris lover (and a Bill Joy fan too). For any real UNIX head, Slack just seems to make the most sense to me where GNU/Linux is concerned.

If RPM based distros were so great (and their marketing surely is), then there woul be no place in the enterprise for NetBSD and the like. I've seen slack arch's come and go over the years, and yet, there's an arch for S/390. Hm... There's gotta be a reason for that.

I'm not bashing anyone for running slack as their workstation ( I do myself) - it does whatever you want it to do, but the less stable rpm based distros seemed to have more to offer out of the box for that for the average power user who wanted bleeding edge over that of stability (Like Mandrake, before they had their IPO, crashed, and burned).

Slackware is kind of a bitch to deploy across a desktop environment compared to a couple of other distros, and flame me people if you like, but I still recommennd mACROSfOT on the corporate desktop almost unequivicably.

Hey That would be fantastic, although I don't know how receptive Matthew is to having his flavor of UNIX marginalized at the expenxe of of his file system being widely adopted ;) For those who watched the FreeBSD 4/5 meltdown on the devel lists which resulted in the birth of DragonFly, well, you'll recall how ugly it was.

Still That's a great idea Shingoshi!, Yes, please keep us posted and email me anytime!

Kindest regards,

It would be helpful if some of you thanked me!
 

I'm not talking here about tooting my own horn for the sake of making my ego bigger. No, I'm talking about showing by the tally of votes garnered, just how many people believe the suggestion made is something they would like to see happen. Since I already advocate for the introduction of many technologies, it would help those responsible for the development of those technologies to see what level of support they could expect to see from this (Slackware) group in particular.

So if you as I do believe that Slackware is an excellent foundation for Enterprise Linux solutions, show it by voting with thumbs-up on this suggestion.

Thank you!
Shingoshi

I'm looking for the brave who could manhandle a SlackHammer!
 

I've started a new topic dedicated to the implementation of Hammer on Slackware. Please participate there instead of corrupting this thread.

http://www.linuxquestions.org/questi...hammer-744248/

Shingoshi

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.

today's changelog looks interesting for your problem ;)

Just out of curiosity, has anyone else noticed strange behavior from ntfs-3g since installing slackware64-current? I've never had issues with it before, and it very well could be my configuration of it, but every time I boot linux (and not even necessarily use my ntfs partition, just mounting it at boot does this) and then reboot into windows, windows insists on running chkdsk on it. my fstab for the drive is as follows:

Mmm, it happened to me years ago and after I solved mounting the partition by hand and umounting the partition by hand too... I don't know why this happens, maybe the mounting of this partition breaks some cluster or I don't know :)

so is the sad joke of KDE-4.2 over yet or was that just a bad dream I had ?

Well, the wait is finally over!!!!


WOOOO-HOO!!