Profile cover photo
Profile photo
Rick Troth
... try to take over the world!
... try to take over the world!

Rick's interests
View all
Rick's posts

CMS TAR includes TARLIST, which VM/CMS people will recognize as similar to FILELIST and RDRLIST.

I had been tweaking TAR and TARLIST to have URL support. Got it working yesterday (before work) and then removed the scaffolding last night (after work). It's on Github and on There's probably one other minor change before I roll the version number.

The tough part was TARLIST because it's an XEDIT macro and there are some 8-character tokens in its interface. (TAR itself could always be fed from a pipeline with 'curl' for URL operation.)

Post has attachment
I've been re-driving the core NORD build. No particular package updates, just mostly trying for platform consistency (I386, S390, PPC, SPARC, ARM). Also forcing "-static" on GCC and getting some good results, relaxed runtime depencencies.

Justification for the time and effort is always a struggle. But I'm concerned about the growing dependence on really complex supporting environments made up of pre-compiled components.

We need safer systems. Prevailing wisdom suggests that complexity corrodes safety (both reliability and security). Do we have hard science that says one way or the other?

We need serviceable systems. In the FOSS world, we believe source code is the solution. Enterprise operations eschew in-house build work. They don't want to compile stuff.

Nobody seems to notice how siloed the distributions have gotten. BASH, for example, is everywhere, but can BASH built on SUSE run on Red Hat? Debian? Not likely it would work on Alpine. Just sayin.

Post has attachment

Post has attachment
Then I heard about this from +Jon Disnard ...

Sad for those affected. Sad for the rest of us.

Does SPARC offer anything architecturally? If so, then why has it faded? Possibly proprietary poisoning paranoia?

Does Solaris offer anything w/r/t POSIX? Time was, it was the gold standard. Even now, though Linux performs really well (and Solaris got into trouble on that front), there are features of Solaris that subjectively "feel better". (For systems I depend on, I positively can't stand being locked into any single solution. How many times have we warned each other about monoculture? And yet we casually let Solaris drift into the history books.)

Not that I expect Oracle* to care about any of these ideals. "It's just business.", the excuse used for any number of evils. These things happen because someone saw an opportunity and managed to convince the board (or other directors) that it would pad the bottom line.

*I am not singling out Oracle, nor slamming them as a company, and I myself work for a tech giant.

Post has shared content
The article points out a real problem: long-term keys. But it misses two important points: volunteer/human managed trust and statistical assurance.

I'm not giving up on PGP. Quite the opposite. But true, there are pain points, and now there are remedies. Of note, provides alternate vetting of key ownership. It's statistical. Given enough "proofs" that so-and-so actually owns a particular key, you may decide that it is in fact legit. Statistical assurance is already in PGP, so it's not really new. (Just that and other tools offer different channels besides explicit signing.)

We need trust webs like the PGP WOT. It's the cathedral vs the bazaar. Let's have more "alternate vetting" like, but let's not call that giving up.

Reshared instead of appended, FYI +Bill Perrin, because comments were disabled. (Maybe I was just late to the party.)

Post has shared content
I discarded my 386 because it had gotten "too old" for use by/with a contemporary op sys. And here Alan Cox and co are making real use of even older machines. Y'all are awesome.

You don't need a COCO3 any more 8)

Xroar plus some patches to emulate the Cloud9 IDE controller running FUZIX as a 16K Cartridge that loads the rest of itself off IDE disk on boot. Needs a 64K COCO2/Dragon64 (and testing on real hardware). A bit over 2K free with a 256x192 bitmapped display, so I now need to squash in some minimal partition table support. Once I fixed the discard recovery there should be another couple of K free.

It's just about possible to do a cartridgeless port but you lose the space for partition table handling, graphical screens (so you get the nasty upper case shouty text mode) and wouldn't have enough space to run some of the bigger apps.


Post has attachment
Sad, though affirming.
I've been saying for years that my objection (w/r/t the climate debate) is to the sound-bite remedies and unreasonable mandates. And here's Roger Pielke, far from being a "climate denier", vilified by the mainstream press and thrown under the bus by those he might have helped.

It's evident that some have hi-jacked legit science for their own agenda. It's evident that not all the politically polluted pundits are on the side of the "deniers".

Post has attachment
I am again trying to describe the package management scheme now called Chicory. (Used to go by different names. This one actually has flavor.)

Here's an early draft of the overview ...

(The page is dynamic doc, so it's going to change. Feedback welcomed.)

Chicory package management seems to be hard to describe although it is incredibly easy to use.

Am curious if FreeBSD could serve as a hypervisor. I know it sports KVM now, but I'd also need LVM2 and bridged ethernet. 

security without flexibility is ... not
Wait while more posts are being loaded