Linux

Oh that, yeah I have a laptop like that too, getting Debian to use my Nvidia GPU was a headache, and even then I could never figure out how to fix the screen tearing. I remember having to point to the device ID to make it actually use it. I should have another go at it since I don't really use the laptop too much anyway.
 
I seem to get a kernel panic every time I shut down Arch from what I can see, but I don't know what's causing it. I guess it's not the biggest issue as it only actually happens when I shut down the OS.
 
Still using Arch for the moment. If I ever have to reinstall the OS and can't really be bothered, I wouldn't mind using Debian again. The only real difference is that Debian is behind when it comes to deoendancies.
 
I decided to try out Gentoo and I got it to work. It might not be LFS, but compiling everything took ages, and I'm glad it actually works.
 
Fifo said:
I’m happy you got it to work. ;)
Click to expand...
Thanks, I changed the KDE icon to a Gentoo one for the application menu, and I changed the desktop background too. :mrgreen:
Screenshot_20200406_175638.png
 
I want to bring this back again to say I'm currently using an LFS build I worked on a couple of months ago. I managed to get it to be perfectly stable, and also managed to get multilib working so it can even play games etc.

Since the only programming language I'm even somewhat familiar with is Python, I've been trying to work on making something (a package manager) for it that will update certain packages from the BLFS site without me having to do it all manually (that really would be a nightmare). I've been putting it off for a while, but I think it's about time that I get back to it since I don't want my system to be outdated and vulnerable. :mrgreen: There are certain packages though which I guess I should still stick to updating manually such as PAM, since something going wrong with the likes of those could be somewhat fatal. :P

I tested what I have done so far on packages such as libdrm and mesa, but I think the best way for me to do it would be to just make a complete list of every dependency that I have installed, then make the program go through them in order to check if they're up to date. It works by checking a text file which essentially works as a database. It says the name of the files in a list, for example "mesa=20.0.15", then if the version on the BLFS website has a higher version number, it will download, compile, and install it, then alter the file to say that it now has the current version.

I'm using bash scripts too just to make it somewhat less confusing when it comes to the installation itself for the dependencies, but I think this will be fine as long as it works and the files are in the correct directories for it to function.
 
Speaking of which: https://www.phoronix.com/scan.php?page=news_item&px=Linux-From-Scratch-10.0-Release

Anyway, I've been maintaining something similar for the past few years, but it's all written in Perl, including the myriad package-specific scripts I had to hack together for things that don't work with the usual "./configure; make; make check; make install" or "meson build; cd build; ninja; ninja test; ninja install" flows. Not to mention the hacks I even had to include in the main script, like this stack of ternary conditionals to which I added yet another layer just last night:
snip-1599073161.png
 
At the moment, I'm just reconstructing the base system over what I already have since everything went wrong. I still have a toolchain I kept a backup of, which means I only have to do chapter 6. I still have a backup of everything anyway, but it would be nice to have things up to date and working properly. Once I finish going through chapter 6 again, I'll try to compile QT and KDE again, then see if it works. The only reason I need to do all of this is because of files left behind from when I tried to install both in /usr, so they conflict with the new version of KDE I guess.
 
I'm still really into LFS, but of course things like to go wrong sometimes due to the differences between things such as glibc. :mefiant:
 
The weirdest thing that's been happening to me lately is the bitflips in the cached copy of /usr/lib64/gcc/x86_64-pc-linux-gnu/11.2.0/cc1, but I don't think that's related to LFS…
 
I haven't had a problem in some time (touch wood), other than some of my scripts being a little outdated for some things making them fail, since the method for compiling them seems to change sometimes.
 
A Very long time i haven't use linux. For those i am looking oldest distro linux in the past years. I tried Vine Linux 2.5 in VMware, the most oldest GNOME Desktop Environment.

However, i downloaded Ubuntu Daily Build some reason. though likely it's still Development branch. I uploaded it on Internet Archive.
 
I still don't know what environment is best to use. I still use KDE at the moment, but I'd be open to trying out other ones just to change things up a bit. KDE just happens to work well, so < has always used it. < would have to compile a lot of things just to try another environment though, such as GNOME.

EDIT: Oops, this isn't the you game. :lol:
 
You must log in or register to reply here.
Back
Top