http://www.linuxquestions.org/questions/linux-newbie-8/command-line-equivalent-of-network-manager-833898/#post4106241

Smoking Tux.

Here’s a quick update. As I mentioned in the previous post, one of my intentions of using Slackware is that I want a stable system on which I’ll run Virtualbox. After my first install, I went and downloaded the latest .run package from the above website, which according to this thread should install nicely.

Here I ran into problems. The package installed, but when I started Virtualbox (virtualbox in terminal emulator), I got an error stating that vboxdrv could not be loaded. Not even this link helped me. I finally figured out that the problem was that my kernel was not an SMP enabled one. I tried to change the kernel, but I couldn’t figure it out, so I went and reinstalled the entire system, since it would be a lot faster. This time around, instead of going with the default boot kernel, I choose the SMP one. Can you imaginge that the Virtualbox installation went flawlessly on the new installation? Any ways, it did. And yes, I will learn to change the kernel some day. I’m just not there yet.

Keep on slacking!

Smoking Tux.

Don’t get me wrong, I want people to use open source software and I’m an avid Linux preacher. Still, you should ask yourself the question in the title of this article. As expressed in this blog post, Slackware is not simple as in easy, but design wise. The KISS principle applies to Slackware Linux. This means that customization is left to the user. As good as all packages (as far as I know) are left as they were released by their authors. So, let’s take a look at who might be interested in this seemingly boring Linux distribution.

Who want’s Slack?

By far the biggest selling point of Slackware is the stability. What makes Slackware o stable is a combination of things. The “vanilla” packages and the tendency to choose older but more stable versions of software over newer versions are two big factors. If you’re setting up a server, stability should be one of your top priorities, and hence make Slackware a competitor. Maybe you want a file server for your home, or maybe your’re planning on setting up a web server? Check out Slackware.

Setting up a server?

My own excuse for wanting a stable operating system is that I want something that won’t break or freeze. I want a stable foundation. I then plan on running virtual machines on my Slack box. For example, I wanted to check out Arch Linux, but I’ll do that in a virtual machine on in Slackware since Arch Linux is more of a bleeding edge distro. I get the experience without the frustration of an update making something break.

Another decisive factor for me is simply the coolness. To me there is something attractive about really understanding the ins and outs of Linux. Ubuntu won’t give me that. Slackware will, or at least so the saying goes. Slackware aims to be the most UNIX-like distro out there.

If you want stability, control and sheer knowledge of what’s going on behind the scenes in fancy GUI programs, Slackware is a good place to start.

What kind of installation do you want?

You can install Slackware in several ways. Just throwing out some ideas, but this might already be familiar to you. First of all, if you’re setting up a server, you might want to do all the tweaking via SSH from another computer. Since servers usually don’t need a screen, this means you could opt out the X window manager and the desktop environments on installation.

My first thought was to do a minimal install, just the basics and then expand as I go, but on a second thought this is (at least for me) completely the wrong way. Expecially since I figured it would take a while to get used to the fact that Slackware’s package manager doesn’t resolve dependencies. Instead I chose the full install. This way I get a complete system in which I can experiment end try out things before I settle on for example a favourite desktop environment (currently I’m running fluxbox). Once I feel confident enough, I can remove the stuff I don’t use.

How do I get Slackware?

First of all, download the ISO’s. They are available here. I recommend getting the DVD ISO, which includes the full system. After this, find or buy a USB drive that’s larger than roughly 4.2 GB. Get UNetbootin. Run it with your USB drive plugged in, and instead of choosing a distro in the drop down menu, choose to supply your own ISO. This will put Slackware on the USB drive and make it bootalble. Keep UNetbootin for those days you feel like trying a new distro. You can pick from the menu and UNetbootin dowloads it for you. Now you boot up your computer with the thumbdrive. You might have to press F12 or something similar during boot. Keep an eye out, since the boot screen usually tells which key you need to press to get the boot menu. Select your USB drive (sometimes listed under hard drives) and the installation program will start. Follow the instructions and go with the safe choices if you’re uncertain what to pick.

The Slackbook is a great resource for installing and configuring Slackware Linux. It really contains everything you need to know. Otherwise, try Google.

Note that the above is my way of installing Slackware. I’m not very fond of CD or DVD media and would use the USB method any day. The downside is that if you don’t have a USB drive already (chances are you do), then CDs and DVDs are a lot cheaper.

Summing it up

This concludes the second part of the Slackware series. In the next part we’ll take a look at configuring. One thing that I spent some time with was the cofiguration of wireless networking. Wireless is getting more and more common, so well give that some attention in the next article. ‘Til then; Happy hacking!

Tux the linux penguin smoking Dobb's pipe.

So I figured it might be a good idea to start something fresh here. A new series. Don’t think for a second that I’ll stop the BASHtronaut series (which you’ll find here). I’ll just add to it when I find something fitting.

You have probably already guessed it. We’re going to take a look on Slackware Linux, a long time dream of mine. It’s not until recently that I’ve mustered up the confidence to actually give it a go.

So what should I focus on in this new series? There are plenty of HOWTO’s out there, and they already do a good job. Instead I’ll focus on the things others might not. For example, stuff that might seem self evident to the seasoned slacker, but is a big “why?” to the beginner.

