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.

I have a small amount of webspace opening up and am thinking about putting up a web site that guides the reader through setting up a simple but full featured desktop on Slackware. The idea is not to skimp on the apps themselves but rather to save resouces at the desktop level.

This would be an extension of a Linux Journal article by Marcel Gagne where he used icewm but also stayed with lightweight apps (ie dillo as a browser). All I seem to need from my desktop is a pleasing look and a way to launch my apps. I recently setup a gnome 2. 12 desktop and feel that my lightweight desktop can do anything that the Gnome desktop can.

I basically did a base install of slackware of the a/, ap/, d/ + python, n/, l/ x/ then compiled all the apps I use from source. I have been able to keep it very up to date. When ever a new release comes out, gimp for example, I just copy the ".configure" line from the config.log and if it successfully configures run "make uninstall" on the old code. Then "make && make install && make clean" on the new code.

Slack-packages could also be used but source code has the advantage of being able to
upgrade quickly when new code is released

This looks like a fair undertaking so I wanted to get feedback up front before investing alot of time.

I quickly found that Vector didn't give me enough control Install-time which apps I wanted.
I also noticed that almost everything Gnome or KDE can offer can be done easily enough with IceWM and have been trying to do this exact thing. I only got around to figuring out some of the apps and a set of configuration tricks and tips.
There is not as much point in figuring it all out if nobody uses it, so creating a tarball of downloaders and installers would make it nice and easy. Source might be difficult to automate.

There is not as much point in figuring it all out if nobody uses it, so creating a tarball of downloaders and installers would make it nice and easy. Source might be difficult to automate.

Tarballs are an option and many of the programs come with Slackware or can be had on LinuxPackages. I was actually thinking of setting it up so users could copy and paste the commands to compile the packages - sort of like Linux from Scratch. Source automation is too much for me to tackle - besides why not use FreeBSD with the ports system (for me is was because Slackware supported some of my hardware better).

My laptop has a Via C3 CPU and some of the LinuxPackages i686 packages would not work on it so I ended up compiling my own. Once I had the the compile setup it became easy to to do my own updates. I am still running Slackware 10.1 but have upgraded many applications. I had firefox-1.0.7 long before Pat V. released a security patch. My version of gxine, midnight commander, bittorrent, gimp and abiword are all newer than came with Slackware 10.1 and it should be easy for me to continue to do upgrades 6 months from now.
.

You are mixing your audience somewhat. Anybody who would do anything like LFS would not need the guide. Anybody who couldn't, would be lost at most of the console commands, even if *most* of the time, it works fine. *most* people run i686, so packages would be no different from source.

I've been hoping to get some help/input on some of this stuff.
I set it up using wmaker, fluxbox or xfce with taskbar or fbpanel and a patched ROX-filer for the icon and drag-n-drop handling. I even have wmaker setup so that no icons, mini-windows or even DOCK apps will show! I choose window-maker because of it's speed, size, smoothness, and 2 available GUI programs for configuration, especially of desktop menus (I'd really like to do more work on the panel and get drag-n-drop menu creation working there. I let the window manager take care of any paging capabilities available. I also use the WDM diplay manager for login(on runlevel 5 to avoid interfwering with KDM/GDM).

The main idea besides being light, is that the panel, window manager and filer all run separately -using non-integrated components has some great advantages.

You can get a very nice GTK-1.2/lesstif desktop for around 250MB including dozens of GUI programs!

Nice! I also like WindowMaker, but with that arrangement, the dock and the panel seems a bit redundant. IceWM and WindowMaker are so alike, but I like IceWM more cause of the easy manual configuration.

It is a tribute to Slackware flexiblity that the Dropline developers can come up with an i686 optimized, all the bells and whistles destop.

The desktop that I have in mind may be more in keeping with the basic Slackware goals of simplicity and elegance while providing full functionality. I have a box setup with Gware Revison E (Gnome 2.12) and my basic box actually can do anything the Gnome box can but is much more efficient.

Quote:

I quickly found that Vector didn't give me enough control Install-time which apps I wanted.
I also noticed that almost everything Gnome or KDE can offer can be done easily enough with IceWM and have been trying to do this exact thing. I only got around to figuring out some of the apps and a set of configuration tricks and tips.

For me Vector was my first exposure to Slackware but the more recent versions that I have tried I have had to tweak things like Xorg using what I subsequently learned in Slackware.

Quote:

You are mixing your audience somewhat. Anybody who would do anything like LFS would not need the guide. Anybody who couldn't, would be lost at most of the console commands, even if *most* of the time, it works fine. *most* people run i686, so packages would be no different from source.

I was thinking of a shorter path. LFS/Beyond LFS is a very long journey from start to Desktop. Newbies could get an introduction to basic commands, and be walked through compiling about 35 apps/libaries to get their desktop. Since Icewm uses a simple set of easily edited files to set up menus, newbies would not have to deal with editing all the *.desktop files that are now needed in Gnome.

Quote:

I set it up using wmaker, fluxbox or xfce with taskbar or fbpanel and a patched ROX-filer for the icon and drag-n-drop handling.

I suppose it could be setup for several different windowmanagers although Zenwalk does a pretty good job with XFce. I am not excited about desktop icons. I already can start apps from the toolbar and the menu, why add the overhead of desktop icons for a third way to start apps?
Windowmaker, Fluxbox and XFce all come with Slackware in xap/. Icewm does not. We could
set up links to Your site on tweaking Windowmaker. I also kinda planned to keep gtk2 as firefox, , thunderbird, nvu, gimp, gtkam, and beep media player all utilize gtk2.