This profile is from a federated server and may be incomplete. Browse more on the original instance.

Debian Resumes Merged /usr Transition By Repealing Moratorium (www.phoronix.com)

Debian 12 had aimed to have a merged “/usr” file-system layout similar to other Linux distributions, but The Debian Technical Committee earlier this year decided to impose a merged-/usr file movement moratorium. But now with Debian 12 having been out for a few months, that moratorium has been repealed....

PAPPP,

The argument was that if you put all your static resources in /usr, you can mount it RO (for integrity, or to use a ROM on something embeddedish) or from a shared volume (it’s not uncommon to NFS mount a common /usr for a pool of managed similar machines).

…that said, many of the same people who made that argument are also the ones that went with making it so systemd won’t boot without /usr populated anymore, so that feature is now less useful because it has to be something your initramfs/initcpio/whatever preboot environment mounts rather than mounted by the normal fstab/mount behavior, and the initcpio/initramfs/dracut schemes for doing that all (1) require a redundant set of tools and network configs in the preboot (2) are different and (3) are brittle in annoying ways.

It still works OK if you’re using a management tool like Warewulf to manage configs and generate all the relevant filesystems and such, but it’s a lot more fucking around than a line in fstab to mount usr once the real system is up like the old days.

PAPPP,

Systemd-boot didn’t start as part of systemd, it used to be gummiboot (joke in German, it’s what those little rubber inflatible boats are called).

Systemd absorbed and integrated it in 2015.

It did start at RedHat with Kay Sievers and Harald Hoyer, which makes it unsurprising it was absorbed.

I’ve been transitioning to it as my default choice, I’ve never liked grub2, so I defaulted to syslinux for a long time, but lately systemd-boot is even less of a hassle.

PAPPP,

The near instant heat up is a big part of how I ended up with my Bambino with its “Thermojet”(Thermoblock coil thing) heater.

3s from wake to ready, it takes longer to grind and prep than to heat. I usually pull a blank shot through the clean portafilter into the cup I’m going to pull the shot in so the downstream parts aren’t crashing the temperature, but that’s still seconds.

Ascaso and Decent have more up-market offerings with thermoblock heaters that are similarly fast but offer more control. I wasn’t 5-10x price compelled for my needs, and I’m certainly not over 100x price in to that thing… But it is a great feature that the commercial derived machines don’t do.

PAPPP,

I’ve definitely had (good) blends were the components were taken to significantly different roast levels.

AFIK generally the components in blends are roasted separately for added control. Different beans behave differently in roasting so coffee that is blended then roasted will generally not be consistent anyway.

The separation lets a roaster take components to different levels to compliment each, eg. Roast a component with really good body but harsh flavor relatively dark to reduce the perceived bitterness, or keep a component you’re adding for fruity flavors or acidity light so you don’t suppress it’s desirable properties.

The former (harsh but big-bodied) thing is a common trick for Espresso in particular, a lot of really big-bodied beans tend to taste harsh, and that can be reduced with darker roasts without killing thr body. Robusta/Canephora (rather than Arabica) beans especially tend to be big bodied and highly caffeinated and hardy to grow…and have a major burning rubber note to their flavor. Good espresso blends often add some to improve mouth feel…but also cheap coffee products tend to use it, most instant or coffee flavoring starts as Robusta.

Single origin doesn’t automatically mean good coffee, but roasters who bother to source and label a single origin (which can sometimes be as specific as a farm, or broad as a country) will tend to be more mindful of that particular beans’ flavor. Also, smaller fancier roasters will generally sell fresher coffee. Beans that have been sitting roasted in a grocery chain’s “nonperishable” supply chain for months will essentially always be stale, and as soon as you get a taste for coffees that aren’t, you are cursed with that knowledge.

Single origins (and “weird” drying processes other than fully washed) will also tend to have way more character than “just coffee” which is fun and interesting but not always desirable. You can build really delicious (and consistent) coffee with blends in ways that might not be achieveable with a single bean.

