HI!

I have just done a full install of slackware64-live-daw-15.0 from the installer on the iso to the HD of my computer and noticed that it has a generic-5.15.117 kernel.

Upon updating slackware64-15.0-iso on another machine I noticed kernels 5.15.139 are already available and I am unsure about what to do.

Because:

https://docs.slackware.com/slackware:liveslak says:
Which seems to guarantee one should be able to use slackpkg and update the packages, but not the kernel packages of course which would be downloaded and installed in another way.

Yet !

I am unsure about it since I think I have read something about using the newer isos.

After searching without finding what I think I might have seen, I found this which may have caused my confusion:

https://download.liveslak.org/latest/says:
It does not suggest that one should use the isos instead of updating from https://slackware.nl/slackware/slack...ches/packages/.

But being guilt of all too many wrong assumptions I am asking just to be 100% sure.

Besides I have had the impression (don't know where I have got it from, too much reading) that DAW uses a kernel which is specially configured for audio and I am afraid that using the kernel from the stable repo might not be a good idea.

I tried to update slackpkg and got an error, as in attached file (slakpkg_update_output.txt). Wonder if it may be related to my question above.

To test my internet connections I downloaded files from several Slackware repos, including https://slackware.nl/alien-kde/ without problem.

Attached Files

slakpkg_update_output.txt (10.3 KB, 6 views)

I think your jumping ahead.

have you worked your way through this page? http://docs.slackware.com/slackware:beginners_guide

The question about upgrading the kernel, and using a generic kernel is probably answered there.

And the very last line of the linked page states. So have you read the change log?

1 members found this post helpful.

I would just remove 'ktown' from the /etc/slackpkg/slackpkgplus.conf file. The URL http://slackware.nl/alien-kde/15.0/latest/ does not exist, I assume Alien Bob never released any package for Slackware 15.0 after his KDE Plasma5 was added to Slackware itself.
Then your first question, on how to upgrade. When you install a Slackware Live to your hard disk using the setup2hd script, the Slackware which gets installed on that hard disk is just the regular Slackware 15.0 minus a lot of packages (DAW Live is a partial install of Slackware) which you should easily keep up to date using "slackpkg update && slackpkg upgrade-all".

1 members found this post helpful.

I loaded my iso from the harddisk (on a partition with Artix) and ran the installer. I suppose that is equivalent, for ny practical purposes, to running setup2hd. Am I right?

And as for kernel, is it OK to update the Kernel on Live DAW ? (Asking because of all the special configuring for DAWs ?)

Thanks for the advice. I had not.
Will from now on.

I am now convinced, of what I had been suspecting all along but could not establish by any rational means, namely that it would be no problem to update the kernel on Slackware-live-daw-15.0.

That based on Post #4 and on an explanation by Alien Bob on https://alien.slackbook.org/blog/daw...-slackware-15/:
(My italics in the quote above.)

I had previously found a section "Updating the kernel (and more) on a USB stick" at
https://docs.slackware.com/slackware...ing_iso_images but was unable to generalize from it in a logical way.

Marking as solved. Thanks for your support!

Hi fredmyra.

I stumbled across this post a little too late to help for the kernel issue, but there were some things in your first post that I wanted to mention since I've used the same daw software here for a few years now.

The "Slackware Live" isos that Alien Bob supplies do all come with the feature to install to the HD with the setup2hd script. However, not all Slackware Live isos are the ideal candidate for a disk install.

As Windu points out, the DAW release is a Slackware installation which has been trimmed down a less than full install, and then it adds on the DAW packages. It also adds a number of performance tweaks for running a DAW. Being less than a full install, you're likely to run into troubles if you try to run this like a full blown slackware installation. E.g. If d/ has been trimmed, you may be unable to compile and install other third party software. Really you should only use Slackware Live from the isos that have a full Slackware installation as install candidates for setup2hd, if you are looking to use a regular slackware system afterwards.

An iso like the DAW release ends up being best used as-is on the USB drive where you get the ready to use system that works anywhere, and can quickly be cleaned up and reused, thanks to the persistence being able to reset easily. This is my opinion of course, but I think the argument makes sense.

For a disk installation, I'd recommend going with a regular full Slackware install, and then adding on slackpkg+ and using the daw template file to install the full daw suite of software to the machine. See the "easy installation" section of this post: https://alien.slackbook.org/blog/exp...ic-production/

It's the same kernel afaik, it just has the 'threadirqs' boot option added to the kernel command line. Thats why updating the kernel does not matter, since it still gets booted with this option enabled with the new kernel. Enabling threadirqs, along with the other tweaks to Slackware from this post are whats used to tweak the DAW installation: https://alien.slackbook.org/blog/con...-use-as-a-daw/

That entire article is worth a good read if you want to get to know what goes into configuring the system for real time audio performance.

If you use a regular slackware installation and add on the DAW packages from the template file I mentioned earlier, then the last step is to apply those configuration tweaks to get performance for real time audio processing. I used a setup like this for making a DAW machine a while ago. Its a regular slackware install with the DAW packages added on, and those performance tweaks. However, its also a full blown slackware system so I build and install other packages and game on there too. The point is, its a more rounded base system than just installing the DAW iso to disk and using that.

Of course if you're happy with the ISO installed on disk and building it up from there, then do what works for you. I just wanted to mention some ins and outs of doing that.

Cheers

Late thanks for your kind post. VERY helpful. I first read it today. I have been experimenting with Slackware 15.0 installed from the LiveSlak version. I installed Audacity, MuseScore, QSynth and Rosegarden which I use most often. Jack too but I never got very far in using it.

I am now starting to read again on this subject, and that is how I finally came upon your post, which is exactly what I needed to read right now. I will also - carefully this time - re-read the articles by Alien Bob which you mention. I did go quickly through them, long time ago.

My plan at the moment is to use the daw template. I also plan to have persistent version on a usb stick, or if possible on a partition of an external usb disk, for eventual use in other machines. If they have sufficient resources - most of my machines are Core2 or intel-i5.

I am a confessed distrohopper and as such I get help from many different forums but I must say that I am always impressed with the attention and good will I find here.

If 0xBF was late to see this, I'm even later! But a few tips on liveslak and kernels. Firstly, updating the kernel on the live usb vs on an installed to hdd ISO is different. If you're using the liveslak usb itself as your system, you not only need to do the usual "slackpkg update && slackpkg upgrade-all" but also run the included "upslak.sh" utility to update the included boot/kernel modules on the usb. Reason being, the boot info is part of a different squashfs module and the normal Slackware package updating routine does not account for the unique filesystem, nor module-like installation. Options are given for "upslak.sh" when ran, but to successfully update a liveslak system kernel one must use this utility.

If you've locally installed with "setup2hd" then updating the kernel would follow the normal Slackware guidelines, and is a much simpler overall process to deal with. Upgrade packages and then update the bootloader.

I hope this information helps in any future liveslak installs!

2 members found this post helpful.

Thanks jloco!

That is what I call useful info for an user on my level!