Re: error with install, "Unable to make device nodes..."

1999-12-20 Thread Bob Willcox
lesystem > DEBUG: Scanning disk ad0 for swap partitions > DEBUG: MakeDev: Unable to lookup user "root". >[ last line repeated several times ] I am seeing this as well. I am also trying to install the 4.0-19991220-CURRENT snapshot (on an IBM 9G IDE drive). From scanning the so

Re: Mount msdos floppy

1999-12-20 Thread Edwin Culp
Doug White wrote: > On Sun, 19 Dec 1999, Edwin Culp wrote: > > > When I try to mount an msdos floppy, that I almost never do, I am > > getting the following: > > > > # mount -tmsdos /dev/fd0 /mnt > > msdos: vfsload(msdos): Exec format error > > Disk works in windows. > > > > Your /modules/msdos.k

Re: ESS 1868, newpcm,

1999-12-20 Thread Edwin Culp
Cameron, Thanks, my sound now works but something is different. I am getting very high frequency oscillations that I've never had and don't understand. It must have something to to with the mike and the speakers on my laptop but there has never been regenerative feedback between them before. C

Re: Recent current hangs frequently for 1 to 2 seconds.

1999-12-20 Thread Peter Jeremy
On 1999-Dec-21 12:08:27 +1100, Matthew Dillon <[EMAIL PROTECTED]> wrote: >Tape drives may: >* Not support disconnection ... >* Implement a crappy SCSI command stack ... >* Not properly terminate the SCSI bus ... >* Introduce too much noise onto the SCSI bus due to bad design.

Re: Recent current hangs frequently for 1 to 2 seconds.

1999-12-20 Thread Matthew Dillon
:It's possible you might be on to something. I've been running iostat :at 1 second intervals, and during the last hang I saw: : : ttyad2 da1 sa1 cpu : tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id : 36 142 7.

Re: Mount msdos floppy

1999-12-20 Thread Doug White
On Sun, 19 Dec 1999, Edwin Culp wrote: > When I try to mount an msdos floppy, that I almost never do, I am > getting the following: > > # mount -tmsdos /dev/fd0 /mnt > msdos: vfsload(msdos): Exec format error > Disk works in windows. > Your /modules/msdos.ko file is corrupted. cd /sys/modules

Re: Recent current hangs frequently for 1 to 2 seconds.

