Re: [DNG] Lead or follow? this decade’s dilemma for GNU/Linux based ICT industry

2021-12-29 Thread Steve Litt
Jaromil said on Wed, 29 Dec 2021 19:14:28 +0100

>Dear DNG'ers
>
>this summer I wrote a small critical post about what I believe to be a
>dilemma for anyone using GNU/Linux at scale for mission critical
>operations.
>
>I'm curious about your opinions here and if it can spawn an interesting
>thread, there is so little discussion about these topics online and I
>guess this is a good place for it given the experience gathered in this
>community.

> Online version with links and gifs:
> https://medium.com/think-do-tank/lead-or-follow-the-dilemma-of-ict-industry-for-the-coming-decade-4f83ee1851bc

What I especially like about this article is it recognizes Redhat
malfeasance, and generalizes it as something that's anti-community and
also anti-user, whether the user knows it or not. I'm soo tired of
people giving lip service to technocracy, when comparing runit and s6
with their one (each) unpaid developer, vs systemd requiring a crew of
6 highly paid full time developers to keep from imploding.

The one improvement I can suggest with the article is to define all
acronyms once within the text. Because I'm from North America, I call
it "IT", and it took 10 minutes of looking up to find out that "ICT" is
a European acronym for basically the same thing. It took about 25
minutes to find out what an "SME" is.

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Lead or follow? this decade’s dilemma for GNU/Linux based ICT industry

2021-12-29 Thread Hendrik Boom
This is eloquent and profound enough that it needs to be somewhere where people 
are likely to run into it if they are investigating Devuan.

Preferably with links to the five other documents you list for background 
information.

-- hendrik

On Wed, Dec 29, 2021 at 07:14:28PM +0100, Jaromil wrote:
> Dear DNG'ers
> 
> this summer I wrote a small critical post about what I believe to be a
> dilemma for anyone using GNU/Linux at scale for mission critical
> operations.
> 
> I'm curious about your opinions here and if it can spawn an interesting
> thread, there is so little discussion about these topics online and I
> guess this is a good place for it given the experience gathered in this
> community.
> 
> The article is pasted below and a link to it is provided for those who
> prefer the web with links and animated gifs.
> 
>  Lead or follow? this decade’s dilemma for GNU/Linux based ICT industry
> 
>   Online version with links and gifs:
>   
> https://medium.com/think-do-tank/lead-or-follow-the-dilemma-of-ict-industry-for-the-coming-decade-4f83ee1851bc
> 
>I’m writing this post prompted by the disclosure of yet another bug on
>systemd, this time a “nasty security bug” as journalists at ZDNet defined
>it that has been granting all this time local privilege escalation through
>an excessive memory allocation.
> 
> Nasty Linux systemd security bug revealed | ZDNet
> 
>   Systemd, the Linux system and service manager that has largely replaced init
>   as the master Linux startup and control…
> 
>This is very bad news for people running most GNU/Linux desktop or server
>installations with multi-user environments: it means that for the past 5
>years or so their systems may have been compromised, with a few
>exceptions.
> 
>But this post goes beyond these obvious considerations: I argue this is
>just the tip of an iceberg passing almost unnoticed.
> 
>  I’ll share some reasoning about the present and future challenges that
>  are defining a turning point for most of us using and developing
>  GNU/Linux based systems.
> 
> Context
> 
>  The major event I like to focus is not a bug, but the landmark
>  acquisition of RedHat by IBM for 36 whopping billions of dollars just 2
>  years ago.
> 
>This event shall not go unobserved when debating about the future of
>GNU/Linux. It is plausible to think that the enterprise strategy of
>companies dealing with GNU/Linux technologies will evolve well beyond the
>business on certifications, and make bold steps into more aggressive
>exploitation of their huge “market”, something once was a community and
>has lost that status.
> 
>Even the temporal context has a major role in this equation as this is all
>happening during the troubled beginning of a decade marked by pandemic: we
>are witnessing a boost in usage of ICT infrastructure due to COVID with
>growing investments from both public and private sectors into this market.
> 
> Strategy
> 
>  The big and ever-growing conglomerate of the IBM/Linux armada aims to
>  seize the market with renewed dependencies.
> 
>The strategy to form and consolidate dependencies around the needs of
>clients makes sense for an oligopoly that wants to keep its dominant
>position. For a big technology provider today the business of support and
>certifications is marginal when compared to the opportunity to lead
>research, standardization and the pace of innovation according to own
>interests.
> 
>The one who can lead standards can also confine risks where he may please,
>and accelerate testing of own developments no matter how experimental. For
>example systemd builds a lot of dependencies with new untested software
>whose risk is delegated to… anyone using Linux.
> 
>This is precisely what is happening as the big-tech industry establishes
>new core standards for its sector— systemd being a too-big-to-fail example
>— it offloads the risk of innovating strategies on user communities and
>small clients.
> 
>  Right after a successful trial on communities, the big-tech industry is
>  now turning small clients into guinea-pigs to externalize risks attached
>  to innovation strategies.
> 
>This is evident through the strategic changes applied by this new RedHat,
>now lead by IBM, as we come to another landmark event for the ICT
>industry: the so called “death of CentOS”.
> 
> CentOS Is Dead, Long Live CentOS
> 
>   On Tuesday, December 8th, Red Hat and CentOS announced the end of CentOS 8. 
> To
>   be specific, CentOS 8 will reach end of…
> 
>The end of life of RHEL 8 and CentOS 8 has been announced, to be
>substituted by new “stream” releases that have de-facto buried CentOS
>original mission as a stable distribution and resurrected it as the new
>guinea-pig to join 

