Hmm, I hadn't considered using a link but that would definitely do the trick.
Ok, so I copied an existing rule on /etc/udev/rules.d/ and modified it a bit just to test the behavior, then I ran udevcontrol reload_rules but I don't see the link getting created under /dev/disk/by-id (which is the path I used for my rule).
hi,
1) is logical partition the same as physical partition except that one is physical and the other is logical?
2) then it must a one to one ratio? (3 Replies)
I've created a partition with GNU Parted, how do I mount the partition?
The manual information at http://www.gnu.org/software/parted/manual/parted.html is good, but I am sure about how I mount the partition afterwards.
Thanks,
--Todd (1 Reply)
Hi all
i got this filesystem
Filesystem size used avail capacity Mounted on
/dev/dsk/c0t600A0B80001F350A000033404A5D29D9d0s2
492G 64M 487G 1% /u10
How do i change the name for /dev/dsk/c0t600A0B80001F350A000033404A5D29D9d0s2 to the... (3 Replies)
Gentleman,
Please move if I have chose the incorrect forum section. I am trying to move data that is not backed up from partition 1 to partition 2 on a SAN that has a GFS2 filesystem. Since the data is not backed up I am rsyncing this data and once verified I will delete from the source... (6 Replies)
Hi folks,
is there any possibility how to rename soft partitions??
Here I found that this is not possible (I know that it is) but I need do it in some supported way.
http://dlc.sun.com/osol/docs/content/LOGVOLMGRADMIN/tasks-basics-5.html
This is production system it is why I need do it... (0 Replies)
hi all
while formatting hard disk i am getting following error.
Partition 1 ends at 266338338
It must be between 34 and 143374704.
label error: EFI Labels do not support overlapping partitions
Partition 8 overlaps partition 1.
Warning: error writing EFI.
Label failed.
I have formatted the... (2 Replies)
Hi Experts
I would like to know different between soft partition concept and hard partition concept on solaris.
Here is little explanation between soft partition concept and hard partition concept on solaris.
Soft Partition:
1TB total space available in storage in all mapped to the OS to... (2 Replies)
Hello All,
I have a Red Hat Linux 5.9 Server installed with one hard disk & 2 Partitions created on it as follows,
/boot - Linux Partition & another is
LVM - One VG & under that 5-6 Logical volumes(var,opt,home etc).
Here my requirement is to take out 1GB of space from LVM ( Any logical... (5 Replies)
Discussion started by: gr8_usk
5 Replies
LEARN ABOUT BSD
symlink
SYMLINK(2) System Calls Manual SYMLINK(2)NAME
symlink - make symbolic link to a file
SYNOPSIS
symlink(name1, name2)
char *name1, *name2;
DESCRIPTION
A symbolic link name2 is created to name1 (name2 is the name of the file created, name1 is the string used in creating the symbolic link).
Either name may be an arbitrary path name; the files need not be on the same file system.
RETURN VALUE
Upon successful completion, a zero value is returned. If an error occurs, the error code is stored in errno and a -1 value is returned.
ERRORS
The symbolic link is made unless on or more of the following are true:
[ENOTDIR] A component of the name2 prefix is not a directory.
[EINVAL] Either name1 or name2 contains a character with the high-order bit set.
[ENAMETOOLONG] A component of either pathname exceeded 255 characters, or the entire length of either path name exceeded 1023 characters.
[ENOENT] The named file does not exist.
[EACCES] A component of the name2 path prefix denies search permission.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[EEXIST] Name2 already exists.
[EIO] An I/O error occurred while making the directory entry for name2, or allocating the inode for name2, or writing out the link
contents of name2.
[EROFS] The file name2 would reside on a read-only file system.
[ENOSPC] The directory in which the entry for the new symbolic link is being placed cannot be extended because there is no space left
on the file system containing the directory.
[ENOSPC] The new symbolic link cannot be created because there there is no space left on the file system that will contain the sym-
bolic link.
[ENOSPC] There are no free inodes on the file system on which the symbolic link is being created.
[EDQUOT] The directory in which the entry for the new symbolic link is being placed cannot be extended because the user's quota of
disk blocks on the file system containing the directory has been exhausted.
[EDQUOT] The new symbolic link cannot be created because the user's quota of disk blocks on the file system that will contain the
symbolic link has been exhausted.
[EDQUOT] The user's quota of inodes on the file system on which the symbolic link is being created has been exhausted.
[EIO] An I/O error occurred while making the directory entry or allocating the inode.
[EFAULT] Name1 or name2 points outside the process's allocated address space.
SEE ALSO link(2), ln(1), unlink(2)4.2 Berkeley Distribution August 26, 1985 SYMLINK(2)