From: Alex deVries <adevries@engsoc.carleton.ca>
To: "Francis M.J. Hsieh" <mjhsieh@life.nthu.edu.tw>,
Ariel Faigon <ariel@cthulhu.engr.sgi.com>
Cc: SGI/Linux mailing list <linux@cthulhu.engr.sgi.com>
Subject: Re: apache and other problems (fwd)
Date: Fri, 17 Jul 1998 01:32:29 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.95.980717012901.5792D-100000@lager.engsoc.carleton.ca> (raw)
In-Reply-To: <199807161853.LAA91562@oz.engr.sgi.com>
On Thu, 16 Jul 1998, Ariel Faigon wrote:
> ----- Forwarded message from owner-linux@cthulhu -----
> From: "Francis M.J. Hsieh" <mjhsieh@life.nthu.edu.tw>
>
> This two files were uploaded in ftp://helix.life.nthu.edu.tw/pub/
> (yes, it is a Linux/SGI machine) for people in Taiwan save their
> download time.
Cool.
> I got some problem here.
> - apache httpd is still buggy (can't deliver text/html correctly)
I don't know what that problem is; mine works fine. Does it accept a TCP
connection properly?
> - ifconfig is still buggy, TX packets is 0 (see followed)
Yeah, I think we went over that before although I don't remember what the
solution was.
> - mouse doesn't work?
In the HH install, there's a package called 'kernel-2.1.100-2'. If you
install this, you'll have something like /boot/vmlinux-2.1.100. That
kernel (2.1.100) should have mouse support in it. you'll have to make a
symbolic link from /dev/psaux to /dev/mouse.
For reasons I don't want to get into, the kernel in the install really
sucks, and you should throw it away ASAP and use the packaged one.
- Alex
next prev parent reply other threads:[~1998-07-17 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-16 18:53 apache and other problems (fwd) Ariel Faigon
1998-07-16 18:53 ` Ariel Faigon
1998-07-17 5:32 ` Alex deVries [this message]
1998-07-17 8:09 ` Mouse support in 2.1.100-2 Honza Pazdziora
1998-07-17 8:09 ` Honza Pazdziora
1998-07-17 8:23 ` apache and other problems (fwd) Francis M. J. Hsieh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.3.95.980717012901.5792D-100000@lager.engsoc.carleton.ca \
--to=adevries@engsoc.carleton.ca \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=mjhsieh@life.nthu.edu.tw \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.