SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Because to use the stock Slackware kernel on a XEN host anyway requires additional XEN tools which aren't included in Slackware?
And from what I know, even the Big Houses does NOT ship a XEN-enabled kernel by default - apparently, they take a pride on shipping a separate kernel for this.
So, in fact you suggests the Slackware to ship a new/separate XEN-enabled set of kernel packages? Like in kernel, kernel-modules and kernel-sources?
No, my idea is to enable it on the default kernel, it not harm if you don't use it (i don't use it, I prefer kvm, more easy, xen has only the "paravirtualization" as a "plus"), if anyone want to use Xen on Slackware can use it without have to recompile the kernel, for the xen-tools this is a good guide https://pub.nethence.com/xen/slackware
Well, looks like you can NOT compile the XEN support as modules.
As far as I know (or I remember) the XEN is a virtualization solution highly oriented to servers and you will need a kernel customized as XEN host and another kernel customized as XEN client.
The fun part is that you can NOT run a XEN client kernel as XEN host, or vice-versa. And the proprietary NVIDIA drivers will not work on any of these kernels. Neither the AMD proprietary driver and any other virtualization solution will stop working too.
Believe it or not, that's WHY they the Big Houses ships separate XEN kernels.
So, you suggest us to show the Torvald's Sign to NVIDIA in the general direction of proprietary NVIDIA blob users, along with the proprietary AMD driver users and the users of any other virtualization solution like VMware or VirtualBox?
And for gaining what? A high performance server virtualization solution which is supposed to give us a shiny 80x25 characters Linux console?
Please note that I am NOT against XEN . If our BDFL wants to add on his tab two another sets of kernel-generic, kernel-huge, kernel-modules and kernel-source for XEN's each dom0 and domU , I believe that's his call.
However, let's be realistic that's the single way to have XEN goodness on Slackware.
I never considered this problem, because I ever avoid proprietary drivers (for my "needs" nouveau or radeon are perfect).
GNU Stow is a symlink farm manager which takes distinct packages of
software and/or data located in separate directories on the
filesystem, and makes them appear to be installed in the same place.
do you have something in particular that is needing python 3.12.x, USUARIONUEVO?
My question is more like: "During the lifetime of Slackware-15.1 (i.e., before the release of the next version), will the Python version version it will ship be supported or compatible with Python-based software that I need to package?"
As a practical example: in order to be able to update the Orca screen reader to version 46.1, which I am about to ship for Slint 15.0 (based on Slackware 15.0) as it contains major enhancements and major fixes I had to install Python 3.11 alongside 3.9 and build several related Python packages based on it as build and run dependencies (alongside the versions based on Python 3.9). Not a piece of cake. I did this because otherwise I would have had to wait for the release of Slackware 15.1 which I don't know when it will be but probably several (6 or more?) months from now.
Last edited by Didier Spaier; 06-11-2024 at 03:55 PM.
Reason: wording sligthly enhanced
otherwise I would have had to wait for the release on Slackware 15.1 which I don't know when it will be but probably several (6 or more?) months from now.
Quote:
Originally Posted by volkerdi
There will be another mainline kernel after this one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
