I've got a Wyse 5070 thin client coming, that (when I get it) will only have
16 GBs of storage. (It does take an M.2. 2280 SSD, so it won't stay that way
for long, but I was curious what distribution I could install on the 16 GB
limit and still have some room to do things.)

Ran into BunsenLabs Linux. Very small, based on Debian 12, and a nice,
clean, well configured OpenBox desktop. So I tried it (there is a live
trial) and liked it — then decided to replace my Ubuntu server SSD, formerly
a Windows 10 SSD (since BunsenLabs Linux gives you the option to install the
LAMP stack as part of the installation process). A light desktop and Debian
server together, pretty nice.

One thing that I did run into (for the first time) was screen tearing. Now I
know what they're talking about. I guess it is a common issue in OpenBox,
but there was a fix — I ran its compositor (Picom) with the option
"--experimental backend" and that fixed it.

https://www.bunsenlabs.org/

This was originally based on CrunchBang Linux, but CrunchBang was never this
slick.

--
[Self-centered, Woke] "pride is a life of self-destructive fakery, an
entrapment to a false and self-created matrix of twisted unreality."
"It was pride that changed angels into devils..." — St. Augustine

RonB wrote this copyrighted missive and expects royalties:

> I've got a Wyse 5070 thin client coming, that (when I get it) will only have
> 16 GBs of storage. (It does take an M.2. 2280 SSD, so it won't stay that way
> for long, but I was curious what distribution I could install on the 16 GB
> limit and still have some room to do things.)
>
> Ran into BunsenLabs Linux. Very small, based on Debian 12, and a nice,
> clean, well configured OpenBox desktop. So I tried it (there is a live
> trial) and liked it — then decided to replace my Ubuntu server SSD, formerly
> a Windows 10 SSD (since BunsenLabs Linux gives you the option to install the
> LAMP stack as part of the installation process). A light desktop and Debian
> server together, pretty nice.
>
> One thing that I did run into (for the first time) was screen tearing. Now I
> know what they're talking about. I guess it is a common issue in OpenBox,
> but there was a fix — I ran its compositor (Picom) with the option
> "--experimental backend" and that fixed it.
>
> https://www.bunsenlabs.org/
>
> This was originally based on CrunchBang Linux, but CrunchBang was never this
> slick.

+1

Thanks for that information!

--
You like to form new friendships and make new acquaintances.

On 4/17/2024 9:03 AM, Chris Ahlstrom wrote:
> RonB wrote this copyrighted missive and expects royalties:
>
>> I guess it is a common issue in OpenBox,
>> but there was a fix — I ran its compositor (Picom) with the option
>> "--experimental backend" and that fixed it.

JHC. Only in GuhNoo bizarro world.

LibreOffice also puts half-baked "experimental" and "limited" code in
their production releases, labeled as such to excuse their lackadaisacal
efforts.

No doubt "Picom" is still at version 0.13 after 10 years of "development".

This! Is! Linux!

DFS <nospam@dfs.com> wrote:
>> RonB wrote this copyrighted missive and expects royalties:
>>
>>> I guess it is a common issue in OpenBox,
>>> but there was a fix — I ran its compositor (Picom) with the option
>>> "--experimental backend" and that fixed it.
>
>JHC. Only in GuhNoo bizarro world.
>
>LibreOffice also puts half-baked "experimental" and "limited" code in
>their production releases, labeled as such to excuse their lackadaisacal
>efforts.
>
>No doubt "Picom" is still at version 0.13 after 10 years of "development".
>
>This! Is! Linux!

The fix sounds exactly like something M$ did.

--
Joel W. Crump

Amendment XIV
Section 1.

[...] No state shall make or enforce any law which shall
abridge the privileges or immunities of citizens of the
United States; nor shall any state deprive any person of
life, liberty, or property, without due process of law;
nor deny to any person within its jurisdiction the equal
protection of the laws.

Dobbs rewrites this, it is invalid precedent. States are
liable for denying needed abortions, e.g. TX.

On 4/17/2024 10:58 AM, Joel wrote:
> DFS <nospam@dfs.com> wrote:
>>> RonB wrote this copyrighted missive and expects royalties:
>>>
>>>> I guess it is a common issue in OpenBox,
>>>> but there was a fix — I ran its compositor (Picom) with the option
>>>> "--experimental backend" and that fixed it.
>>
>> JHC. Only in GuhNoo bizarro world.
>>
>> LibreOffice also puts half-baked "experimental" and "limited" code in
>> their production releases, labeled as such to excuse their lackadaisacal
>> efforts.
>>
>> No doubt "Picom" is still at version 0.13 after 10 years of "development".

