Permission Problems?

[labeas]

Quiet honestly, I never run as NON-root unless forced to do so.
And I thought that `sudo` gave root-permission, which is total
permission.

I'm continual having problems with permission with TC; eg.

tc@box:/home$ sudo ls /mnt/sdb2/CRG/Utilities/TstFprune
FindTimeStr234Dir  Fp2                Fp3                Fprune

tc@box:/home$ cd /mnt/sdb2/CRG/Utilities/TstFprune
sh: cd: can't cd to /mnt/sdb2/CRG/Utilities/TstFprune

tc@box:~$ sudo cd /mnt/sdb2/CRG/Utilities/TstFprune
sudo: cd: command not found
           
tc@box:/home$ sudo su
root@box:/home# cd /mnt/sdb2/CRG/Utilities/TstFprune
root@box:/mnt/sdb2/CRG/Utilities/TstFprune#.

Is this a quirk of TC? If so it should be warned against UP FRONT.

[patrikg]

I think you have problems with busybox.
You have to know if you run bash... or busybox.

[gerald_clark]

"sudo cd" makes no sense.
cd is not a program, it is a shell builtin command.
Even if it was, after sudo completed you would be right back in the directory where you started.
Quit blaming TC and its authors for your foolishness.

[labeas]

>cd is not a program, it is a shell builtin command.
> Even if it was, after sudo completed you would be right back in the directory where you
>  started.
>  Quit blaming TC and its authors for your foolishness.
--When I used mulinux: linux on a single 1M7fd0; it also used ash,
but had no problem with this 2nd most fundamental/essential command
after `ls`.
}}    I think you have problems with busybox.
}}   You have to know if you run bash... or busybox.
--ash/busybox is the default for TC64.
`cd` is a MOST fundamental command.
I'm running TC off a USBstik.
If I expected to have bash & full X11 & KDE with dancing-moneys I wouldn't
use TC.