Re: RIP

[Johnny]

On Fri, 18 Aug 2023 21:02:14 +0200
Usenet Office <use...@usenet.invalid> wrote:

> It is with great sadness that we have to inform you that this
> newsgroup has passed away.
> Condolences can be send to the Editorial Board of Usenet and the Board
> of Directors of the Debian Society.
>
> Usenet Office

No big loss. The worst operating system I have ever used.

I doubt many people use it since MX Linux came out.

[magardner2010]

I personally have never heard of MX Linux outside of your posts to this
newsgroup, while pretty much every large company that uses Linux either
uses a Red Hat, or Debian Derivative.

[Chris Elvidge]

Without Debian, there would be no MX Linux, Ubuntu, Mint.


--

Chris Elvidge, England
I WILL NOT GET VERY FAR WITH THIS ATTITUDE

[Johnny]

On Sun, 20 Aug 2023 15:08:09 +0100
Chris Elvidge <ch...@mshome.net> wrote:

> On 20/08/2023 14:20, Johnny wrote:
> > On Fri, 18 Aug 2023 21:02:14 +0200
> > Usenet Office <use...@usenet.invalid> wrote:
> >
> >> It is with great sadness that we have to inform you that this
> >> newsgroup has passed away.
> >> Condolences can be send to the Editorial Board of Usenet and the
> >> Board of Directors of the Debian Society.
> >>
> >> Usenet Office
> >
> > No big loss. The worst operating system I have ever used.
> >
> > I doubt many people use it since MX Linux came out.
> >
> >
>
> Without Debian, there would be no MX Linux, Ubuntu, Mint.
>
>

MX Linux and Linux Mint improved on it.

I tried Debian twice several years apart. I just couldn't use it
either time. First of all I didn't like the installation method. MX
Linux and Mint both have a simple installer.

MX Linux is the best operating system I have ever used. I believe its
what Debian should have been. Zero problems.

[songbird]

Usenet Office wrote:
> It is with great sadness that we have to inform you that this
> newsgroup has passed away.
> Condolences can be send to the Editorial Board of Usenet and the Board
> of Directors of the Debian Society.
>
> Usenet Office

seems to be working just fine.

HTHAHAND


songbird

[bad sector]

Using AvLinux (MX I think) su'd as root the command
fdisk doesn't work because that path isn't set for
root (so I have to do /sbin/fdisk)



--
Debian GNU/Linux 11 (bullseye), Kernel=6.4.12-1-liquorix-amd64
on x86_64, DM=Unknown, DE=XFCE, ST=x11,grub2, GPT, BIOS-boot
Warning to any and all internet merchants: if any part of my
communications before, during or after a transaction with you
is routed to any 3rd party such as google, faecesbook or such
other without my explicit consent each time then you will never
smell my money.

[Johnny]

On Sun, 27 Aug 2023 07:11:42 -0400
bad sector <forg...@invalid.net> wrote:

> On 8/20/23 9:20 AM, Johnny wrote:
> > On Fri, 18 Aug 2023 21:02:14 +0200
> > Usenet Office <use...@usenet.invalid> wrote:
> >
> >> It is with great sadness that we have to inform you that this
> >> newsgroup has passed away.
> >> Condolences can be send to the Editorial Board of Usenet and the
> >> Board of Directors of the Debian Society.
> >>
> >> Usenet Office
> >
> > No big loss. The worst operating system I have ever used.
> >
> > I doubt many people use it since MX Linux came out.
>
>
> Using AvLinux (MX I think) su'd as root the command
> fdisk doesn't work because that path isn't set for
> root (so I have to do /sbin/fdisk)

Have you ever tried MX Linux? I have never opened a terminal since
using it. During installation, I don't bother entering a root password.

[William Unruh]

On 2023-08-27, bad sector <forg...@invalid.net> wrote:
> On 8/20/23 9:20 AM, Johnny wrote:
>> On Fri, 18 Aug 2023 21:02:14 +0200
>> Usenet Office <use...@usenet.invalid> wrote:
>>
>>> It is with great sadness that we have to inform you that this
>>> newsgroup has passed away.
>>> Condolences can be send to the Editorial Board of Usenet and the Board
>>> of Directors of the Debian Society.
>>>
>>> Usenet Office
>>
>> No big loss. The worst operating system I have ever used.
>>
>> I doubt many people use it since MX Linux came out.
>
>
> Using AvLinux (MX I think) su'd as root the command
> fdisk doesn't work because that path isn't set for
> root (so I have to do /sbin/fdisk)