Re: [DNG] no ttyS0 - Chimaera, vanilla kernel 5.10.0-10 on Atom C2750

2021-12-29 Thread Gregory Nowak via Dng
On Tue, Dec 28, 2021 at 08:15:54PM +0100, Andrzej Peszynski wrote:
> I am trying to use onboard RS-232 @ supermicro A1Sai-2750 with Intel C2750,
> Devuan Chimaera, vanilla kernel 5.10.0-10-amd64. In BIOS the ports COM1 and
> COM2 are configured on 24MHz/13.

24MHz/13 makes no sense here, unless you're trying to use an IrCOMM
device. If the serial section of your UEFI/BIOS has IRDA support, you
want to disable that if you just want to use a standard serial port.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] Yet another test

2021-12-29 Thread golinux

Thanks for you patience . . .
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Lead or follow? this decade’s dilemma for GNU/Linux based ICT industry

2021-12-29 Thread Steve Litt
Jaromil said on Wed, 29 Dec 2021 19:14:28 +0100

>  Systemd, the Linux system and service manager that has largely
> replaced init as the master Linux startup and control…
   

Replaced Sysv-init. "init" nowadays is a category of software that
includes PID1, is the first user program run by the kernel, and is
responsible for bringing the computer up to a steady, functional state,
sometimes including respawning and other features.

The reason this is important is because systemd was successfully sold
as being better than Sysv-init, a deliberate false-choice fallacy when
those in the know, including the "systemd cabal" and Redhat, knew darn
well about other inits such as runit, s6, OpenRC, and Busybox init, as
well as hybrids using the perfectly reasonable Sysv-init PID1 with
process supervisors from softwares including runit, daemontools-encore,
and s6.

In my opinion Sysv-init's process manager sucks big time. Its only
redeeming feature is that it sucks much less than systemd. But it's
important to keep reminding people there are many excellent choices of
init systems by mentioning those init systems, and calling the thing
that systemd tried to replace "Sysv-init".

Thanks, 

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] Test to debug delivery issues

2021-12-29 Thread golinux

@fsmithred's requrest
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] broken dependency chain for libgtk-3-dev ?

2021-12-29 Thread alphalpha--- via Dng
thanks, i found a solution to get the correct versions:
sudo apt install libatspi2.0-0=2.38.0-4 libepoxy0=1.5.5-1

greetings, alphalpha
(this is my first time using the mailing list so i hope this gets send to the 
correct thread)


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] test message

2021-12-29 Thread onefang
On 2021-12-29 13:15:07, fsmithred via Dng wrote:
> Sorry for the noise.
> 
> Don't reply. I made other arrangements, thanks.
> 
> fsr

As per fsmithred's request on IRC, I'm sending a replay to this to the
list.

-- 
A big old stinking pile of genius that no one wants
coz there are too many silver coated monkeys in the world.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] Lead or follow? this decade’s dilemma for GNU/Linux based ICT industry

2021-12-29 Thread Jaromil
Dear DNG'ers

this summer I wrote a small critical post about what I believe to be a
dilemma for anyone using GNU/Linux at scale for mission critical
operations.

I'm curious about your opinions here and if it can spawn an interesting
thread, there is so little discussion about these topics online and I
guess this is a good place for it given the experience gathered in this
community.

The article is pasted below and a link to it is provided for those who
prefer the web with links and animated gifs.

 Lead or follow? this decade’s dilemma for GNU/Linux based ICT industry

Online version with links and gifs:

