Seriously considering torching my laptop and doing #lfs #LinuxFromScratch on bare metal again.
Seriously considering torching my laptop and doing #lfs #LinuxFromScratch on bare metal again.
A huge benefit with building your custom Linux From Scratch is that the software that has been built and tested on the latest version of LFS is _very_ recent.
Compared to my Debian stable there is a big difference. For example curl on Debian stable is version 7.88.1 and on LFS it's 8.12.1 and Emacs Debian is 28.2 compared to 30.1 on LFS.
I'll resurface a bit from LFS a few days now before diving back in again. A few thoughts I had this morning:
* I'm honestly baffled Linux works at all. There are so many systems running side by side. It's more like a brain really.
* I very much appreciate the work distro maintainers are doing. In particular the Debian devs since that's my go to distro
* A package manager simplifies matters a lot. And it's not an easy problem to solve
When GRUB later launches the kernel the path to the linux kernel image is relative to the /boot _partition_ so you must remove /boot from the path to the kernel IF you have a separate boot partition.
Once you get that right you can also pass a root=UUID=... argument to the kernel (to avoid specifying /dev/sdb2 etc), but this requires you to have initramfs running, which isn't available in LFS, so it doesn't work.
However, you CAN use root=PARTUUID=.. which is available.
2/2
My first #LFS push. 👶
#UE5 werkt met hele grote binaries. Je hele wereld, waar je uren werk aan besteed hebt met sculpten en verven en beplanten, bestaat uit binaries. Eigenlijk wil je wel versiebeheer hebben op je binaries, maar daar is git van origine niet voor bedoeld. Het kan wel met Large File Storage en de gratis #GitLab tier geeft je 10GB storage per project. Dat neemt niet weg dat #Unreal om de haverklap die ~700MB aan wereld voor je updatet, dus sporadisch pushen is dan wel het devies.
Systemd seems to be taking over more and more and there's a specific sub project within LFS to use that as the main process started by the kernel.
However, the default docs for LFS use the old school SysVinit. I think I'll go with this to start with. Maybe it's even possible to have different GRUB configurations so I can start the kernel with different inits? E.g. have the option to boot with SysVinit OR systemd.
@Linux The opposite is exactly what I loved about the #lfs #LinuxFromScratch IRC channel 25 years ago.
2 CIBC: And the pain was clearly due to #trade tensions. The largest drop in #employment came in #manufacturing (-31K) and #wholesale and #retail trade (-27K). #cdnecon #jobs #jobsdata #LFS
Nach dem anstrengenden Tag an der Schule zieh ich mir jetzt noch ne Sitcom rein.
I'm a mid-level #linux amateur.
I recently switched from a little bit of everything but mainly #debian to #ArchLinux. The great think is the possibility to be light and have the right setup.
with #pacman and #aur almost everything is there.
i do web, office, virtualization, and it want ok on day to day computer.
The small frustration is that if you want more, choose #init for example...is there a way inside linux to do #lfs?
But in fact building a day by day #os with #freebsd seems demanding.
LFS is so tricky. You *think* your big binary files are being cleverly handled so as not to bloat your local and remote drive space, but…No. Nope.
Afaict, the only use for git-lfs is to ensure that when someone *CLONES* your repo, they will get the minimum number of large files fetched.
If you are using it, look into `git lfs prune` This will actually remove a bunch of duplicates in your local .git/lfs directory and save you a tonne of space.
Read docs first!
🦇
Is anyone having trouble pushing to Codeberg?
I was getting "connection closed by remote host" errors.
Turns out my git-lfs was old, and Codeberg has some strict ssh settings.
To fix this, read: https://codeberg.org/Codeberg/Community/issues/1895#issuecomment-4057007
Short version, do this (once per repo) before pushing:
git config --local lfs.sshTransfer never
Ensure lfs version is > 3.5.x
hth
🦇
#git #lfs
I was told, a few days ago, that git lfs only saves space on my local drive but that the server (origin, i guess) grows full of file versions.
E.g i push 3d.blend, it's 10mb.
I edit it, push again, server now reports 20mb used. Then 30mb etc.
Is this the expected lfs behaviour? Can someone point me to where this is documented?
I'd much rather there be one 3d.blend file locally AND remotely. Is that even possible to do?
I don't think people realize this issue about lfs.