05-15-2008
I find that irritating, though.
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Does any1 hav the idea abt wat cause this bug in unix on jan 19th 2038??? please enlighten me abt it.... (2 Replies)
Discussion started by: bourne
2 Replies
2. Shell Programming and Scripting
hello all
im trying to use in sun Solaris the information received from the top command
now i several machines that dont have install the top program so when im running the script im geting error
saying after im running this code :
set MemoryInfo = `top | grep Memory`
if (... (2 Replies)
Discussion started by: umen
2 Replies
3. Shell Programming and Scripting
Hi All,
I am using Red Hat Linux on my servers. The problem that I am facing is, sometimes the /opt usage on the server shows used percentage as 100% , when actually it is simply 20%.
When I reboot the system, it comes back to 20%.Is this a bug in the system or my settings have gone wrong... (1 Reply)
Discussion started by: nua7
1 Replies
4. AIX
xxxxserver# lsattr -El inet0 | grep 255.240.0.0,32.224.0.0,32.78.120.254 | grep '.40'
route net,-hopcount,1,-netmask,255.240.0.0,32.224.0.0,32.78.120.254
How this is possible? (1 Reply)
Discussion started by: itik
1 Replies
5. UNIX for Dummies Questions & Answers
#!/bin/bash
if then
#echo "infinite loop"
exit 0
fi
when I run this file I get the following error:
./test_infinite_loop: line 5: syntax error near unexpected token `fi'
./test_infinite_loop: line 5: `fi'
:confused: (4 Replies)
Discussion started by: jon80
4 Replies
6. Shell Programming and Scripting
foreach x ( *.foo)
echo "move file?"
set move=$<
if($move == y) then
echo "enter new pathname:"
set path=$<
mv $x $path/$x
endif
end
ok guys, im creating this script so i can move files with *.foo extensions and *.bar... (6 Replies)
Discussion started by: pantelis
6 Replies
7. Programming
Hello,
Im using the g++(g++ Ubuntu/Linaro 4.4.4-14ubuntu5 4.4.5) and im trying to compile a small snippet code and got into an endless loop.I recompiled that in VS2010 under Windows 7 and the answer is as expected.so i wonder is this a bug of g++?here is my code.
#include<iostream>
using... (5 Replies)
Discussion started by: homeboy
5 Replies
8. UNIX for Advanced & Expert Users
Using AudioScope.sh on Ubuntu 17.04 from a live DVD disc I came across an error.
Consider the code below it is a MUCH shortened version of the KEYBOARD input in AudioScope.
#!/bin/bash
bash --version
uname -a
status=0
KEYBOARD()
{
read -r -p "Enter QUIT or EXIT to quit:- " kbinput
if ||... (11 Replies)
Discussion started by: wisecracker
11 Replies
LEARN ABOUT MOJAVE
vga_getmodenumber
vga_getmodenumber(3) Svgalib User Manual vga_getmodenumber(3)
NAME
vga_getmodenumber - return a number for the given video mode
SYNOPSIS
#include <vga.h>
int vga_getmodenumber(char *name);
DESCRIPTION
The function parses *name and tries to find a videomode corresponding on it. *name is parsed case insensitive and should be either an
integer string just giving a mode number or consist of a capital G followed by the amount of x pixels, followed by a lower case x, followed
by the amount of y pixels, followed by a lower case x. Finally the number of different colors is appended. Here the shortcuts 32K,64K,16M,
and 16M4 are used for 32768, 65536, and 16777216 are used. The last refers also to 16777216 which are store in 4 bytes (highest address
byte unused) for easier screen access.
For unsupported values or the string "PROMPT" the value -1 is returned. Also a irritating error message is printed to stdout. This is used
during parsing the SVGALIB_DEFAULT_MODE environment variable. Probably it should not be used for anything else.
EXAMPLE
vga_getmodenumber("G640x480x256") returns 10.
SEE ALSO
svgalib(7), vgagl(7), libvga.config(5), vgatest(6), vga_hasmode(3), vga_modeinfo(3), vga_setmode(3), vga_lastmodenumber(3), vga_getcurrent-
mode(3), vga_getdefaultmode(3), vga_getmodename(3)
AUTHOR
This manual page was edited by Michael Weller <eowmob@exp-math.uni-essen.de>. The exact source of the referenced function as well as of the
original documentation is unknown.
It is very likely that both are at least to some extent are due to Harm Hanemaayer <H.Hanemaayer@inter.nl.net>.
Occasionally this might be wrong. I hereby asked to be excused by the original author and will happily accept any additions or corrections
to this first version of the svgalib manual.
Svgalib 1.3.0 8 April 1998 vga_getmodenumber(3)