Date: Thu, 23 Sep 2021 15:01:25 -0300 From: =?utf-8?Q?Lucas_Nali_de_Magalh=C3=A3es?= <rollingbits@gmail.com> To: Baptiste Daroussin <bapt@freebsd.org> Cc: current@freebsd.org, arch@freebsd.org Subject: Re: [HEADSUP] making /bin/sh the default shell for root Message-ID: <577BC6B6-DA44-47FD-A70B-A30404968E4F@gmail.com> In-Reply-To: <20210922083645.4vnoajyvwq6wfhdf@aniel.nours.eu> References: <20210922083645.4vnoajyvwq6wfhdf@aniel.nours.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-BF42553D-5B8F-4B87-AF9D-75DD8B359C1D Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Sep 22, 2021, at 5:38 AM, Baptiste Daroussin <bapt@freebsd.org> wrote: > TL;DR: this is not a proposal to deorbit csh from base!!! (=E2=80=A6) I'm used to see FreeBSD remembered as a traditional OS full of professionali= sm and open to innovation. The front door for the BSD world and an OS that does= n't copy Linux. But more and more I'm seeing that BSD will need a new front door= soon, that this OS is becoming more and more another Linux, that professiona= lism is being left aside and that innovation is being undone and/or simply erased= . I wish I were about to write that it's the first time in a lot of time that I= see a problem being systematically recreated but this isn't true either. And I feel sad I'= m being getting used to this, too. Mark Millard found that LLVM multi-threaded linker is buggy on Armv7 and rep= orted it in another thread. I commented on it, even. It wasn't mention in that thr= ead that the numbers there shows another problem recreated that must be solved again. The= processes there were killed *before* virtual memory started to being heavily= used. This goes against the intended use of virtual memory. If virtual memory isn't use= d it's lost resource: a thing that must be removed from the system, optimized away. In t= hat specific case, virtual memory should have entered into place, being fully fi= lled and then the process will be killed. And just to be complete, the non-debuggability o= f LLVM were a known problem of LLVM by the time of the discussions that lead to it's imp= ort in the tree. --=20 rollingbits =E2=80=94 =F0=9F=93=A7 rollingbits@icloud.com =F0=9F=93=A7 rolli= ngbits@gmail.com =F0=9F=93=A7 rollingbits@yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?577BC6B6-DA44-47FD-A70B-A30404968E4F>