Home
D C's Library tagged → View Popular, Search in Google
Directory permissions
Permissions for directories aren't exactly the same as they are for files. Here are some typical permissions required on directories:
Execute permission is required for a user to cd into a directory.
Read permission is required for a user to use a command such as ls to view the files contained in a directory.
Execute-only permission allows a user to access the files in a directory as long as the user knows the names of the files in the directory, and the user is allowed to read the files.
Write permission allows the user to create, delete, or modify any files or subdirectories, even if the file or subdirectory is owned by another user.
in list: Linux
-
- Directory permissions
- Execute permission is required for a user to cd into a directory.
- Read permission is required for a user to use a command such as ls to view the files contained in a directory.
- Execute-only permission allows a user to access the files in a directory as long as the user knows the names of the files in the directory, and the user is allowed to read the files.
- Write permission allows the user to create, delete, or modify any files or subdirectories, even if the file or subdirectory is owned by another user.
Permissions for directories aren't exactly the same as they are for files. Here are some typical permissions required on directories:
If you've used the Linux LVM to create your partitions, you'll need to make those accessible before you run fsck:
"lvm pvscan"
"lvm vgscan"
"lvm lvchange -ay 'NameOfYourVolumeGroup' "
"lvm lvscan"
Then you can run fsck:
"fsck -f NameOfYourVolumeGroup"
in list: Linux
-
If you've used the Linux LVM to create your partitions, you'll need to make those accessible before you run fsck:
"lvm pvscan"
"lvm vgscan"
"lvm lvchange -ay 'NameOfYourVolumeGroup' "
"lvm lvscan"
Then you can run fsck:
"fsck -f NameOfYourVolumeGroup"
you can either a) umount the mounted LVs under /mnt/sysimage
or b) bring up the LVM after saying 'no' to finding and mounting filesystems
if b), then
Code:
lvm pvscan
lvm vgscan
lvm lvchange -ay
lvm lvscan
the lvscan should show the expected LVs and then you should be able to safely fsck the ones you need to run it on since they will not be mounted.
fsck /dev/VolGroup00/LogVol00 (or whatever the device name )
Hope this helps.
in list: Linux
-
you can either a) umount the mounted LVs under /mnt/sysimage
or b) bring up the LVM after saying 'no' to finding and mounting filesystems
if b), then
the lvscan should show the expected LVs and then you should be able to safely fsck the ones you need to run it on since they will not be mounted.Code:lvm pvscan lvm vgscan lvm lvchange -ay lvm lvscan
fsck /dev/VolGroup00/LogVol00 (or whatever the device name
)
Hope this helps. -
As a simple workaround for those weary of picking the right PVs:
As root (or user allowed to shut down the box) type at a console "shutdown -r -F now". That'll perform an immediate reboot with a forced file system check (-F option) for all partitions and you can watch the results during boot...
in list: Linux
-
MUTT
One of major drawbacks of using the mail command is that it does not support the sending of attachments. mutt, on the other hand, does support it. I’ve found this feature particularly useful for scripts that generate non-textual reports or backups which are relatively small in size which I’d like to backup elsewhere. Of course, mutt allows you to do a lot more than just send attachments. It is a much more complete command line mail client than the “mail” command. Right now we’ll just explore the basic stuff we might need often. Here’s how you would attach a file to a mail:
# echo “Sending an attachment.” | mutt -a backup.zip -s “attachment” calvin@cnh.com
This command will send a mail to calvin@cnh.com with the subject (-s) “attachment”, the body text “Sending an attachment.”, containing the attachment (-a) backup.zip. Like with the mail command you can use the “-c” option to mark a copy to another mail id.
$ find / -name 'program.c' 2>/dev/null
$ find / -name 'program.c' 2>errors.txt
/
Start searching from the root directory (i.e / directory)
-name
Given search text is the filename rather than any other attribute of a file
'program.c'
Search tex
in list: Linux
-
$ find / - name 'Metallica*' -exec ls -l {\}\ \;
This command would find all the files on your system that begin with the letters 'Metallica' and would then execute the 'ls -l' command on these files. So basically you would be able to see the details of the files that were returned according to your search criteria.
The words following the -exec option is the command that you want to execute i.e. ls -l in this case.
{\}\ is basically an indicator that the filenames returned by the search should be substituted here.
\; is the terminating string, and is required at the end of the command
In the console type the following, and leave the console minimized while you are using the computer.
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so skype
in list: Linux
in list: Linux
-
An alternativ for base64 coding: ... | openssl base64 This makes the cut-offs with sed obsolet
in list: Linux
-
- -L 5901:localhost:5901 : Specifies that the given port on the local (client) host is to be forwarded to the given host and port on the remote side. Here you are using port 5901 on the localhost to be forward to sshserver.mydomain.com on the 5901 port.
- -N : Do not execute a remote command i.e. just forward ports.
- -f : Requests ssh to go to background just before command execution. Requests ssh to go to background just before command execution. Once password supplied it will go to background and you can use prompt for type commands on local system.
- -l rocky : rocky is the user to log in as on the remote machine (sshserver.mydomain.com).
- sshserver.mydomain.com (192.168.1.100): Remote system with VNC server
$ ssh -L 5901:localhost:5901 -N -f -l rocky sshserver.mydomain.com
OR
$ ssh -L 5901:127.0.0.1:5901 -N -f -l rocky 192.168.1.100Where,
Hi,
use
Code:
ps -ax
to determine process id. And then use
Code:
kill process_id
in list: Linux
-
Hi,
useto determine process id. And then useCode:ps -ax
Code:kill process_id
-
It seems impossible but even the Google search has been blocked. So, to solve this unfortunate situation, we sit down and log onto our
REMOTE_HOSTlike that:worker@LOCAL_HOST:~$ ssh user@IP_NUMBER \\ -L 10080:www.google.com:80Just a few clicks in Firefox:
Edit -> Preferences -> Connection Settings -> Manual proxy configuration. Here we can put in theHTTP proxy serverfield:localhostand10080forport. If there has been some other values in those fields, we shall write them down. We may need to use them later on. I’ll call those extra settingsPROXY_SVRandPROXY_PORT.
"ds, the addition of boundary firewalls, and tightening of the number of allowed network ports, users need a method that is simple to configure, easy to operate and, above all, secure to a"
in list: Linux
Selected Tags
Related Tags
Top Contributors
Groups interested in linux
-
linux
Items: 92 | Visits: 142
Created by: Djiezes Kraaijst
-
troubleshooting
Items: 24 | Visits: 133
Created by: Kenyth Zeng
-
disk and file system activity, kernel and memory — Mac OS X
Focused mostly on Mac OS X, ...
Items: 11 | Visits: 133
Created by: Graham Perrin
Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »
Join Diigo