1999-12-20 Thread Greg Lehey
On Monday, 20 December 1999 at 16:19:06 -0800, Matthew Dillon wrote: > > :Thanks. I've put in the patch, but I'm still seeing the problems. It > :seems to be related to SCSI activity (I'm currently performing a > :backup on a DLT drive, and apart from that very little disk I/O). Any > :other id

Re: Recent current hangs frequently for 1 to 2 seconds.

1999-12-20 Thread Matthew Dillon
:Thanks. I've put in the patch, but I'm still seeing the problems. It :seems to be related to SCSI activity (I'm currently performing a :backup on a DLT drive, and apart from that very little disk I/O). Any :other ideas? It seems to me as if the whole system freezes :(keystrokes don't echo, f

Re: Status on building modula-3 and cvsup on -current ...

1999-12-20 Thread John Polstra
In article <[EMAIL PROTECTED]>, Bush Doctor I <[EMAIL PROTECTED]> wrote: > What's the latest on building modula 3 and cvsup on -current systems? It probably doesn't work right yet -- I'm not sure. I've been too busy and there have been too many code freezes to get the patches for the sigset_t e

Re: Recent current hangs frequently for 1 to 2 seconds.

1999-12-20 Thread Greg Lehey
On Saturday, 18 December 1999 at 20:16:53 -0800, Matthew Dillon wrote: >> I've just upgraded to -CURRENT as of yesterday, and I'm noticing a >> number of occasions where all activity ceases for a second or two at a >> time; it seems to be related to IDE disk activity with the new ATA >> driver, bu

Re: rlogin receiving sig 11 (randomly)

1999-12-20 Thread David O'Brien
> `rlogin -x' has consistently failed for me (sending garbage on the > transmit channel) since something happened a few months ago. It's > somewhere between September 10 (which still works on my desktop) and > late November (can't get a precise date right now) (which fails on my > laptop). Compi

Re: error with install, "Unable to make device nodes..."

1999-12-20 Thread Mike Heffner
On 20-Dec-99 Bill Fumerola said: | On Mon, 20 Dec 1999, Mike Heffner wrote: | |> |> Unable to make device node of /dev/ad0s1b in /dev! |> The creation of filesystems will be aborted. |> |> If I switch to the second virtual terminal it says: |> |> DEBUG: Scanning disk a

mic cannot be deactivated

1999-12-20 Thread Eric Lakin
It appears that the microphone controls for newpcm are not functioning, at least for my sound device. I've got a Vaio 505TX laptop. On probing the sound device, the speaker and mic together cause terrible feedback. mixer shows 0:0 for the mic, and adjusting this or using 'mixer -rec mic' has no e

Re: vm_page_remove panic

1999-12-20 Thread Tamiji Homma
Matt>What's your filesystem configuration? Do a 'df'. Are any of the Matt>filesystems non-standard? non-standard? You mean block size, etc? I don't have access to that machine right now but it should be what you call standard ;-) I'll get back to you later today. No special newfs fl

Re: error with install, "Unable to make device nodes..."

1999-12-20 Thread Bill Fumerola
On Mon, 20 Dec 1999, Mike Heffner wrote: > > Unable to make device node of /dev/ad0s1b in /dev! > The creation of filesystems will be aborted. > > If I switch to the second virtual terminal it says: > > DEBUG: Scanning disk ad0 for root filesystem > DEBUG: Scanning disk ad0 for swap pa

error with install, "Unable to make device nodes..."

1999-12-20 Thread Mike Heffner
[ sorry if you get this twice, it didn't seem to go through the first time ] I'm having a problem trying to install the 12/20/99 -current snapshot. When I finalize all the settings and sysinstall is about to partition/setup the drive I get the following message: Unable to make device node of /

Re: vm_page_remove panic

1999-12-20 Thread Matthew Dillon
:Hi, : :I have been seeing vm_page_remove panic three times since :last week. During make world once, cvsup twice. It seems :reproducible. : :Any clue? : :Thanks : :Tammy What's your filesystem configuration? Do a 'df'. Are any of the filesystems non-standard?

sio.c

1999-12-20 Thread Kenneth Wayne Culver
I have included a patch for my Diamond SupraExpress 56i to be detected: --- sio.c.orig Sat Dec 11 19:51:29 1999 +++ sio.c Sat Dec 11 19:51:20 1999 @@ -553,6 +553,7 @@ {0x31307256, NULL}, /* USR3031 */ {0x8020b04e, NULL},

Re: building world on pre-signals-change systems

1999-12-20 Thread Marcel Moolenaar
Ben Rosengart wrote: > > If I recall correctly, someone posted recently that the time is not far > off when one will be able to make world on an older, pre-signals-change > system. You can already do a buildworld, but you still have to make and install a new kernel in order to do a installworld.

Archive mirror problem

1999-12-20 Thread Forrest Aldrich
I'm trying to get a snapshot from current.freebsd.org and keep getting this error all morning: Failure at end of remote directory () because: timed out This is using mirror.pl. It's worked flawlessly in the past, and for everything else I do. Has something changed on current.freebsd.org?

rlogin receiving sig 11 (randomly)

1999-12-20 Thread Garrett Wollman
< said: >This happens very randomly - 1 out of 50. But, when it fails, it > typically fails multiple times as shown above. I've seen this over > the last 5 weeks or so. `rlogin -x' has consistently failed for me (sending garbage on the transmit channel) since something happened a few month

Status on building modula-3 and cvsup on -current ...

1999-12-20 Thread Bush Doctor I
What's the latest on building modula 3 and cvsup on -current systems? thanxs ... #:^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

building world on pre-signals-change systems

1999-12-20 Thread Ben Rosengart
If I recall correctly, someone posted recently that the time is not far off when one will be able to make world on an older, pre-signals-change system. Is there going to be an announcement when that happens, or has it perhaps happened already? I'm running an Oct 1 -current box, and I will eventu

is this really a bad disklabel?

1999-12-20 Thread Anthony Kimball
(This is probably a -questions issue, but I've tried without success, and the boot programs are all -current.) I can't seem to boot from wd1s3a. When I run the loader, and set currdev=disk2s3a, it won't ls, and when I try to lsdev, it says there is a bad partition table on wd1. I found it nece

Re: cc taking a signal 11

1999-12-20 Thread Bosko Milekic
On Mon, 20 Dec 1999, Thomas David Rivers wrote: !>> FreeBSD(root)/tmp %cc -O foo.c -o foo.o -c !>> cc: Internal compiler error: program cc1 got fatal signal 11 !>> !>> !>> !>> static void getsig11(parfree,dbl,lambda) !>> long parfree; !>> double *dbl; !>> double *lambda; !>> { !>> long

Re: ATA: more Promise Ultra wedges

1999-12-20 Thread Andrew Gallatin
Soren Schmidt writes: > It seems Andrew Gallatin wrote: > > > > Søren, > > > > It looks like I spoke to soon when I said the world was safe for > > Promise Ultra users: > > > > ad3: ad_timeout: lost disk contact - resetting > > ata4: resetting devices .. ad3: HARD WRITE ERROR blk# 659

Re: cc taking a signal 11

1999-12-20 Thread Thomas David Rivers
> >Nawww... I've tried this on a bunch of different machines.. as a matter > of fact it replicates with gcc version 2.7.2.1 from December of last > year. I find it hard to believe that I have 80 machines that all > exhibit the exact same memory failure... :-) > > -John > > > Yep - othe

Re: cc taking a signal 11

1999-12-20 Thread John W. DeBoskey
> > > > Hi, > > > >While I'm at it, a co-worker gave this one to me earlier today. > > > >cc: Internal compiler error: program cc1 got fatal signal 11 > > > >4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999 > > > > > > > > FreeBSD(root)/tmp %cc -v > > Using built

vm_page_remove panic

1999-12-20 Thread Tamiji Homma
Hi, I have been seeing vm_page_remove panic three times since last week. During make world once, cvsup twice. It seems reproducible. Any clue? Thanks Tammy snoopy# uname -a FreeBSD snoopy.pochi.com 4.0-CURRENT FreeBSD 4.0-CURRENT #94: Sun Dec 19 10:40:05 PST 1999 [EMAIL PROTECTED]:/usr

Empty core files left with coredumpsize=0 (Was Re: cc taking a signal 11)

1999-12-20 Thread FreeBSD mailing list
> Hi, > >While I'm at it, a co-worker gave this one to me earlier today. > >cc: Internal compiler error: program cc1 got fatal signal 11 > >4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999 > > > > FreeBSD(root)/tmp %cc -v > Using builtin specs. > gcc version 2.95.

Re: cc taking a signal 11

1999-12-20 Thread Thomas David Rivers
> > Hi, > >While I'm at it, a co-worker gave this one to me earlier today. > >cc: Internal compiler error: program cc1 got fatal signal 11 > >4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999 > > > > FreeBSD(root)/tmp %cc -v > Using builtin specs. > gcc version 2.

cc taking a signal 11

1999-12-20 Thread John W. DeBoskey
Hi, While I'm at it, a co-worker gave this one to me earlier today. cc: Internal compiler error: program cc1 got fatal signal 11 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999 FreeBSD(root)/tmp %cc -v Using builtin specs. gcc version 2.95.2 19991024 (release) Free

Re: current for production?

1999-12-20 Thread Kenneth Wayne Culver
I'm inclined to agree. I have had great luck in production boxes with FreeBSD-CURRENT, but it's not reccomended to use -CURRENT for production just because sometimes things break. :-) = | Kenneth Culver | FreeBSD: The b

rlogin receiving sig 11 (randomly)

1999-12-20 Thread John W. DeBoskey
Hi, Before I dig into this, I'd like to know if anyone else is seeing the following on -current: (Not tested/seen on stable/release). Dec 20 10:57:58 magenta /kernel: pid 9869 (rlogin), uid 227: exited on signal 11 Dec 20 10:58:02 magenta /kernel: pid 9875 (rlogin), uid 227: exited on signa

Re: current for production?

1999-12-20 Thread Ben Rosengart
On 20 Dec 1999, Fritz Heinrichmeyer wrote: > as there now is almost only talk about sound and ata drivers in this > list, would it be adviseable to use a current-snap on a server machine > (apache,samba,ftp) without need for sound and ata drivers (box with > aic-scsi-only drives)? > > The integr

Re: sh(1) broken caching [was: Re: Broken sh(1)?]

1999-12-20 Thread Martin Cracauer
In <[EMAIL PROTECTED]>, Brian Fundakowski Feldman wrote: > > Is there something substantially you'd like to contribute to the > > discussion, like - say - an example where bash-2.03 doesn't work well? > > It's definitely broken on some of my scripts before. If you want me > to go try to find o

Re: Got diskless Sun booting from FreeBSD server...

1999-12-20 Thread patrick
I'll put one together over the holidays :) Patrick On 20 Dec, Jesper Skriver wrote: > Hi, > > How about adding a "howto" to the handbook ? > > /Jesper > > On Sun, Dec 19, 1999 at 09:38:09PM +0100, Ron Klinkien wrote: >> >> Thanks to Ian Dowse and Patrick Gardella i got my SPARCclassic >> boo

Re: sh(1) broken caching [was: Re: Broken sh(1)?]

1999-12-20 Thread Brian Fundakowski Feldman
> > Over the last year, I did an extensive amount of testinging on bourne > shell behaviour. bash2 was the only free sh clone that I never had to > complain over. I'm surprised. > > Is there something substantially you'd like to contribute to the > discussion, like - say - an example where bas

Re: ESS 1868, newpcm, and Linux RealPlayer 5.0

1999-12-20 Thread Marcel Moolenaar
Cameron Grant wrote: > > The ESS 18xx support seems to be broken at the moment. I have one here and > > I'll fix it as soon as I get a chance to work on it. > > a recent commit changed the assumptions made by the upper layer code, > breaking devices not using auto-init dma. last night i committ

Re: Sound and -current.

1999-12-20 Thread Alexander Leidinger
On 19 Dec, Devin Butterfield wrote: > sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b > irq 5 drq1,3 on isa0 > pcm0: on sbc0 > unknown0: at port 0x201 on isa0r > > Of course I'm not using the game port. :) Just add "device joy0" to your config. sbc0: at port 0x220-0x22f,0x330-0x331,0x388

current for production?

1999-12-20 Thread Fritz Heinrichmeyer
as there now is almost only talk about sound and ata drivers in this list, would it be adviseable to use a current-snap on a server machine (apache,samba,ftp) without need for sound and ata drivers (box with aic-scsi-only drives)? The integrated gcc-2.95.2 is so handy and current does all i want

Re: ESS 1868, newpcm, and Linux RealPlayer 5.0

1999-12-20 Thread Cameron Grant
> On Sat, 18 Dec 1999, Donn Miller wrote: > > > I just rebuilt my kernel from a recent cvsup. Of course, I have > > > > device pcm0 > > device sbc0 > > > > in my kernel config file. When I try to play a realaudio clip > > with Linux rvplayer (RealPlayer 5.0), rvplayer downloads

SMP

1999-12-20 Thread Emre
Hi people, I went to ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-19991218-CURRENT/README.TXT and read that document. Most hardware that I need to use is supported on that list, but I have a question: is SMP enabled in the GENERIC kernel in FreeBSD 4.0-current? we have a server

Re: New sound driver and Linux games

1999-12-20 Thread Daniel O'Connor
On 19-Dec-99 Brian W. Buchanan wrote: > (and hence its sound system) in mind, not portability. snes9x plays > a half second of audio for me, then loops it a few times before > either SIGBUS or SIGSEGV. I've tried rebuilding it in case it had > something to do with include file changes, but

Re: PCCARD vs GENERIC

1999-12-20 Thread Nate Williams
> : So, my only comment is that if you believe that the code is stable > : enough to not negatively effect desktop systems, and not too much bloat, > : then have at it. Note, enabling PCCARD functionality w/out APM will be > : a losing situation for many laptops, and adding APM functionality for

Re: PCCARD vs GENERIC

1999-12-20 Thread Nate Williams
> PCCARD used to exist separate from GENERIC due to the zp and ze > drivers not being compatible with pccard's pcic driver. These drivers > were removed from the system not too long ago by phk. The reason I added PCCARD to the system was because in the old code, I didn't trust the PCCARD functio

Re: PCCARD vs GENERIC

1999-12-20 Thread Warner Losh
In message <[EMAIL PROTECTED]> Nate Williams writes: : So, my only comment is that if you believe that the code is stable : enough to not negatively effect desktop systems, and not too much bloat, : then have at it. Note, enabling PCCARD functionality w/out APM will be : a losing situation for ma

more fun && games...

1999-12-20 Thread Matthew Jacob
as far as I know, I have all sources up to date including today, but eventually I got (on a Tyan board): ad0: ad_timeout: lost disk contact - resetting ata0: resetting devices .. ata0: mask=01 status0=50 status1=00 ata0: master: success setting up WDMA2 mode on PIIX4 chip done To Unsubscri

more patch for secondary buffer, polling and DMA emulation in

1999-12-20 Thread Seigo Tanimura
ch; charset=US-ASCII Content-Disposition: attachment; filename="2ndbuf-19991220.diff" Content-Transfer-Encoding: 7bit diff -urN -x CVS -x compile -x SILVER -x RINA -x aic7xxx -x ata sys.apictimer/dev/sound/isa/ad1816.c sys.2ndbuf/dev/sound/isa/ad1816.c --- sys.apictimer/dev/sound/isa/ad181

Re: fsck not cleaning on first try

1999-12-20 Thread Mike Smith
> On Sun, 19 Dec 1999, Alex Zepeda wrote: > > > Hmm. It happened again. This time I was playing around with the vmware > > stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think > > this is the way to go, not bloating *our* procfs), and eventually when run > > panic'd the syste

Re: sh(1) broken caching [was: Re: Broken sh(1)?]

1999-12-20 Thread Brian Fundakowski Feldman
On Fri, 17 Dec 1999, Martin Cracauer wrote: > > I still think we should *seriously* consider switching to pdksh. > > As I said before, pdksh has other bugs. > Also we would loose all the PRs we received in the past. This testing > effort by our user base is a valuable resource. From the tests I

Re: fsck not cleaning on first try

1999-12-20 Thread Bill Fumerola
On Sun, 19 Dec 1999, Alex Zepeda wrote: > Hmm. It happened again. This time I was playing around with the vmware > stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think > this is the way to go, not bloating *our* procfs), and eventually when run > panic'd the system. I just r

fsck not cleaning on first try

1999-12-20 Thread Alex Zepeda
Hmm. It happened again. This time I was playing around with the vmware stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think this is the way to go, not bloating *our* procfs), and eventually when run panic'd the system. I just rebooted it (nearly a day later), and fsck cleaned