su does not read root's .bash_profile or .bashrc, but uses the users
version AFAIK. Thus sbin is probably not in your path as user.

However if you do su -, then .bashrc and .bash_profile are read, and
/sbin will be in root's path

From man su
For backward compatibility, su defaults to not change the current directory and to only set the
environment variables HOME and SHELL (plus USER and LOGNAME if the target user is not root). It
is recommended to always use the --login option (instead of its shortcut -) to avoid side ef-
fects caused by mixing environments.


>
>
>

[Chris Elvidge]

Or sudo -i

--

Chris Elvidge, England
I WILL NOT DO MATH IN CLASS

[Giovanni]

On 8/27/23 14:47, Johnny wrote:
>> Using AvLinux (MX I think) su'd as root the command
>> fdisk doesn't work because that path isn't set for
>> root (so I have to do /sbin/fdisk)
> Have you ever tried MX Linux? I have never opened a terminal since
> using it. During installation, I don't bother entering a root password.

A good reason not to use it. Thirty years ago i gave up using Windows
for not having administrator password and administrator account :-(

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
< https://giovanni.homelinux.net/ >

[bad sector]

On 8/27/23 8:55 AM, William Unruh wrote:
> On 2023-08-27, bad sector <forg...@invalid.net> wrote:
>> On 8/20/23 9:20 AM, Johnny wrote:
>>> On Fri, 18 Aug 2023 21:02:14 +0200
>>> Usenet Office <use...@usenet.invalid> wrote:
>>>
>>>> It is with great sadness that we have to inform you that this
>>>> newsgroup has passed away.
>>>> Condolences can be send to the Editorial Board of Usenet and the Board
>>>> of Directors of the Debian Society.
>>>>
>>>> Usenet Office
>>>
>>> No big loss. The worst operating system I have ever used.
>>>
>>> I doubt many people use it since MX Linux came out.
>>
>>
>> Using AvLinux (MX I think) su'd as root the command
>> fdisk doesn't work because that path isn't set for
>> root (so I have to do /sbin/fdisk)
>
> su does not read root's .bash_profile or .bashrc, but uses the users
> version AFAIK. Thus sbin is probably not in your path as user.
>
> However if you do su -, then .bashrc and .bash_profile are read, and
> /sbin will be in root's path

su *is* what I do

and there's more ..seeing that AvLinux uses MX?.... :-)

My ssd's are in a 2.5" rack and my magnetics in a 3.5.
One of my data drives in the 3.5 rack is a 4tb WD,
and fdisk, even when invoked with /sbin/fdisk just
won't detect it.

BOTH of the above work without fault in 6 other distros I use.

[Dan Purgert]

On 2023-08-27, bad sector wrote:
> [...]

> Using AvLinux (MX I think) su'd as root the command
> fdisk doesn't work because that path isn't set for
> root (so I have to do /sbin/fdisk)

use 'su -', to get a login session for root (although the manpage
suggests to use '--login' instead).


--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

[William Unruh]

That is of course stupid if you are connected in any way to the net
(especially now that you have announced it to the net). And even stupid
if it is disconnected. (One of the things is to prevent you from doing
stupid things, like doing rm -rf . when you thought you were in .cache
when you were actually in /

>
>

[Johnny]

How is it stupid if I'm connected to the Internet?

[Dan Purgert]

On 2023-08-29, William Unruh wrote:
> On 2023-08-27, Johnny <joh...@invalid.net> wrote:

>> [...]

>> Have you ever tried MX Linux? I have never opened a terminal since
>> using it. During installation, I don't bother entering a root password.
>
> That is of course stupid if you are connected in any way to the net
> (especially now that you have announced it to the net). And even stupid

Most distros that still ask for a root password during install will
setup Ubuntu-esque usage of sudo if you leave the root password blank.

Well, least Debian/Devuan do (and MX did, but it's been an age since
I've followed the MX installer)

[John Hasler]

Johnny wrote:
>> Have you ever tried MX Linux? I have never opened a terminal since
>> using it. During installation, I don't bother entering a root password.

William Unruh wrote:
> That is of course stupid if you are connected in any way to the net
> (especially now that you have announced it to the net).

Not entering a password when installing Debian means that it is not
possible to log in as root at all. All administrative work must be done
with sudo. Some people find this inconvenient but it is not insecure.
--
John Hasler
jo...@sugarbit.com
Dancing Horse Hill
Elmwood, WI USA

[bad sector]

On 8/27/23 11:31, Giovanni wrote:
> On 8/27/23 14:47, Johnny wrote:
>>> Using AvLinux (MX I think) su'd as root the command
>>> fdisk doesn't work because that path isn't set for
>>> root (so I have to do /sbin/fdisk)
>> Have you ever tried MX Linux?  I have never opened a terminal since
>> using it.  During installation, I don't bother entering a root password.
>
> A good reason not to use it.  Thirty years ago i gave up using Windows
> for not having administrator password and administrator account :-(
>
> Ciao
> Giovanni

My late brother logged in as root for something like
30 years, that wasn't what killed him. NB. People used
to be very polite when dueling was legal :-)


--
Fridays are Tumbleweed days: openSUSE Tumbleweed,
Kernel=6.4.11-1-default on x86_64, DM=sddm, DE=KDE,
ST=x11,grub2, GPT, BIOS-boot
https://imgur.com/mWjMS5W.png https://imgur.com/RsbswMP.png

[bad sector]

On 8/28/23 06:12, Dan Purgert wrote:
> On 2023-08-27, bad sector wrote:
>> [...]
>> Using AvLinux (MX I think) su'd as root the command
>> fdisk doesn't work because that path isn't set for
>> root (so I have to do /sbin/fdisk)
>
> use 'su -', to get a login session for root (although the manpage
> suggests to use '--login' instead).

what's the rationale behind the suggestion?

[Dan Purgert]

On 2023-09-01, bad sector wrote:
> On 8/28/23 06:12, Dan Purgert wrote:
>> On 2023-08-27, bad sector wrote:
>>> [...]
>>> Using AvLinux (MX I think) su'd as root the command
>>> fdisk doesn't work because that path isn't set for
>>> root (so I have to do /sbin/fdisk)
>>
>> use 'su -', to get a login session for root (although the manpage
>> suggests to use '--login' instead).
>
>
> what's the rationale behind the suggestion?

Without using one of the '-' or '--login' options, 'su(1)' doesn't give
you a "login" session. That is, root's profile (from .profile /
.bash_profile / etc.) is not read, and the environment variables ($PATH
included) are those of the calling user.

On the other hand, using either the '-' or '--login' option (I've never
noticed a difference, but the manpage indicates there is one) means
root's profile is loaded and environment variables are set. Therefore,
$PATH ends up including /sbin (amongst other things).

[bad sector]

On 9/1/23 09:40, Dan Purgert wrote:
> On 2023-09-01, bad sector wrote:
>> On 8/28/23 06:12, Dan Purgert wrote:
>>> On 2023-08-27, bad sector wrote:
>>>> [...]
>>>> Using AvLinux (MX I think) su'd as root the command
>>>> fdisk doesn't work because that path isn't set for
>>>> root (so I have to do /sbin/fdisk)
>>>
>>> use 'su -', to get a login session for root (although the manpage
>>> suggests to use '--login' instead).
>>
>>
>> what's the rationale behind the suggestion?
>
> Without using one of the '-' or '--login' options, 'su(1)' doesn't give
> you a "login" session. That is, root's profile (from .profile /
> .bash_profile / etc.) is not read, and the environment variables ($PATH
> included) are those of the calling user.
>
> On the other hand, using either the '-' or '--login' option (I've never
> noticed a difference, but the manpage indicates there is one) means
> root's profile is loaded and environment variables are set. Therefore,
> $PATH ends up including /sbin (amongst other things).

hmmm, most interesting, i didn't know that. I notice that
with the --login switch the resulting prompt is different too.
Thanks!

[Dan Purgert]

No problem :)

Best to read /root/{.bashrc, .profile, [etc. dotfiles]} to get an idea
of what all you can expect. It's been an absolute age since I've had
the "debian defaults", so I can't remember exactly what's my addition
vs. the (root) defaults.