Linux-Misc Digest #703, Volume #18 Wed, 20 Jan 99 15:13:07 EST
Contents:
Limit Bandwidth ("Russ")
Can I run a DOS Device Driver in an emulator ("Norm Dresner")
Re: Linux keyboard? (For emacs use) (Gabor)
Re: Nedit for w95 (William Boyle)
Re: Linux keyboard? (For emacs use) (Sven Utcke)
Help Desk Apps ("Rick Glunt")
Re: 2038 and Linux (Christopher B. Browne)
Redhat 5.2 ld problems (Jesse Jensen)
A Tale of Two Installations (Giftzwerg)
Re: Kernel Panic - Help! (David Kirkpatrick)
mkdir fails: too many links (Brian Rankin)
Re: A newbie versus "vi" (Ed Young)
Re: A newbie versus "vi" (Kelly and Sandy)
----------------------------------------------------------------------------
From: "Russ" <[EMAIL PROTECTED]>
Subject: Limit Bandwidth
Date: Wed, 20 Jan 1999 11:02:40 -0600
Is there a way to limit the bandwidth of a machine below the settings on the
network card. Or can you limit the bandwidth to you web server ? I use
apache for a web server?
Russ
------------------------------
Crossposted-To:
comp.os.linux.development,comp.os.linux.development.system,comp.os.linux.hardware
From: "Norm Dresner" <[EMAIL PROTECTED]>
Subject: Can I run a DOS Device Driver in an emulator
Date: Wed, 20 Jan 1999 13:44:34 GMT
I have a special video card that needs to be initialized by a DOS device
driver. There's nothing else available (unless you count windoze). (For
the curious, it's a Targa+ overlay card.)
Once the initialization is done, I could throw DOS away and run CP/M-86
(only joking).
I might be able to boot DOS, initialize the board, and then boot Linux, but
that stinks, especially if I have to modify the settings.
Is there any way that I can call (perhaps hack up a DOS-style
load-device-driver-from-the-command-line program) the driver from a DOS
emulator in Linux to do the job.
All suggestions, hints, and even sympathy, gratefully accepted.
Norm D.
------------------------------
From: [EMAIL PROTECTED] (Gabor)
Crossposted-To:
comp.os.linux.hardware,comp.unix.questions,comp.unix.misc,comp.emacs,comp.editors
Subject: Re: Linux keyboard? (For emacs use)
Date: Wed, 20 Jan 1999 17:30:04 GMT
In comp.editors, Erik Naggum <[EMAIL PROTECTED]> wrote :
# * Sven Utcke <[EMAIL PROTECTED]>
# | So I noticed. Strangely enough you still employ capital letters for
# | the words "I" and "Emacs". Or rather Emacs does, I guess :-)
#
# case is an important property of a word. randomly capitalizing words
# just because they happen to start sentences destroys valuable information
# about that word. I therefore maintain the case properties of a word
# regardless of its position in the sentence.
That is utterly ridiculous, IMHO. The capitalization isn't random, it
signifies the beginning of a new sentence. Why use punctuation, by
your rationalization, it's also a bad idea.
Just my $0.02.
------------------------------
From: William Boyle <[EMAIL PROTECTED]>
Crossposted-To: comp.editors
Subject: Re: Nedit for w95
Date: Wed, 20 Jan 1999 01:03:24 -0500
Thanks, I got it. Now all I have to do is get MI/X working...
-Bill
Alvaro A. Novo wrote:
>
> On Mon, 18 Jan 1999, William Boyle wrote:
>
> > Could you tell me how you got NEdit for Win 95/NT? I cannot find an NT
> > build in the fnal ftp site (ftp.fnal.gov/pub/nedit). TIA.
> >
> > -Bill Boyle ([EMAIL PROTECTED])
> >
> >
>
> Follow this link:
>
> http://www-pat.fnal.gov/nirvana/nedit.html
>
> and then click on
>
> Max Volken's souped up NEdit (incl. Windows/NT version)
>
> Alvaro
>
> > Antoni Zochowski wrote:
> > >
> > > Could someone tell me, how to make Nedit for W95 to work with
> > > MI/X free Xwindows server ? The available package is configured
> > > for Exceed, but there is mention of running it also under
> > > MI/X. The MI/X alone works fine.
> > > Thanks
> > >
> > > [EMAIL PROTECTED]
> >
> >
>
> -- -- -- -- -- -- -- --
> Alvaro A. Novo
> 2116 S. Orchard St., #304
> Urbana, IL 61801
>
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> http://www.students.uiuc.edu/~novo/Alvaro.htm
> 217-337-4893
> -- -- -- -- -- -- -- --
------------------------------
From: Sven Utcke <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.hardware,comp.unix.questions,comp.unix.misc,comp.emacs,comp.editors
Subject: Re: Linux keyboard? (For emacs use)
Date: 20 Jan 1999 17:48:01 +0100
Erik Naggum <[EMAIL PROTECTED]> writes:
> * Sven Utcke <[EMAIL PROTECTED]>
> | So I noticed. Strangely enough you still employ capital letters for
> | the words "I" and "Emacs". Or rather Emacs does, I guess :-)
>
> case is an important property of a word. randomly capitalizing words
> just because they happen to start sentences destroys valuable information
> about that word. I therefore maintain the case properties of a word
> regardless of its position in the sentence.
Alright.
Although I can't say that I agree with you:
a) In English, so few words are capitalised at all, that it makes the
whole thing rather pointless.
b) I believe that having capital letters at the beginning of sentences
makes for a rather valuable visual guide in reading.
But then, this is a free world...
Sven
--
_ _ Lehrstuhl fuer Mustererkennung und Bildverarbeitung
| |_ __ | |__ Sven Utcke
| | ' \| '_ \ phone: +49 761 203 8274 Am Flughafen 17
|_|_|_|_|_.__/ fax : +49 761 203 8262 79110 Freiburg i. Brsg.
mailto:[EMAIL PROTECTED] www.informatik.uni-freiburg.de/~utcke
------------------------------
From: "Rick Glunt" <[EMAIL PROTECTED]>
Subject: Help Desk Apps
Date: Wed, 20 Jan 1999 13:30:18 -0500
I am looking for a help desk application for Linux (preferibly X Win). Does
anyone know of any? I am really looking for just something our IT
department can log problems/services issued by our employees along with
perhaps a searchable database to search for solutions to problems previously
solved.
------------------------------
From: [EMAIL PROTECTED] (Christopher B. Browne)
Crossposted-To:
comp.os.linux.advocacy,comp.software.year-2000,comp.os.linux.development.system
Subject: Re: 2038 and Linux
Reply-To: [EMAIL PROTECTED]
Date: Wed, 20 Jan 1999 06:02:29 GMT
On 20 Jan 1999 04:27:13 GMT, Bloody Viking <[EMAIL PROTECTED]> posted:
>In comp.os.linux.advocacy John Savard <[EMAIL PROTECTED]> wrote:
>
>: Of course, in the very short term, building better IA-32 chips is
>: indeed the only useful thing to do.
>
>Which means that the Y2K+38 expiry still exists. To work around it, I have
>thought of a few ideas, none of which are "elegant".
>
>Method 1: Backdating. Every 56 years, you backdate 56 years, so the date
>is 56 years * X off. You keep a file around to record the number of
>backdatings To extract a date, the apps check the date then check
>/etc/backdate. A refinement of course is a once in 56 years cron job to
>auto-backdate. Beware of the Y2.1K problem. :) (Not a leap year.) If I
>need to, this is most likely my method of choice for my computers.
Nope. This doesn't cope well with the fact that one of the most major
places where date stamps of the form time_t are used is for time stamps in
filesystems.
Bonus points for the consideration that if /etc/backdate gets nuked, this
affects dates on other partitions that weren't touched.
This is *not* a good answer.
>Method 2: Unsugning time_t. Time_t is a signed integer. You could make it
>unsigned at least in theory. Anyone try this? An alternative is to make it
>a double, a floating point double, etc. Slows the system, but nicer than
>backdating. An unsigned integer only delays the inevitable of having to
>backdate by some long time.
This means that you can't represent dates before 1970. My birthday
disappears. Oops.
>Method 3: A perpetual calendar routine. The years repeat themselves every
>400 years in the Gregorian pattern. You could use Y2K as a reference date
>and design a routine that backdates as above, but backdates funny at
>Y2.1K, Y2.2K, and Y2.3K then at Y2.4K reverts to Y2K. Of course, you need
>that goofy /etc/backdate file to remember the config for apps to use.
>Again, you can use a goofy cron job.
Definitely sounds goofy.
>Method 4: Use a DEC Alpha or other 64 bit CPU. :) For those of you who
>have the money, this is the best solution. Those of us on low budgets,
>it's time to impliment the backdating crap.
Method 5: The *right* answer is to do the remediation via standardization
(in C9X) of the representation of 64 bit values. These days, the
"nonstandard but common" approach is for "long long" to be 64 bits.
Apparently behaviour is to be standardized in C9X.
Given standardized behaviour of the data type, we can then have GLIBC use a
64 bit value as its time_t, and hopefully fairly rapidly thereafter get that
functionality to integrate into libraries and filesystems.
Note that this might also provide a natural route to solution of the "large
files problem."
Unlike the other solutions, this *isn't* a "hack." If we can cope with the
ambiguity until C gets fixed to specifically know 64 bits, then there's no
need to have hacks that will cause the code to look unclean.
As a wild prediction, I'll suggest the thought that Linux 2.4 is liable to
be the point at which 2038 "compliance" should be sought.
--
Those who do not understand Unix are condemned to reinvent it, poorly.
-- Henry Spencer <http://www.hex.net/~cbbrowne/linuxy2k.html>
[EMAIL PROTECTED] - "What have you contributed to Linux today?..."
------------------------------
Crossposted-To: comp.os.linux.setup
From: Jesse Jensen <[EMAIL PROTECTED]>
Subject: Redhat 5.2 ld problems
Date: Wed, 20 Jan 1999 04:41:24 GMT
I'm having major problems upgrading and installing software on my Redhat
5.2 computer. Everything craps out when I try to compile it.
At first I was getting a missing "crt1.o" error, but I was able to find
all the crt* stuff (I wonder why it wasn't there to begin with).
Then, gcc started crapping out when it got a "-02" flag. As I
understand it, this is a very important and popular optimization flag,
so I don't know why that didn't work. I RPMed in a new gcc, and that
problem went away.
Now, ld doesn't work. It always says it can't find file "-lc". I guess
"-lc" is an important flag that ld is mistaking for the name of a file.
So, I tried installing egcs and making gcc point to it. ld does the
same thing. I tried reinstalling ld, but I can't find the binary
version and I can't compile it without a working version of ld.
These are the programs I'm trying to install:
wu-ftpd-2.4.2-beta-18-vr12
binutils-2.9.1.0.19a
fileutils-3.16
xferstats
Thank you for your time and help in this matter.
Jesse
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Giftzwerg)
Subject: A Tale of Two Installations
Date: Wed, 20 Jan 1999 12:38:28 -0500
This afternoon - becoming desirous of listening to some web-radio on my
system here at work - I wandered on over to the RealAudio site and
grabbed their free audio player.
Actually, I grabbed it twice; one version for Linux, and one for Win98,
since this machine runs both OS's.
Care to hear how long it took me to install RealPlayer in Win98?
Two minutes (I got a coffee while it was installing...).
Care to hear how difficult it was?
I placed my mouse pointer over the setup.exe icon, and depressed the left
button (note that since I have "view as web-page" active, I don't need to
double-click and thus only did half as much work as I used to...).
Care to hear how long it took me to install RealPlayer in Linux?
I have no idea how long - since it *still* isn't working.
Care to hear how difficult it was?
Oh, it involved the usual brain-damaged Linux hoop-jumping;
LD_LIBRARY_PATH, *.so, links, RA*, ldconfig, grepping for permission
issues, trips to DejaNews to find messages in bottles from other poor
souls who had the same problem, trips to AltaVista to seek out websites
devoted to poor souls dumb enough to think that a web browser plugin
should install easily...
...the usual suspects that everyone silly enough to like Linux has to
deal with every fscking time we want to install something new...
<sigh>
Maybe it's just me. I've only had 15 years experience with *NIX.
</sigh>
The Moral Of The Story:
Linux is not going anywhere as a mainstream OS until the pain of
installing new software is *always* commensurate with the benefit derived
from that software once installed. A web-browser plugin is worth exactly
one command and two minutes...
...just like it is in Windows.
--
Giftzwerg
<[EMAIL PROTECTED]>
************************************
ladies and gentlemen, please welcome reagan and haig,
mr. begin and friend mrs. thatcher and paisley
mr. brezhnev and party
the ghost of mccarthy
and the memories of nixon
and now adding colour a group of anonymous latin
american meat packing glitterati
------------------------------
From: David Kirkpatrick <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.hardware,comp.os.linux.setup,linux.redhat,linux.redhat.misc
Subject: Re: Kernel Panic - Help!
Date: Wed, 20 Jan 1999 13:30:56 +0000
Reply-To: [EMAIL PROTECTED]
Dan,
I'm new to Linux so take this with the understanding I have
to guess at
a few things.
It looks like someone was trying to write 110 chars into a
buffer
that is smaller. The only handling for this is a panic with the
return
address of the caller - see the panic call below for a match to
your
sync text error messages.
Panic was called from skb_put (below) which is called from
many places.
If the return address call can be relied on then I think that the
address
can be pegged to the caller at the address given in the panic -
001a5818
in your case.
I believe the caller can be found for your system build in
the file
System.map in /usr/src/linux. Grep for the address to find the
calling
code. If you can please let me know which call is pointed out.
david
Len here is too large -> 110.
unsigned char *skb_put(struct sk_buff *skb, int len)
{
unsigned char *tmp=skb->tail;
IS_SKB(skb);
skb->tail+=len;
skb->len+=len;
IS_SKB(skb);
if(skb->tail>skb->end)
panic("skput:over: %p:%d", __builtin_return_address(0),len);
return tmp;
}
NORET_TYPE void panic(const char * fmt, ...)
{
static char buf[1024];
va_list args;
int i;
va_start(args, fmt);
vsprintf(buf, fmt, args);
va_end(args);
printk(KERN_EMERG "Kernel panic: %s\n",buf);
if (current == task[0])
printk(KERN_EMERG "In swapper task - not syncing\n");
else
sys_sync();
Dan Warren wrote:
>
> Can someone tell me the severity of this message and possibly what
> caused it:
>
> Kernel panic: skput:over 001a5818:110
> In swapper task - not syncing
>
> Thanks
>
> Dan Warren
> [EMAIL PROTECTED]
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
------------------------------
From: Brian Rankin <[EMAIL PROTECTED]>
Subject: mkdir fails: too many links
Date: Tue, 19 Jan 1999 22:22:50 -0800
Hello,
I have a system (2.0.33) which doesn't permit me to create more than
32,000 directories under a given directory. I can create trees of as
many directories as I want, but no more than 32,000 at a given level.
Attempting to create additional directories produces a "too many links"
error.
This isn't an inode limit as I have about 40% still available. Here's
an ls -l of such a directory:
drwxrwxr-x 32000 root root 24576 Jan 8 17:38 new2
Is 32,000 a hard limit of the number of directories that can exist -- at
one level -- under a directory? Is there a parameter I can change to
increase this number?
Since
------------------------------
From: Ed Young <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: A newbie versus "vi"
Date: 20 Jan 1999 03:39:34 GMT
RedHat 5.2 comes with gvim. gvim will give you syntax highlighting. It is very
configurable. I have the following lines in my .bashrc file to cause 'vi' to
run gvim when in Xwindows. You can also get syntax highlighting in terminal
windows. You are running vim in compatibility mode when you run vim from a
terminal. It defaults to that.
======= in .bashrc ===========
if [ $TERM = "linux" ]
then
alias vi=vim
else
alias vi=gvim
fi
==============================
======= .gvimrc ======================================================
" Vim
" Make external commands work through a pipe instead of a pseudo-tty
"set noguipty
set nocp " not compatible, use vim's extra advantages over vi
set nobackup " does not backup the currently edited file on save
set autoindent " turn on auto increment
set backspace=2 " allow backspacing over everything in insert mode
set expandtab " spaces are used instead of tabs
set icon " display edit file in window title
set ruler " shows line, column position on status line
set shiftwidth=2 " shift width
set showcmd " shows the command in the status line
set showmode " show mode of editor (Insert, Replace, or Visual
set smartindent " works of C and perl programs
set smarttab " makes tab key work as I would expect
set tabstop=2 " number of spaces that a TAB covers
set ttyfast " because I am directly connected to the computer
set ch=2 " Make command line two lines high
set laststatus=2 " place status bar at bottom of a single buffer screen
set lines=48 " lines of editable text
set guifont=8x13
map <F7> :set hls!<CR><Bar>:echo "HLSearch: " . strpart("OffOn", 3 * &hlsearch,
3)<CR>
" Only do this for Vim version 5.0 and later.
if version >= 500
syntax on " Switch on syntax highlighting.
set hlsearch " Switch on search pattern highlighting.
set mousehide " Hide the mouse pointer while typing
" Set nice colors
highlight Normal guibg=AntiqueWhite3
highlight Cursor guibg=darkblue guifg=Green
highlight NonText guibg=AntiqueWhite4
highlight StatusLine guibg=white guifg=Black
highlight Menu guibg=AntiqueWhite4 guifg=Black
highlight Scrollbar guibg=AntiqueWhite4 guifg=AntiqueWhite3
endif
======================================================================
Have fun...
Kelly and Sandy wrote:
>
> Dear Linux Users, A newbie versus "vi"
> --------------------
>
> I am a newbie again. Unix, this time.
>
> I am writing from my minimal emergency NT installation. (I have
> recently decided to once an for all jettison MS, and in the process have
> started to get interested in Linux.)
>
> I installed Red Hat 5.2 on my x86 PC last week. I logged in as
> root, typed startx, and lo, verily, XWindows started up. Wonderful.
>
> Now, the last Unix I used was at college, at Middlesex University to
> be precise. (We had no time there to learn anything about Unix or
> anything else -- we were too busy handing in assignments and getting our
> names ticked off registers.)
>
> I used Silicon Graphics' Unix there, to edit C code for an OpenGL
> project to visualize three-body problems. (Sounds fancy, but really it
> was getting vast asteroid fields to attack the Earth at 20 kilometres a
> second. It was quite amazing to watch, and our moon is a mysterious
> influence. I have the strongest hunch we'll only find life on planets
> with an Earth-moon setup like ours. But I digress!)
>
> What made me able to hand in the assignment on time was the Silicon
> Graphics' beautiful "vi" editor. I think it was called "vi". Anyway,
> it was fully GUI with pull-down menus with all sorts of menu-items
> goodies. Like "auto-indent" toggle and "pretty-print" and "code
> completion...". It was really lovely.
>
> Well, of course, I was expecting the same level of wonderment when I
> typed "vi" in Linux. But instead I got this white-on-black VDU-type
> editor, no help, no menus, no indication of being in command mode ...
> and had to spend half an hour "finding the light switch" by reading
> through "Linux in a Nutshell" (by Jessica Perry Hekman, O'Reilly ISBN
> 1-56592-167-4) Chapter 8, The vi Editor.
>
> An unpleasant newbie experience.
>
> "And what was a newbie doing trying to use vi?" you may be
> wondering. Well, I was trying to edit .bashrc, to make "ls" listing
> come up in colours and set the defaults. This was to give me _some_
> sense of achievement and control, after the initial installation, in
> other words. Now, from the "Official Red Hat Linux Operating System
> Installation Guide" (that's in the blue and red-hatted startup box)
> under the Red Hat Linux Installation Support FAQ chapter, page 326:
>
> E.7.3 Getting colors with ls
> -----------------------------
>
> Question
>
> How come I don't see colors when I run ls? When I am using my
> old Linux, the file names all have different colors.
>
> Answer
>
> In order to allow the color option you must edit .bashrc. This
> line must be placed in the file:
>
> alias ls='ls --color=auto'
>
> So the first time I tried "vi" then, I created five "vi" processes,
> which took another half hour to kill off. More Linux in a Nutshell,
> this time the ps (list processes) [p 87] and kill (processes) [p 63]
> commands. All this was quite a shock, discovering how dangerously
> primitive and "VDU"-ish the standard editor is in Linux. Configuring
> everything (not least internet access) and getting it all to work for me
> is too important and delicate a job to start using an editor that's it's
> _own_problem_ on top of everything else!
>
> Therefore I made a mental note to write off a letter, as I am doing
> now, to the Linux newsgroups to find out about using an alternative
> easy-to-use pull-down-menu editor somehow.
>
> So, reiterating: can I get a GUI editor by invoking some other
> command, or the right vi -switches or is it something I have to download
> off the web?
>
> With Kind Regards,
>
> Sandy
>
> /* Please be sure you're not sending us any Spam or JUNK!
> --
> // <[EMAIL PROTECTED]>
> // Kelly Siegel Alexander "Sandy" Anderson
> // Home Fone +44 (0) 171-794-4543
> // London, UK http://www.almide.demon.co.uk/
> // PGP print C6 8C 55 F2 77 7B 99 9B 14 77 66 F5 B8 74 CF 12
> */
------------------------------
From: Kelly and Sandy <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: A newbie versus "vi"
Date: Wed, 20 Jan 1999 03:37:44 +0000
In a comp.os.linux.setup newsletter entitled "A newbie versus "vi"",
rdt@c.?.q wrote
> > So, reiterating: can I get a GUI editor by invoking some other
> >command
> >
>Of course. There are dozens of editors available. Nothing forces you to
>use vi to edit a file. Try jed or joe or nedit or gxedit or xwe or ....
>You may not have all of these installed but they're not hard to find.
Thank you very much for this valuable assistance to yet another
Linux newbie. Do people have any recommendations about the relative
merits of these strange-sounding editors? I have no idea which to
choose.
However, jed sounds good, because it sounds better than wookie. I
mean
wookie .bashrc
is not nearly as light-swordish as
jed .bashrc
With Kind Regards,
Sandy
/* Please be sure you're not sending us any Spam or JUNK!
--
// <[EMAIL PROTECTED]>
// Kelly Siegel Alexander "Sandy" Anderson
// Home Fone +44 (0) 171-794-4543
// London, UK http://www.almide.demon.co.uk/
// PGP print C6 8C 55 F2 77 7B 99 9B 14 77 66 F5 B8 74 CF 12
*/
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
