If anyone wants to try it, I would appreciate the feedback.
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.
Make a 3 Gig ext4 first partition on your USB key , enable boot flag.
Extract the slackjack folder onto the created partition.
Go into /slackjack/boot and run 'sh bootinst.sh'.
Boot from USB key, the user password is slackjack. root is root.
(although I think you have to use a console login and startx to be root.. and not through kdm).
Some things that some may find interest in, is that it uses what has been called a "lightweight KDE", meaning that it has been compiled without nepomuk/soprano/sonata/akonadi/shared desktop ontologies/kde-pim/kwallet. (I also recompiled some of the KDE core apps not to use those libraries.. K3B, kate, gwenview, etc).
It also has PAM built in. (Almost have to have a degree to set that up)
I've tried it out on all of three computers, all Intel chipset.
On two of those internet didn't work out of the box (driver issues?).
I know it works for sure on a Dell Latitude 2100.
YMMV. I may try to polish it up eventually.
thank you for your USB-image. I tried it on my Dell Optiplex GX270. Booting the image first gives a failure because it cannot find vesamenuC.32. After that further booting results in a kernel-panic, it isn't syncing: VFS: unable to mount rootfs on unknown block(0,0). It is a pity. I would love to have live slackware-on-a-stick very much, especially with Multimedia software (for my son, he likes to play with video's and music). Good luck with your build!
I appreciate the feedback. I saw something similar when trying to boot from a DVD/ISO. It is a problem with isolinux bootloader on some hardware (or at least I believe this to be the case). Haven't delved in it too far yet, I have no solution as of yet.
Tried it, followed the instructions and it works perfectly.
I'm running this off my Imitaion 500GB usb external HD.
All I have left now are small setup annoyances with kde that keep piling up.
Like to have a big ' SAVE settings' button instead of having to reconfigure on every boot.
Like to have dhcpcd program instead of gui - its not there.
Have not yet found a way to change background wallpaper, but i will -- eventually.
But other than these cosmetic problems, it works!.
Wallpaper is easy. Right click on desktop, "Default Desktop Settings". I change at least once a week, if not daily, depending on mood.
As far as saving settings, perhaps make another partition on your USB drive and mount it on /home/slackjack (Still not a painless, easy way of doing it every boot). Then if you wanted to get fancy with it, you could encrypt it as well, lol.
(I think it's Knoppix live that has the really cool utility that allows for the creation of a container to save changes and also allows you to encrypt it as well. Works great... as long as you remember the key.)
About the host name, I have three younger sisters, it actually started years ago from a band.. 'Big Brother and the Holding Company'. Maybe I should have kept it darkstar
For those not familiar with JACK, you can configure it with cadence, configure, driver, find your device, give it two output channels, force restart. (If working with midi, enable it).
A hint on Carla plugin host, unclick LADSPA, skip sooperlooper, and will find the rest of the plugins.
On dhcpcd, if you hit <ctl-alt-f2> and login as root there, you can issue a manual dhcpcd. PAM blocks some commands from root in an emulated terminal (like ldconfig, iptables, etc). Use <ctl-alt-f7> to return to gui.
Oh, and I'm glad to hear that it works for at least someone. Thanks for that.
I've seen some people trying to lump PAM in the same category as systemd.
I don't feel that way. I've heard the PAM developers complain that *so far* any vulnerabilities that have arisen have been with external 3rd party modules (*ah-hem*, selinux). There was a very practical reason for me to use it, some audio apps want memory locking. That was the only way I knew to achieve it: https://wiki.archlinux.org/index.php...ess_management
I, myself, do have some questions on how POSIX message queues work and kernel interaction thereof, anyway...
I was actually surprised at what a positive performance increase that came from the use of PAM caused.
And just as note, I've found that if wireless doesn't work on boot, you may have to go into wicd settings and change wlan0 to wlan1.
Mainly this was an attempt to fix the network bug by removing the persistent udev rules that I accidentally left. Despite this, I have still found it necessary to adjust interface names in wicd settings at times for it to work.
It's also quite a bit larger than the first version because I was experimenting with different window and file managers.
I have added a rudimentary standalone compiz desktop selection along with the others. You can also go in the settings and add an icon for lancelot menu for it, but it enables half the kde suite (which is why I don't have it there by default).
To "log out" gracefully from compiz (to go back to kdm) you can issue a 'killall cairo-dock'.
Oh, btw, Cairo-dock communicates to the internet... don't blame me.
XFCE is broke in that the window decorator doesn't start. I thought I had fixed this before I made the image. The cure is to issue a 'xfwm4 --replace', you can also try out any of the other window managers/compositors (kwin, compiz, emerald, mutter, gala, compton) from xfce.
Let it be known that I purposefully broke some of gnome backends that allow some of these and other gnome-centric apps (like pantheon-files and the other file manager) to work.
For example, if you su in and cd /usr/libexec/store and issue a 'mv at-spi-bus-launcher ../' then you can try out mutter in xfce ('mutter --replace'). You'll have to do the same thing to try out some of other file managers that I installed (running in terminal will give you a good idea of what it's wanting). Instead of figuring out which ones I guess you could just 'mv * ../' in /usr/libexec/store...
This is going to be the last version, as it's already too bloated. It was a learning experience and experiment for me (eventually I would like to build a lightweight arm OS). I have cross compiled for arm before, but here I was exploring different interfaces/app options (processes involved, dependencies, etc) for that.
I also added a few more soundfonts in /usr/share/sounds/sf2.
This version takes about a 3.4-3.5 gig partition to install.
Oh, BTW, I failed to mention previously, I compiled to use SSE extensions.. IE. 686.