My thoughts on Slackware, life and everything

Beta 6 for my Live ISO images

blueSW-64pxYesterday  I uploaded new ISO images for Slackware Live Edition, release “0.6.0“. Then I waited a bit before writing this article to allow the mirrors to catch up with the 8 GB of new files.

Check out my previous articles about Slackware Live Edition for more background information and read the README.txt file provided with the “liveslak” sources to get a grasp on a more technical level of how this all works.

What’s new in 0.6.0?

Still working towards a stable 1.0 release, I think I am mostly there feature-wise and I would like to see bug reports so that I can be sure that a future stable release is going to be enjoyed by everyone – seasoned or aspiring Slackware user alike. If I am not at version 1.0 by the time Slackware 14.2 is released, that event will trigger a Live Edition v1.0 for sure! But we’ll get there before Pat 🙂

The persistent USB variant of Slackware Live is what most people are probably going to use. But the ISO on DVD or a read-only stick is just as awesome, because that variant will be particularly interesting for people who are demo-ing Slackware (because they are new to Slackware or because they want to see how slackware-current performs). For this new beta, I have focused on fixing all the small bugs I ran into, but here are some of the highlights in terms of new functionality:

  • You can now use an encrypted container file to store persistent data. The “” script was extended with a new “-C” parameter that allows you to specify a size for this LUKS container file, quite similar to what you already could do for a LUKS encrypted homedirectory. The data on your persistent USB Live will be safe from people who steal the stick from you.
  • A hard disk installer was added to all Live variants except the minimal XFCE. As far as I am concerned, the XFCE version is nice to run as a small Live OS but unsuited for hard disk installation. This works straight from the DVD, and also in USB versions.
    You will be able to install the latest Slackware64-current, or the Plasma5 or Mate version to your computer’s hard drive, in the background while you are working/playing in your Live Desktop.
    From within the Live environment (either at the console or in an X terminal in your running Desktop Environment) you can call “setup2hd” which will guide you. The script is a modified Slackware setup as known from the official install media, but it has already made the choice of package SOURCE for you. Note that you are responsible for partitioning your hard drive before you call “setup2hd”. This aspect is no different from the regular Slackware installer.
    The “setup2hd” script will install all the active Live modules to your hard drive (this encompasses all “system” modules, and furthermore including modules in addons/” and “optional/” which you enabled).
  • Documentation was added. A README.txt file contains all the details of using the Live Edition, as well as technical background on how the liveslak scripts do their work.
  • Customizing the Live Edition has been made easier. You are no longer tied to the choice of “SLACKWARE”, “PLASMA5”, “KDE4”, “XFCE”, “MATE” or “CINNAMON” when generating a new ISO variant. A “custom” variant with its own custom name and custom post-install configuration is now also possible.

Download the ISO images

I have created ISO images for the SLACKWARE, XFCE, PLASMA5 and MATE flavours using the latest Slackware64-current packages available (Tue Feb 23 19:31:59 UTC 2016) as well as latest Plasma 5 and Mate releases.

You can find the ISO images plus their MD5 checksum and GPG signature at any of the following locations – look in the “0.6.0” subdirectory for ISOs based on the liveslak-0.6.0 scripts. I made a symlink called “latest” which will always point to the latest set of ISO images:

These mirror servers should have synchronized by now.

The ISOs have two user accounts: root (with password ‘root’) and live (with password ‘live’). My advice: login as user live and use “su” or “sudo” to get root access (note: “su” and “sudo” will want the live password!).

The ISOs are able to boot both on BIOS-based computers (where syslinux takes care of the boot menu) and UEFI systems (where grub builds the boot menu, which looks quite similar to the syslinux menu):


