03-15-2012
In the meanwhile I found out, that setting the group of the device to "root" instead of "db2usrl1" makes the udev rule work as expected. The device mode is correctly set to 0600.
But changing the group back to anything else but "root" and ... peng ... the device mode goes back to 0660.
When you want NO access for a group, it doesn't really matter, which group it is, that has no access. So I can live with this. But I still wonder, what might cause this behaviour. The word "bug" comes to mind. Or is there something I do not get?
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a directory. To this directory, for Group bits combination, it is showing as 's'. Which I found out, it means "Set User ID on execution mode". Within this directory I am not able to create subfolder.
Does it mean, only the Owner of this directory will be able to create subdirectories &... (5 Replies)
Discussion started by: videsh77
5 Replies
2. Shell Programming and Scripting
hi all,
is there somebody that know how can I set an permanently option for the lynx text browser?
The reason is if I open some URL's and type my login infos
then lynx show follow message:
P)roceed, use G)ET or C)ancel
Server asked for 301 redirection of POST content to
URL: The UNIX... (1 Reply)
Discussion started by: research3
1 Replies
3. Solaris
Hi all,
I don't want to enter below command on solaris every time.
How do i permanently set this command on Solaris.
I know that this operation is a piece of cake on redhat because there is a /etc/rc.local file on it.
But Solaris ????
bash-3.00#export PS1="\e (2 Replies)
Discussion started by: getrue
2 Replies
4. Linux
Hello,
whenever I plugin my webcam, I want to use its microphone instead of the one integrated in my laptop.
I therefore created a udev rule:
SUBSYSTEM=="usb", ATTR{idVendor}=="046d", ATTR{idProduct}=="0807", RUN+="/usr/local/bin/webcammic"This rule works, I've tested it with a testscript (the... (0 Replies)
Discussion started by: MojoDodo
0 Replies
5. Solaris
Hi ,
How to set autolist permanently in Solaris 10 (2 Replies)
Discussion started by: ankit.padhiyar
2 Replies
6. AIX
Hi,
I've a 32-bit program running on AIX. By default the memory limit of the process is 256 MB as per the 32-bit AIX OS behavior. This can be changed using the LDR_CNTRL=maxdata environment variable. Baseed on the value that we set in terms of increments of segments the process... (6 Replies)
Discussion started by: kprajesh
6 Replies
7. Red Hat
I need to add a VMware virtual disk to the 99-oracle-asmdevices.rules file but the OS is not assigning a WWID to the disk. It has been fdisk'd and a single partition created.
What TAG inside the file needs to be added? the Program scsi-id does not work for some reason. latest patches... (0 Replies)
Discussion started by: mrmurdock
0 Replies
8. Web Development
hi
i have code in iplanet webserver in obj.conf file
<If $uri !~'^/app/literature/item/(.*)'>
AuthTrans fn="set-variable" insert-srvhdrs="X-UA-Compatible:IE=EmulateIE8"
</If>
i want to migrate it to apache webserver need your help to replace the above code for apache webserver.
i... (0 Replies)
Discussion started by: raghur77
0 Replies
lofi(7D) Devices lofi(7D)
NAME
lofi - Loopback file driver
DESCRIPTION
The lofi file driver exports a file as a block device. Reads and writes to the block device are translated to reads and writes on the
underlying file. This is useful when the file contains a file system image. Exporting it as a block device through the lofi file driver
allows normal system utilities to operate on the image through the block device (like fstyp(1M)fsck(1M), and mount(1M). This is useful for
accessing CD-ROM and FAT floppy images. See lofiadm(1M) for examples.
File block device entries are contained in /dev/lofi, while /dev/rlofi contains the character (or raw) device entries. Entries are in the
form of decimal numbers which are assigned through lofiadm(1M). When created, these device entries are owned by root, in group sys, and
have permissions 0600. While ownership, group, and permission settings can be altered, there are possible ramifications. See lofiadm(1M)
for more information.
FILES
/dev/lofictl
Master control device
/dev/lofi/n
Block device for file n
/dev/rlofi/n
Character device for file n
/kernel/drv/lofi
32-bit driver
/kernel/drv/lofi.conf
Driver configuration file. (Should not be altered.)
/kernel/drv/sparcv9/lofi
64-bit driver
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsr, SUNWcarx.u |
+-----------------------------+-----------------------------+
SEE ALSO
lofiadm(1M), fsck(1M), fstyp(1M), mount(1M), newfs(1M), attributes(5), lofs(7FS)
NOTES
Just as you would not directly access a disk device that has mounted file systems, you should not access a file associated with a block
device except through the lofi file driver.
For compatability purposes, a raw device is also exported along with the block device. For example, newfs(1M) requires one.
SunOS 5.10 30 Jul 1999 lofi(7D)