02-12-2010
Maybe silly..., but have you tried to convert your .txt file using dos2ux or similar before any further processing?
9 More Discussions You Might Find Interesting
1. AIX
Hi all, my RS/6k 7043 150 with aix 4.3.3 takes FOREVER to log in. When I power the machine on, the boot process procedes normally and I get 2 short beeps (which I don't recall hearing before) and then I get the login window. If I log in, as root, say, the machine goes to its usual blue screen... (3 Replies)
Discussion started by: Jwoollard
3 Replies
2. Programming
When I am using msgrcv to get a message from a queue, in case of msgsnd some error, the msgrcv thread will waiting forever.
Is there some way that I can specify a time out value for this queue ? just let msgrcv wait for some time, if no message comes during this time slot, msgrcv just return... (3 Replies)
Discussion started by: Yun Gang Chen
3 Replies
3. Solaris
Hi I am very new for Solaris, I want to make some users' passwords never expired. My ssytem kernel is: 5.8
# uname -a
SunOS sspfs_svr 5.8 Generic_117000-01 sun4u sparc SUNW,Netra-240
Could you make some advice?
Thanks (5 Replies)
Discussion started by: xramm
5 Replies
4. UNIX for Dummies Questions & Answers
Hello all
i found out about the sar command but when looking in the man pages
there is no way to make sar working for ever .. only
with some kind of interval . like sar 2 30 .
my question is can i just run sar for ever ? (5 Replies)
Discussion started by: umen
5 Replies
5. Linux
Hi guys! I've just mounted my drive in fstab:
/dev/sdb /myfolder ext3 defaults 0 0
and rebooted linux.
I've got severel failers during booting process and also I can't login as root first time:
login: root
password:root
incorrect login
login:user
password: user
... (1 Reply)
Discussion started by: Junior Admin
1 Replies
6. IP Networking
Just looking at my ethernet interface.. I see this response... what does this mean...?
ipconfig...
lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft... (0 Replies)
Discussion started by: jimmyc
0 Replies
7. Programming
looking in pthread's source code I can see that as an epilogue both pthread_cond_timedwait and pthread_cond_wait will try to relock the mutex by means of __pthread_mutex_cond_lock.
Does this mean that any of them both could eventually block forever if the mutex is never again available after... (4 Replies)
Discussion started by: ramestica
4 Replies
8. Red Hat
Hello All,
I was trying to install one rpm and it failed due to missing dependencies, when I try to look at the dependencies and try to install them it is asking for 100+ dependencies, did any one ever face this problem? how can we fix this?
rpm -ivh /var/tmp/erlang-R15B-02.1.el6.x86_64.rpm... (0 Replies)
Discussion started by: lovesaikrishna
0 Replies
9. UNIX for Dummies Questions & Answers
I am trying to use the forever command. I can get it to work if I do not use the w option to watch for changes and cause an automatic restart on a change to the contents of the directory being watched.
I would really like to use the watch option. Is this option fully implemented? here is an... (4 Replies)
Discussion started by: barrygordon
4 Replies
dosif(4) Kernel Interfaces Manual dosif(4)
NAME
DOSIF - DOS interchange format
DESCRIPTION
The DOS Interchange Format (DOSIF) is the name given to the media format used by the DOS operating system. This format is based upon that
used in IBM PC and PC AT and HP Vectra systems.
Use the and commands to convert files between HP-UX and DOS file formats; see dos2ux(1). Use these utilities to retrieve information from
a DOSIF volume.
The dos*(1) utilities are the only HP-UX commands that can interact directly with the contents of a DOSIF volume. The only other way to
interact with the contents of a DOSIF volume is to use an HP-UX DOS emulation or coprocessor facility such as SoftPC or the DOS Coproces-
sor. The command cannot be used on a DOSIF volume because the operating system does not recognize it (see mount(1M)).
When constructing file names for the dos*(1) commands, start with the HP-UX path name of the DOSIF volume, then add a colon followed by the
file name:
or
This file naming convention is suitable for use only in arguments of the dos*(1) utilities. It does not constitute a legal path name for
any other use in HP-UX applications.
Metacharacters and can be used when specifying both HP-UX and DOS file names. These must be quoted when specifying a DOS file name,
because file name expansion is performed by the DOS utilities, not by the shell. The dos*(1) utilities expand file names as described in
regexp(5) in the section.
By convention, if the HP-UX device name and a trailing colon are specified, but no file or directory name is provided (for example, the
root of the DOS file system is assumed.
EXAMPLES
Example 1
Specify DOSIF file accessed through HP-UX special file
Example 2
Specify DOSIF file accessed through the DOS volume stored as HP-UX file
SEE ALSO
dos2ux(1).
dosif(4)