PAPPP,

The 2.5 development only tree had a ton of behind the scenes big long projects that weren’t visible to users until the stable 2.6 dropped and everything suddenly changed.

Like a complete redesign of the scheduling code especially but not exclusively for multiprocessor systems, swapping much of the networking stack, and the change from devfs to udev.

If you hold udev up next to devd and devpubd that solve similar problems on the BSDs, it’s a clear leap into “Linux will do bespoke binary interfaces, and DSLs for configuration and policy, and similar traditionally un-UNIX-y things that trade accepting complex state and additional abstractions to make things faster and less brittle to misconfiguration” which is the path that the typical Linux pluming has continued down with eg. Systemd.

A lot of modern Kernel development flow is about never having that kind of divergence and sudden epoch change again.

PAPPP,

The CB3-431 is device name EDGAR. You’d most likely pull the write protect screws and flash a UEFI payload into the firmware, probably using Mr. Chromebox’s tooling and payloads. Most modern Chromebooks boot Coreboot with a depthcharge payload, and it can either be coerced to boot something different with a lot of effort, or easily swapped with a Tianocore UEFI payload to make it behave like a normal PC. Once flashed, it’s an ordinary Braswell generation PC with 4GB of RAM and 32GB of storage.

The S330 is an ARM machine built on a Mediatech MT8173C. Installing normal Linux on ARM Chromebooks is substantially less well-established, but often possible. It looks like those are doable but you won’t get graphics acceleration, and the bootloader situation is a little klutzy.

Of the two, the CB3-431will be easier and better documented to bend to your will.

The major limitation with Chromebooks is really just that there isn’t much onboard storage, so you’ll want to pick reasonably light software (A distro where you pick packages on a small base install or at least a lighter spin will be preferable) and avoid storage-intensive distros (eg. Nix or the immutable-core-plus-containers schemes whose packaging models have substantial storage overhead are probably unsuitable). You may have a little hassle with sound because many Chromebooks have a goofy half-soc-half-external-codec sound layout for which the Linux tooling is still improving - a pair of annoying PipeWire and Kernel bugs that sometimes cause them to come up wrong and spew log messages got fixed last week but aren’t in a release yet.

They aren’t fancy machines, but hacked used Chromebooks make great beaters.

PAPPP,

Suggestion: the Search key under your left pinkie emits SuperL (aka. Meta, same as a Windows key), and it is an great way to make up for some other keyboard weirdness Chromebooks have, and map to WM controls.

I recently discovered keyd, an excellent system-wide key remapper that works as a tiny daemon that intercepts input events and re-emits them as a virtual keyboard, and have it mapping Search+Arrows to PgUp/PgDn/Home/End (like a lot of laptops do with Fn+Arrows, or ChromeOS does with Ctrl+Shift+Arrows). I’ve already run into a couple other folks doing the same because it’s such a clean solution to the Chromebook keyboard.

AFIK GalliumOS has been unmaintained for over a year, and most of the patches they used to add are now in mainline, so long term you may want to consider a different distro - it’s probably OK for a while still though.

PAPPP, (edited )

Relevant place to ask: I’ve been trying to find a reference for the earliest Emacs that could host a terminal emulator or subshell in a window.

Multics emacs appears to have had both split windows and a character-at-a-time input and output mode as far back as 1978 for use as a SUPDUP and/or TELNET client, which is currently the earliest I’m aware of. Ancient ITS TECO EMACS had splits pretty early on, and may have sprung the necessary character plumbing earlier - but I’ve never found any reference material to confirm/deny.

