There are several options in /etc , and I dont claim to understand it.
It seems to depend on which services you have installed.
1 Like
Of course - if you change /etc/environment - you need to either logout - or reload your profileā¦
Pretty sure .profile reads /etc/environment (and /etc/profile)ā¦ maybe as an undocumented āincludeā?
Also note : this was on server environments - but worked on all the DEB and RPM families Iāve used that onā¦
However - I donāt think you can append to existing $PATH with /etc/environment - i.e. āPATH=$PATH:/dir2:/dir2/ā doesnāt work (I think?)
Shame it canāt be more consistentā¦ Oh wellā¦
2 Likes
Will give this a try!!!
2 Likes
There is no /etc/environment in LFS but there is a .bashrc.
2 Likes
Yeah, it varies between distros. Some of mine have /etc/profile.
Do the user one, it is easier.
1 Like
There are 2 files where settings can be added or modified in each userās home directory. Theyāre dot files so you need to use ls -a to see them in the directory. Thereās a .profile file that runs when you log in and a .bashrc file. Usually, the path is set in one or the other.
2 Likes
Yes, I used the .bashrc, for my user account and bashrc for my root account.
With LFS I have to use āls -laā!!
The main problem I am having now is with the mesa install!! My old Nvidia GT430 and the libglvnd, is nowhere to be founf for LFS12.3, so I have switched to my onboard Intell HD4000, for my GPU and am rebuilding llvm in hopes of getting the dependencies needed for Mesa.
If I cannot get a Mesa compile, then I would have to use an older version of LFS!!
2 Likes
Started updating and rebuilding some of the older packages on my system. Hereās a list of what Iāve been building: https://lmemsm.dreamwidth.org/33313.html If anyone wants to compare notes, please post.
2 Likes
I had a look and I see where you are headed
āOnce I have a compiler, core utilities and basic build tools in place, I build libraries and programs in these four categories: archive, communications, graphics, audio. After that, I typically build my graphics/GUI libraries. Then I build applications that use those GUI libraries and my audio and generic cli programs. On Linux, I build X11 libraries before building GUI libraries.ā
When you go to put these components together, how do you stand on things like dbus, polkit, elogind or consolekit or turnstile, pam.
I find authentication and permissions to be a maze of barriers hampering me from doing things. Are they really necessary in a single user home PC , and can I set up a system without them ( eg like hyperbola linux)
When you get to the app stage, you are going to have to decide how apps interact, with the kernel and with other apps. I would vote for open access and interaction rather than security, but it depends on your target.
Dreamwidth is fascinating.
1 Like
I typically concentrate more on the libraries, compiler and applications I want to run and donāt delve as much into the lower level parts of Linux. I build applications for a variety of operating systems, so many of those issues just donāt exist on other operating systems. Right now, Iām investigating using the Linux kernel with Busybox. I also typically run my Linux system offline and sneakernet applications to it. So, Iām not as concerned about security. I do have an article at my site about replacements for sudo. With the new development in Rust for sudo, it turned out to be useful to find some alternatives. Iām also using Busybox, sbase, BSD and Minix programs, plus a few of my own to replace core utilities. Iām trying to keep the number of interpreters and other compilers on the system down to a minimal and mainly working with C and C++. I havenāt had any issues with the programs Iām running needing higher level permissions or authentication to date. However, I run a lot of lightweight, non-standard programs. Iām experimenting with using an older version of X11 similar to what TinyCore Linux does. Glad you enjoyed my articles on Dreamwidth.
2 Likes
Have you seen smolBSD?
Do you have an opimion on that?
I am thinking of trying a BSD from source build. ā¦ just kernel and utilities ā¦ no DE.
1 Like
Havenāt tried smolBSD. I did like some of the programs in PicoBSD a while ago, but development hasnāt been active for a long time. I recently built NetBSD on Linux and Iām running it in a virtual machine. Was thinking of trying to build the same libraries and programs on that system and see how it goes. Iāve read that NetBSD is fairly easy to build from source, plus it works with several types of CPUs and offers 32 or 64 bit choices.
1 Like
Yes, NetBSD would be one of my choices to try a build.
I think any BSD build would be simpler than linux
I am leaning towards a manual effort ( like LFS) rather than something like smolBSD.
Thanks for comments.
1 Like
To build NetBSD, I downloaded netbsd-11.0_RC1-i486-1l32.tgz, sharesrc.tgz, gnusrc.tgz syssrc.tgz I think I ran ./usr/src/build.sh -m i386 -U -O obj -T tools release Ended up with a netbsd.img file in the release directory. If you want a 64 bit system, youād need to download the appropriate files and run commands to build that. It took about 5 1/2 hours to compile. The image file seems to work well with qemu.
2 Likes
If you want to compare notes on building source on NetBSD, let me know.
2 Likes