I have a large file with the first 2 characters of each line determining the type of record. type 03 being a subheader and then it will have multiple 04 records.
eg: 03,xxx,xxxx,xxxx
04,xxxxxxxxxxxxxxxxxxxxxxxxxxxx
04,xxxxxxxxxxxxxxxxxxxxxxxxxxxx
03,xxx,xxx,xxx
... (2 Replies)
Hi
I am using awk command for string replacement.
I have 2 servers. The command runs perfectly well on 1st server
On the second server when i run the command on the same datset
The command gets stuck while processing a large piece of record..
Does it have anything to with setting on the 2... (1 Reply)
Hi Gurus,
I tried FTP one file to UNIX which got values like
wel^come
If I see the content in unix, it shows like
wel^Zcome
^ coverted into ^Z (Control + Z )
Can someone please share what is happening here?
Thanks,
Shahnaz (5 Replies)
I have two servers on same domain. one can nslookup other cannot
Psu100 can lookup to psu000, psu010 & psu011
Psu110 can NOT lookup to psu000, psu010 & psu011
I verified resolv.conf entries on both psu000 and psu010 and it contains both name servers (10.200.10.21 & 10.200.11.22).I am... (1 Reply)
Hi,
I need to count number of '$' symbol in a file and assign it to a variable.
I am using below command.
grep -c '\$' inputfile
O/p:
10359
Its giving correct o/p but when I am assigning the same to a variable its giving completely different o/p.
ab1=`grep -c '\$' inputfile`
$... (3 Replies)
Here is my test script:
#!/bin/sh
result=`jobs`
echo "
Jobs:
"$result
result=`ls`
echo "
LS
"$result
Here is the output:
Jobs:
LS
0 1 2 3 4 5 6 7 gcd initialize.sh #inter_round_clean.sh# inter_round_clean.sh inter_round_clean.sh~ look parallel_first_run.sh... (3 Replies)
Hi,
We have few hundered scripts using cut command in thousands of lines. On HP-UX shell script developer used echo "ABCEFG" | cut -c -1-3 to cut first three character of the string. We recently moved to Linux and this command throws error. I think this might be due to different version of... (3 Replies)
Hi,
Immediate help on below will be appreciated.
I have to read a file (max of 10MB) which will have no new line characters, i.e. data in single line. and have to inster '\n' at every 100 characters. and if record starts with 'BUCA' then need to pick value of length 10 at position 71 and... (7 Replies)
Can anyone explain why wc is behaving weirdly? Their are only 2 occurrences but wc thinks their are 7 occurrences. I have even manually checked this.
$ grep -i base *
lit: base xx
lit.lst:003- 00103 BASE XX
$ grep -i base * | wc -w ... (2 Replies)
Discussion started by: cokedude
2 Replies
LEARN ABOUT NETBSD
drm
DRM(4) BSD Kernel Interfaces Manual DRM(4)NAME
drm -- Direct Rendering Manager (DRI kernel support)
SYNOPSIS
i915drm* at vga?
mach64drm* at vga?
mgadrm* at vga?
r128drm* at vga?
radeondrm* at vga?
savagedrm* at vga?
sisdrm* at vga?
tdfxdrm* at vga?
viadrm* at vga?
options DRM_DEBUG
options DRM_NO_AGP
DESCRIPTION
The Direct Rendering Manager is part of the Direct Rendering Infrastructure (see http://dri.freedesktop.org/) for supporting video accelera-
tion (3d acceleration, mostly).
The drm drivers provide support for the following chipsets:
i915drm Intel i915, i945
mach64drm Mach64 (3D Rage Pro, Rage)
mgadrm Matrox G[24]00, G[45]50
r128drm ATI Rage 128
radeondrm ATI Radeon
savagedrm S3 Savage
sisdrm SiS
tdfxdrm 3dfx (Voodoo)
viadrm VIA
To make use of the driver, the kernel must include agp(4) (for some drivers, using options DRM_NO_AGP instead may be sufficient), X(7) must
be compiled with DRI support, Mesa DRI drivers must be installed, the appropriate /dev/dri/card* device must exist, and DRI must be enabled
in the X configuration file. X(7) provided with NetBSD and compiled from pkgsrc(7) do so automatically where supported.
X(7) will attempt to create the device node automatically. To create the device node manually:
mkdir -p /dev/dri
mknod /dev/dri/card0 c 180 0
chgrp wheel /dev/dri/card0
chmod 0660 /dev/dri/card0
To enable DRI in the X configuration add the following to either xorg.conf for Xorg(1) or XF86Config for XFree86(1) :
Section "Module"
...
Load "dri"
Load "dri2"
Load "glx"
EndSection
...
Section "DRI"
Group "wheel"
Mode 0660
EndSection
Debugging output can be enabled and disabled by setting the sysctl(8) node hw.dri.debug. Additional information can be obtained from the
sysctl(8) nodes hw.dri, hw.dri.card0, hw.dri.card1, etc.
SEE ALSO XFree86(1), Xorg(1), agp(4), XF86Config(5), xorg.conf(5), X(7), /usr/X11R[67]/lib/X11/doc/README.DRI
HISTORY
DRM was first available for Linux. Subsequently Eric Anholt ported the DRM kernel modules to FreeBSD. Erik Reid adapted the FreeBSD DRM
kernel modules to NetBSD. As DRM continued to develop the NetBSD support was neglected. Tonnerre Lombard got the DRM modules working again,
but DRM development once again left the NetBSD support behind. Finally Yorick Hardy took the FreeBSD DRM source and managed to get it com-
piling and working again on NetBSD, thanks largely to the efforts of all those mentioned above. Subsequently Matthias Drochner improved the
DRM file hierarchy for NetBSD and committed the DRM kernel drivers. Matthew Green cleaned up this port and merged a set of newer drivers,
with Arto Huusko and FUKAUMI Naoki helping to get the latest Mesa port up to date.
The drm drivers appeared in NetBSD 5.0.
AUTHORS
Eric Anholt, Terry Barnaby, Erdi Chen, Michel Daenzer, Leif Delgass, Frank C. Earl, Rickard E. Faith, Jose Fonseca, Nicolai Haehnle, Jeff
Hartmann, Thomas Hellstrom, Gareth Hughes, Felix Kuehling, Sung-Ching Lin, Kevin E. Martin, Jared D. McNeill, Daryll Strauss, Keith Whitwell
CAVEATS
In case of errors, /dev/dri/card0 may be changed, make sure to recreate it in that case.
options DRM_DEBUG can slow DRI down a lot; disable it once drm works.
BSD May 11, 2010 BSD