Re: first impressions after upgrading from 3.4-RELASE to 4.0-20000209-CURRENT

2000-02-12 Thread David O'Brien
On Thu, Feb 10, 2000 at 06:08:36PM +0100, Jose M. Alcaide wrote: >/usr/X11R6/bin/XF86_SVGA: > libxpg4.so.2 => /usr/lib/libxpg4.so.2 (0x282ee000) > libz.so.2 => /usr/lib/libz.so.2 (0x282f2000) > libm.so.2 => /usr/lib/libm.so.2 (0x282ff000) > libc.so.3 => /usr/lib

Re: first impressions after upgrading from 3.4-RELASE to 4.0-20000209-CURRENT

2000-02-11 Thread Ricardo Bernardini
Devices that show on visual user config are the ones that have a driver built into the kernel, which has no relation to automatically detected devices. Regards Ricardo >From: "Eugene M. Kim" <[EMAIL PROTECTED]> >| On Thu, 10 Feb 2000, Eugene M. Kim wrote: >| > It would be nice to state this a

Re: first impressions after upgrading from 3.4-RELASE to 4.0-20000209-CURRENT

2000-02-10 Thread Eugene M. Kim
On Fri, 11 Feb 2000, Matthew N. Dodd wrote: | On Thu, 10 Feb 2000, Eugene M. Kim wrote: | > It would be nice to state this at startup of userconfig then, since | > many users (including most of my friends) expect all their devices to | > show up there. | | Thats not what userconfig is for. Righ

Re: first impressions after upgrading from 3.4-RELASE to 4.0-20000209-CURRENT

2000-02-10 Thread Matthew N. Dodd
On Thu, 10 Feb 2000, Eugene M. Kim wrote: > It would be nice to state this at startup of userconfig then, since > many users (including most of my friends) expect all their devices to > show up there. Thats not what userconfig is for. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | F

Re: first impressions after upgrading from 3.4-RELASE to 4.0-20000209-CURRENT

2000-02-10 Thread Eugene M. Kim
On Thu, 10 Feb 2000, Matthew N. Dodd wrote: | Not all devices are listed in the boot configuration screen; it is for | devices that do not support auto-detection. It would be nice to state this at startup of userconfig then, since many users (including most of my friends) expect all their device

Re: first impressions after upgrading from 3.4-RELASE to 4.0-20000209-CURRENT

2000-02-10 Thread David Wolfskill
OK; I'm cheating a bit, since I didn't really "upgrade" -- I waylaid our backup server, which gets beat on in the morning, and installed the 4.0-2208-CURRENT onto some otherwise-unused disk on the box. I can certainly report that the "custom" install doesn't SIGSEGV. :-) (Only thing I found

Re: first impressions after upgrading from 3.4-RELASE to 4.0-20000209-CURRENT

2000-02-10 Thread Jose M. Alcaide
Kenneth Wayne Culver wrote: > > >Hummm... This is ugly. This means that the XFree86 3.3.6 which will > >be distributed with 4.0-RELEASE needs the "compat3x" libraries. > >This should be documented somewhere. > > if you cd to /usr/ports/x11/XFree86 and do a make... this problem will b

Re: first impressions after upgrading from 3.4-RELASE to 4.0-20000209-CURRENT

2000-02-10 Thread Matthew N. Dodd
On Thu, 10 Feb 2000, Jose M. Alcaide wrote: > 1. Just after booting the install kernel, I went to the visual configuration >screen in order to disable all drivers for unexistent devices. My first >surprise was that the ep(4) driver was not listed. However, the install >kernel includes

first impressions after upgrading from 3.4-RELASE to 4.0-20000209-CURRENT

2000-02-10 Thread Jose M. Alcaide
I have just finished a net install of 4.0-2209-CURRENT using the sysinstall's "Upgrade" procedure, over a 3.4-RELEASE system. Well, the system is now running OK, but I found some small issues. First, I must say that I was not following the -CURRENT branch since the transition to 3.1-STABLE. T