How does that make configuring lilo easier?
With lilo in slackware I always have found a very well commented config file, and a graphical (yes, those menus in the console are graphical) setup utility.
With grub in Kubuntu I had to search in the gentoo documentation before I got anything else than "format and reinstall" as an advice to updating the mbr. After that, I had to edit menu.lst 3 times because I made some errors due to bad comments.
Grub may try to configure everything "automagically", but when it fails, you're better of with lilo.

For keeping Slackware up to date, the best thing to do, whatever method you use to update it, is watch the changelogs at www.slackware.com

I personally keep a local mirror using Alien Bobs' mirror-slackware-current script. You can use it to keep a local mirror for any slackware version, just edit it to change the version number and set the mirror to a reliable nearby one.

As for editing configuration files at the command line, you will almost certainly find nano or pico easier to use than vim. Vi and Emacs can extremely obtuse if you are not used to them, although it is a good idea to pick up at least basic familiarity.

EDIT: let's not turn this thread into an X is better than Y flamewar, please

X is better than Y

I'm of the opinion that updating is best done by backing up data and doing a fresh install from scratch...and if it isn't worth doing that, then the update is more likely the result of obsessive desire to run the latest without a real need to do so.

I also use Debian some and it is claimed with apt-get you only install once and then update to keep the system current over many years. I learned the hard way that this is true 99% of the time -- but it's that 1% of the time that bites you.

So, when it comes to "mission critical" machines, that ability to update easily isn't an advantage other distributions have over Slackware, IMHOP. Within my LAN, I have servers running Slackware 7 all the way through 11. The one Debian server is locked in the time warp of "Potato," and next week, the CentOS 5 webserver will be "updated" to Slackware 12.

I understand that some people are into Linux for the fun, and updating is part of the fun. Me, I'm into Linux because I would rather be able to sit on my butt and post at forums than have to scramble constantly to fix broken systems. I keep the LAN firewalled and tunnel in with SSH to a dedicated box from which I ssh within a new shell to any other box I want to look at...that way, things stay pretty secure even though some of the installations are getting a bit old and creaky.

I NEVER upgrade an installation I'm reasonably satisfied with. And since 1998, I've found that most Slackware releases are put together with sufficient care that unless a third party application (not part of Slackware) requires an upgrade and won't run on the earlier Slackware release, there is no compelling reason to upgrade. If it worked five years ago and if it's still working today, and if the iron is still reliable, I leave it in peace.

So really, to me, the lack of an "automagic" update/upgrade is a desirable feature of Slackware -- not a shortcoming in comparison to other distros. For example, to compare Slackware to Debian: With Debian, I can add a lot of non Debian software respositories to /etc/apt and with a quick "apt-get update" --> "apt-get upgrade" --> "apt-get install foo" I can quickly grab any of several thousand software packages. Sounds great, and it is, if I'm experimenting.

But unless I've been rigorous in keeping the Debian machine updated every few days, there is a good chance something will be broken after the upgrade...and even if I update very 24 hours, the upgrades occasionally hose a configuration that I have to go in and patch up...and it's often enough that I've concluded the best way to keep a Debian server going is to ignore apt-get after the initial installation and compile most of the additional software packages from source when I discover I need them (which isn't too often)...same as I do with Slackware if they aren't available as a tar.gz slack pack for the particular release.

So what do I get with something like Debian or CentOS as examples? They're not bad, but mostly I get a system that isn't quite as reliable as a Slackware system...a bunch of "labor saving" utilities that I don't really dare use because they create too much work fixing broken stuff...and in the case of CentOS, a whole lot of overhead that consumes processor cycles and ram that makes the system slow and doggy compared to a Slackware installation on the same hardware.

That actually deserves two:


Good one mate!

Hi,

Yes, you should be offended! But just consider the source.

Eric, I read b0uncer's post. I just didn't have the time to reply to such a trivial vial post. He has a right to post his views. But, why does he continue to use the OS if it is so bad.

I don't need to defend Slackware because I know the OS is the best GNU/Linux available!

I think for the most part Slackware users are very unidialistic, which for some reason seems to piss off idealistic fellows such as your self. If someone asks a technical question, they will almost always get an accurate answer. I think the common factor in your poor experiences with Slackware users is most likely yourself.

You don't like it? Hey, I got an idea. Why don't you go use that other distribution/Windows/Kubuntu/stop using computers.