It’s a fringe to a larger interest, which is that I’ve been trying to document the history of terminal multiplexers, especially in the Window (1986)-Screen(1987)-Tmux(2007) tradition (as opposed to the historical meaning which we’d call terminal servers). I’m slowly becoming convinced they came about after the advent of floating window GUIs hosting multiple terminal emulators. If you were super connected and could get access to one, sometime fairly early in the window between the 1973 introduction of the Alto and the surviving 1979 manuals the Alto program “Chat” could run multiple telnet sessions in floating windows (I’m also looking for a more precise date for when Bob Sproull made Chat able to do that trick). Several other early graphical systems like Blit terminals (1982 inside Bell, commercial as the 5620 in 1984) and early Sun Windowing System of early SunOS (1983) could also do multiple floating terminal emulators, so they were common by the early 80s.

Because the 36-bit DEC lineage had pretty robust psuedoterminals all the way back into the mid 1960s ref, a lot of hackers did a lot of fun shit on PDP-10s with ITS and TENEX and WAITS, and Stanford and MIT had PDP-10s connected to fancy video terminals by the mid 70s, it’s IMO the most likely place for the first terminal multiplexers to emerge… if I could just find some documentation or dated code or accounts.

PAPPP,

Forking Linux would involve taking on a huge maintenance burden, so everyone just uses it, though often basing on an older version and/or with some custom patches. That is typically how healthy open source stuff works.

Companies DO put brand names on systems built on top of Linux (or a BSD) all the time though, often ones that don’t make it obvious that’s what it is. ChromeOS and Android are both Linux based, but Android doesn’t ship most of the UNIX-y parts that are typically layered on top, and instead uses their own (also largely open source) components. ChromeOS is actually a fairly close relative of Gentoo with a few custom pieces.

Google has their own internal project for a kernel called Fuchsia, and it’s really interesting modern OS development that they’ve assembled a bunch of experts to work on… But it’s increasingly unclear if they plan to deploy it on customer facing products.

A ton of appliance type devices are basically very tiny custom Linux systems, often assembled with tools like Yocto. A lot if the vendors who sell components to go into said devices contribute code and/or money to Linux and Yocto, in order to make their products more attractive to device builders and avoid having to make and maintain their own tooling.

Most consumer routers are basically Linux (usually with a minimal userland like BusyBox), often essentially shitty old customized versions of OpenWRT. Sony alpha cameras? Customized Linux. Off on the BSD side, CellOS and OrbisOS that the PS3 and PS4 run, respectively are modified FreeBSD. Open Source OSes and tooling are everywhere because making, maintaining, and building tooling and developer support for an OS that runs on especially relatively large modern computers is a big, hard project, so very few entities try to do it themselves.

PAPPP,

I’ll give them a little credit: OS X is not quite built on a verbatim copy, it’s cobbled from a few open source and licensed parts, and a not-insignificant amount of in-house development some of which is contributed back upstream.

NextStep started out as more or less the 4.3BSD userland hosted on the Mach 2.5 kernel instead of the monolithic traditional Unix style kernel the BSDs are built on, with a DisplayPostScript based UI (large parts licensed from Adobe) layered on top.

After Apple bought Next (or Next bought Apple with Apple’s money, because Apple’s management at the time was staggeringly dysfunctional and almost all the management after the dust settled ended up being Next people), they made major changes. NextStep/OpenStep tended to perform not-that-well because of additional overhead passing things in and out of the microkernel, a problem many microkernel based Unix-likes had, so they updated to the OSFMK 7.3 Mach variant, the BSD code to versions from FreeBSD, then hybridized it by pushing some pieces that traditional Microkernels ran in user space into kernel space for performance reasons, resulting in the XNU kernel that essentially every modern Apple product runs.

They also completely replaced the GUI layer with something custom and proprietary - the original plan for what became OS X was to use the Display Post Script system + a hosted classic environment, but 1. Many third party developers revolted against needing to make a ground-up new port of their software in a totally different environment and 2. the Adobe licensing costs were higher than the price of a normal PC, which was kind of OK for Next competing in the workstation market, but not OK for Apple selling consumer machines.

