Are we having fun yet? Yesterday I did some "experimenting" and rendered my machine unbootable for about 4 hours...education is expensive and the day to day lesson are seldom cheap.
I pinched this from
http://www.linuxadvocates.com/2013/03/the-linux-filesystem-need-not-be.html They pinched it from codepuppet.com
Attachment:
File comment: Stylized Linux Directory Structure
linux_directory_structure.png [ 11.39 KiB | Viewed 32589 times ]
As a 'normal' user, generally you 'own' files/directories downstream from /home/$USER, but not necessarily. Most of the files/directories in the system are not 'yours'. You might be able to 'see' them, but they are not 'yours' to modify, move, or delete. Frequently, executable files are even 'not yours' to run. They belong to another process...another 'owner'....yeah, Sybil lives in your machine. For funzies see who's there; run
Code:
awk -F":" '{ print "username: " $1 }' /etc/passwd
...whatever it is that the do; they keep things humming in the background. They have their own set of permissions and limitatiions. This 'compartmentalizing' is a good security feature. The one who rules them all is root (
/). Not content with having the whole machine root also has its own private space (
/root).
If you know the root password you can act like root and do 'superuser' stuff. For most of Navigatrix work on the USB stick this password has been hardcoded in so you don't need to type it in....but you still need to tell the machine you want to act as root. There fore, as
superuser
do <whatever>.
That is, to become "root" you can either preface a command with
sudo, for example to
ma
ke a
directory in root's space
Code:
nx@nx:~$ mkdir /root/test
mkdir: cannot create directory ‘/root/test’: Permission denied
nx@nx:~$ sudo mkdir /root/test <-------------------------------command is executed
nx@nxi:~$ ls /root
ls: cannot open directory /root: Permission denied
nx@nx:~$ sudo ls /root
Desktop test <------------------------------listed directory
nx@nx:~$ rm -r /root/test
rm: cannot remove ‘/root/test’: Permission denied
nx@nx:~$ sudo !!
sudo rm -r /root/test <-------------------------------command is executed
nx@nx:~$ ls /root
ls: cannot open directory /root: Permission denied
nx@nx:~$ sudo !! <-------------------------------repeat last command as superuser (root)
sudo ls /root <-------------------------------shows what command is
Desktop
nx@nx:~$
or you tell the machine
sudo !! which means "Repeat the last command, but this time do it as root."
Additionally, you could just take over the terminal as root with
sudo -s and act as root until the cows come home...or until you
exit to 'logoff' as root.
Ok...that's a long-winded explaination how to become root. Unfortunately it doesn't solve your problem.
If you try to install the .deb file that came with the archive; it will fail. That module is created for a different kernel than the one you have.
Your solution lies back at your earlier attempt.
Quote:
nx@nx:/cdrom/DOWNLOADS/Pico/libusb$ ./configure
bash: ./configure: Permission denied
For whatever reason, as I shrug my shoulders in ignorance, sometimes we need to tell the machine to run a
shell to execute a command. Therefore
Code:
sh ./configure
...is your solution. If you didn't 'own' the directory than;
sudo sh ./configure.
I don't know if it was because my installation was on a hardrive and yours in on the USB...or what. Sometime I have to
sh ./<whatever> to execute a script...sometimes not. I still haven't found rhyme nor reason, but it's there...I just haven't figure it out. I do know that running sudo <anything> can lead to unintended consequences so it's good to know what you are doing or are willing to learn.
