upgraded to -CURRENT et al -- solved; X and PAM work for me

Dear FreeBSDers, after a couple of days spent RTFMing like crazy, I am back at my console at last ! (yawn ...) I have read some of the recent messages about X not working on -CURRENT as well as other issues. Although my -CURRENT sources are the same (last cvsup on 06-Mar-2000 11pm GMT), I seem

Re: upgraded to -CURRENT et al -- solved; X and PAM work for me

On Mon, Mar 13, 2000 at 12:29:14AM +, Salvo Bartolotta wrote: Dear FreeBSDers, after a couple of days spent RTFMing like crazy, I am back at my console at last ! (yawn ...) snip Am I the sole person running X (compiled with PAM support) without problems under -CURRENT ? :-)

upgraded to -CURRENT (?) et al.

Dear users, I (last) cvupped -CURRENT on 6 March at about 11:00 pm GMT, and, with few (necessary) variations, I tried to follow the instructions in UPDATING on the next day. I *seem* to have upgraded to -CURRENT. FWIW, here is what I did: 1) /usr/src/make -j48 buildworld 2)

upgraded to -CURRENT (?) et al. III

Dear users, I forgot to specify another point in my first letter: "N.B. I am Italian and I chose MD5, discarding everything DES-related. I suppose this has automagically eliminated a few problems." I chose MD5 when installing FreeBSD-3.3-Release, whence I upgraded to -STABLE and finally to

Re: upgraded to -CURRENT (?) et al. III

On Wed, 08 Mar 2000, in a never-ending search for enlightenment, Salvo Bartolotta wrote: Dear users, I forgot to specify another point in my first letter: "N.B. I am Italian and I chose MD5, discarding everything DES-related. I suppose this has automagically eliminated a few problems."