LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   What features/changes would you like to see in future Slackware? (https://www.linuxquestions.org/questions/slackware-14/what-features-changes-would-you-like-to-see-in-future-slackware-605827/)

allend 05-28-2015 07:25 AM

Quote:

Edit: I should write a Wiki page for this.
You damn well should! :)
For me, the ability to PXE boot and read/write to NTFS file systems, would be extremely useful. This technique makes it possible to easily add support for NTFS file systems.
My grateful thanks for the insight!

Alien Bob 05-28-2015 08:24 AM

Quote:

Originally Posted by allend (Post 5368711)
You damn well should! :)
For me, the ability to PXE boot and read/write to NTFS file systems, would be extremely. This technique makes it possible to easily add support for NTFS file systems.
My grateful thanks for the insight!

Every Slackware ISO can act as a PXE server if you boot it and run "pxesetup" instead of "setup". Of course this will only make sense if the ISO contains the packages as well, so the DVD ISO or CDROM #1 are good candidates.
The mini ISO will happily run a PXE server but it will not be able to serve packages to PXE clients, unless the computer which booted the ISO has a local repository which you can mount in the installer.

allend 05-28-2015 09:32 AM

I am aware of the ability of the Slackware ISO to act as a PXE server, thanks to your good self.
My use case is a Slackware server, acting as a gateway between an intranet of Windows PCs and a corporate LAN. On occasion, it has been necessary to restore an image to a Windows PC on the intranet and then update the image with recently changed files.
I have been using PXE boot with a custom version of the Slackware installer with NTFS support added to do this. The intention of my previous post was to point out the broader application of the technique that you provided, as there is no need to build a custom version of the installer.

As always, my grateful thanks for all that you do for Slackware.

jostber 05-28-2015 12:22 PM

Quote:

Originally Posted by Alien Bob (Post 5368645)
You do not even have to modify the Slackware installer, only the bootable ISO. Isolinux has a little known feature that it can use multiple initramfs image files and combine them on the fly when booting the kernel.
I once created a modified Slackware mini ISO for a friend who needed an installer that additionally needed to contain ethtool and tcpdump. Instead of modifying the initrd.img file (which contains the Slackware installer), I created a second initramfs file.
I extracted the binaries and libraries from the Slackware packages for ethtool and tcpdump into a temporary directory (dumping binaries in ./sbin and libraries in ./lib64) like this:

Code:

/path/to/initrd64_14.1_addon/
+-- etc
|  +-- libnl
|      +-- classid
|      +-- pktloc
+-- lib64
|  +-- libnl-3.so -> libnl-3.so.200.16.1
|  +-- libnl-3.so.200 -> libnl-3.so.200.16.1
|  +-- libnl-3.so.200.16.1
|  +-- libnl-genl-3.so -> libnl-genl-3.so.200.16.1
|  +-- libnl-genl-3.so.200 -> libnl-genl-3.so.200.16.1
|  +-- libnl-genl-3.so.200.16.1
|  +-- libnl.a
|  +-- libnl.so -> libnl.so.1
|  +-- libnl.so.1 -> libnl.so.1.1.4
|  +-- libnl.so.1.1.4
|  +-- libpcap.a
|  +-- libpcap.so -> libpcap.so.1
|  +-- libpcap.so.1 -> libpcap.so.1.4.0
|  +-- libpcap.so.1.4.0
+-- sbin
    +-- ethtool
    +-- mii-tool
    +-- tcpdump -> tcpdump.4.4.0
    +-- tcpdump.4.4.0

I then packed that directory tree into a new initramfs file using my initramfs generator script, like this:

Code:

# cd /usr/local/bin
# wget http://www.slackware.com/~alien/tools/extract_initramfs.sh
# ln -s extract_initramfs.sh create_initramfs.sh
# create_initramfs.sh /tmp/addons.img /path/to/initrd64_14.1_addon/

Then I modified my standard mini ISO image as follows:

Loop-mount the ISO image and modify the isolinux configuration to take the addons.img into account:
Code:

#mkdir -p /mnt/iso
# mount -o loop slackware_x86_64-14.1-mini-install.iso /mnt/iso/
# mkdir ~/workdir
# cp -a /mnt/iso/* ~/workdir/
# cp -a tmp/addons.img ~/workdir/isolinux
# sed -i 's/initrd.img/&,addons.img/' ~/workdir/isolinux/isolinux.cfg

Which lets isolinux do its magic of combining two separate initramfs images into one filesystem for the kernel to boot with, thus making the addons part of the installer transparently.

Finally a new ISO needs to be created from that workdir, something like this:

Code:

# cd ~/workdir
# mkisofs -o ~/slackware-mini-install.iso \
    -R -J -V "Slackware Mini Install" \
    -hide-rr-moved -hide-joliet-trans-tbl \
    -v -d -N -no-emul-boot -boot-load-size 4 -boot-info-table \
    -b isolinux/isolinux.bin \
    -c isolinux/isolinux.boot \
    -sort isolinux/iso.sort \
    -publisher "The Slackware Linux Project - http://www.slackware.com/" \
    -A "Slackware-14.1 for x86_64 Mini Install CD - build $(date +Y%m%d)" \
    .

After which you can collect the modified ISO in your homedirectory.

If you are using PXE boot then you do not even have to create new ISO images of course, just dump the addons.img file in the pxeboot directory and update the configuration file.
h
Edit: I should write a Wiki page for this.

Thanks, this looks great. Could you give a recipe for adding and modifying to usbboot.img as well?

Alien Bob 05-28-2015 12:32 PM

Quote:

Originally Posted by jostber (Post 5368874)
Thanks, this looks great. Could you give a recipe for adding and modifying to usbboot.img as well?

I could but I won't. The above will give you enough clues. Modifying the USB installer is even easier.

j_v 05-28-2015 04:51 PM

@Alien Bob
Thanks. Nice example. A good prod for me to put the syslinux/isolinux docs back on my reading list.

Citramonum 06-05-2015 09:36 AM

Is it possible to add SDL 2.0 to Slackware? SDL 1.2 is here for long time but still no new version. 2.0 is live for almost 2 years so many games use it.

ReaperX7 06-05-2015 05:16 PM

Curious, but how about adding OpenCL and OpenMAX support to Mesa?

willysr 06-05-2015 07:51 PM

Quote:

Originally Posted by Citramonum (Post 5372574)
Is it possible to add SDL 2.0 to Slackware? SDL 1.2 is here for long time but still no new version. 2.0 is live for almost 2 years so many games use it.

If no other packages in Slackware's core packages are using SDL 2.0, then I don't think it will be included.
If others are starting to use it then perhaps it can be suggested. afaik many packages in SBo does utilize SDL 2.0

---------- Post added 06-06-15 at 07:52 ----------

Quote:

Originally Posted by ReaperX7 (Post 5372798)
Curious, but how about adding OpenCL and OpenMAX support to Mesa?

Does it require new packages?

ReaperX7 06-05-2015 08:54 PM

OpenCL is provided by libclc and OpenMAX by libomxil-bellagio. Both of which are available in my repo. These are fairly small packages though.

I also found out this, the Gallium ilo driver is the new gallium driver for Intel 965 or later GPUs. Also, does anyone know how well the mesa nine d3dx9 state tracker performs?

55020 06-06-2015 03:16 AM

Quote:

Originally Posted by ReaperX7 (Post 5372891)
OpenCL is provided by libclc

AIUI, libclc is nvidia-only?

BrZ 06-06-2015 08:48 PM

Quote:

Originally Posted by ReaperX7 (Post 5372891)
OpenCL is provided by libclc...

Perhaps you also need some** of the headers inside '/usr/include/CL'...

**(cl_ext.h, cl_gl_ext.h, cl_gl.h, cl.h, cl.hpp, cl_platform.h, opencl.h)

ReaperX7 06-06-2015 09:57 PM

libclc has it's own headers which are used by Mesa. The reference headers are completely different for developers looking to add OpenCL support to applications.

libclc is for all modern graphics adapters, not just Nvidia. They have AMD and Intel support also.

dugan 06-07-2015 10:24 AM

Any chance of getting hald back, since I hear it's still required to watched DRM'd Flash videos?

ReaperX7 06-07-2015 10:38 AM

We have hal-flash which builds the library needed. Freshplayerplugin and Adobe flashplayer should work with it.

However, building haldeamon, as described by my Slackbuild set, requires a heavily edited and/or patched glib header set to exclude the mentioned error generator. The source pull I included in my Slackworks edition contains a prepatched and updated source archive, but vanilla glib without the required edits will prevent building, plus I have not tested it against kernel 4.x yet.

Truth be told, I was considering removing it since OpenRC doesn't have a haldaemon bootscript, and it's unmaintained outside of BSD circles. I might keep it, for now though. However, eventually it will be removed or pastured.


All times are GMT -5. The time now is 09:31 PM.