It's even better: it's 31 releases in 5.5 years.

Fix a bug or 3 in your part time, and make a new release. It's the
GuhNoo way.

>> This! Is! Linux!
>
>
> The fix sounds exactly like something M$ did.

Very substantive retort, with multiple examples... lamer.

Here's the chaotic FOSS hobbyist history:

1 "picom is a compositor for X, and a fork of Compton."

"Picom was forked in 2016 from the original Compton because it seemed
to have become unmaintained."

2 "Compton is a compositor for X, and a fork of xcompmgr-dana."

"I was frustrated by the low amount of standalone lightweight
compositors."

3 xcompmgr-dana (dcompmgr) is a fork of Xcompmgr
"Dana's composite manager (not for production use)"

4 "Xcompmgr is a simple compositor capable of rendering drop shadows
and, with the use of the transset utility, primitive window
transparency. Designed solely as a proof-of-concept, Xcompmgr is a
lightweight alternative to Compiz and similar composite managers."

1 https://github.com/yshui/picom
2 https://github.com/chjj/compton
3 http://git.openbox.org/?p=dana/dcompmgr.git;a=summary
4 https://wiki.archlinux.org/title/xcompmgr

Got all that?

From 'proof of concept' to 'experimental' in only 12 years.

MS is doomed.

DFS <nospam@dfs.com> wrote:
>On 4/17/2024 10:58 AM, Joel wrote:
>> DFS <nospam@dfs.com> wrote:
>>>> RonB wrote this copyrighted missive and expects royalties:
>>>>
>>>>> I guess it is a common issue in OpenBox,
>>>>> but there was a fix — I ran its compositor (Picom) with the option
>>>>> "--experimental backend" and that fixed it.
>>>
>>> JHC. Only in GuhNoo bizarro world.
>>>
>>> LibreOffice also puts half-baked "experimental" and "limited" code in
>>> their production releases, labeled as such to excuse their lackadaisacal
>>> efforts.
>>>
>>> No doubt "Picom" is still at version 0.13 after 10 years of "development".
>
>It's even better: it's 31 releases in 5.5 years.
>
>Fix a bug or 3 in your part time, and make a new release. It's the
>GuhNoo way.
>
>>> This! Is! Linux!
>>
>> The fix sounds exactly like something M$ did.
>
>Very substantive retort, with multiple examples... lamer.

It was an extreme case, but regarding a common feature.

>Here's the chaotic FOSS hobbyist history:
>
>1 "picom is a compositor for X, and a fork of Compton."
>
> "Picom was forked in 2016 from the original Compton because it seemed
> to have become unmaintained."
>
>2 "Compton is a compositor for X, and a fork of xcompmgr-dana."
>
> "I was frustrated by the low amount of standalone lightweight
> compositors."
>
>3 xcompmgr-dana (dcompmgr) is a fork of Xcompmgr
> "Dana's composite manager (not for production use)"
>
>4 "Xcompmgr is a simple compositor capable of rendering drop shadows
> and, with the use of the transset utility, primitive window
> transparency. Designed solely as a proof-of-concept, Xcompmgr is a
> lightweight alternative to Compiz and similar composite managers."
>
>
>1 https://github.com/yshui/picom
>2 https://github.com/chjj/compton
>3 http://git.openbox.org/?p=dana/dcompmgr.git;a=summary
>4 https://wiki.archlinux.org/title/xcompmgr
>
>Got all that?
>
>
> From 'proof of concept' to 'experimental' in only 12 years.
>
>MS is doomed.

The core of GNU/Linux will always be rock solid. Just as Winblows is,
which is why they could get away with their Win10 public beta test
that led me to use Linux for a real length of time in 2019, that later
influenced my decision to start using it on this machine. M$ is far
from "doomed" but Linux is very strong.

--
Joel W. Crump

Amendment XIV
Section 1.

[...] No state shall make or enforce any law which shall
abridge the privileges or immunities of citizens of the
United States; nor shall any state deprive any person of
life, liberty, or property, without due process of law;
nor deny to any person within its jurisdiction the equal
protection of the laws.

Dobbs rewrites this, it is invalid precedent. States are
liable for denying needed abortions, e.g. TX.