Apple publishes the open-source parts including most of the kernel (lately an increasing portion of drivers and platform support stuff are distributed as object files not under the open license) on a regular basis, formerly under the name “Darwin” which could be built as a pretty typical BSD-like OS, but in a way that’s sufficiently community hostile to prevent anyone from really building successful derivative projects or contributing back to it. I think the most recent attempt was called “PureDarwin” and last I checked they’ve been stalled for about 2 years.

The engineer in charge of kernel stuff for the NeXTStep/OpenStep/Rhapsody/OS X family from inception in the late 80s to 2006 was Avie Tevanian, one of the original developers of Mach.

One who does use a lot of FreeBSD parts where it’s not entirely clear how much they contribute back is Sony. The CellOS and OrbisOS that the PS3 and PS4 used are close relatives of FreeBSD, and it’s possible they hid their contributions via contractors or consultants to not expose internal plans…or they just leeched, it’s not really clear.

PAPPP,

Most of my machines are KDE on X, but I have one where I’ve been feeling stuff out in Wayland-land. The most appealing thing I’ve tried has been Hyprland with Waybar. It’s a little bit of a kit in traditional WM fashion, but easy to configure from straightforward config files, fairly light, and not “Just like this X WM, but broken because of missing Wayland functionality” (I know, I know, it’s not technically Wayland deficiencies, its “not yet complete extensions”, because it’s all extensions, the Wayland protocol itself does almost nothing).

I’ve been using Kitty for a terminal emulator and it’s pleasing as well.

I haven’t found a launcher I love, I have fuzzel right now and the only major issue is it doesn’t currently support mouse interaction, and I prefer a “use whichever input device your hand is on at the time” to keyboard-only.

PAPPP,

They’re both simple text formats, but Hyprland uses a “key = value” type config with section labels. Sway is largely compatible with i3 config files which are more like an unstructured script.

PAPPP,

Originally it was a governance structure thing.

Now, Rocky is aiming to hold RHEL bug for bug compatibility, and Alma is giving up on that and situating to ABI but not bug for bug compatible.

This Weeks' Candidate(s) (lemmy.sdf.org)

I’ve been touring local (to Lexington, KY) roasters’ espresso blends for the last couple months - a bag lasts me a week or two and we have a whole slate of small roasters so it’s a slow process. I’m consciously working on my shot tuning and palate as I go, bringing each espresso blend to a roughly 16:34g/ 5s preeinfusion...

PAPPP, (edited )

Most Chromebook’s firmware is Coreboot, but it’s running a Depthcharge payload instead of UEFI (or BIOS or whatever). Mr. Chromebox maintains UEFI Coreboot payloads and install tools for a wide variety of (x86) Chromebooks, which can be used to flash a normal UEFI payload and boot normal OSes. It’s strictly possible to boot normal Linux systems on a the Depthcharge payload modern Chromebooks use, but uh… here’s the gentoo wiki on it, it’s a substantial pain in the ass.

PAPPP,

Sure, drop me a note with the details and I’ll see if I can give you a hand. I’m not super expert in all the specifics of the Chromebook ecosystem, but I have good general computer/Unix skills and have hacked a couple so I know where to look for resources.

PAPPP,

I really enjoy the ritual of espresso as a little morning meditation.
Here’s the current station, and the current process goes:

Turn on Bambino, load portafilter with empty “double” single wall basket into machine.

Place a small glass on the scale, turn on, spoon in 16g of whatever coffee I have that week.

Start an empty single auto-shot into the glass I’m going to brew into to heat everything up.

Dump measured beans into SK40 grinder which will typically be about “6” on its scale for good fresh coffee, or 5 for not quite so fresh coffee, and start it.

Remove, drain, and wipe portafilter, set it in the little 3D printed base I ran off to hold it level (not my design). Drop the dosing ring on. Set glass of usually dirty with fines hot water aside.

Pump the grinder bellows 3 times when it sounds empty, then turn off.

Dump grounds into basket, massage briefly with a cheap little WDT tool and tamp.