Have fun! Eric


  1. Didier Spaier

    Congrats for Beta 6, Eric.

    I just had a look to setup2hd. Well done!

    gettextizing it wouldn’t take me more than one hour if you are interested.

    It would also be easy to cherry-pick the already translated messages from Slint PO files. Just a few new or modified ones would need to be translated in addition to those.

    So I see no issue technically speaking. But of course I can understand that seeing what they get in Slackware Live some users could request an internationalized installer be included in Slackware, not realizing the implications regarding maintenance of a far more complex installer and associated config scripts, and I assume that would worry Pat.

    Anyway, thanks for this Beta 6.

    Take care,

  2. alienbob

    Indeed, maintainability is what withheld me from implementing setup2hd as an internationalized installer. I would be dependent on a dozen other people to supply translations and I hate to be dependent, so that was not an option.
    Furthermore, with an internationalized installer, the non-english speaking user would be confronted with US-english Slackware tools and man pages, so this too would have to be addressed. And at this point, the slint changes would modify the stock Slackware setup. I want the SLACKWARE variant of the Live ISO to be void of 3rd party stuff so then I would have to maintain two separate installers. It’s just too much work for this small side project.

  3. Armin Herzer

    Hello Eric, thanks for liveslak 0.6.0. No issues with german keyboard anymore. Everything works as expected. Now I will start to do some customizations and build my own modules.

  4. Owen Greaves

    Howdy! Fired up LIVE – it seemed to be doing well, and then it just sat at a black screen at the loading of X11. The system has an old NVidia card in it 7500 me thinks. Will try again with a different card later today.

  5. ikke

    Downloaded and did a frugal install of the XFCE version. Everything seems to work as expected.
    So just one more time : thank you very much. Nice piece of work!

  6. alienbob

    Owen – try adding a “3” to the syslinux or grub boot command and you will end up in runlevel 3 (console login). Then run “startx” in the hope hat you are able to catch some errors.

  7. Phil

    Installing from usb at the moment. One problem when I select UK keyboard at the start of the install process still get US keyboard.

  8. alienbob

    Phil, that may be something I need to fix in setup2hd… I copy the “/etc/rc.d/rc.keymap” from the ISO to the harddisk irrespective of your choice. That is not OK of course.

  9. SangDae YU

    In, the BIOS Boot Partition is built. Where is this partition used?

    In liveinit, two lines are identical.
    cp /mnt/overlay/usr/share/zoneinfo/${TZ} /mnt/overlay/etc/localtime
    cp /mnt/overlay/usr/share/zoneinfo/${TZ} /mnt/overlay/etc/localtime

    In, KGEN is changed for the 32-bit Slackware.
    echo kernel-modules-smp-4.4.1_smp-i686-1 |head -1 |rev | cut -d- -f3 |rev | tr _ –

  10. Ricardo J. Barberis

    Off-Topic: Is there a way to subscribe to an article’s comments without actually commenting?

    Commenting only “Thanks!” without providing something more valuable seems silly after doing it a couple of times 🙂


  11. alienbob

    Thanks SangDae, I have applied your suggestions & fixes.

  12. alienbob

    Ricardo, I did not see a way to enable a subscription to an article’s future comments without actually commenting yourself first, but I added a generic “Subscribe to Blog via Email” widget to the right sidebar, which will subscribe you to any future update (all new posts and all comments).

  13. Owen Greaves

    Hey Eric,

    I was successful in running Init 3, and then start X (startx) the boot process is DOG slow, I got the KDE splash screen for 5 seconds, and then it went to black. The cursor is on the screen, as it is not black in color…but so far I am only getting a black screen using LIVE Plasma 5 ISO. I was getting IO errors from the disc, so I burned another disc. I did not see any errors while loading X.

    Second DISC – the boot process went a little faster without going to init 3, but the loading of X is really, really slow, but this time it loaded to the login screen. After providing login password, screen goes black, for a good 20 seconds, then the desktop appears. Once it’s loaded, it runs cool. So I can only assume the first disc I burned was the problem : )

    Thought I would share my experience with you. Thanks for all your hard work on this. I’ve been running it now for 20 minutes and so far nothing has broken, or is glaring as a problem.

  14. alienbob

    Owen, Plasma 5 and its graphical login manager SDDM are heavy on the machine, so you will notice slow startup on “older” computers anyway. But running it from a USB stick as a Live OS puts additional demand on the quality of that USB stick. With a stick that has fast read speeds, you will be a lot happier.

  15. pal

    frugal install of the XFCE version

    how is that ?

  16. twotonman

    Something is missing in slackware64-live-plasma5-current.iso:

    live@darkstar:~$ 7zFM
    /usr/lib64/p7zip/7zFM: error while loading shared libraries: cannot open shared object file: No such file or directory
    live@darkstar:~$ 7zG
    /usr/lib64/p7zip/7zG: error while loading shared libraries: cannot open shared object file: No such file or directory
    live@darkstar:~$ ldd /usr/lib64/p7zip/7zFM (0x00007fff507ee000) => not found => not found => not found => not found => not found => not found => not found => not found => not found => not found => /lib64/ (0x00007f02b8a09000) => /lib64/ (0x00007f02b8805000) => /usr/lib64/ (0x00007f02b848a000) => /lib64/ (0x00007f02b8181000) => /usr/lib64/ (0x00007f02b7f6b000) => /lib64/ (0x00007f02b7ba1000)
    /lib64/ (0x0000562276aa8000)
    live@darkstar:~$ ldd /usr/lib64/p7zip/7zG (0x00007ffd3bbe2000) => not found => not found => not found => not found => not found => not found => not found => not found => not found => not found => /lib64/ (0x00007f11b29be000) => /lib64/ (0x00007f11b27ba000) => /usr/lib64/ (0x00007f11b243f000) => /lib64/ (0x00007f11b2136000) => /usr/lib64/ (0x00007f11b1f20000) => /lib64/ (0x00007f11b1b56000)
    /lib64/ (0x000056364859a000)

  17. alienbob

    twotonman it seems I must add wxGTK to the package list, it is a dependency of p7zip.

  18. alienbob

    Someone noticed that vim is missing from the ISOs. It looks like a grep statement is not filtering out “vim-gvim” when looking for “vim-*”. This should only return the vim package but it also finds vim-gvim, therefore vim-gvim gets installed twice and vim not at all:

    FULLPKG=$(find ${SL_PKGROOT} -name "${PKG}-*.t?z" 2>/dev/null |grep -E "${PKG//+/\\+}-[^-]+-[^-]+-[^-]+.t?z" |head -1)

  19. ikke

    @pal “frugal install of the XFCE version
    how is that ?”

    you copy the iso (or at least the essential files) on a usb stick or on a hard disk and boot from syslinux or grub installed on the same usb stick or hard disk

    • pal

      @ ikke :

      thank you very much for the feedback but aint followin you …

      let\’s say i download xfce version and put it to a USB then what ???

      maybe in others words , what do you say …

  20. alienbob

    Well at least thanks to my friends in the Slackware coreteam I figured out what was wrong in my grep command. Updated script will be moved to git as soon as I have my new test ISO ready.

  21. SangDae YU

    Thanks Eric for your all scripts. What a nice live USB drive!

    It is difficult to know how to reduce the time delay between “Welcome to GRUB!” message and grub menu in UEFI boot…

    However some efficient codes are found in as follows.

    # No longer needed:
    # /sbin/umount ${USBMNT}
    /sbin/umount ${EFIMNT}

    if [ $EFIBOOT -eq 1 ]; then
    # Mount the EFI partition and copy /EFI as well as /boot directories into it:
    /sbin/mount -t vfat -o shortname=mixed ${TARGET}2 ${EFIMNT}
    mkdir -p ${EFIMNT}/EFI/BOOT
    rsync -rlptD ${ISOMNT}/EFI/BOOT/* ${EFIMNT}/EFI/BOOT/
    mkdir -p ${EFIMNT}/boot
    rsync -rlptD ${USBMNT}/boot/* ${EFIMNT}/boot/
    # Add more USB WAIT seconds to the initrd:
    # update_initrd ${EFIMNT}/boot/initrd.img

    # No longer needed:
    /sbin/umount ${USBMNT}
    /sbin/umount ${EFIMNT}

  22. alienbob

    SangDae, the code in has nothing to do with the delay between the “Welcome to GRUB”” line and showing the boot menu. That delay is internal to the startup of GRUB.
    The initrd only comes to play when you have selected your boot options from the GRUB menu. The delay mentioned in the script is meant to give the Linux kernel more time to initialize slow USB medium.

  23. Kalaha

    Dear Eric,

    thanks a lot for your work – you are the best.

    I have installed the live iso 0.6 to harddisk. I also installed genymotion 2.6, and it is working.

    best regards

  24. Kalaha

    Dear Eric,

    i forget to tell that i use the plasma iso.

    best regards

  25. Niki Kovacs

    Hi Eric,

    I have a small suggestion that’s easy to put into practice. The README text ( is weirdly wrapped… or not wrapped at all. On my monitor I have several hundred characters per line, which makes it somewhat difficult to read.

    Suggestion: wrap the README to a more classical format, e. g. something like roughly 80 characters per line?



  26. alienbob

    Niki, that README wraps nicely in my browser (chromium as well as firefox). Lines in the README are indeed long, but I do not see that as an issue.

    I imported the README into the SlackDocs wiki as by the way.

  27. Didier Spaier

    wrt the delay between the “Welcome to GRUB”” line and showing the boot menu:

    I made several tests out of curiosity booting off an USB stick on my laptop having booting mode set to priority UEFI
    _ using a genuine ISO (xfce): around 12 seconds
    _ using an ISO remastered with xorriso: idem
    _ with the /boot/syslinux up one level (becoming /syslinux): idem.

    However, booting the ISO as a virtual CD in a VirtualBox VM, there is almost no delay.

    There is also almost no delay booting in legacy mode (thus using syslinux instead of grub).

    So i assume that yes the delay is due to GRUB, but especially when booting off an USB device. I didn’t try booting off a “real” CD or DVD though, thus i don’t know if a delay similar to the one observed with an USB stick would occur. Maybe that doesn’t matter much as probably few people would use a CD anyway.

  28. ikke

    @pal “in others words ” :

    1. an HD / USB stick Ext4 formatted and grub legacy installed on it
    2. made a /liveslak directory on it
    3, in this /liveslak I copied the boot/optional /rootcopy /system directories from the iso
    4. my boot entry in ‘menu.lst’
    title slackware64-live-xfce-current “0.5.1 (Beta5)”
    root (hd0,0)
    kernel /liveslak/boot/generic load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 kbd=us locale=us_EN.utf8 tz=Europe/Brussels
    initrd /liveslak/boot/initrd.img

    you can easily replace grub legacy with grub 2.0 or syslinux

    Hope this helps …

    • babam

      Hi ikke,

      Does the “Frugal Install” can use persistence.img.


  29. Ricardo J. Barberis

    @alienbob, thanks for the widget! I’ll check it out.


  30. Jim

    live@darkstar:~$ gnome-mplayer
    gnome-mplayer: error while loading shared libraries: cannot open shared object file: No such file or directory

    good work, many thanks.

  31. alienbob

    Jim, yeah obviously the ‘gmtk’ package needs a rebuild on slackware-current. Thanks for checking and reporting.

  32. Grog

    Using the latest current from 23 Feb, and it boots very quickly and is running well on a usb3 stick.

    Two small boogers though…

    For some reason ‘user’ can not logout/restart/shut down using the menu or the taskbar widget. One has to become root to reboot. (I’m sure a simple thing like becoming a member of shutdown or something, but that used to be automatic)

    Pale Moon won’t compile and run. I tried starting it in konsole to get any messages and all I get is ‘segmentation fault’. It compiles just fine and installs with no hiccups.

    Okay, I lied…three boogers…I still have to go through all the bs to get my controls I use in a mixer (kmix), by adding and deleting in a few .conf files (as per this conversation here ).

    Other than these, it seems it’s still just getting better and better and closer to 1.0.

  33. Jim

    These apps don’t open for PLASMA5.
    No time for double check. Cheers.

    Adonadi Console
    DBPedia References
    KMail Header Theme Editor
    KMail Import Wizard
    KNetAttach ok twice?
    KsirK skin editor
    Okteta 2 times
    OpenjDK all
    PIM Setting Explorer
    Plan error
    Plan WorkPackage
    SCIM smart
    SSH SkPass

  34. Grog

    I tried to install the nvidia package per your instruction on an earlier post:

    “Copy to the “/liveslak/addons/” directory of your USB stick (if you used the Plasma5 ISO then this file is already in /liveslak/optional/ so you can simply move the file from optional to addons).

    If you reboot the USB stick, the Nvidia 352.79 drivers will (should) automatically be used, nothing else you need to do to make it work.”

    Unfortunately that doesn’t seem to work on this latest liveslak 0.6.0 ‘current’. It gets to the install of it, then goes to a blank screen with a blinking cursor forever.

  35. alienbob

    Jim you dump a shitload of application package names here and yell “These apps don’t open for PLASMA5.
    No time for double check”. At least tell me what does not work. How did you create the list, seems auto-generated?
    I tried random programs in a Live ISO I just booted without persistence and kmahjongg, ksirk, skanlite, okteta are working for me.
    Blogilo does indeed not work because of the upgraded There may be others but don’t leave it to me to guess please.

  36. alienbob

    Grog, debug your issue and let me know if I need to change anything.

  37. Grog

    The shutdown problem was as I suspected, one needs to become a member of group ‘shutdown’ which needs to be unchecked in ‘groups’ to even be seen by ‘user’ to become a part of it. I have no reason why this came about as usually I’ve never had to do this as a user.

    The pulse/alsa audio thing I can handle, it’s just that it has to be done at all, but seems more folk use bluetooth than those of us who use our systems as our music for the house and parties etc, heh. Oh well. Nothing you can fix there.

    I have no clue how to debug/figure out the problem with the nvidia not installing as it did on the 0.5.1 beta of ‘current’. I even made sure it’s executable, but it made no difference. I’m not trying to make more work for you, I just don’t have the knowledge for much of this debugging stuff.

  38. alienbob

    Grog, the nvidia issue is caused by the fact that the module is meant for a 4.4.1 kernel (which I show by using the kernel version as part of the module name).
    The 0.6.0 Live ISOs you can download have Slackware with kernel 4.4.3, therefore the package you downloaded is missing the kernel module for that version. But the install script will tell X.Org to use a nvidia kernel module which leads to your black screen.
    The Plasma5 ISO itself contains the proper version of the nvidia module in the /liveslak/optional directory, if you move or copy it to /liveslak/addons it will be used automatically on every boot.
    I also refreshed the public download locations such as the one you were referring to, so that the proper nvidia squashfs module can be downloaded from now.

  39. jim

    Hi alienbob,
    i want to apologize, you are correct.
    I use a live iso on usb. PLASMA5 0.6.1,without persistence. The previous list is a result from Application Finder. I checked all the applications one-by-one. Theese apps on the list didn’t launch. Today I tried from the commandline, all ok except: akonadiconsole, blogilo, cervisia, krubyapplication, kalarm, kgpg, kmail, headerthemeeditor, importwizard, korganizer and ktnef ( error… I hope I make sense.
    I appriciate your hard work. All the best.

  40. Grog

    Well crud. It was so obvious if it had been a snake it would have bit me. Sorry for making more work for you, i just really want to help, and there will be folk like me using this who aren’t the best at coding or even have an idea what to look for at times and I figure that’s a different perspective to keep an eye on.

    Anyway, thanks for the help with this.

  41. Grog

    Where can I find the 4.4.2 nvidia sxz package? Or better yet, how do I make an sxz package like the ones you have on the site?

  42. alienbob

    Read the end of if you want to know how I create that nvidia squashfs module.

  43. Grog

    Well, here’s what’s happened since my last post…

    I re-downloaded the ‘current’ liveslak from ‘latest’ (I even reloaded the page to make sure I was getting the actual latest from 0.6.0 current).

    I re-did the install to my usb stick using I also again did a luks system on it. I then copied the 4.3.3 nvidia from your link to the ‘addons’ so that when I booted to the usb stick it would automatically load.

    Once I booted to the stick, it all went as it was supposed to, I also changed livepwd and rootpwd, even attempting to load the nvidia module, yet again it halted at a forever blinking cursor (I found that I need the 4.3.2 Nvidia module for this ‘latest’ current off all the locations hosting all the latest live iso’s, not the 4.3.3). 🙁

    So, I rebooted to my hdd system and deleted the nvidia module from the usb stick and rebooted to the stick and all went well. But, here’s what happened next…

    The first thing I do is make my most common ‘changes’ to the system to suit my preferences and tastes and likes. I change the menu launcher to ‘classic’ and go from there:

    I open ‘system settings’ and make these changes simply going in the order of everything in that window. …

    App. Appearance: Style to ‘Plastique’
    Colors to ‘Desert’
    All fonts to ‘Deja vu sans ‘book, 10”

    Launch feedback: No cursor bounce or anything, taskbar notification to 15 seconds from 30 seconds

    Locale: Calendar-Special Religious Observation(s) to ‘none
    Time – to ’24 hour’
    Short date – to DD SHORTMONTH YY

    Desktop: Uncheck ‘Enable effects at startup’
    Uncheck ‘Various animations’

    Workspace appearance: Window decoration to ‘Keramik’
    Cursor to ‘Oxygen blue’
    Desktop theme to ‘Produkt’

    Display monitor: Change gamma to ‘.85’ from 1.00

    Input devices: Mouse – Pointer acceleration to ‘4.2’

    Multimedia: Hardware settings – set to use my only card an SB Live!
    Adjust sound and Video – to SB Live! 5.1, analog surround preferred in all categories

    Panel: Remove/hide the ‘HP’ icon
    Remove quicklaunch ‘Firefox’ and ‘activities’ icons
    Add widget ‘Lock/Logout’
    Adjust clock settings to ‘Bold’ font and ‘custom font color (white)’
    Calendar to use ‘Israel and US America ‘information’ from holidays

    This particular time I forgot to make ‘user’ a part of ‘shutdown’, but the shutdown button worked sort of this time as it allowed me to *only* shutdown the computer, no reboot or anything else.

    Anyway, when I rebooted to the stick, I got to the ‘live’ window where I enter my password and all it does is blink once then bring me right back to the same window where I enter my ‘live’ password. It will do this as long as I have the patience to keep entering my password.

    It *does* still have the choices of desktops to try/use (none being chosen made any difference btw), and also console login – which I know nothing to do with on this particular setup with a live usb stick. All I can do is reboot to my regular hdd system and wonder what went wrong.

    As far as I can figure nothing I ‘changed’ to suit me should have made anything go haywire, but this is the second time in a row I’ve done this in the same exact way and it not let me to my desktop.

  44. Grog

    I also forgot to mention that before I ever booted to the usb stick and made all those changes in my last post, I had put the nvidia module int eh ‘addons’ directory and of course when I did boot to the usb stick it *tried* to install it. I have a feeling that something is being leftover and is messing with the system by leaving small portions of who-knows-what instead of simply not installing anything at all from that nvidia module (I hope that makes sense to someone).

  45. Phil

    Had similar problem on my laptop. Try checking the ownership of your ~/.Xauthority file. Now and again mine would change to root. If you boot to runlevel 3 and then delete the file you should be then able to boot to Plasma 5.

    On further investigation the ownership was changed when I su’ed to root from a terminal emulator. From then on was unable to start any program unless I reset the proper ownership with chown. My problem turned out to be in the root .bashrc file. There was a line
    xauth merge ~/.Xauthority
    which was causing the problem. Commenting it out did the trick. Don’t know if this is the same problem as you but by deleting the ~/.Xauthority file you should be able to get back in.

  46. Grog

    @Phil – Thanks for the advice. Unfortunately that didn’t help anything on the stick liveslak. I booted up to the loging screen and then dropped to console login and then to root in that and opened mc (gotta love mc!) and found that file and commented it out. Still didn’t work. I even deleted the file and no go. I even found an nvidia ‘egl’ something or other and deleted that as I couldn’t install the nvidia anyway and that looked to be something that stuck in the system even though it shouldn’t have since it was for the wrong kernel. That didn’t help either. bleh, heh heh.

    Oh well, that’s the good thing about this ‘live’ stuff and a fast usb stick – I can just start again and try something else and see what happens and maybe help pinpoint what or where things are going wrong. I’m going to try this time to make all those same exact ‘changes’ but *without* trying to install the nvidia module in any way.

  47. ahz

    Hi Eric,

    I build a bunch of modules and copied them to the addons folder. All modules work as expected. But it seems that for some reasons I can not add more than something around 48 modules. If I add more the boot process will not finish (X does not start) and I am dropped to a shell with some error messages (varying content). After this occurs I must do a Ctrl-Alt-Del to reset. I reproduced this behaviour on different machines and different mixtures of my own modules. I use the Plasma 5 edition with bootparameters nop luksvol= .

  48. alienbob

    Hi ahz

    That happens probably because I did not expect people to add this amount of add-on modules to be honest. If you are all about modules then you might want to reconsider if liveslak is the best solution for you – modules can not be added on the fly like SLAX or Porteus does it.

    However the fix should be easy.
    In the init script (called ‘liveinit’ in the source tree) there is a hard-coded limit on loop devices that are created in order to mount modules:
    # We exhausted the available loop devices, so create the block device:
    for NOD in $(seq 0 64); do
    if [ ! -b /dev/loop${NOD} ]; then
    mknod -m660 /dev/loop${NOD} b 7 ${NOD}
    You can increase the number to something larger than 64 and that will allow a larger total of modules to be mounted in the Live OS.

    I am going to increase the default of 64 and will also add a boot parameter “maxloops=” to change that default at boot time.

    Update: Done –

  49. ahz

    Thanks for the fast fix Eric! You are right about Porteus. But the problem is, that I have a brand new Skylake CPU and Porteus isn’t able to boot on this machine (even with the alternative kernel you can get as an update). At the moment liveslak is the best choice for me and because it is very similar to Porteus this is a very good alternative.

  50. Michael

    Hey, this is a very cool thing you do here, thank you alienbob 🙂

    I currently play around with it on an older box that got replaced recently because it had some sporadic problems, which means some stress testing etc 🙂

    I noticed to compile a linux kernel I had to install 2 missing packages:

    Maybe it would be good to have those 2 included, so it can compile out of the box.

  51. twotonman

    Hi alienbob,

    many thanks for Slackware live! Version 1.0 will be
    fantastic. However there are still some unresolved
    things. Here are my results from
    slackware64-live-plasma5-current.iso (0.6.1, 13.03.2016):

    I have shortened the output from ldd to show only
    the missing parts. Sorry, I don’t know how I can find
    out which packages are missing.

    /usr/bin/akonadi_indexing_agent => not found => not found

    /usr/lib64/kde4/ => not found

    /usr/lib64/kde4/ => not found

    /usr/lib64/kde4/ => not found

    /usr/lib64/kde4/ => not found

    /usr/lib64/kde4/ => not found

    /usr/lib64/kde4/ => not found

    /usr/lib64/calibre/calibre/plugins/ => not found

    /usr/lib64/nautilus/extensions-2.0/ => not found

  52. alienbob

    twotonman, Slackware Live Edition is the product of my ‘liveslak’ scripts, and those scripts are not at fault here.
    You are looking at one of the scripts’ output products (a Live ISO image) and the content of those ISOs is based on several package repositories. The one you inspected is the Plasma 5 variant. It comes with a lot of packages that build on top of Slackware-current, replacing several stock Slackware packages. The result is that some of the other stock Slackware packages will experience library linking issues – however in many cases you won’t touch upon a situation where you will be affected by that.

    You must realize that Plasma 5 for Slackware-current is a testing ground on top of a testing ground (albeit slackware-current at this moment in time is quite stable) and if Slackware programs break as a result of using Plasma 5, then I may or may not fix that, depending on the free time I have. Compiling costs time. Time is what I lack most.

    Now, back to the linker errors you mentioned.
    Actually, one of them is an omission on my part, which I cure in the next release of liveslak: I forgot to add the ‘podofo’ package to the Plasma5 ISO image. Hence the calibre error.

    The nautilus error can not be resolved: the dropbox package is a binary re-packaging of a Fedora RPM which expects Nautilus to be present on the system for which it provides a plugin. We do not need that plugin because Dolphin in Plasma 5 (and in KDE 4 too by the way) has its own dropbox support extension.

    The akonadi error about libical has been fixed some time ago in my ‘ktown’ repository but that was after the release of liveslak-0.6.0.

    The remaining errors are all coming from Slackware’s calligra package. If you want to get rid of all these errors you will have to recompile calligra. I may, or may not, do that at some point. If you show me a situation where you run into this error and a program does not work as a result, that may give me more incentive.

  53. alienbob

    Michael if you use the Slackware ISO instead of the XFCE ISO you will not have any issues at all compiling a Linux kernel.

  54. Michael

    Ok thanks, yes I was using the XFCE Iso 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

© 2024 Alien Pastures

Theme by Anders NorenUp ↑