02-03-2011
give only read and execute access by using 755.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I'm looking for a way to get the date of creation for a file. Is it possible ? I know that these informations are in the i-node but I don't know how to access them (if the 'find' command can do it with option -ctime, I have reasons to believe in it).
Thanks for helping me ! (1 Reply)
Discussion started by: mullmafr
1 Replies
2. UNIX for Dummies Questions & Answers
folks;
I created a new users on my SUSE box and i need to give this user/group a read write access to one specific folder. here's the details:
- I created new user "funny" under group "users".
- I need to give this user "funny" a read/write access to another directory that is owned by "root".... (3 Replies)
Discussion started by: Katkota
3 Replies
3. Red Hat
Hi
Thanks in advance.
How to create a user without useradd command ?? (1 Reply)
Discussion started by: krish4linux
1 Replies
4. Solaris
Hello guys,
i have a problem where i cant create a user and here some problem that i encounter.
1. /etc/passwd seems locked.
2. getting this error UX: useradd: ERROR: Cannot update system files - login cannot be created.
# useradd -u 47367 -g 1084 -c "user123" -d /local/home/user123 -s... (2 Replies)
Discussion started by: brew
2 Replies
5. Shell Programming and Scripting
hi,
how to create user name with read only access.
i think first need to create group with read only access after that i need to create the user and assign it to that group. If it is correct, how to create user with read only access? (4 Replies)
Discussion started by: rsivasan
4 Replies
6. AIX
hi seniors
i want to create the users like when the user try to login it should not
should not promt for passwd is it possible to create users like this
please help me (6 Replies)
Discussion started by: senmak
6 Replies
7. UNIX for Advanced & Expert Users
Hi,
I want to create files and directories with below access control
System. AIX
File should have 664 permission
Directories should have 755
Can you please let me know how to achieve this? (3 Replies)
Discussion started by: balasubramani04
3 Replies
8. Solaris
Hi All,
I want to configure samba share permission so that only directory creator/owner has a read and write permission and other users should not have any read/write access to that folder.Will that be possible and how can this be achieved within samba configuration.
Regards,
Sahil (1 Reply)
Discussion started by: sahil_shine
1 Replies
9. Shell Programming and Scripting
Hi All,
I would have many files in the server with
xyz*.dat -- Static file name
Physical files:
xyz1.dat - 01PM
xyz2.dat - 02PM
xyz3.dat - 03PM
In present version we are using
for f in $file_name
do
fname=`ls $f | grep -v ^'\|'$ | sed s/' '/'\\ '/g`
....
sqlldr... (4 Replies)
Discussion started by: Dharv
4 Replies
MKFS(1) General Commands Manual MKFS(1)
NAME
mkfs - make a file system
SYNOPSIS
mkfs [-Ldot] [-i inodes] [-b blocks] special prototype
OPTIONS
-L Make a listing on standard output
-d Use mod time of mkfs binary for all files
-o Use a drive other than 0 or 1 (safety precaution)
-t Do not test if file system fits on the medium
-1 Make a version 1 file system (for backward compatibility)
-i Number of i-nodes (files)
-b Filesystem size
EXAMPLES
mkfs /dev/fd1 proto # Make a file system on /dev/fd1
mkfs -b 360 /dev/fd1
# Make empty 360 block file system
mkfs /dev/fd1 360 # Alternate way to specify the size
DESCRIPTION
Mkfs builds a file system and copies specified files to it. The prototype file tells which directories and files to copy to it. If the
prototype file cannot be opened, and its name is just a string of digits, an empty file system will be made with the specified number of
blocks. A sample prototype file follows. The text following the # sign in the example below is comment. In real prototype files, com-
ments are not allowed.
boot # boot block file (ignored)
360 63 # blocks and i-nodes
d--755 1 1 # root directory
bin d--755 2 1 # bin dir: mode (755), uid (2), gid (1)
sh ---755 2 1 /user/bin/shell # shell has mode rwxr-xr-x
mv -u-755 2 1 /user/bin/mv # u = SETUID bit
login -ug755 2 1 /user/bin/login# SETUID and SETGID
$ # end of /bin
dev d--755 2 1 # special files: tty (char), fd0 (block)
tty c--777 2 1 4 0 # uid=2, gid=1, major=4, minor=0
fd0 b--644 2 1 2 0 360 # uid, gid, major, minor, blocks
$ # end of /dev
user d--755 12 1 # user dir: mode (755), uid (12), gid (1)
ast d--755 12 1 # /user/ast
$ # /user/ast is empty
$ # end of /user
$ # end of root directory
The first entry on each line (except the first 3 and the $ lines, which terminate directories) is the name the file or directory will get
on the new file system. Next comes its mode, with the first character being -dbc for regular files, directories, block special files and
character special files, respectively. The next two characters are used to specify the SETUID and SETGID bits, as shown above. The last
three characters of the mode are the rwx protection bits.
Following the mode are the uid and gid. For special files, the major and minor devices are needed. The size in blocks must also be speci-
fied for block special files (the MINIX block size is 1K; this can only be changed by changing BLOCK_SIZE and then recompiling the operat-
ing system).
The maximum size of a file system is 1 Gb for a version 2 file system, and 64 Mb for a version 1 file system. Alas the 8086 fsck runs out
of memory on a V2 file system larger than 128 Mb, so for the 8086 version of MINIX you have to limit yourself to file systems of that size.
SEE ALSO
mkproto(1), fsck(1), mount(1).
MKFS(1)