11-19-2010
Quote:
Originally Posted by
Corona688
What devices it finds (or
doesn't find) seems quite related to me!
And the message might possibly mean something different than you think it means, but I can't tell that if you omit it or rephrase it according to your understanding of it. I know you can't copy/paste from a crashed terminal prompt, but still; paraphrased error messages are a big pet peeve of mine.
Yeah ok,
maybe it
does
But I can't tell you anything new until monday :/ And I can't test it until mondey
And btw thanks for helping me again Corona
Last edited by al0x; 11-19-2010 at 02:12 PM..
9 More Discussions You Might Find Interesting
1. Linux
Hi all
I have a usb external drive with two partitions sdb1 ntfs and sdb2 ext3 with label Linux
I copied a knoppix live distro in the second partition, then I installed grub on the drive. Now in the directory /media/sdb2/boot/grub i have the file device.map with the following content:
(hd0) ... (4 Replies)
Discussion started by: guast
4 Replies
2. UNIX for Dummies Questions & Answers
Alright. Here we go...
The other day, I was referred to this neat little command-line Unix simulator called Cygwin. To put it lightly, I fell in love. I found Knoppix, and from what I can tell, it's a viable OS once I strip off the KDE desktop environment to make it 'old-school'. I'm... (2 Replies)
Discussion started by: dev_squid
2 Replies
3. UNIX for Dummies Questions & Answers
Is there an easy way to setup a cross-over cable (USB-USB) between a linux box and a windows PC? My 2 machines are next to each other but I really do not want to keep transfering my files using my USB drive.
Thanks! (4 Replies)
Discussion started by: Xterra
4 Replies
4. Red Hat
im using Dell Inspiron with windows 7 as operating system.....in my hard drive there is some 34 gb unpartitioned space and now i want to install fedora 13 into it, after installation it should be dual boot.
problem here is...
i have the fedora 13 image file ie fedora13-i386-DVD.iso file.
... (13 Replies)
Discussion started by: karthik437
13 Replies
5. UNIX for Dummies Questions & Answers
I have 2 computers, from now on i shall call these computers A and B.
Made a live linux distro (bodhi) on A which has 1GB internal memory , because windows is unstable on B, which has 512MB internal memory.
I mean with memory the internal memory of the computer, not the memory of the usb... (0 Replies)
Discussion started by: anno
0 Replies
6. BSD
Hello. I'm going to make freebsd live usb based on FreeBSD-8.3-RELEASE-i386-livefs.iso. The iso is 257 Megabytes, but after i copy its content to usb drive its volume increases to 971 Megabytes. I tried different methods of copying (tar,cp,cpio) but with the same result. Could anyone help? (0 Replies)
Discussion started by: urello
0 Replies
7. Solaris
I am trying to create a live image of solaris 11.1.
I have used #pkg image-update to upgrade from 11 to 11.1 already. (since only 11.1 can make images of 11.1 due to using new grub)
then from within 11.1 I used pkg install install distribution-constructor
to get latest usbcopy that should be... (1 Reply)
Discussion started by: taltamir
1 Replies
8. Solaris
Hello All,
I am attempting to boot and install Solaris 11 via live USB on a HP DL580 Gen9 Server.
Unfortunately, when I do this it boots into System Maintenance Mode.
The attachment (Pic1) shows what I am seeing via the console.
The BIOS is in UEFI boot. Does not work on legacy mode as I... (15 Replies)
Discussion started by: Kerbi
15 Replies
9. What is on Your Mind?
Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates
In this version of the UserCP, I have changed "Live Chat" to "Live Updates" by disabling the ability to post in the "live chat" area and changed the name to "Live Updates"
The reason for this change is that experienced... (6 Replies)
Discussion started by: Neo
6 Replies
LEARN ABOUT SUNOS
ttysrch
ttysrch(4) File Formats ttysrch(4)
NAME
ttysrch - directory search list for ttyname
DESCRIPTION
ttysrch is an optional file that is used by the ttyname library routine. This file contains the names of directories in /dev that contain
terminal and terminal-related device files. The purpose of this file is to improve the performance of ttyname by indicating which subdirec-
tories in /dev contain terminal-related device files and should be searched first. These subdirectory names must appear on separate lines
and must begin with /dev. Those path names that do not begin with /dev will be ignored and a warning will be sent to the console. Blank
lines (lines containing only white space) and lines beginning with the comment character "#" will be ignored. For each file listed (except
for the special entry /dev), ttyname will recursively search through subdirectories looking for a match. If /dev appears in the ttysrch
file, the /dev directory itself will be searched but there will not be a recursive search through its subdirectories.
When ttyname searches through the device files, it tries to find a file whose major/minor device number, file system identifier, and inode
number match that of the file descriptor it was given as an argument. If a match is not found, it will settle for a match of just
major/minor device and file system identifier, if one can be found. However, if the file descriptor is associated with a cloned device,
this algorithm does not work efficiently because the inode number of the device file associated with a clonable device will never match
the inode number of the file descriptor that was returned by the open of that clonable device. To help with these situations, entries can
be put into the /etc/ttysrch file to improve performance when cloned devices are used as terminals on a system (for example, for remote
login). However, this is only useful if the minor devices related to a cloned device are put into a subdirectory. (It is important to note
that device files need not exist for cloned devices and if that is the case, ttyname will eventually fail.) An optional second field is
used in the /etc/ttysrch file to indicate the matching criteria. This field is separated by white space (any combination of blanks or
tabs). The letter M means major/minor device number, F means file system identifier, and I means inode number. If this field is not speci-
fied for an entry, the default is MFI which means try to match on all three. For cloned devices the field should be MF, which indicates
that it is not necessary to match on the inode number.
Without the /etc/ttysrch file, ttyname will search the /dev directory by first looking in the directories /dev/term, /dev/pts, and /dev/xt.
If a system has terminal devices installed in directories other than these, it may help performance if the ttysrch file is created and con-
tains that list of directories.
EXAMPLES
Example 1: A sample display of /etc/ttysrch command.
A sample /etc/ttysrch file follows:
/dev/term MFI
/dev/pts MFI
/dev/xt MFI
/dev/slan MF
This file tells ttyname that it should first search through those directories listed and that when searching through the /dev/slan direc-
tory, if a file is encountered whose major/minor devices and file system identifier match that of the file descriptor argument to ttyname,
this device name should be considered a match.
FILES
/etc/ttysrch
SEE ALSO
ttyname(3C)
SunOS 5.10 23 Feb 1994 ttysrch(4)