Re: fsck not cleaning on first try

1999-12-20 Thread Julian Elischer
On Sun, 19 Dec 1999, Mike Smith wrote: > > On Sun, 19 Dec 1999, Alex Zepeda wrote: > > Ditto. mount was telling me my fs wasn't clean, but after I rebooted > > it was fine and it didn't fsck that second time. > > Bruce posted (but did not commit) what may be a fix for this a while back: I wis

Re: No disks found msg in /stand/sysinstall, how come?

1999-12-20 Thread Vallo Kallaste
On Sun, Dec 19, 1999 at 08:45:17PM +, Nik Clayton <[EMAIL PROTECTED]> wrote: > > Well, thanks for the pointer, I've never looked at sysinstall > > build process. > > # cd /usr/src/release/sysinstall > # make all install > > This is in the "make world" section of the Handbook (makewo

Re: fsck not cleaning on first try

1999-12-20 Thread Mark Newton
On Sun, Dec 19, 1999 at 11:28:29PM -0500, Bill Fumerola wrote: > On Sun, 19 Dec 1999, Alex Zepeda wrote: > > Hmm. It happened again. This time I was playing around with the vmware > > stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think > > this is the way to go, not bloa

Re: Sound and -current.

1999-12-20 Thread Devin Butterfield
Julian Elischer wrote: > > So is there any chance that my Vibra16 Soundblaster will ever be > recognised again? > > I was surprised because I had imagined that the soundblaster would be the > first card supported under the new code. > > unknown0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b

