SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Give DragonFly a try, if for no other reason than for the HAMMER FS, which is totally bitchen!
The one thing that really bothered me for a while was the 'non-trivial' procedure I had to go through to run XFS on Slack. I never liked Ext2 (and especially not Ext3 - why make a clunky thing clunkier?), but for years it was all we had. I also like ReiserFS on Linux, but I've never had a prob w/SGI's XFS.
What would be kewl is HAMMER on Slack
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.
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.
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.
Hi folks! We're going to call this set of updates RC2. There are still
README files to be handled (that's the nature of documentation, I guess), as
well as some other things remaining on the TODO list, but X seems pretty
stable now, and it seems like a release soon would be in order so that we
can march right back into development territory with -current again soon. :-)
Enjoy, and let us know about any problems you run into!
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.
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:
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!
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.
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.