On Wed, 17 Apr 2024 13:39:45 -0400, DFS wrote:

> It's even better: it's 31 releases in 5.5 years.
>
> Fix a bug or 3 in your part time, and make a new release. It's the
> GuhNoo way.

https://learn.microsoft.com/en-us/windows-insider/flight-hub/

The behind-the-scenes look at Microsoft trying to get 24H2 in releasable
shape. I can tell you some of the builds are pissers like the one that
bricked SQL Server.

On 2024-04-17, Chris Ahlstrom <OFeem1987@teleworm.us> wrote:
> RonB wrote this copyrighted missive and expects royalties:
>
>> I've got a Wyse 5070 thin client coming, that (when I get it) will only have
>> 16 GBs of storage. (It does take an M.2. 2280 SSD, so it won't stay that way
>> for long, but I was curious what distribution I could install on the 16 GB
>> limit and still have some room to do things.)
>>
>> Ran into BunsenLabs Linux. Very small, based on Debian 12, and a nice,
>> clean, well configured OpenBox desktop. So I tried it (there is a live
>> trial) and liked it — then decided to replace my Ubuntu server SSD, formerly
>> a Windows 10 SSD (since BunsenLabs Linux gives you the option to install the
>> LAMP stack as part of the installation process). A light desktop and Debian
>> server together, pretty nice.
>>
>> One thing that I did run into (for the first time) was screen tearing. Now I
>> know what they're talking about. I guess it is a common issue in OpenBox,
>> but there was a fix — I ran its compositor (Picom) with the option
>> "--experimental backend" and that fixed it.
>>
>> https://www.bunsenlabs.org/
>>
>> This was originally based on CrunchBang Linux, but CrunchBang was never this
>> slick.
>
> +1
>
> Thanks for that information!

You're welcome. I should add that it did lock up on me (once, after about 8
hours) but I think that had something to do with installing NoMachine
(temporarily) to access my main computer.

And I left out a hyphen in the Picom options...

