I recently got this new old server from a friend. I just installed a fresh version of Solaris 10 on it. I have put a static IP of 192.168.100.10 the server. Their is no subnetting scheme on the network. And I made the hostname "SunServ." And I also changed the folder "/etc/inet/hosts" because I... (4 Replies)
Hey All,
Let me start out w/ I have serched the forums and found this to be a typical problem. None of the threads have been able to help in my situation though.
I know cc or gcc needs to be installed in ...bin]# (or lead the path of the app to wherever gcc is when compiling) so the app can... (4 Replies)
Hi,
This is odd, however here goes. There are several shell scripts that run in our production environment AIX 595 LPAR m/c, which has sufficient memory 14GB (physical memory) and horsepower 5CPUs. However from time to time we get the following errors in these shell scripts. The time when these... (11 Replies)
Hi All,
I'm actually trying to configure a Qlogic HBA on a solaris9 connecting in a Brocade SAN. I installed Solaris9 and now trying to look at FC devices..
bash-2.05# luxadm -e port
Found path to 0 HBA ports
bash-2.05# luxadm probe
No Network Array enclosures found in /dev/es... (7 Replies)
I don't know if there's a better name for what I call "file collision"... Basically, I have a script that I'm using for quick and dirty MySQL testing. Here's the idea...
#!/usr/local/bin/bash
for num in `jot $1` ## Yep, jot... this is FreeBSD
do
/usr/bin/time mysql --user=root... (2 Replies)
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
If I enter (simplified):
find . -printf "%p\n"
then all files in the output are prepended by a "." like
./local/share/test23.log
How can achieve that
a.) the leading "./" is omitted
and/or
b.) the full path to the current directory is inserted (enclosed by brackets and a blank)... (1 Reply)
These three finds worked as expected:
$ find . -iname "*.PDF"
$ find . -iname "*.PDF" \( ! -name "*_nobackup.*" \)
$ find . -path "*_nobackup*" -prune -iname "*.PDF"
They all returned the match:
./folder/file.pdf
:b:
This find returned no matches:
$ find . -path "*_nobackup*" -prune... (3 Replies)
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
LEARN ABOUT HPUX
dosif
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)