My point is, people who like and use Slackware use it because it is the way it is. We could care balls about what people like you think about it. If you don't like it, then it's not for you. No loss to us. However, if you're interested in learning about it, there is no shortage in Slackers eager to teach what they know. Otherwise, quit complaining.

Best regards,
~A Slacker

thanks for the help, from those that did help, those that didnt.. we can now see, intelligently, why linux will never be a driving force on the desktop (whether it be the 2 big braggers distros, slack & gentoo, or those that hold hands) with 350+ distros and all the egos involved.. people will be confused, and will ask seemingly stupid questions.. but will need help or a point in the right direction.. to get started on their linux journey/choice..
ive gotten gentoo and slack installed after lots of reading and tries and re-tries.. but i get the same slack(pardon the pun) from the forums or chatrooms..
I will take my name off of this or mark mail from here as spam.. I will continue to use pclinuxos.. (which for 2 1/2 years has always just "worked" after installing and checking out 15 other distros, it's truely the distro hopper stopper)
thanks for the insight into the egos and rudeness of yet another distro and thanks for those that helped...
good luck peoples..
bye

Thank you, that was a *very* interesting post.

I'm sure Pat has excellent advisers. From 2.4.33.3 default kernel to 2.6.21.5 is a huge step.

You don't like Slackware. Ok, it's your choice (choice = the power, right or liberty to choose). I like Slackware. It's my choice. You like GRUB, I like LILO. What's wrong with that? Nothing!
There is only a wrong choice: to offend, insult or affront others. This is your choice till now.

[ Was unable to su to root and then get use of the X server for the use of Kwrite ] (normal, unless modify permissions as shared elsewhere in this same thread).

I was unaware of that one until now.

Kmenu > system > more applications > File Manager - super user mode

Prompts for the root password. Browse to file, right click the file, choose open with editor_of_choice (opens file in super user editor (in my case I choose kate))

I shared of this up near the start of this thread.

But I only add on or post now to 1. say thanks for the kdesu tip. 2. In my super user file manager I set the text color a deep dark red AND in (super user) kate (my editor of choice) I set the background color to lightly colored red. In this way I get immediate distinction of super user since the red in each of those signifies root. My regular user modes of each are of course without the mentioned red colors.

--
Alan.

I like to make "ROOT" shortcuts. I'll make a shortcut (on the kicker or kmenu) to Konsole or Konqueror and edit command to read:

kdesu konsole

or

kdesu konqueror

Nice if you need some quick root privileges. I guess you could always call "sudo konsole" or "sudo konqueror" from a konsole too.

updating... as far as applications go, you do it yourself. Other than that, you can update system components just like applications; rebuild your kernel when a new one comes out or you get sick of the old one.

command line editors are something you must know about. the most popular are emacs, pico, and vim. Personally vim turned me off until I decided that I needed to know how to use it. now other editors annoy me and i use vim exclusively. you might try norton's midnight commander editor - it is standalone, and someone referred me to it on the forums - mcedit. very easy to use; cut/copy/paste functionality is pretty easy once you get the hang of it. By the way, the midnight commander is a nice two-pane file manager if you're copying a lot of single files to different directories; not all that terrific for large copies unless it's an entire directory. builtin ftp and ssh support too.

for getting to the graphical login, follow instructions anywhere to edit your /etc/inittab. it is not necessary to login and then enter your x session every boot.

sadly, I am not familiar with 3d desktop effects yet.

cheers! thanks for trying slackware - hope you'll keep it.

I know this thread is several months old, but I have a problem with this solution - namely that it doesn't help me . After creating ~/.kde/Autostart/startup with "xhost +local:" in it and logging in, KWrite opens the file and I still can't run GUI applications as root. Any ideas?

Not about that way.

But somewhere on the K menu there's can pick/choose the likes of

"file manager, super user"

when used, it launches the konqueror file manager with rootly powers (prompts for root password)

As to that mentioned pick/choose on K menu, I right click it and choose "copy to desktop" and now I got the launcher icon on my desktop (easy to find for next time use).

Anyways, (rootly powers) I can right click a file then choose "open with" (kwrite is there, I usually use kate editor) *as root* now editing (using an X Win editor app) as root.

I changed the background colors of both of the X Win root apps that I use. Made those colors with a noticable red tint to them. (user mode of same apps stays as before, white colored). The red tint visually reminds me I'm using an X Win root app.

Does that help?

--
Alan.