659 lines
24 KiB
Plaintext
659 lines
24 KiB
Plaintext
From: Digestifier <Linux-Development-Request@senator-bedfellow.mit.edu>
|
|
To: Linux-Development@senator-bedfellow.mit.edu
|
|
Reply-To: Linux-Development@senator-bedfellow.mit.edu
|
|
Date: Fri, 9 Sep 94 20:13:06 EDT
|
|
Subject: Linux-Development Digest #146
|
|
|
|
Linux-Development Digest #146, Volume #2 Fri, 9 Sep 94 20:13:06 EDT
|
|
|
|
Contents:
|
|
Re: Survey: who wants f77,cc,c++,hpf for linux?
|
|
Linux/AXP Progress Report posted to comp.os.linux.announce (Jim Paradis)
|
|
Re: Best PCI viceo and SCSI controller (Frederic POTTER)
|
|
Re: Anyone working on ISDN card drivers ?? (Mihail S. Iotov)
|
|
Re: Anyone working on DHCP server? (Piercarlo Grandi)
|
|
Re: News Spool File System - new filesystem type?? (Alan Barrow)
|
|
Re: News Spool File System - new filesystem type?? (Alan Barrow)
|
|
Re: ATI Mach64... Does it work...? (m.s. saed arafat)
|
|
Re: NFS max timeout reached with 1.1.42 (Andy Burgess)
|
|
Re: OS/2.99 Boot Manager and LINUX Slackware problems (Tiger II)
|
|
Re: PCI+Pentium+Linux+X? (Pete Deuel)
|
|
Re: Future of linux -- the sequel (Daniel Garcia)
|
|
Re: 320x200 X resolution? (Sam Oscar Lantinga)
|
|
|
|
----------------------------------------------------------------------------
|
|
|
|
Crossposted-To: comp.lang.fortran
|
|
From: jwest@jwest.ecen.okstate.edu ()
|
|
Subject: Re: Survey: who wants f77,cc,c++,hpf for linux?
|
|
Date: Fri, 9 Sep 1994 17:39:18 GMT
|
|
|
|
In article <34pufe$sf1@sulawesi.lerc.nasa.gov> mshann@hyperthink.lerc.nasa.gov (Ray Hann) writes:
|
|
|
|
>The performance with f2c + gcc seems to vary wildly from one application
|
|
>to the next. A good F77 compiler will beat f2c+gcc on the whetstone
|
|
>benchmarks by 3 fold. But then again I have found on some of my own
|
|
>scientific codes that f2c+gcc produces code that actually executes faster
|
|
>than that of the Sun F77 compiler. The only tweeking that was needed
|
|
>was to set -DREGISTER as an option on the gcc compile. Consistancy is
|
|
>the problem along with the lack of a free F77 debugger.
|
|
|
|
Fortran code compiled by f2c+gcc can be debugged using gdb. Simply
|
|
transform/compile with -g and set the first break point to MAIN__.
|
|
(If you use f77 script that comes with Slackware (and maybe some
|
|
other distributions), make sure you either remove the section that
|
|
transfers the code to f2ctmp_<filename>.f and compiles it, or
|
|
at least comment out the line that removes f2ctmp_<filename>.f if
|
|
you want to debug.)
|
|
|
|
|
|
--
|
|
Jim West jwest@jwest.ecen.okstate.edu
|
|
Associate Professor jwest@master.ceat.okstate.edu
|
|
Electrical and Computer Engineering
|
|
Oklahoma State University
|
|
|
|
------------------------------
|
|
|
|
From: paradis@sousa.amt.ako.dec.com (Jim Paradis)
|
|
Crossposted-To: comp.os.linux.misc,comp.sys.dec
|
|
Subject: Linux/AXP Progress Report posted to comp.os.linux.announce
|
|
Date: 9 Sep 1994 14:26:43 -0400
|
|
|
|
For those who are interested, I posted a progress report for the
|
|
Linux/AXP project to comp.os.linux.announce
|
|
|
|
Linux/AXP is a port of the Linux operating system to DEC's Alpha AXP
|
|
CPU architecture.
|
|
|
|
|
|
--
|
|
Jim Paradis (paradis@tallis.enet.dec.com)
|
|
|
|
The purpose of time is to keep everything from happening at once.
|
|
It's not working.
|
|
|
|
------------------------------
|
|
|
|
From: frederic@swing.ibp.fr (Frederic POTTER)
|
|
Subject: Re: Best PCI viceo and SCSI controller
|
|
Date: 9 Sep 1994 10:42:30 GMT
|
|
|
|
In article <34o0d9$las@senator-bedfellow.MIT.EDU>, jered@mit.edu (Jered J Floyd) writes:
|
|
|> What I use, and find as best, is:
|
|
|> Buslogic BT946C - PCI This SCSI card is absolutely wonderful.
|
|
|> Diamond Stealth 64 PCI This video will be supported in XF3.1
|
|
|>
|
|
|> --
|
|
|> Jered Floyd - jered@mit.edu
|
|
|> Geek Code 2.1 - GAT d? H- s-:- g- p? !au a-- w+ v+ C++++ UL++++ P+ L++
|
|
|> N+++ K+++ W++ M-- V-- -po+ Y++ tv+ 5+++ j++ R v++ b+++ D+++ B--- e* u**
|
|
|> h++ f? r? n- !y+ (Finger for PGP key, picture, humor anOUT OF SPACE
|
|
|
|
I use NCR810 PCI, very nice and bloody cheap ( $70 )
|
|
MIRO10 SD ( s3 chip) quit fast and supported whith 2.1.1 ( already
|
|
available )
|
|
|
|
------------------------------
|
|
|
|
From: iotov@cco.caltech.edu (Mihail S. Iotov)
|
|
Subject: Re: Anyone working on ISDN card drivers ??
|
|
Date: 9 Sep 1994 20:22:51 GMT
|
|
|
|
matthew@rmc1.com (Matthew S. Crocker) writes:
|
|
|
|
|
|
>Only we are using a CISCO 2501 router to handle our IP feed (T1).
|
|
>Putting 64-128k through the ISA bus would be murder on interrupts
|
|
>(even for the P5-90 we have here...)
|
|
|
|
Are you sure about this one ? The IDE drive regularly puts 4Mbps on the ISA
|
|
bus.
|
|
|
|
------------------------------
|
|
|
|
From: piercarl@sabi.demon.co.uk (Piercarlo Grandi)
|
|
Subject: Re: Anyone working on DHCP server?
|
|
Reply-To: piercarl@sabi.demon.co.uk (Piercarlo Grandi)
|
|
Date: Fri, 9 Sep 1994 22:15:25 GMT
|
|
|
|
>>> On Fri, 2 Sep 1994 09:25:55 GMT, iialan@iifeak.swan.ac.uk (Alan Cox) said:
|
|
|
|
Alan> In article <33r85b$7rg@access1.digex.net> esmith@access1.digex.net
|
|
Alan> (Eric V. Smith) writes:
|
|
|
|
Eric> Does a DHCP server for Linux exist? If not, is anyone working on one?
|
|
Alan> No. Not to my knowledge.
|
|
|
|
I just saw a post by somebody who is working on one:
|
|
|
|
From: esmith@access4.digex.net (Eric V. Smith)
|
|
Subject: DHCP server and NT
|
|
Date: 7 Sep 1994 21:59:39 -0400
|
|
|
|
I'm writing a DHCP server to run under Linux, with the specific
|
|
purpose of serving NT Daytona clients (and later, Chicago). I had
|
|
a few questions about NT's usage of DHCP, and wondered if anyone here
|
|
knows the answers. [ .... ]
|
|
|
|
Eric> Does a BOOTP server exist (source code, of course!)? I assume it
|
|
Eric> would be a good starting point.
|
|
|
|
Alan> It's on sunacm.swan.ac.uk. Get the one from Updates as that will also work
|
|
Alan> correctly with later 1.1.x kernels. There is also a bootp client if you
|
|
Alan> feel the urge to write a DHCP client too. The bootp server code is as far as
|
|
Alan> I can remember a cleaned up BSD bootpd
|
|
|
|
Actually the recently posted (in comp.sources.unix, if I remember well)
|
|
bootp 2.4.0 works almost out of the box with Linux; the only corrections
|
|
needed are contained in this patch (which I have sent to the
|
|
maintainer):
|
|
|
|
diff -ru ../bootpd-2.4.0_old/Makefile ./Makefile
|
|
--- ../bootpd-2.4.0_old/Makefile Wed Aug 24 22:05:16 1994
|
|
+++ ./Makefile Wed Aug 24 22:47:44 1994
|
|
@@ -29,17 +29,18 @@
|
|
# filenames bootpd uses for its configuration and dump files.
|
|
#CONFFILE= -DCONFIG_FILE=\"/usr/etc/bootptab\"
|
|
#DUMPFILE= -DDUMPTAB_FILE=\"/usr/etc/bootpd.dump\"
|
|
-#FILEDEFS= $(CONFFILE) $(DUMPFILE)
|
|
+FILEDEFS= $(CONFFILE) $(DUMPFILE)
|
|
|
|
# MORE DEFinitions (whatever you might want to add)
|
|
# One might define NDEBUG (to remove "assert()" checks).
|
|
MOREDEFS=
|
|
|
|
-INSTALL=/usr/bin/install
|
|
-DESTDIR=
|
|
-BINDIR=/usr/etc
|
|
-MANDIR=/usr/local/man
|
|
+INSTALL=install
|
|
|
|
+DEST=
|
|
+BINDIR=$(DEST)/usr/sbin
|
|
+MANDIR=$(DEST)/usr/man
|
|
+
|
|
CFLAGS= $(OPTDEFS) $(SYSDEFS) $(FILEDEFS) $(MOREDEFS)
|
|
PROGS= bootpd bootpef bootpgw bootptest
|
|
TESTS= trylook trygetif trygetea
|
|
@@ -99,6 +100,10 @@
|
|
# Silicon Graphics IRIX (no <sys/sockio.h>, so not SVR4)
|
|
irix:
|
|
$(MAKE) SYSDEFS="-DSYSV -DIRIX"
|
|
+
|
|
+# Linux, mostly BSD
|
|
+linux:
|
|
+ $(MAKE) SYSDEFS='-O2 -m486' BINDIR=/usr/sbin MANDIR=/usr/man
|
|
|
|
# SunOS 4.X
|
|
sunos4:
|
|
diff -ru ../bootpd-2.4.0_old/bootpd.c ./bootpd.c
|
|
--- ../bootpd-2.4.0_old/bootpd.c Wed Aug 24 22:11:11 1994
|
|
+++ ./bootpd.c Wed Aug 24 22:20:19 1994
|
|
@@ -494,6 +494,10 @@
|
|
* Process incoming requests.
|
|
*/
|
|
for (;;) {
|
|
+#ifdef linux
|
|
+ struct timeval dotimeout;
|
|
+ if (timeout) dotimeout = *timeout, timeout = &dotimeout;
|
|
+#endif
|
|
readfds = 1 << s;
|
|
nfound = select(s + 1, (fd_set *)&readfds, NULL, NULL, timeout);
|
|
if (nfound < 0) {
|
|
diff -ru ../bootpd-2.4.0_old/bootpgw.c ./bootpgw.c
|
|
--- ../bootpd-2.4.0_old/bootpgw.c Wed Aug 24 22:11:14 1994
|
|
+++ ./bootpgw.c Wed Aug 24 22:55:09 1994
|
|
@@ -441,6 +441,10 @@
|
|
* Process incoming requests.
|
|
*/
|
|
for (;;) {
|
|
+#ifdef linux
|
|
+ struct timeval dotimeout;
|
|
+ if (timeout) dotimeout = *timeout, timeout = &dotimeout;
|
|
+#endif
|
|
readfds = 1 << s;
|
|
nfound = select(s + 1, (fd_set *)&readfds, NULL, NULL, timeout);
|
|
if (nfound < 0) {
|
|
diff -ru ../bootpd-2.4.0_old/hwaddr.c ./hwaddr.c
|
|
--- ../bootpd-2.4.0_old/hwaddr.c Wed Aug 24 22:05:33 1994
|
|
+++ ./hwaddr.c Wed Aug 24 22:42:59 1994
|
|
@@ -80,7 +80,11 @@
|
|
#endif /* SVR4 */
|
|
|
|
bzero((caddr_t) & arpreq, sizeof(arpreq));
|
|
+#ifndef ATF_INUSE
|
|
+ arpreq.arp_flags = ATF_COM;
|
|
+#else
|
|
arpreq.arp_flags = ATF_INUSE | ATF_COM;
|
|
+#endif
|
|
|
|
/* Set up the protocol address. */
|
|
arpreq.arp_pa.sa_family = AF_INET;
|
|
@@ -88,7 +92,15 @@
|
|
si->sin_addr = *ia;
|
|
|
|
/* Set up the hardware address. */
|
|
+#ifdef ARPHRD_ETHER
|
|
+ arpreq.arp_ha.sa_family = ARPHRD_ETHER;
|
|
+#endif
|
|
bcopy(ha, arpreq.arp_ha.sa_data, len);
|
|
+
|
|
+ if (debug > 1)
|
|
+ report(LOG_DEBUG,"SIOCSADDR: pa (%d,0x08%x) ha (%d,0x%08x)",
|
|
+ arpreq.arp_pa.sa_family,*(long unsigned*)arpreq.arp_pa.sa_data,
|
|
+ arpreq.arp_ha.sa_family,*(long unsigned*)arpreq.arp_ha.sa_data);
|
|
|
|
#ifdef SVR4
|
|
/*
|
|
|
|
------------------------------
|
|
|
|
From: jab@narcesc.atl.hp.com (Alan Barrow)
|
|
Crossposted-To: news.software.b
|
|
Subject: Re: News Spool File System - new filesystem type??
|
|
Date: 9 Sep 1994 21:53:41 GMT
|
|
|
|
In <zSvRkapDlXAA071yn@halcyon.com> mpdillon@halcyon.com (Michael Dillon) writes:
|
|
|
|
>That's why it should be implemented as a file system. All the normal OS
|
|
>tools would continue to work, but under the hood it would be optimised
|
|
>to not waste disk blocks and to not even need a fixed size inode table.
|
|
|
|
I can see how you could do a compressed file system optimized for news
|
|
articles. You could save space very easily, and maybe not take too much
|
|
of a performance hit with the compression.
|
|
|
|
But I do not see how this would help the bigger picture news performance
|
|
issues of:
|
|
|
|
1) eliminate/minimize directory traversal for article access
|
|
(opens?).
|
|
|
|
2) combine history and NOV type functionality, and move it out of
|
|
the filesystem (maybe into the database). Think of how databases
|
|
work. We have redundant "indexes" with the current scheme. (the
|
|
current scheme works well, mind you, but I think a paradigm
|
|
shift is needed to make much more inprovement. Something other
|
|
than newer dbz's)
|
|
|
|
3) Further optimizing expires, which should come from #2.
|
|
|
|
4) Maybe data is "stacked" on the media based on expected expire
|
|
time. Short timer's near the "end" of the list/stack, long timers fill
|
|
holes near the "head". articles that stay around longer I would
|
|
guess get accessed more. Popular groups get preferred status,
|
|
based on number of accesses. (Learn from the Mckusic filesystem,
|
|
how it avoids fragmentation, and optimizes access time)
|
|
|
|
Now add some wishlist features:
|
|
|
|
5) fast indexed search function for string/topic/author/site.
|
|
(Look how CD ROM searches work.) We add new NNTP cmds to allow
|
|
this function from newsreaders, not an external program. With a
|
|
total index, hyper links are much easier. If you move to a
|
|
dictionary/token approach, you should be able to do this for
|
|
free. (Total index)
|
|
|
|
6) Provide for dynamic "scoring" of articles/groups based on
|
|
access time. Groups with higher scores stay around longers.
|
|
Make expires totally dynamic, but allow for override's to the
|
|
scoring.
|
|
|
|
And of course it must:
|
|
|
|
7) Dovetail into INN at the library call level. (No rewrite
|
|
needed, just new modules.)
|
|
|
|
8) Not use proprietary DB's. IE: free (This may be tough)
|
|
(Could someone write a portable, decent performance, SQL DB
|
|
and post it?) :-)
|
|
|
|
9) Be portable at the system call level. (No driver's needed)
|
|
|
|
10) Have complete tools available for:
|
|
o DB unload
|
|
o DB backup
|
|
o DB repair (index repair, rebuild the links, etc)
|
|
o DB size changes (add new chunks of disk space)
|
|
o Brute force emergency expire (If we do items 1-6, we
|
|
should not need this one.)
|
|
|
|
Hmm, I was the one concerned about a DB type approach, but I see a DB
|
|
as the best chance of doing the above. I feel sure that an approach like
|
|
this is doable with even commercial SQL technology.
|
|
|
|
I ran the current spool/history/nov scheme past one of our DB labbies, and
|
|
he cringed! We sketched out one schema that would accomplish most of the
|
|
above items. He was intruiged the concept of dbz, left with source, and
|
|
promises to think about it a news schema.) :-) For a large commercial
|
|
site, it might make sense to consider such a scheme even without the exotic
|
|
wishlist items.
|
|
|
|
Anyway, now I like the idea of a real DB. The logical design will be the
|
|
key, and needs to be flexible enough to be able to add new features.
|
|
|
|
back to the scratch pad! :-)
|
|
|
|
|
|
Alan Barrow km4ba | If a little knowledge.....
|
|
Work: jab@atl.hp.com | is a dangerous thing.....
|
|
Home: alan@km4ba.ampr.org | then what is the Anti-Dote???
|
|
|
|
------------------------------
|
|
|
|
From: jab@narcesc.atl.hp.com (Alan Barrow)
|
|
Crossposted-To: news.software.b
|
|
Subject: Re: News Spool File System - new filesystem type??
|
|
Date: 9 Sep 1994 22:08:37 GMT
|
|
|
|
>LZ dictionaries aren't used to look up words, they are used to look
|
|
>up repeated strings so in your example strings like " thi" and "ing"
|
|
>would end up in the dictionary for that one posting. I'm not sure that
|
|
>there is much payback on LZ compression of short articles, but longer
|
|
>ones should work well.
|
|
|
|
I think you could combine something like LZ dictionaries with my "total"
|
|
keyword index in the DB scheme I described in an earlier post.
|
|
|
|
You have a table with two columns. One has the string, the other the
|
|
pointer to an article ID/location. (You may have to have a 3rd column with the
|
|
token for each word if you want to tokenize for compression)
|
|
|
|
This table has a fixed size, and functions like a cache. Words used
|
|
often hang around, and ones that do not fall off.
|
|
|
|
You could do global keyword searches on, say, the 50,000 most common
|
|
words in usenet articles. These "most common" words are the best
|
|
candidates for "tokenizing", or "pointerizing". Per my pet DB labbie,
|
|
such a table with 50,000 entries is trivial with modern DB strategies.
|
|
|
|
So we kill two birds with one stone. Gain compression via
|
|
token/dictionaries, and a "top 50k keyword" grep capability.
|
|
|
|
I can envision how I would use this. In addition to reading news groups
|
|
(with kill files and such), I might first hit the keyword index for
|
|
articles with the word(s). It is then presented in a meta group like
|
|
nngrep will do. This would be handy. If it is not useful to you, just
|
|
make your table small. (And vice versa)
|
|
|
|
Another concept my labbie brought up is multiple tables. Short tables
|
|
(Fast access) for common words/phrases . Longer tables (slower access)
|
|
for the oddball ones. (small number of occurences, many unique entries)
|
|
Words can expire from one table to another based on usage. The fastest
|
|
DB's do this now transparantly.
|
|
|
|
But back to my original objection, can we move to technology like this
|
|
without having to become DB admins? I do think large gateway style
|
|
commercial sites could justify the migration.
|
|
|
|
Just some ideas!
|
|
|
|
|
|
Alan Barrow km4ba | If a little knowledge.....
|
|
Work: jab@atl.hp.com | is a dangerous thing.....
|
|
Home: alan@km4ba.ampr.org | then what is the Anti-Dote???
|
|
|
|
------------------------------
|
|
|
|
From: eric@news.db.erau.edu (m.s. saed arafat)
|
|
Crossposted-To: comp.os.linux.help,comp.windows.x.i386unix
|
|
Subject: Re: ATI Mach64... Does it work...?
|
|
Date: 8 Sep 1994 16:54:34 GMT
|
|
|
|
Pete Walker (pwalker@pinocchio.encore.com) wrote:
|
|
: Notice that Mach64 is listed under 'others' group in Hardware-HOWTO and
|
|
: just wanted to know if anyone has the Mach64 card working under
|
|
: Xfree and if so what was the proceedure used to get it going.
|
|
: I am purchasing one of these cards (VLB) and wants to know if it is a
|
|
: good decision or safe ivest investment. Thanks for your replys.
|
|
|
|
I have the ATI Graphics Xpression (VLB) which has the Mach64 chipset
|
|
running with X. The server is unaccelerated, but performance on my
|
|
machine still seems decent (486 66 w/ 8 Meg or RAM). It was simple
|
|
to set up since my monitor timmings where in the database. You
|
|
can get the ALPHA, unaccelerated server at:
|
|
|
|
sunsite.unc.edu
|
|
/pub/Linux/X11/X-servers/XF_SVGA_Mach64.tar.gz
|
|
|
|
Don't know if there is anyone working on an accelerated server,
|
|
maybe someone else can answer that question...
|
|
|
|
------------------------------
|
|
|
|
From: aab@loach.cichlid.com (Andy Burgess)
|
|
Subject: Re: NFS max timeout reached with 1.1.42
|
|
Date: 8 Sep 1994 11:38:36 -0700
|
|
|
|
In <3443dc$s37@rs1-hrz.uni-duisburg.de> kranz@sent3.uni-duisburg.de (Christian Kranz) writes:
|
|
|
|
>We have done the jump from kernel 1.1.0 to 1.1.42 before
|
|
>some days and are bothered now with the kernel error message
|
|
><6>NFS max timeout reached on sent5
|
|
>[...]
|
|
|
|
I see this too in 1.1.4x (for x=43,45,..) and 1.1.49. Just installed 1.1.50.
|
|
This problem has kept me at 1.0.9 until now.
|
|
|
|
For me it starts with:
|
|
|
|
Couldn't get a free page.....
|
|
IP: queue_glue: no memory for gluing queue 0x609318
|
|
IP: queue_glue: no memory for gluing queue 0x1237418
|
|
...
|
|
Couldn't get a free page.....
|
|
IP: queue_glue: no memory for gluing queue 0x1237158
|
|
NFS max timeout reached on cichlid
|
|
...
|
|
Couldn't get a free page.....
|
|
nfs_statfs: statfs error = 5
|
|
...
|
|
|
|
Then after about 5 minutes it comes back and all the nfs directories
|
|
are available again.
|
|
|
|
Any guesses?
|
|
|
|
Thanks very much
|
|
Andy
|
|
|
|
PS. I've kept the same rpc.nfsd from 1.0.9 (slackware 1.2). Does this
|
|
(and other /usr/sbin/rpc.* programs) need to be upgraded?
|
|
|
|
Didn't see anything in the kernel README :-)
|
|
|
|
|
|
--
|
|
Andrew A. Burgess aab@cichlid.com
|
|
Free newsfeeds and SLIP, Santa Cruz CA area, mail info@cichlid.com
|
|
|
|
------------------------------
|
|
|
|
From: robisojf@uc.edu (Tiger II)
|
|
Subject: Re: OS/2.99 Boot Manager and LINUX Slackware problems
|
|
Date: 9 Sep 1994 16:32:34 GMT
|
|
|
|
In article <34iok4$6ki@liberator.et.tudelft.nl>, robisojf@uc.edu (Tiger II) says:
|
|
>
|
|
>I repartioned my hard drive with OS/2 2.99 and then installed Linux. Now
|
|
>boot manager says the drive is not formated at all. Any suggestions would
|
|
>be helpful. Thanks in advance.
|
|
|
|
The problem was that some of the FSPed disks from nctuccca.edu.tw appeared to be
|
|
not up to CRC checks. Also, some of the files became cross-linked. The
|
|
files for ftp.cdrom.com cleared up the problem and all is well :)
|
|
|
|
____________ _ _ | Address: robisojf@uc.edu
|
|
_/ / / / | Descript: SDA, spelunker
|
|
_/ / / | Banjo, Guitar
|
|
_/ / /--/ /--| /---| / / | Mandolin, Dobro,
|
|
_/ / / / /--/ / / / | three kids,
|
|
_/ _/ /__/ /__ / _/ _/ | OS/2 Fan, GUI
|
|
/ member, Linux Fan
|
|
_/ "My opinion is expressed as: I'm Mister Cellophane Man."
|
|
|
|
------------------------------
|
|
|
|
From: deuelpm@craft.camp.clarkson.edu (Pete Deuel)
|
|
Crossposted-To: comp.os.linux.admin,comp.os.linux.help,comp.os.linux.misc
|
|
Subject: Re: PCI+Pentium+Linux+X?
|
|
Date: Fri, 9 Sep 1994 01:16:21 GMT
|
|
|
|
In article <34khnj$4f@apakabar.cc.columbia.edu> djt1@ciao.cc.columbia.edu (David J Topper) writes:
|
|
>From: djt1@ciao.cc.columbia.edu (David J Topper)
|
|
>Subject: PCI+Pentium+Linux+X?
|
|
>Date: 7 Sep 1994 14:12:03 GMT
|
|
|
|
>Subject: Pentium PCI + Linux X Motiff
|
|
>I could really use some help on the following:
|
|
|
|
>1) Does Linux support the Pentium?
|
|
|
|
Yup, ours is a Gateway P5-90 (a Gateway better than usual)
|
|
(PCI HOWTO)
|
|
|
|
>2) Does Linux support 32 | 64 bit Video (PCI)?
|
|
|
|
The gateway came with an ATI Mach 64; there's an experimental driver, which is
|
|
working great for us! 1024 x 768--woks spectacularly
|
|
(PCI HOWTO, X Free 86 HOWTO)
|
|
|
|
>3) Would an SCSI HD make life better?
|
|
|
|
Drive access speed will be much better (faster). SCSI may also make it easier
|
|
for you to add a CD ROM and such
|
|
(SCSI HOWTO, Installation HOWTO, I think)
|
|
|
|
>4) How does one get Linux + a GUI (X Windows
|
|
/ Motiff) + a C++ compiler> and other utils?
|
|
|
|
See Distribution HOWTO--Yggdrasil sells OSF Motif WM for Linux, however
|
|
I've been less than satidsfied with their non-standard file structure. I also
|
|
like Trans-Ameritech--if I had to do it again, I'd get the TA dist. and then
|
|
by Motif from Yggdrasil.
|
|
|
|
>5) Are there any major brand hardware peices I need to watch out for?
|
|
|
|
Read the HOWTOs to get a sense of it (theres even a Hardware HOWTO)
|
|
|
|
>6) Or, is there a list (are there lists) of Linux / Xfree86 / C++
|
|
> compatibility and availability w/respect to Pentium / PCI Video.
|
|
|
|
Yup. See The HOWTOs. They are at
|
|
|
|
sunsite.unc.edu /pub/Linux/docs/HOWTO
|
|
|
|
Basically, here's the lowdown--> read the HOWTOs + a little extra commentary.
|
|
Good Luck, Linuxer!
|
|
|
|
Pete
|
|
===================================================
|
|
"Actually, I'm a lab mouse on stilts..."
|
|
|
|
E-mail: deuelpm@craft.camp.clarkson.edu
|
|
===================================================
|
|
|
|
------------------------------
|
|
|
|
From: kender@esu.edu (Daniel Garcia)
|
|
Subject: Re: Future of linux -- the sequel
|
|
Date: 8 Sep 1994 14:36:06 -0400
|
|
Reply-To: kender@esu.edu
|
|
|
|
[flawed pentium prices deleted]
|
|
|
|
I have a 66Mhz pentium system, with 40 megs of ram, 28.8. modem,
|
|
420 meg HD, Soundblaster-16, 14 inch monitor, accelerated video card
|
|
w/2megs of memory and up to 1280x1024 resolution, all for about
|
|
$3500-3700. This machine outperforms the 150Mhz AlphaPC that sits right
|
|
next to it. (BTW - the machine runs quite nicely with only 8 megs of
|
|
ram as well, so you could probably knock about 600-1000 off of the price).
|
|
|
|
BTW - it runs linux like a dream - my only wish is that I could get
|
|
the damn floppy working (perhaps in a newer kernal it does, i have 1.0.8),
|
|
but then again, I don't need the floppy from linux.
|
|
|
|
D
|
|
|
|
--
|
|
===========.,======Coming=soon=to=a=PhD=Program=near=you=====.,==Carpe=Diem===
|
|
Ethernet is||Daniel Garcia - ATP Group - LLNL Gigabit Testbed||AntiClipperCens
|
|
for Sissies|| Lawrence Livermore Nat'l Labs - Livermore, CA ||orshipFightingF
|
|
Disclaimer.||dgarcia@cohl.llnl.gov <=-email-=> kender@esu.edu||reedomLovingCru
|
|
Try Linux || This .sig file (c)1994 by Daniel Garcia ||saderForRights.
|
|
----hi-----'`-PGP-key-available-finger-dgarcia@cohl.llnl.gov-'`---Coram-Deo---
|
|
Fibre Channel - Unix - TCP/IP - Music - MIDI - Biking - Networking - Reading
|
|
GCS/MU d? -p+ c++(----) l++ u+ e+(*) m+@ s/+ !n h f+@ !g w++ t++ r y?
|
|
|
|
------------------------------
|
|
|
|
Crossposted-To: comp.os.linux.misc
|
|
From: slouken@cs.ucdavis.edu (Sam Oscar Lantinga)
|
|
Subject: Re: 320x200 X resolution?
|
|
Date: Fri, 9 Sep 1994 22:25:38 GMT
|
|
|
|
Christopher Wiles (a0017097@wsuaix.csc.wsu.edu) wrote:
|
|
|
|
: Good God, why?!?
|
|
|
|
DOOM for Linux, why else? ;-)
|
|
|
|
: Well ... I suppose you could use the monitor config spreadsheet at
|
|
: sunsite (/pub/Linux/X11 is the closest I can point you ... sunsite is
|
|
: still down). Plug in the rez and you'll get timings.
|
|
|
|
Hmm.
|
|
|
|
: Yeah ... fingering help@idsoftware.com reveals the same message re: Linux
|
|
: port as it has for the last two months: "RSN!! RSN!!"
|
|
|
|
I suppose you speak in ignorance. :) It's out, and
|
|
available from sunsite.unc.edu in /pub/Linux/Incoming and at
|
|
dewdrop.water.ca.gov in /pub/doom as the file lnxdoom.tgz
|
|
|
|
Enjoy folks! *grin*
|
|
|
|
|
|
: Seriously, IMHO Doom will probably be more useable in the promised
|
|
: pixel-doubling mode than in a straight 320x200. Easier to make things
|
|
: look innocent when the boss walks in ... "Hey, you're not actually
|
|
: _working_ in 320x200, are you?"
|
|
|
|
Well, a couple of things... I've tried it in pixel doubling
|
|
mode, and not only is it slower, but the display is broken. It looks
|
|
like you are looking through one of those windows with glass ribs.
|
|
Also... if you should happen to be one of those that actually play
|
|
games at work, you might want to know that Ctrl-Alt-+ and Ctrl-Alt--
|
|
change X11 resolutions on the fly at the Linux console. :)
|
|
|
|
So.... 320x200 resolution anyone? :)
|
|
I'll post if I figure out how to do it.
|
|
|
|
Thanks,
|
|
|
|
-Sam
|
|
|
|
|
|
------------------------------
|
|
|
|
|
|
** 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: Linux-Development-Request@NEWS-DIGESTS.MIT.EDU
|
|
|
|
You can send mail to the entire list (and comp.os.linux.development) via:
|
|
|
|
Internet: Linux-Development@NEWS-DIGESTS.MIT.EDU
|
|
|
|
Linux may be obtained via one of these FTP sites:
|
|
nic.funet.fi pub/OS/Linux
|
|
tsx-11.mit.edu pub/linux
|
|
sunsite.unc.edu pub/Linux
|
|
|
|
End of Linux-Development Digest
|
|
******************************
|