05-12-2009
Overheating is a concern indeed, since frying data is not always an option. Is there a way to protect oneself against overheating? Checking with another usb stick, the problem seems to have disappeared.
The more pertinent problem has been why the da0s1/da1s1 etc slices were not available, even when logged in as root?
10 More Discussions You Might Find Interesting
1. Linux
I got Puppy linux and installed it on a usb stick.
In the BIOS i selected to boot from USB-FDD but it goes to my HD and ignores the USB stick,
What going on ?? (2 Replies)
Discussion started by: perleo
2 Replies
2. Linux
Hello Everybody
I am planning to install Fedora core 8 on an extra PC I have; what I wanna do is to boot from a USB stick then install Fedora from an ISO image I already have via FTP. Could any one tell me how to create bootable USB Stick for Fedora as I already found how to install from FTP... (0 Replies)
Discussion started by: ahmed_nasr2001
0 Replies
3. UNIX for Dummies Questions & Answers
I have a P-Series Machine running AIX 5.3, it has a USB Port on the front of the server, can I use a USB Stick on AIX platforms?? if so how..:rolleyes: (2 Replies)
Discussion started by: BEVAN
2 Replies
4. Filesystems, Disks and Memory
Dummies questions, perfect for this. I cannot mount my idiotic usb stick on Slackware, I input the following on non-graphic mode as root:
Mount -t vfat /dev/sdc1/usbstick
usbstick is the folder i created for mounting my USB, the file system is FAT, and everytime I input that I get some kind... (2 Replies)
Discussion started by: Dax01
2 Replies
5. BSD
When mounting a USB stick or pen drive on a FreeBSD machine I always issue the following command:
mount -t msdosfs /dev/da0s1 /mnt
Something I have always wondered is what the option msdosfs stands for and more importantly, why it is necessary. (7 Replies)
Discussion started by: figaro
7 Replies
6. Shell Programming and Scripting
Hello,
i am using a solaris thinclient that tries to connecting to a terminalserver. (RDP) Everything works fine, but the usb redirection. If i put in a usb stick i always get 2 usb-drives mounted. If i look in /tmp/SUNWut/mnt/<name of the host> i see 2 devices. One with the name of the... (2 Replies)
Discussion started by: anarcy
2 Replies
7. Ubuntu
Hey Guys
I have an Ubuntu CD and I was thinking of creating like a bootable hard drive with various OS so that I can just boot OSs with t drive and not require the CDs. I was just wondering is there a way I can do this, like have Ubuntu boot from a USB stick? If yes how is that possible(even if I... (3 Replies)
Discussion started by: rbansal2
3 Replies
8. SCO
hi
Howto mount an USB stick under SCO 5.0.7?
BTW ist it possible to mount USB stick in the command line using 'tools' at the Boot: prompt from OpenServer Release 5.0.7 installation CD? (1 Reply)
Discussion started by: ccc
1 Replies
9. SCO
I am trying to use a USB (Pen?) drive on Unixware 7.1.4.
The USB stick is in the machine and the machine recognises it when I enter usbprobe as follows:
Path - Address Description
-----------------------------
+++++++ BUS #2
0 - 1 - HUB "UHCI Root Hub"
1 - 2 - HID "Chicony Wireless Device"... (1 Reply)
Discussion started by: BernP
1 Replies
10. BSD
I would probably set all my rubber points here to get some real help for creating a boot device on a usb-stick. There is no CD-drive on this machine, thats why I need to use a usb-stick. And scrumming in a CD-drive to fuddle around in the fstab or something like that is out of reach.
My wisdom so... (9 Replies)
Discussion started by: 1in10
9 Replies
LEARN ABOUT OPENSOLARIS
fbtab
logindevperm(4) File Formats logindevperm(4)
NAME
logindevperm, fbtab - login-based device permissions
SYNOPSIS
/etc/logindevperm
DESCRIPTION
The /etc/logindevperm file contains information that is used by login(1) and ttymon(1M) to change the owner, group, and permissions of
devices upon logging into or out of a console device. By default, this file contains lines for the keyboard, mouse, audio, and frame buffer
devices.
The owner of the devices listed in /etc/logindevperm is set to the owner of the console by login(1). The group of the devices is set to the
owner's group specified in /etc/passwd. The permissions are set as specified in /etc/logindevperm.
If the console is /dev/vt/active, the owner of the devices is the first user logged in on the consoles (/dev/console or /dev/vt/#). Upon
this first user's logout the owner and group of these devices is reset by ttymon(1M) to owner root and root's group as specified in
/etc/passwd.
Fields are separated by a TAB or SPACE characters. Blank lines and comments can appear anywhere in the file; comments start with a hash-
mark, (#), and continue to the end of the line.
The first field specifies the name of a console device (for example, /dev/console). By default, it is /dev/vt/active, which points to the
current active console, including /dev/console and all virtual consoles (/dev/vt/#). The second field specifies the permissions to which
the devices in the device_list field (third field) are set. These permissions must be expressed in octal format, for example, 0774. A
device_list is a colon-separated list of device names. A device name must be a /dev link.
A directory or logical name in the device name can be either one of the following:
o A fully qualified name, for example, fbs.
o A regular expression, for example, [a-z0-9.]+. See regexp(5) for more information on regular expressions.
o The wildcard character * specifying all directory or node names (except . and .., for example, /dev/fbs/* specifies all frame
buffer devices.
Some examples of /etc/logindevperm file entries include:
/dev/usb/[0-9a-f]+[.][0-9a-f]+/[0-9]+/[a-z0-9.]+
/dev/usb/[0-9a-f]+[.][0-9a-f]+/[0-9]+/*
/dev/usb/[0-9a-f]+[.][0-9a-f]+/*/*
Specify all ugen(7D) endpoints and status nodes.
Drivers can also be specified to limit the permission changes to minor nodes owned by the specified drivers. For example,
/dev/console 0600 /dev/usb/[0-9a-f]+[.][0-9a-f]+/[0-9]+/*
driver=usb_mid,scsa2usb,usbprn # libusb devices
Due to the persistence of devfs(7FS) minor node management, the user should be logged in as root if the list of minor nodes will be reduced
and the devices should all be plugged in.
Once the devices are owned by the user, their permissions and ownership can be changed using chmod(1) and chown(1), as with any other user-
owned file.
Upon logout the owner and group of these devices are reset by ttymon(1M) to owner root and root's group as specified in /etc/passwd (typi-
cally other). The permissions are set as specified in the /etc/logindevperm file.
FILES
/etc/passwd File that contains user group information.
SEE ALSO
chmod(1), chown(1), login(1), ttymon(1M), passwd(4), regexp(5), ugen(7D)
NOTES
/etc/logindevperm provides a superset of the functionality provided by /etc/fbtab in SunOS 4.x releases.
SunOS 5.11 25 Sep 2008 logindevperm(4)