07-04-2002
UNIX machine is connected to several file systems, each with its own i-list. One of those i-lists points to a special storage area, known as the root file system. The root file system contains the files for the operating system itself, and must be available at all times. Other file systems are removable. Removable file systems can be attached, or mounted, to the root file system. Typically, an empty directory is created on the root file system as a mount point, and a removable file system is attached there. When you issue a cd command to access the files and directories of a mounted removable file system, your file operations will be controlled through the i-list of the removable file system.
Each file system that is mounted on a UNIX machine is accessed through its own block special file. The information on each of the block special files is kept in a system database called the file system table, and is usually located in /etc/fstab. It includes information about the name of the device, the directory name under which it will be mounted, and the read and write privileges for the device. It is possible to mount a file system as "read-only," to prevent users from changing anything.
Example: Important File system Used by HP-UX
/hp-ux
The kernel program
/dev/
Where special files are kept
/bin/
Executable system utilities, like sh, cp, rm
/etc/
System configuration files and databases
/lib/
Operating system and programming libraries
/tmp/
System scratch files (all users can write here)
/lost+found/
Where the file system checker puts detached files
/usr/bin/
Additional user commands
/usr/include/
Standard system header files
/usr/lib/
More programming and system call libraries
/usr/local/
Typically a place where local utilities go
/usr/man
The manual pages are kept here
Also pls do re-define your question on 'format' Is it a filesystem format? floppy format? hard disk format?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Can anyone help me? I have 2 servers on the same LAN, one as a live server and one as a backup server, both running SCO OpenServer Enterprise. I need to mount the /u filesystem of the backup server as a directory on the live server, so that if I use the df -v command I can see it as an additional... (1 Reply)
Discussion started by: darkestafrica
1 Replies
2. Filesystems, Disks and Memory
I'm installing SCO Unix Open Server 5.05 on an IBM 300PL Desktop with a 60Gig HDD (IDE) and 32 MB physical RAM.
When the install goes to the phase where the hard disk needs to be partitioned, I can only see 8 Gig out of the 60Gig that I have on the mahine.
I have tried the option of display... (2 Replies)
Discussion started by: budrito
2 Replies
3. Filesystems, Disks and Memory
someone help me to figure out about this error
i´m installing a 36Gb SCSI Hd and i used the custom option in unixSCO for create the diferents filesystems, when the process is finish the next error message apears:
Exit value 139 status value -29952
Fatal error in disk info.c line 3525... (3 Replies)
Discussion started by: jav_v
3 Replies
4. UNIX for Dummies Questions & Answers
Hi,
we have a strange problem.
We have to format any floppy disk HD in unix filesystem mode (SCO) but we haven't unix workstations.
Are there any software to make this formatting from windows xp pc ?
Regards
Gianpaolo (1 Reply)
Discussion started by: elektra
1 Replies
5. UNIX for Dummies Questions & Answers
hello all,
i want to know about the unix file system. about the boot block,super block,and how to access them ,all the geometry details of the file systemetc etc...
where can i find this??? i'l b happy if u can help me with a link!!!!!
thanx in advance (2 Replies)
Discussion started by: anwerreyaz
2 Replies
6. UNIX for Dummies Questions & Answers
Hello again.
Please can someone tell me how can i check if my filesystem is raw on unix/linux ?
Is there some file to check or something like that to be sure ?
also ,
when i do :
$ ls -l /dev/rdisk
i get among other things , this also(there resides are oracle related files) :
... (2 Replies)
Discussion started by: tonijel
2 Replies
7. SuSE
Hi all.
Im migrating from a Unix 32 bit to a linux suse 10 64 bit and would like to know whats the best way to migrate the filesystems? cpio? tar? ftp? Could I make a backup in tape in the unix 32 and restore it in the linux 64?
thanx (1 Reply)
Discussion started by: mrodrig
1 Replies
8. UNIX for Dummies Questions & Answers
Hi all
Is there a way to copy a unix filesystem (folders, subfolder and files) to windows (AD) and at the same time maintaine the unix permission (user/group) when copied to windows (AD) filesystem?
I want the same permission in windows as I had in unix in one copy job.
Is this... (8 Replies)
Discussion started by: tomjen
8 Replies
9. Homework & Coursework Questions
1. The problem statement, all variables and given/known data:
The file system unix use a multilevel indexes access to disk, 12 direct blocks, 1 single indirect block, 1 double indirect block, 1 triple indirect block:
Assuming a:
block = 512 bytes,
pointer = 4 byte,
and there is a file of 200... (4 Replies)
Discussion started by: blob84
4 Replies
10. Solaris
I have been trying to fill all available file space on my Solaris box for my project but have not been successful. I have tried the following script:
tr '\0' '\060' < /dev/zero | dd of=zero2.txt bs=1024 count=1953125
But the only thing i get in return is this:
"d: bad numeric argument:... (8 Replies)
Discussion started by: rbur101
8 Replies
LEARN ABOUT DEBIAN
wipefs
WIPEFS(8) System Administration WIPEFS(8)
NAME
wipefs - wipe a filesystem signature from a device
SYNOPSIS
wipefs [-ahnpV] [-o offset] device
DESCRIPTION
wipefs can erase filesystem or raid signatures (magic strings) from the specified device to make the filesystem invisible for libblkid.
wipefs does not erase the filesystem itself nor any other data from the device. When used without options -a or -o, it lists all visible
filesystems and the offsets of their signatures.
OPTIONS
-a, --all
Erase all available signatures.
-h, --help
Print help and exit.
-n, --no-act
Causes everything to be done except for the write() call.
-o, --offset offset
Specify the location (in bytes) of the signature which should be erased from the device. The offset number may include a "0x" pre-
fix; then the number will be interpreted as a hex value. It is possible to specify multiple -o options.
The offset argument may be followed by binary (2^N) suffixes KiB, MiB, GiB, TiB, PiB and EiB (the "iB" is optional, e.g. "K" has the
same meaning as "KiB") or decimal (10^N) suffixes KB, MB, GB, PB and EB.
-p, --parsable
Print out in parsable instead of printable format. Encode all potentially unsafe characters of a string to the corresponding hex
value prefixed by 'x'.
-V, --version
Output version information and exit.
AUTHOR
Karel Zak <kzak@redhat.com>.
AVAILABILITY
The wipefs command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
SEE ALSO
blkid(8) findfs(8)
util-linux October 2009 WIPEFS(8)