Re: Sound and -current.

1999-12-20 Thread Chris Costello
On Sun, Dec 19, 1999, Julian Elischer wrote: > So is there any chance that my Vibra16 Soundblaster will ever be > recognised again? Did you add the sbc0 bridge driver to your kernel configuration file? (I managed to miss that heads-up the first time around too.) -- |Chris Costello <[EMAIL P

Sound and -current.

1999-12-20 Thread Julian Elischer
So is there any chance that my Vibra16 Soundblaster will ever be recognised again? I was surprised because I had imagined that the soundblaster would be the first card supported under the new code. unknown0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 7 drq 0,5 on isa0 unknown1: at po

Re: Sound and -current.

1999-12-20 Thread Julian Elischer
That's the hint I was looking for.. I had the pcm0 but didn't know we now had to add a special sbc entry.. THANKS! Now I know what I'm looking for i'll ge an dlook at LINT to see what else is in that vicinty. I guess I stopped reading at: # For pnp sound cards: #device pcm0 On Sun, 1

Re: SMP

1999-12-20 Thread Thierry Herbelot
Emre wrote: > > Hi people, > > I went to >ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-19991218-CURRENT/README.TXT >and read that document. > > Most hardware that I need to use is supported on that list, but I have a question: >is SMP enabled in the GENERIC kernel in FreeBSD 4.0

Re: sh(1) broken caching [was: Re: Broken sh(1)?]

1999-12-20 Thread Martin Cracauer
In <[EMAIL PROTECTED]>, Brian Fundakowski Feldman wrote: > On Fri, 17 Dec 1999, Martin Cracauer wrote: > > > > I still think we should *seriously* consider switching to pdksh. > > > > As I said before, pdksh has other bugs. > > > Also we would loose all the PRs we received in the past. This t

Re: ESS 1868, newpcm, and Linux RealPlayer 5.0

1999-12-20 Thread Doug Rabson
On Sat, 18 Dec 1999, Donn Miller wrote: > I just rebuilt my kernel from a recent cvsup. Of course, I have > > device pcm0 > device sbc0 > > in my kernel config file. When I try to play a realaudio clip > with Linux rvplayer (RealPlayer 5.0), rvplayer downloads the > clip, a

Re: make world broken with NO_FORTRAN=true

1999-12-20 Thread Marcel Moolenaar
Jos Backus wrote: > > After some more digging I have found out why buildworlds are failing on my > system: it's because I have NO_FORTRAN=true in /etc/make.conf. [snip] Thanks. Will be fixed. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking & Databases

make world broken with NO_FORTRAN=true

1999-12-20 Thread Jos Backus
After some more digging I have found out why buildworlds are failing on my system: it's because I have NO_FORTRAN=true in /etc/make.conf. cd /usr/src/gnu/usr.bin/cc/f771; make build-tools cc -O -pipe -march=pentium -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DD

Re: Got diskless Sun booting from FreeBSD server...

1999-12-20 Thread Jesper Skriver
Hi, How about adding a "howto" to the handbook ? /Jesper On Sun, Dec 19, 1999 at 09:38:09PM +0100, Ron Klinkien wrote: > > Thanks to Ian Dowse and Patrick Gardella i got my SPARCclassic > booting and running as a nice Xterminal server. [cut] > Thanks all. > Ron. /Jesper -- Jesper Skriver,