Dump glass into a waste cup I keep on hand for the purpose, wipe, and place on scale. Place scale on drip tray, and re-tare.

If I’ve dialed the coffee: Hold single button for ~5s of preeinfusion, release, and tap again aiming for a ~32g shot.

If I’m still working on the coffee: Get out my phone, hold single button, start timer on phone when the preeinfusion pump kicks in, tap lap and release button at ~5s, watch timer and scale aiming for vicinity of 32g/30s. Grunt and adjust the grinder in the appropriate direction if it’s not close.

Stir espresso, taste, add a little milk while I make my breakfast food if needed.

Consume espresso and breakfast.

Come back to to put away the glass, dump the puck (no 3-way valve, it’ll sneeze at you if you don’t wait a second), and rinse the portafilter. Place it upside down on the base to dry.

The setup is a recent upgrade so I’m still pretty pleased and working on refining my technique. I’ve been trying different beans (mostly espresso blends from local roasters, but also some weird stuff just for fun).

PAPPP,

Now days they’re almost all flavored coconut oil.

Which, as someone who is rather allergic to coconut, is annoying, because I have to assume I’ll have an issue with any not-actually-milk coffee cream product.

Land O Lakes Mini Moos are shelf-stable actual milk products and I keep some in my desk. Essentially all the rest of the shelf stable products, liquid or powder, have converted to coconut based. I don’t know if the economics have changed, or if it’s because they don’t have to say “Hydrogenated” if its hydrogenated right from the plant.

PAPPP,

I’m making at least a partial tour of my local roasters’ espresso blends to exercise my recently upgraded home espresso setup (I’m tipping my location here, but have decided that’s fine for this account). I live in a sufficiently hipstery city that it’s going to take months to work all the way through at my rate of consumption, we’ve got at least 8-10 roasters in the area now, and …most… of them aren’t known to be wildly distasteful businesses.

First two candidates:

An 8oz bag of 4th Level Roasters’ Espresso Blend. Not terrible, but $18/lb, darker than I prefer, and “robusta forward” in that great body but unfortunate tire-fire flavor sort of way, so I don’t think I’ll get it again.

A pound of Nate’s Coffee’s Nate’s Espresso Blend which is $15/lb, and delicious. I’ve been meaning to visit their brick-and-mortar for a while, it’s in easy biking distance, and they have a lovely “Free local shipping OR $2 drink credit if purchased in their brick-and-mortar” deal on pound bags, so I rolled myself down one afternoon to pick up the beans and a cup of coldbrew made with their After Midnight Dark Roast, which was delicious enough that I might interrupt my plan and grab bag of that soon for some hottest-months coldbrew.

Barring that diversion, I think next is Magic Beans, a lot of folks seem to be in to them and their espresso blend isn’t super dark, which I usually prefer. garagebeand’s EspressYoSelf is also on my list.

PAPPP,

My use case is mostly espresso with an occasional crank out to coldbrew, which is a bit different than “filter,” but I’ll say I’m very pleased with the Turin SK40 I picked up a few weeks ago so far. I was also eyeballing the Baratza Encore ESP and Fellow Opus in the same general price/performance class, and decided to take a gamble on a fancy option from a smaller “manufacturer”.

I quote because, as far as I can tell, it’s an ODM customized Guangzhou Itop IT-CG100B variant, but none of the other dealers seem to have a version with the step-less adjust worm, side switch, apparently the burrs vary, etc.

The workflow is lovely, retention is nearly nonexistent, noise is not obnoxious, adjustment is easy and precise, etc. Longevity, obviously, remains to be seen.

PAPPP,

Many manufacturers have been moving to cardboard. Less wasteful than plastic spools, more convenient than reusable spools.

PAPPP,

For the most part, I’d rather have native packages. I’m not deeply philosophically opposed to secondary packaging systems, and only mildly opposed to “ship the whole dependency tree in an archive” software distribution methods (lookin’ at you NextStep/OS X style bundles), and see their potential especially on platforms with no/bad native package managers or to bring in specific software that would pose a compatibility problem for the host system… but they never seem to work nearly as well as native packages, and the two big players on Linux have problems.