Should be "picom --experimental-backend." On a basic install, I believe
BunsenLabs Linux takes up about 2.1 GBs of storage space. LibreOffice was
installed by default, so removing it (if you don't use it) would make that
footprint even smaller. (The 2.1 GBs might be an earlier number because I
don't think LibreOffice was originally installed by default.) I'll know more
when I install BunsenLabs Boron (the current version) on the Wyse 5070 with
16 GBs of storage.

There's also a 386 version of this distribution.

--
[Self-centered, Woke] "pride is a life of self-destructive fakery, an
entrapment to a false and self-created matrix of twisted unreality."
"It was pride that changed angels into devils..." — St. Augustine

On 4/17/2024 9:47 AM, RonB wrote:
> I've got a Wyse 5070 thin client coming, that (when I get it) will only have
> 16 GBs of storage. (It does take an M.2. 2280 SSD, so it won't stay that way
> for long, but I was curious what distribution I could install on the 16 GB
> limit and still have some room to do things.)
>
> Ran into BunsenLabs Linux. Very small, based on Debian 12, and a nice,
> clean, well configured OpenBox desktop. So I tried it (there is a live
> trial) and liked it — then decided to replace my Ubuntu server SSD, formerly
> a Windows 10 SSD (since BunsenLabs Linux gives you the option to install the
> LAMP stack as part of the installation process). A light desktop and Debian
> server together, pretty nice.
>
> One thing that I did run into (for the first time) was screen tearing. Now I
> know what they're talking about. I guess it is a common issue in OpenBox,
> but there was a fix — I ran its compositor (Picom) with the option
> "--experimental backend" and that fixed it.
>
> https://www.bunsenlabs.org/
>
> This was originally based on CrunchBang Linux, but CrunchBang was never this
> slick.
>

I have it installed on my HP laptop,which somehow is so godawfully slow
I couldn't use Windows on it anymore. It makes it usable again, so that
definitely is great.
I do have fond memories of Crunchbank Linux, and I miss that system.
Bunsenlabs is looking almost too slick.
But otherwise it's quite nice and usable.

DFS <nospam@dfs.com> wrote at 14:36 this Wednesday (GMT):
> On 4/17/2024 9:03 AM, Chris Ahlstrom wrote:
>> RonB wrote this copyrighted missive and expects royalties:
>>
>>> I guess it is a common issue in OpenBox,
>>> but there was a fix — I ran its compositor (Picom) with the option
>>> "--experimental backend" and that fixed it.
>
>
> JHC. Only in GuhNoo bizarro world.
>
> LibreOffice also puts half-baked "experimental" and "limited" code in
> their production releases, labeled as such to excuse their lackadaisacal
> efforts.
>
> No doubt "Picom" is still at version 0.13 after 10 years of "development".
>
> This! Is! Linux!

$ pacman -Si picom
Name : picom
Version : 11.2-1
[...]
Build Date : Tue 13 Feb 24
--
user <candycane> is generated from /dev/urandom

Joel wrote this copyrighted missive and expects royalties:

> DFS <nospam@dfs.com> wrote:
>>> RonB wrote this copyrighted missive and expects royalties:
>>>
>>>> I guess it is a common issue in OpenBox,
>>>> but there was a fix — I ran its compositor (Picom) with the option
>>>> "--experimental backend" and that fixed it.
>>
>>JHC. Only in GuhNoo bizarro world.
>>
>>LibreOffice also puts half-baked "experimental" and "limited" code in
>>their production releases, labeled as such to excuse their lackadaisacal
>>efforts.

Not like Microsoft's famous beta code (foisted on and tested by the poor
users), eh Spunky?

>>No doubt "Picom" is still at version 0.13 after 10 years of "development".

Doof, it is a fork of a fork of fork of xcompmgr.

Who knows what the version number is? Who cares?

--
My dear People.
My dear Bagginses and Boffins, and my dear Tooks and Brandybucks,
and Grubbs, and Chubbs, and Burrowses, and Hornblowers, and Bolgers,
Bracegirdles, Goodbodies, Brockhouses and Proudfoots. Also my good
Sackville Bagginses that I welcome back at last to Bag End. Today is my
one hundred and eleventh birthday: I am eleventy-one today!"
-- J. R. R. Tolkien

On 2024-04-18, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
> DFS <nospam@dfs.com> wrote at 14:36 this Wednesday (GMT):
>> On 4/17/2024 9:03 AM, Chris Ahlstrom wrote:
>>> RonB wrote this copyrighted missive and expects royalties:
>>>
>>>> I guess it is a common issue in OpenBox,
>>>> but there was a fix — I ran its compositor (Picom) with the option
>>>> "--experimental backend" and that fixed it.
>>
>>
>> JHC. Only in GuhNoo bizarro world.
>>
>> LibreOffice also puts half-baked "experimental" and "limited" code in
>> their production releases, labeled as such to excuse their lackadaisacal
>> efforts.
>>
>> No doubt "Picom" is still at version 0.13 after 10 years of "development".
>>
>> This! Is! Linux!
>
>
> $ pacman -Si picom
> Name : picom
> Version : 11.2-1
> [...]
> Build Date : Tue 13 Feb 24

9.1 is the default for BunsenLabs Linux. (Probably the default for Debian 12
then?) Someone mentioned installing Picom with git, so maybe I'll look into
that. The Wyse 5070 ("Pentium Silver" quad core — just a new name for
Celeron? — has a newer Intel CPU chip) and I haven't noticed any screen
tearing on it so far.

The install went well on the 5070, using its built-in 16 GB EMCC drive.
Boots in about 20 seconds (which I think is pretty good considering its
limitations). No fan, 8 GBs of RAM, using a Pentium Silver J5005 CPU, three
display ports, plus a USB-C/Display Port combo. 5 USB 3.1 (or 3.2) ports,
plus 2 USB 2 ports. Headphone jack on front and back, plus a line out jack
on the front. Came with a GB Ethernet port, plus an Intel WiFi / BlueTooth
card (I believe dual channel). It uses about 6 GBs of disk space, but this
includes Firefox and LibreOffice and quite a few other applications
installed by default — I think the 2.1 GB figure I gave earlier was for a
very basic install.

My only issue was that it automatically took 8 GBs of my flash memory for a
swap file, so I had to turn off swap momentarily, decreases its size to 1.5
GBs and then increase the size of the my main partition in Gparted. So a
very nice, usable $30 basic computer, if don't need to install a lot of
extra applications. When the 128 GB M.2 2280 SATA SSD gets here, I'll
install Linux Mint on that, so I'll able to dual-boot Linuxes.

This computer can use up to 16 GBs of DDR4 RAM – maybe 32 GBs?

--
[Self-centered, Woke] "pride is a life of self-destructive fakery, an
entrapment to a false and self-created matrix of twisted unreality."
"It was pride that changed angels into devils..." — St. Augustine