Please wait...
Today I came to the realization that ever since NPTL was merged into glibc some ~20 years ago, it's no longer necessary to specify "-lpthread" when compiling a multithreaded program. I tried it and it worked fine. I looked at the library on disk and, sure enough, it's just a null library that is only there to keep build scripts from breaking.
I was about to remove "-lpthread" from my published Makefiles but then I stopped to consider, it might still be required on non-Linux systems. FreeBSD in particular looks like it has several different implementations of POSIX Threads to choose from (why?) and you have to specify "-lpthread" to make it link that one, or you can specify one of several others.
Am I correct about that? If you try to use POSIX Threads library calls on BSD and don't link a threading library, will it fail to link?
Am I correct about that? If you try to use POSIX Threads library
calls on BSD and don't link a threading library, will it fail to link?
I think it will fail, but then I have not experimented with that in a while. I still have not so old memories of forgetting to add -lpthread and have the build failin my face.
New GhostBSD release. I should try it again. Tried that long ago, dismal failure ( i forget why, but was nothing but frustration )
( its essentially a desktop centric flavor of FreeBSD, not a fork, designed to optionally hide the complexities of real FreeBSD from newbies. Or the lazy, like myself. )
Officially back from the dead:
"The Damn Small Linux team has released Release Candidate 4 (RC4) for DSL 2024! This update brings a series of improvements focused on user experience, administrative tasks, and international accessibility.
2024-05-26 10:29 from Nurb432
Officially back from the dead:
"The Damn Small Linux team has released Release Candidate 4 (RC4) for
DSL 2024! This update brings a series of improvements focused on user
experience, administrative tasks, and international accessibility.
I had heard that work on DSL had resumed a good while ago.
Nowadays I use Tiny Core Linux instead. Suffices to say that TCL was born when the current DSL developper stabbed the guy who ended up leaving and creating TCL. TCL is cool because they have some in-house projects in order to keep their system bloat free.
I think it was last year when i read about it first, but having an official release this year means its really alive and not a 'flash in the pan' rebirth.
Used to carry DSL on a CD and a usb stick in my 'harddrive toolkit bag', for recovery use in the old days. Switched to "system rescue" when DSL went away . ( the bag also had adapters for both sizes IDE, scsi, sata, later m.2 too. was used when friends got new drives, and needed to copy stuff, or toasted their install and needed help. )
Wed May 29 2024 16:58:46 EDTfrom darknetuserI had heard that work on DSL had resumed a good while ago.
2024-05-29 17:08 from Nurb432
I think it was last year when i read about it first, but having an
official release this year means its really alive and not a 'flash in
the pan' rebirth.
Used to carry DSL on a CD and a usb stick in my 'harddrive toolkit
bag', for recovery use in the old days. Switched to "system
rescue" when DSL went away . ( the bag also had adapters for both
sizes IDE, scsi, sata, later m.2 too. was used when friends got new
drives, and needed to copy stuff, or toasted their install and needed
help. )
I also have a System Rescue DVD in every one of my work locations. I don't have a toolkit bag, I just have a kit in each place I work at. I carry enough stuff on me as it is :)
That said, I never found microdistributions to be very good for resucue and repair. They don't have much stuff in them, and I much prefer to have something compact (like a CD or thumbdrive) that has a bit of everything than something that just has the basics.
What microdistributions shine for is creating custom solutions. If you need a laser-focused system you can put a Tiny Core Linux remaster togetther very quickly that will include only the stuff necessary for the job. You will be able to run your remaster in a toaster and it will be run blazing fast anyway.
System Rescue is golden because it has a very hackable boot process. You can use it as a poorman's service provisioner and everything. System Rescue can be programmed to download a script via http and execute it upon boot... with a creative ussage of a custom http application you can supply instructions to System Rescue you are booting without hyaving to interface with your recovery DVD directly. Fucking neat.
I source most of my recovery media from Linux and ADMIN magazine lol.
Not directly related. Just this weekend i tossed a couple of STart magazines, back when magazines came with a floppy taped to the front cover.
Wed May 29 2024 17:23:27 EDT from darknetuserI source most of my recovery media from Linux and ADMIN magazine lol.
|
To:
announce@FreeBSD.org |
figure in the history of BSD UNIX, a respected member of the FreeBSD
community, and the Deputy Release Engineer for the FreeBSD
Project. Mike’s contributions to the development and advancement of
BSD systems were profound and have left an indelible mark on the
Project.
Mike’s vision and dedication were instrumental in shaping the FreeBSD
we know and use today. His legacy will continue to inspire and guide
us in our future endeavors.
Our thoughts are with Mike’s family, friends, and all who knew him. He
will be greatly missed.
In lieu of flowers, the family has asked for donations to the FreeBSD
Foundation to fund future FreeBSD projects.
The FreeBSD Foundation is hosting a tribute page to share thoughts and
memories of Mike and receive donations in his memory:
https://freebsdfoundation.org/mike_karels/
While true, without Bell Labs there may not have been UNIX to fight over. I do think Berkeley played a large part in the legal trouble a lot too. Plenty of blame to go around.
That said, I do think Linux may still exist, as a pet learning project off Minix by Linus, but doubt it would have made it past pet-project stage. like a lof of projects back then. Would stand beside VSTa, or plan9 as loss to history ( tho never as good as either )
Fri Jun 21 2024 09:11:12 EDT from IGnatius T FoobarHmmph, AT&T ... without that lawsuit BSD would have become much bigger much faster and there might not have ever been a Linux (and rms would be trying to call it "GNU/BSD").
Thought id take a serous look at Devuan again. Ditch systemD perhaps.
Grab the latest desktop installer. 1/2 thru. BOOOM something about "bla bla not compatible with an unmerged /usr directory bla bla" Um its a fresh install on a brand new VM folks, using your installer.. it should 'just work'
Oh well. lost interest if its going to take troubleshooting just to install.
I installed Alping Linux just for kicks without knowing anything about it, and it's working well for me so far.
The advantage for me of going that route its its based on Debian, so its something im used to.
And im sure i could take some time to figure it out, but of something as simple as the installer fails ( which is basically the Debian one, re-branded ), is it worth the time? I'm sure there are other issues too.
Fri Jul 05 2024 18:06:57 EDT from nonservatorI installed Alping Linux just for kicks without knowing anything about it, and it's working well for me so far.
I installed Alping Linux just for kicks without knowing anything
about it, and it's working well for me so far.
As a general purpose machine? It will be interesting to hear how that works out.
I've used Alpine from time to time but it's always been as the base OS layer of a container, since it's substantially smaller than a full size OS image.
Some containers worked well that way, particularly if the container was just running a web microservice built in Python or something very common like that.
As soon as things started getting complicated I would start having build troubles and had to switch to minideb.
But then minideb became problematic too, because Bitnami was swallowed by VMware, and VMware was swallowed by Broadcom, and now you have to pay a $9,000,000,000,000,000,000 fee per container to use minideb. Ok that's not true but it's directionally accurate.
So now I use Debian Slim for containers. It strips a bunch of packages, docs, and localization files, and the bare minimal image was reduced by another 45MB. Pretty good for containers. So if you're just looking to save space, Debian Slim seems to be the way to go. If you're looking to avoid systemd however, you're still on your own :)
ya, that was a shame. At that point i turned around and never looked back.
Nice thing about them is they were more up to date and more options than turnkey. ( for lazy people like me.. its nothing you cant do on your own. but just to 'look' its nice to have that option )
Sat Jul 06 2024 12:19:16 EDT from IGnatius T FoobarBitnami was swallowed by VMware
These days i use FAI.. Its also pretty minimal, and auto install. Its not quite a headless install, but zero effort other than hitting enter to reboot, to give you a chance to pull the boot USB, but that is the only interaction. And you can add any package you want to the installer, easily. Sure you can always 'roll your own' in most distros, but this is painless.
Sat Jul 06 2024 12:19:16 EDT from IGnatius T Foobar
So now I use Debian Slim for containers. It strips a bunch of packages, docs, and localization files, and the bare minimal image was reduced by another 45MB. Pretty good for containers. So if you're just looking to save space, Debian Slim seems to be the way to go. If you're looking to avoid systemd however, you're still on your own :)
I'm actually using it as a file server to test out ZFS - only played with that once previously, and that was a few years back. As far as Alpine goes, I particularly like that it's using less than a gig of RAM with X running, yet it doesn't have that OpenBSD "stone knives and bear skins" feel.