Swapon bash:command not found ?

greenjeans · 2024-12-03 18:54:20

Okay another weird one.

At some point in my frequent frenetic installing and more installing this last week, I screwed up swap. No biggie, done it before, just usually have to adjust /etc/fstab.

That didn't work out for some reason this time, so I fired up gparted on main system (sda/1) and assigned a new UUID, closed it, modded fstab on sda/1, then opened terminal and su'ed to root and ran

swapon --all --verbose

and swap fired right up. All good.

Now on to sda/2, did same thing, worked perfectly.

Now to sda/3 the new Daedalus Mate-mini, fixed fstab, terminal, su-to-root, run swapon command again and I get the same message that you would get if you tried that command as a user instead of root

bash: command not found

??? It has mount installed and all files are there, swapon and swapoff in /sbin....i'm at a loss here, why would it not let root run swapon?

And the thing is, swap is not off on that partition, the system monitor reports it sees it and it's working.

???

Edit: And tried swapoff, got the same message, bash can't find it.

Last edited by greenjeans (2024-12-03 18:55:07)

GlennW · 2024-12-03 20:35:54

hi, reminds me of the $PATH shinanighans that came with Devuan Chimaera release...

where su no longer gave the user the path root would have.

I wonder if you get a different path if you type 'su -' instead of su.

Seems weird, but maybe you could check that.

greenjeans · 2024-12-03 20:44:21

I'm an idiot.

Thank you Glenn!

Last edited by greenjeans (2024-12-03 22:20:05)

greenjeans · 2024-12-03 20:46:01

hi, reminds me of the $PATH shinanighans that came with Devuan Chimaera release...
where su no longer gave the user the path root would have.
I wonder if you get a different path if you type 'su -' instead of su.
Seems weird, but maybe you could check that.

Wow, I hadn't heard about that, will give it a check.

golinux · 2024-12-03 20:50:08

That's what happens when you play Rip Van Winkle for so long . . .

rolfie · 2024-12-03 20:51:07

The su stuff has already changed in Beowulf: https://files.devuan.org/devuan_beowulf … _notes.txt

greenjeans · 2024-12-03 21:09:38

The su stuff has already changed in Beowulf: https://files.devuan.org/devuan_beowulf … _notes.txt

I'm sitting here right now using stock Daedalus from a netinstall I did a year ago, and that's not the behavior it exhibits, plain old su works just like it always did. That's why I didn't expect this. And I never modified anything to do with the $PATH.

The default settings for the system in all the files i've checked are identical in Daedalus installed a year ago and the one I installed last week from the most recent netinstall iso.

greenjeans · 2024-12-03 21:31:32

Wow @rolfie, thanks for the link big-time, sure enough that new install is doing that, su - has all access. That makes me happy and sad and confused all at the same time.

Happy because I didn't do badly, my goal with the Mate-mini was to make a 100% stock Devuan with no changes or additions by me, pure Devuan as-delivered. So I guess I did that, and if that's the way they want it, so be it. Relieved.

Confused because if this goes all the way back to Beowulf, why did it not do it on my other Devuan installs from a year ago? And also, if someone would humor an out-of-touch old curmudgeon:

Why was this necessary?
Where is it? Hard-coded into Bash?

rolfie · 2024-12-03 22:00:49

You should have been trapped in any release including Beowulf and later. The only way around is a dedicated root terminal.