As far as I’m concerned, they’re just taking the old last-ditch practice of “I have this piece of recalcitrant software that is incompatible with the rest of my system, so I’ll throw it in /opt with its entire dependency tree,” replacing opt with a bunch of bind mounts, and doing so with varying degrees of additional tooling.

The sandboxing is a nice idea, but it seems like in practice the models on both snap and flatpack are simultaneously restrictive in ways that make them annoying-to-unusable for many tasks, and too sloppy to provide reliable security guarantees.

They make debugging problems harder because you can’t check functionality from another program because they likely don’t share libs. ldd is a lot easier than spelunking around with eg. flatpak list --app --columns=application,runtime until you find a “peer” to test.

If I need a one-off piece of software that is a compatibility nuisance on my host distro (but not so much of a nuisance it needs to go in a container or VM, which is a pretty narrow window), I’ll usually reach for an AppImage because unlike the other two, they’re actually fairly standalone and don’t involve a big invasive runtime/tooling system.

The Immutable-core OSes that depend on them are kind of the same way at the moment. Fundamentally a pretty neat idea, but so far I find them super frustrating in practice. Nix is …different… to work with, but is likely a more elegant scheme to solve the same class of problems.

PAPPP,

I’ve never been much of a poster (not even 2 posts/yr for the almost dozen years I’ve had a reddit habit), but I was a regular commenter in various specific-interest subs.

I am, as a rule, no longer contributing content to Reddit, since they’ve made it clear they plan to finish their transition from “hosting communities” to “extracting value from users.” Frankly, it’s not as much of an imposition as I feared, because many of those communities seem to be broadly taking the same attitude.

I’m actively trying to comment heavily here to to try to help establish communities. If I had a little more free time I’d do some posting and/or try to help spin some successor communities for my interests.

PAPPP,

My usual suggestion: Get a generation-old business or workstation class machine from one of the major manufacturers, as a refurb. Mostly meaning keep an eye on Dell Refurbished or Lenovo Outlet - sometimes you can also get a deal on a refurb via woot - for something that appeals to you. The stock is always changing at those, and there are almost always sales/coupons for around 40% off at the first-party refurb stores, so +/- a week of patience can save you a bunch of money.

Business or workstation class machines (think Dell Latitude or Precision, especially the ones with models that start with a 7, or Thinkpad) are typically mechanically much better built than their consumer counterparts, and usually full of reputable components that are connected in standard ways - low end consumer stuff sometimes has issues where they got weird less-common components or connected things in stupid ways to save a few cents per unit that will cause driver issues.

Waiting a generation gives time for mainline kernel driver support to fully mature to minimize driver problems, and drastically cuts the price.

I’ve had several machines following that advice, and I think the only driver trouble I’ve had with them has been with unsupported fingerprint/smartcard readers, which I …don’t care about anyway.

Or, if you want a way cheap beater and don’t mind some hackin’, grab a used/refurbished AUE Chromebook that is on the Mr. Chromebox Supported List. AUE means they no longer receive ChromeOS updates, so their price craters to like $50, and you can flash a normal UEFI payload and use them as a (feeble, storage starved, low resolution) computer. Not a good main machine, but they make fun beaters for experimenting. There are often batches of them being dumped via woot.

…also, don’t buy anything with an Nvidia GPU unless you have a specific compelling reason, it’ll be a pain in your ass for the life of the machine.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • uselessserver093
  • Food
  • aaaaaaacccccccce
  • test
  • CafeMeta
  • testmag
  • MUD
  • RhythmGameZone
  • RSS
  • dabs
  • KamenRider
  • TheResearchGuardian
  • KbinCafe
  • Socialism
  • oklahoma
  • SuperSentai
  • feritale
  • All magazines