When I do things a certain way, I’ll try to explain why I think that is the way to go. Since there is no true objectivity in this world, I can only give you my view, and not the ultimate best way of doing things.

Background

Patrick Volkerding

So what is Slackware? You probably know that it is a linux distribution, which means that it is a Unix-like operating system built on the Linux kernel. Follow the links if you want to do some more reading. According to wikipedia, Slackware is one of the oldest Linux distributions, and the oldest one still being maintained. It was created in 1993 by Patrick ‘Pat’ Volkerding, and is still being maintained by him.

We see new releases roughly once per year, which means we might see a new release soon (at the time of writing this post March 15, 2011, the last release was version 13.1 on May 24, 2010). However, there is no garantuee of that. One of the central design philosophies of Slackware is to release only when, and only if, the next version is considered ready and stable enough.

Stability is one of the key tenets of Slackware, and because of this, it’s not uncommon for the software to be “a few versions old”. By that I mean that there’s no pursuit of having the latest versions of the different software packages, since they tend to contain more bugs. Also, Pat is reluctant to include any distribution specific patches, so most packages are “vanilla”, which means that they are kept as released by their developers. All for stability’s sake.

Slackware aims to be simple, but not in the sense that it does everything for you, but in the aspect of design. It puts the user in the driver’s seat, and leaves less to auto configuration. It is not uncommon to hear Slackware users say that using for example Ubuntu, will teach you to use Ubuntu, while using Slackware will teach you to use Linux. I will leave this statement unverified. It’s up to you to find out.

Summing it up

I hope that gives you a general understanding of the philosophy of Slackware. I see no point in re-writing what others have already written, so if you want to go more in depth, check out the provided links, or consult the all-knowing oracle known as Google. In the next article, we’re going to take a look at who might want to install Slackware, what kind of installation you would do, and lastly some ways to go about it. See you then! Happy hacking!

I took the time to scale down the computer. I want this computer to be as silent as possible, and this means I have to use the motherboard and case I saved from my parents a while back.

As we speak I’m doing my first ever Slackware install.

[time passes]

21 minutes after beginning the installation, I’m done and booted. Success.

This winter has as usual been rather chaotic when it comes to trains. One could expect the Swedish train companies to be better prepared since we live in a country that most certainly sees snow every year. However, this is not the case.

The Swedish train companies panic in the winter because the switches freeze and the heaters in the trains fail. The Swedish train companies panic in the spring and autumn because of the storms, and more so in the autumn because of leaves(!) on the track. Lastly, the Swedish train companies panic in the summer, because the air conditioning stops working, resulting in cooked passengers.

Over all, the Swedish train companies just make it hard to depend on them. I can’t really build a life involving commuting by train unless I leave an hour earlier than I intended, and expect to be home an hour later than I first planned.

Another thing that bugs me about the train traffic is the escuses. As soon as the train is delayed, the  train personel has the habit of blaming someone else via the intercom. It can go something like this:

“At the moment we can only keep a speed of 80 km/h, since there is a freight train before us.”

I have no interest in why you fail to provide the service you’re selling! The train traffic would be so much better if the tracks had been properly served and upgraded, but public transportation, unfortunately, is very secondary to cars these days. Also, the greed of the individual train companies has packed the tracks so full, that the slightest disturbance will cause a chain reaction and cause delays over large regions.

Still I go by train to school. Mostly for economical reasons, but environmental reasons are also a big factor. If no one uses the public transportation, it will be all the more neglected. That’s a good enough reason for anyone to choose the train or bus over the car.

That concludes today’s rant. Five to go. Happy hacking!

• I’M A DAD! Yes it’s true. This is the main reason for my abscense on the blog. I just don’t have the time. Also, it’s way more fun hanging out with Alfred than blogging. Expect pictures.
• I’m studying more than ever. This is another reason why I can’t devote as much time as I’d like. Family first, you know, and studying is my way of providing for my family (yes, it’s a proper family now! )

However, as the title says, I will give the one-week challenge a try. If you’ve been on my blog before you might have read of my plans of “converting” the blog to Swedish. A lot of material has to be re-written, so I’ll postpone that undertaking.

Since I don’t have as much time at the computer as I used to, the weeks ahead of us will probably be more centered around news, rather than how-to’s. There simply isn’t enough time for re research required. Bare with me and I’ll try to rev up the update intervals. Don’t be scared of contacting me if you want something specific written.

Happy hacking!

At launch I’ll make sure to have lots of material, some translated from this blog, and some new. Keep an eye out for it. I hope you’ll enjoy it.

Happy hacking!

I will still keep the original blog – I’ll just make a new one in swedish. I’ll translate the “Earning your BASHtronaut wings” series to swedish to start with. As if my posting here wasn’t sporadic already, it’ll be even more sporadic from now on.

If you still wish to see posts here, let me know. The translation itself isn’t all that painful, but I don’t think too many people read this anyway Instead, look forward to a spankin’ new shineh pretty blog – this time in swedish/svenska.

If you’re reading this in a regular browser, feel free to try it in Lynx. Since I don’t get any user feedback, all and any feedback is welcome. Constructive criticism is preferred, but if you think the blog sucks, I can’t stop you from saying so. Is there anything in particular you would like to see on R3DPiLL in the near future?

Happy hacking!