The problem itself is inherited from Debian. In Buster there was a move of the su command from one package to another (I don't know exactly the names, can be found in the internet). They told me now the su command behaves as in any other Unix/Linux. Not that I like it, I see that very often the "normal" user stumbles across this behaviour. Not really user friendly. Not a bug, works as intended by the people knowing better.

Last edited by rolfie (2024-12-03 22:02:22)

greenjeans · 2024-12-03 22:18:29

Thanks rolfie, the workaround posted at the link you gave me worked fine and now it's behaving as i'm used to.

I don't like either, but I seem to be an old man yelling at clouds the last couple days anyway.

But hey, I learned new things so it's a good day. Really appreciate the forum members here helping me out.

greenjeans · 2024-12-03 22:24:16

That's what happens when you play Rip Van Winkle for so long . . .

It's like I walk out to my truck, put in the key and start it up, but the transmission won't shift out of park today because I didn't use my extra-super-dooper-superuser-key that I didn't know I had or needed to use.

golinux · 2024-12-03 22:43:45

Nothing lasts for long these days . . . except for human stupidity. You can always count on that especially from those on top of the food chain. It seems that stability is not very profitable . . .

EDX-0 · Yesterday 05:55:37

ah yes the PATH shenanigans, i simply append to path in my .profile

PATH="$PATH:/usr/local/sbin:/usr/sbin:/sbin:$HOME/.local/bin"

this way i always get the sbin programs on my path, they will still require sudo to run.

GlennW · Yesterday 08:25:35

I remembered the path abnomally, but forgot the fix... I had made an alias in bash that made it behave the same way I was used to. (and I carry it over from my backup/restore file from install to install)

So, it was Beowulf... my bad.

Glad you got it sorted. And, you're obviously not an idiot, greenjeans.

stargate-sg1-cheyenne-mtn · Yesterday 10:10:21

it has been said many times before but bears repeating, debian is a lost cause and it is only a matter of time before it becomes more effort than it is worth to continue to use it as a base. for those who refuse to use alphabet/apple/microsoft/redhat(directly at least...yes everyone has their fingers in everyone else's pies), where to go/look/turn? [tongue_in_cheek_but_not_totally_in_jest] https://en.wikipedia.org/wiki/KolibriOS [/tongue_in_cheek_but_not_totally_in_jest]

fsmithred · Yesterday 18:14:28

Another way to revert su to the old behavior is to put the following in /etc/default/su (which you will probably have to create).

ALWAYS_SET_PATH yes

greenjeans · Yesterday 22:44:45

Another way to revert su to the old behavior is to put the following in /etc/default/su (which you will probably have to create).

Yep, that's the method I mentioned at the link Rolfie posted, works great!

In addition, despite that, synaptic and other admin stuff would still not start from menu, turns out the policy kit was not starting up at boot, even though there's an entry for it in /etc/xdg/autostart, I had to add a line to start it in /home/vuudo/.config/openbox/autostart, after that everything started working fine, almost....

But my extensions for root edit/access would still not work using pkexec instead of gksu.

So I found a little code online, modded it some, and made a little script I called gksu.sh and dropped it in the $PATH, all it does when you call it is convert the gksu.sh command to a full pkexec command and then executes pkexec and the action you asked for. Keeps me from having to add a bunch of code into the .desktop exec command lines.

Working soooo smooth now, and so much faster and lighter weight than MATE, I am literally almost done building Vuu-do 2, really the only issues I have left are these:

1. Getting a bunch of video artifacts on startup, logout, and shutdown, weird stuff, the Devuan-mate-mini does it too. My original install of Daedalus a year ago did it too at first, then for some reason it stopped doing it all on it's own, wonder what that's about?

2. Totally personal to my machine i'm sure, but whenever I boot any version of Daedalus, it hangs up right at first when you boot for a minute or two, then puts out a message "Gave up on waiting for a suspend/resume device". Not sure what it's looking for, any way to bypass that behavior on my machine?

3. Alsa doesn't seem to want to start at all, so volumeicon isn't working properly and cannot fire up alsamixer or equalizer. I pulled Pulse out (YAY!) and it installed pipewire instead, pretty stoked about dumping pulse, but have no experience with Pipewire so don't know what to expect.

4. I started this from a clean install of Devuan-mate-mini, loaded openbox stuff and got a good working environment, logged into openbox session, uninstalled all the MATE stuff in Synaptic, but now Synaptic thinks that a whole lotta important stuff is now "auto removable". We're talking stuff that would destroy the whole system if I auto-removed it, the entirety of Xorg, most prgrams and system libraries, all of gstreamer, it's bizarre, like 60-70 of the most important packages in the system. What the heck?

greenjeans · Yesterday 23:51:30

And I just gotta say, great googly-moo, the stupid policy kit takes 75-100 mb of ram while it's running, what the actual? Is that really necessary?

#linuxatemyram

The officially official Devuan Forum!

#1 2024-12-03 18:54:20

Swapon bash:command not found ?

#2 2024-12-03 20:35:54

Re: Swapon bash:command not found ?

#3 2024-12-03 20:44:21

Re: Swapon bash:command not found ?

#4 2024-12-03 20:46:01

Re: Swapon bash:command not found ?

#5 2024-12-03 20:50:08

Re: Swapon bash:command not found ?

#6 2024-12-03 20:51:07

Re: Swapon bash:command not found ?

#7 2024-12-03 21:09:38

Re: Swapon bash:command not found ?

#8 2024-12-03 21:31:32

Re: Swapon bash:command not found ?

#9 2024-12-03 22:00:49

Re: Swapon bash:command not found ?

#10 2024-12-03 22:18:29

Re: Swapon bash:command not found ?

#11 2024-12-03 22:24:16

Re: Swapon bash:command not found ?

#12 2024-12-03 22:43:45

Re: Swapon bash:command not found ?

#13 Yesterday 05:55:37

Re: Swapon bash:command not found ?

#14 Yesterday 08:25:35

Re: Swapon bash:command not found ?

#15 Yesterday 10:10:21

Re: Swapon bash:command not found ?

#16 Yesterday 18:14:28

Re: Swapon bash:command not found ?

#17 Yesterday 22:44:45

Re: Swapon bash:command not found ?

#18 Yesterday 23:51:30

Re: Swapon bash:command not found ?

Board footer