mount point /windows does not exist because you do not have a
*directory* /windows in your linux system. Above /windows/C. Linux is *very* particular and instructions that you are given will *not* succeed unless they are followed specifically, provided that they were correct <grin>. Your posts will be much easier to read if you change your *indent* character from ">" to "><space>" thats ">" + a space. < Thanks Franklin, dano, Patrick et al: Got it mounted: just needed to have a directory in the tree named windows and that fixed it. Mounts fine now. I did have touble getting to an editor than Im comfortable with in root, however. Tried to use kate as root but the suse way: sh kate (as root) or ./kate didnt work. Had to use file manage-superuser mode and it didnt let me edit the /etc/fstab file. How do you open kate as root if not by the 2 commands above which I found in the manual! BTW, do the <space> make the post easier to read?
On Friday 31 January 2003 14:13, Doug Weeks wrote:
Tried to use kate as root but the suse way: sh kate (as root) or ./kate didnt work. Had to use file manage-superuser mode and it didnt let me edit the /etc/fstab file. How do you open kate as root if not by the 2 commands above which I found in the manual!
Did you try simply kate? That should do it. Otherwise you could use midnight commander in a root console - it's a file manager with a perfectly servicable text editor built in. Or just right click on the file in the superuser filemanager and chose from Open with... Since the filemanager is root, the editor it calls will also be root.
BTW, do the <space> make the post easier to read?
yes Dylan -- "Sweet moderation Heart of this nation Desert us not We are between the wars" Billy Bragg
Doug Weeks <fourweeks.vet@mindspring.com> writes:
Tried to use kate as root but the suse way: sh kate (as root) or ./kate didnt work. Had to use file manage-superuser mode and it didnt let me edit the /etc/fstab file. How do you open kate as root if not by the 2 commands above which I found in the manual!
In which manual? The manual should be fixed, these commands are wrong. -- Alexandr.Malusek@imv.liu.se
Alexandr Malusek wrote:
Doug Weeks <fourweeks.vet@mindspring.com> writes:
Tried to use kate as root but the suse way: sh kate (as root) or ./kate didnt work. Had to use file manage-superuser mode and it didnt let me edit the /etc/fstab file. How do you open kate as root if not by the 2 commands above which I found in the manual! <
I used th online SuSe help menu and did a search on root. This is the 8.1 pro distro Suse help>"search" root then link on "root cannot execute certain commands" is where I got this. I was used to just typing in the command after su'ing as root in Mandrake so this was a bit confusing. Guess I have to open superuser file manager then open with right click on the file to get others???
In which manual? The manual should be fixed, these commands are wrong.
-- Alexandr.Malusek@imv.liu.se
Doug Weeks <fourweeks.vet@mindspring.com> writes:
Alexandr Malusek wrote:
Doug Weeks <fourweeks.vet@mindspring.com> writes:
Tried to use kate as root but the suse way: sh kate (as root) or ./kate didnt work. Had to use file manage-superuser mode and it didnt let me edit the /etc/fstab file. How do you open kate as root if not by the 2 commands above which I found in the manual! <
In which manual? The manual should be fixed, these commands are wrong.
I used th online SuSe help menu and did a search on root. This is the 8.1 pro distro Suse help>"search" root then link on "root cannot execute certain commands" is where I got this.
The SDB advice (note SDB is not a manual) is OK you just misinterpreted it.
I was used to just typing in the command after su'ing as root in Mandrake so this was a bit confusing.
It's the same in SuSE - use "su" for text based and "sux" for GUI based programs.
Guess I have to open superuser file manager then open with right click on the file to get others???
It can be done like that. In general, programs inherit the root ID from their parents so if the file manager runs with the root ID then all programs it starts will also run with the root ID (unless the code was written in a special way to prevent this). -- Alexandr.Malusek@imv.liu.se
participants (3)
-
Alexandr Malusek -
Doug Weeks -
Dylan