https://medium.com/think-do-tank/lead-or-follow-the-dilemma-of-ict-industry-for-the-coming-decade-4f83ee1851bc

   I’m writing this post prompted by the disclosure of yet another bug on
   systemd, this time a “nasty security bug” as journalists at ZDNet defined
   it that has been granting all this time local privilege escalation through
   an excessive memory allocation.

Nasty Linux systemd security bug revealed | ZDNet

  Systemd, the Linux system and service manager that has largely replaced init
  as the master Linux startup and control…

   This is very bad news for people running most GNU/Linux desktop or server
   installations with multi-user environments: it means that for the past 5
   years or so their systems may have been compromised, with a few
   exceptions.

   But this post goes beyond these obvious considerations: I argue this is
   just the tip of an iceberg passing almost unnoticed.

 I’ll share some reasoning about the present and future challenges that
 are defining a turning point for most of us using and developing
 GNU/Linux based systems.

Context

 The major event I like to focus is not a bug, but the landmark
 acquisition of RedHat by IBM for 36 whopping billions of dollars just 2
 years ago.

   This event shall not go unobserved when debating about the future of
   GNU/Linux. It is plausible to think that the enterprise strategy of
   companies dealing with GNU/Linux technologies will evolve well beyond the
   business on certifications, and make bold steps into more aggressive
   exploitation of their huge “market”, something once was a community and
   has lost that status.

   Even the temporal context has a major role in this equation as this is all
   happening during the troubled beginning of a decade marked by pandemic: we
   are witnessing a boost in usage of ICT infrastructure due to COVID with
   growing investments from both public and private sectors into this market.

Strategy

 The big and ever-growing conglomerate of the IBM/Linux armada aims to
 seize the market with renewed dependencies.

   The strategy to form and consolidate dependencies around the needs of
   clients makes sense for an oligopoly that wants to keep its dominant
   position. For a big technology provider today the business of support and
   certifications is marginal when compared to the opportunity to lead
   research, standardization and the pace of innovation according to own
   interests.

   The one who can lead standards can also confine risks where he may please,
   and accelerate testing of own developments no matter how experimental. For
   example systemd builds a lot of dependencies with new untested software
   whose risk is delegated to… anyone using Linux.

   This is precisely what is happening as the big-tech industry establishes
   new core standards for its sector— systemd being a too-big-to-fail example
   — it offloads the risk of innovating strategies on user communities and
   small clients.

 Right after a successful trial on communities, the big-tech industry is
 now turning small clients into guinea-pigs to externalize risks attached
 to innovation strategies.

   This is evident through the strategic changes applied by this new RedHat,
   now lead by IBM, as we come to another landmark event for the ICT
   industry: the so called “death of CentOS”.

CentOS Is Dead, Long Live CentOS

  On Tuesday, December 8th, Red Hat and CentOS announced the end of CentOS 8. To
  be specific, CentOS 8 will reach end of…

   The end of life of RHEL 8 and CentOS 8 has been announced, to be
   substituted by new “stream” releases that have de-facto buried CentOS
   original mission as a stable distribution and resurrected it as the new
   guinea-pig to join Fedora in the gratuitous “downstream cage” of
   experimentation.

 Lets be aware now that what comes “free as in beer” comes at a high cost
 in priorities and control.

  Opportunity

 All things considered this is the perfect storm. We may free ourselves
 from the big and ever-growing conglomerate of the IBM/Linux armada
 before they entangle us with ever growing dependencies.

   Thanks to courage, a vibrant community of experts and some 

[DNG] test message

2021-12-29 Thread fsmithred via Dng
Sorry for the noise.

Don't reply. I made other arrangements, thanks.

fsr
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] no ttyS0 - Chimaera, vanilla kernel 5.10.0-10 on Atom C2750

2021-12-29 Thread Andrzej Peszynski

Greetings Devuan!

I am trying to use onboard RS-232 @ supermicro A1Sai-2750 with Intel 
C2750, Devuan Chimaera, vanilla kernel 5.10.0-10-amd64. In BIOS the 
ports COM1 and COM2 are configured on 24MHz/13.


In dmesg I can see:
"/Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled/"
but no tty (except console), and receive IO errors on /cat /dev/ttySx/, 
and on /stty -F /dev/ttySx/



Searching brought me to the kernel rebuild with options like 
CONFIG_SERIAL_8250_PCI, which are already enabled in current kernel. 
Tried to load 8250_lpss.ko too, with no luck.


Shortcut would be to use the USB RS-232 dongle, however it will be too 
easy, I guess, and boring too.


Can you give me some light, please? Many thanks!
Andrzej___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng