libre-void - Void + Libre-Linux kernel
- Inicie sesión o regístrese para enviar comentarios
It's a compelling argument for Westend. However, Tennant was born and raised in England, and the music video was shot in East and West London. So....
You've got to admit, "In every city, in every nation
From Lake Geneva to the Finland Station" has a natural rhythm to it. Maybe he was just word-smithing the lyrics a bit?
Or maybe he wanted us to think of both the West End of London AND Westend, Espoo.
That's not quite the argument I wanted to make.
I'm talking about my impressions. I know it's about London.
I only thought mistakenly there was a place called 'Westend' (apart from Espoo Finland) somewhere in Tennant's native England, but in reality it's not a place but a vague area and written separately.
When the song first had popularity in the eighties, I thought he was singing about Western girls and Eastern Bloc boys, about some illicit relationship over the iron curtain.
Not sure about the name Westend as in Espoo. I think some wealthy people moved there and wanted to make an association with the greater affluent world out there in continental Europe or England, the British Isles, before globalism was a thing, and ended up renaming their abode 'Westend'.
>"When the song first had popularity in the eighties, I thought he was singing about Western girls and Eastern Bloc boys, about some illicit relationship over the iron curtain."
That's very possible, the music has dark and moody segments, and seems to be about something bigger than unfulfilled teenage desire.
> I thought he was singing about Western girls and Eastern Bloc boys
That does not sound far fetched at all, coming from the authors of the "Go West" cover.
I thought West End was mostly known for its permanent entertainment options, as opposed to more dormitory suburbs.
Here's my Linux-libre kernel build procedure for Void. I'm posting this here mainly so I can find it later. It should work for anyone. Leave me responses if you have questions.
References:
Arch step by step kernel "Traditional" compilation process - I used this pretty much step by step for Void: https://wiki.archlinux.org/title/Kernel/Traditional_compilation
Arch - generating a new grub.cfg after kernel installed: https://wiki.archlinux.org/title/GRUB#Generated_grub.cfg
Download the linux-libre kernel: https://linux-libre.fsfla.org/pub/linux-libre/releases/
The original instructions for building Linux-libre on opensuse from Anahuac (handy general reference, but not a guide for Void): https://www.anahuac.eu/linux-libre-on-opensuse/
#install dependencies [a very long build process will definitely fail without having pretty much all of these installed ahead of time - I know, from experience]
sudo xbps-install elfutils-devel libssl48 linux5.13-headers libelf-devel ncurses ncurses-devel base-devel make gcc xmlto kmod inetutils bc libelf git cpio perl tar xz openssl-devel pahole pahole-devel
#make a folder in the home directory for building the kernel
mkdir ~/kernelbuild
cd ~/kernelbuild
#download kernel - I'll use the version 4.19.206 as the example here
#You should also verify the correctness of the download before trusting it. First grab the signature, then use that to grab the fingerprint of the signing key, then use the fingerprint to obtain the actual signing key:
wget https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.19.206.tar.sign
gpg --list-packets linux-4.19.206.tar.sign
gpg --recv-keys
#Note the signature was generated for the tar archive (i.e. extension .tar), not the compressed .tar.xz file that you have downloaded. You need to decompress the latter without untarring it. Verify that you have xz installed, then you can proceed like so:
unxz linux-4.19.206.tar.xz
gpg --verify linux-4.19.206.tar.sign linux-4.19.206.tar
# now untar the tarball in preparation for build
tar -xvf linux-4.19.206.tar
cd linux-4.19.206/
#run the command to clean the kernel tree:
make mrproper
#Advanced configuration - this will give you a menu of options for changing your build config. If you don't understand these options, you can simply save and exit after running the command - it will make a workable config file for you
make menuconfig
#Compilation
make -j4
make modules
#AS ROOT:
make modules_install ###[MUST DO AS ROOT]
#Copy the kernel to /boot directory
#for a 32-bit (i686) kernel [AS ROOT]:
cp -v arch/x86/boot/bzImage /boot/vmlinuz-linux419
# for a 64-bit (x86_64) kernel [AS ROOT]:
cp -v arch/x86_64/boot/bzImage /boot/vmlinuz-linux419
#manually generate an initramfs file (I chose "linux419.img" as the name for mine - this naming convention is apparently good practice) [AS ROOT]:
mkinitcpio -k 4.19.206-gnu1_1 -g /boot/initramfs-linux419.img
#rebuild grub:
sudo grub-mkconfig -o /boot/grub/grub.cfg
#I had to stop the disabling of os-prober to get grub-mkconfig to probe for my other installations and add them to the boot list -
#edit /etc/default/grub and add/uncomment:
GRUB_DISABLE_OS_PROBER=false
#then run the grub-mkconfig -o /boot/grub/grub.cfg command again
sudo grub-mkconfig -o /boot/grub/grub.cfg
"Here's my Linux-libre kernel build procedure "
But yet your procedure doesn't actually build Linux-libre? What's up with that?
Please tell me what I'm doing wrong here, I would very much appreciate it. You clearly know vastly more than me about building Linux-libre, I'm just trying to stitch together a workable method on Void. Is my config file going to end up all wrong? I've been worried about that with this Arch method, but I only know enough about kernel config files to get myself into trouble.
EDIT - Never mind my question, I'm reading through the Linux-libre PKGBUILD in the AUR - looks like there's quite a bit I'm doing wrong with these steps. I'll try to work through the steps as laid out in the AUR, see if I can come up with something that works. If you know of a different how-to you could point me to, I'd appreciate it.
Found an xbps template for building Linux-libre on Void - https://github.com/ymir-linux/void-packages
Should be interesting.
You really are the Indiana Jones of fully freeing minimalist distros.
jxself might soon start calling you "Junior".
I think jxself was trying to imply that the procedure you have, downloads the kernel from kernel.org instead of linux-libre kernel. No kernels from kernel.org, Linux's site, are libre.
Ohhh! stupid me! That's just a really stupid copy-paste error in my instructions. I was copying the procedure from the Arch wiki, but when I did it myself I went to the Linux-libre releases URL. Thanks for pointing that out, I'll edit the post.
I still think my procedure is wrong, however. Even with the correct source, I'm not using the patch like the AUR PKGBUILD does, and I think my config file is still wrong. This does not seem to be the way the AUR or the Void template make their Linux-libre config file.
Thanks!
[NOTE -I'm not being allowed by the forum software to edit my earlier Linux-libre building "instructions" post, so here's a re-do with the corrected URLs for Linux-Libre. My earlier instructions copied a URL from the Arch Wiki for grabbing a vanilla Linux kernel, which is definitely NOT what we want to do. We want the Linux-libre kernel.]
[NOTE - This may still have errors - it's a work in process as I learn more about building Linux-libre on Void. Expect me to make more updates. If you try to follow these steps and they cause your computer to crash and for you to lose a million dollars worth of data and for your computer to steal your girlfriend and run off to Las Vegas with her - I take no responsibility.]
Here's my Linux-libre kernel build procedure for Void. I'm posting this here mainly so I can find it later. It should work for anyone. Leave me responses if you have questions.
References:
Arch step by step kernel "Traditional" compilation process - I used this pretty much step by step for Void: https://wiki.archlinux.org/title/Kernel/Traditional_compilation
Arch - generating a new grub.cfg after kernel installed: https://wiki.archlinux.org/title/GRUB#Generated_grub.cfg
Download the linux-libre kernel: https://linux-libre.fsfla.org/pub/linux-libre/releases/
The original instructions for building Linux-libre on opensuse from Anahuac (handy general reference, but not a guide for Void): https://www.anahuac.eu/linux-libre-on-opensuse/
#install dependencies [a very long build process will definitely fail without having pretty much all of these installed ahead of time - I know, from experience]
sudo xbps-install elfutils-devel libssl48 linux5.13-headers libelf-devel ncurses ncurses-devel base-devel make gcc xmlto kmod inetutils bc libelf git cpio perl tar xz openssl-devel pahole pahole-devel
#make a folder in the home directory for building the kernel
mkdir ~/kernelbuild
cd ~/kernelbuild
#download kernel - I'll use the version 4.19.206 as the example here
wget https://linux-libre.fsfla.org/pub/linux-libre/releases/4.19.206-gnu1/linux-libre-4.19.206-gnu1.tar.xz
#You should also verify the correctness of the download before trusting it. First grab the signature, then use that to grab the fingerprint of the signing key, then use the fingerprint to obtain the actual signing key:
wget https://linux-libre.fsfla.org/pub/linux-libre/releases/4.19.206-gnu1/linux-libre-4.19.206-gnu1.tar.xz.sign
gpg --list-packets linux-libre-4.19.206-gnu1.tar.xz.sign
gpg --recv-keys
#Note the signature was generated for the tar archive (i.e. extension .tar), not the compressed .tar.xz file that you have downloaded. You need to decompress the latter without untarring it. Verify that you have xz installed, then you can proceed like so:
unxz linux-libre-4.19.206-gnu1.tar.xz
gpg --verify linux-libre-4.19.206-gnu1.tar.xz.sign linux-libre-4.19.206-gnu1.tar
# now untar the tarball in preparation for build
tar -xvf linux-libre-4.19.206-gnu1.tar
cd linux-4.19.206/
#run the command to clean the kernel tree:
make mrproper
#Advanced configuration - this will give you a menu of options for changing your build config. If you don't understand these options, you can simply save and exit after running the command - it will make a workable config file for you
make menuconfig
#Compilation
make -j4
make modules
#AS ROOT:
make modules_install ###[MUST DO AS ROOT]
#Copy the kernel to /boot directory
#for a 32-bit (i686) kernel [AS ROOT]:
cp -v arch/x86/boot/bzImage /boot/vmlinuz-linux419
# for a 64-bit (x86_64) kernel [AS ROOT]:
cp -v arch/x86_64/boot/bzImage /boot/vmlinuz-linux419
#manually generate an initramfs file (I chose "linux419.img" as the name for mine - this naming convention is apparently good practice) [AS ROOT]:
mkinitcpio -k 4.19.206-gnu1_1 -g /boot/initramfs-linux419.img
#rebuild grub:
sudo grub-mkconfig -o /boot/grub/grub.cfg
#I had to stop the disabling of os-prober to get grub-mkconfig to probe for my other installations and add them to the boot list -
#edit /etc/default/grub and add/uncomment:
GRUB_DISABLE_OS_PROBER=false
#then run the grub-mkconfig -o /boot/grub/grub.cfg command again
sudo grub-mkconfig -o /boot/grub/grub.cfg
So I got an interesting result - built a Linux-libre 5.10.66 kernel with a highly customized config file, stripping out everything that looked unnecessary. I was able to boot into Void with only 39mb of ram in use, and log into dwm using only 70mb of ram. However, networking is completely broken beyond repair, so I clearly went to far in my config modifications.
Back to the drawing board. But, if I ever can find a use for a system without networking, this one is pretty nifty.
Hi, I don't want to open another topic about that but did you tried hyperbola GNU/Linux-libre ? Packages are old. It's use pacman and openRC. It's secure by default. It's nice.
https://www.hyperbola.info/
https://en.wikipedia.org/wiki/Hyperbola_GNU/Linux-libre
I tried to install it a couple years ago and couldn't get it to boot on my equipment. I've got a friend who is a big promoter for it, constantly bugging me to try it again.
What do you think of it? Is it fast? Minimal?
It's minimal and fast. It's really secure by default.
I'll try it. I'm not a big fan of distros that are derived from Arch, just like I'm not a big fan of distros that are derived from Debian. I think they have to jump through a lot of hoops to undo the poor design decisions of the parent distro.
Something that I'm super intrigued about with Void is that in its most basic form, you don't have any systemd, dbus, polkit, pulseaudio, NetworkManager, etc. That's pretty awesome to run a machine without the entire IBM/RedHat underbelly of modern corporate distros, and to do it naturally, without some devs having to work like crazy to undo the mistakes that the upstream distro made.
They are working on hyperbola 0.4
I installed it, it's nice and minimal - 41mb memory used at first boot.
I'm glad that it's booting for me now. I have an old 32-bit computer that I think this would be perfect for. I'd like to get dwm up and running and try out the latest Hyperbola iceweasel-uxp and icedove-uxp and iceape-uxp. I haven't used these uxp versions, and I'm very excited to see what the Hyperbola devs have done with them.
Posting this from iceweasel inside Hyperbola. It's a very fast system, comparable to Void. Setting up minimal networking and some graphics is taking much more work than with Void, but it's progressing.
Void, without systemd or dbus, with libreoffice and librewolf running. This method should work for Hyperbola as well - I'll check it out over the next couple of days.
The trick to getting rid of dbus-x11 was to put an 'ignorepkg' line in a new file - /etc/xbps.d/ignorepkg.conf
Install gtk+3, a dependency for running the Librewolf Appimage:
$ sudo xbps-install gtk+3
This will install dbus-x11 as a dependency of gtk+3, but we can "ignore" it and then remove it.
"Ignore" the dbus-x11 package:
$ sudo nano /etc/xbps.d/ignorepkg.conf
Insert the following line into this file:
ignorepkg=dbus-x11
Save and exit nano.
Remove dbus-x11:
$ sudo xbps-remove -Ro dbus-x11
Create a ~/librewolf directory:
$ mkdir ~/librewolf
$ cd ~/librewolf
Download the LibreWolf Appimage from https://gitlab.com/librewolf-community/browser/appimage/-/packages
Make the Appimage executable:
$ chmod +x LibreWolf....AppImage
Decompress the Appimage package:
$ ./LibreWolf.....AppImage --appimage-extract
This creates a squashfs-root director - go into it and run the 'AppRun' executable - this will start Librewolf:
$ cd squashfs-root/
$ ./AppRun
Make sure it works, then close it. Now link the AppRun file to "librewolf" for the whole system (must write out the full path):
$ sudo ln -sf /home/[YOUR_USER_NAME_GOES_HERE]/librewolf/squashfs-root/AppRun /usr/local/bin/librewolf
The latest Libreoffice AppImage also works without dbus this way - download the AppImage from LO Download site and follow similar steps as to Librewolf
- Inicie sesión o regístrese para enviar comentarios