On Fri, 18 Aug 2023 21:02:14 +0200
Usenet Office <usenet@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.
On 20/08/2023 14:20, Johnny wrote:
On Fri, 18 Aug 2023 21:02:14 +0200
Usenet Office <usenet@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.
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
On Fri, 18 Aug 2023 21:02:14 +0200
Usenet Office <usenet@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.
On 8/20/23 9:20 AM, Johnny wrote:
On Fri, 18 Aug 2023 21:02:14 +0200
Usenet Office <usenet@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)
On 8/20/23 9:20 AM, Johnny wrote:
On Fri, 18 Aug 2023 21:02:14 +0200
Usenet Office <usenet@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)
On 2023-08-27, bad sector <forgetski@invalid.net> wrote:
On 8/20/23 9:20 AM, Johnny wrote:
On Fri, 18 Aug 2023 21:02:14 +0200
Usenet Office <usenet@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.
Using AvLinux (MX I think) su'd as root the commandHave you ever tried MX Linux? I have never opened a terminal since
fdisk doesn't work because that path isn't set for
root (so I have to do /sbin/fdisk)
using it. During installation, I don't bother entering a root password.
On 2023-08-27, bad sector <forgetski@invalid.net> wrote:
On 8/20/23 9:20 AM, Johnny wrote:
On Fri, 18 Aug 2023 21:02:14 +0200
Usenet Office <usenet@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
[...]
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)
On Sun, 27 Aug 2023 07:11:42 -0400
bad sector <forgetski@invalid.net> wrote:
On 8/20/23 9:20 AM, Johnny wrote:
On Fri, 18 Aug 2023 21:02:14 +0200
Usenet Office <usenet@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.
On 2023-08-27, Johnny <johnny@invalid.net> wrote:
On Sun, 27 Aug 2023 07:11:42 -0400
bad sector <forgetski@invalid.net> wrote:
On 8/20/23 9:20 AM, Johnny wrote:
On Fri, 18 Aug 2023 21:02:14 +0200
Usenet Office <usenet@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.
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 /
On 2023-08-27, Johnny <johnny@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
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).
On 8/27/23 14:47, Johnny wrote:
Using AvLinux (MX I think) su'd as root the commandHave you ever tried MX Linux?-a I have never opened a terminal since
fdisk doesn't work because that path isn't set for
root (so I have to do /sbin/fdisk)
using it.-a During installation, I don't bother entering a root password.
A good reason not to use it.-a Thirty years ago i gave up using Windows
for not having administrator password and administrator account :-(
Ciao
Giovanni
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).
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?
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).
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!
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 01:43:46 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
10 files (20,373K bytes) |
| Messages: | 264,188 |
