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 to have solved most of my difficulties. Remark I Since I am a bit paranoid, I remade the world once more (exactly by the book, except for m.m. of course), and, wait for it, I met NO errors in making installworld. NO errors. Even sysinstall, after making (it) clean, was made smoothly. I am running a full-blown -CURRENT :-)) [wild screams of joy censored] In the past few weeks, under a -STABLE installation of mine (which was to become my present -CURRENT), I had compiled XFree86-3.3.6 with PAM support, among other things. As I wrote a couple of days ago, I met authentication errors with my freshly-(re)made -CURRENT. However, my pam.conf and ttys files were perfectly correct. Thus I recompiled X (with PAM support yet again!) and this time ... it worked seamlessly. Am I the sole person running X (compiled with PAM support) without problems under -CURRENT ? :-) HTH, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 ? :-) Well, it works for me too. I use wdm with pam for pam_ssh.so's session features. Works great and it's a lot handier than having to open an xterm every session to 'ssh-add' or having ssh-askpass load up after login. -Chris -- [EMAIL PROTECTED] [EMAIL PROTECTED] Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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) /usr/src/sbin/mknod/make install 3) followed the directions to build/install a kernel. Remark: config -r core dumps (bad system call); config (no option) does not. 4) rebuilt disk /dev entries; updated the relevant files (/etc/fstab). In order not to forget anything, I issued various grep -r commands. 5) reboot in s.u.m. Remark I : the root partition is seen as wd1s2a; the others are seen correctly. Remark II: if one happens to reboot, one meets a FATAL TRAP; after rebooting, one is denied access to / . Workaround: I booted from another installation of mine (-STABLE) on another slice, and ran fsck from there. 6) /usr/src/make installworld I got this error: lib/libcom_errdoc [omissis] unrecognized option `--defsection=Programming development tools.' Error code 1 (six times) 7) /usr/src/usr.bin/xinstall/make clean all install NOSHARED=YES 8) /usr/src/make installworld It failed with the same errors as sub 6). 9) /usr/src/make -DNOINFO installworld I got another error: install: genassym: no such file or directory. Error code 71. Error code 1 (five times.) It was time to use ... the Force. 10) /usr/src/make -DNOINFO -k installworld 11) /usr/src/make -k installworld Alas, I did not log the sessions sub 10) and sub 11) because ... I did NOT believe I would succeed in making installworld #@[]*^ยง [severely censored] 12) mergemaster, devices, sysinstall and (yet another) kernel by the book. Remark I: making sysintall failed: undefined reference in pccard Initialize. Error code 1. Remark II: this time config -r worked. If I had used -k properly, I would have finished earlier. I suppose I am somehow running -CURRENT (?) N.B. I am Italian and I chose MD5, discarding everything DES-related. I suppose this has automagically eliminated a few problems. Under -STABLE, I used to compile my kernels with a0ffa0ff flags for my IDE disks 0 and 1, and b0ff for my third IDE disk. Under -CURRENT, I specified the ata driver as per the suggestions in LINT, and I did NOT specified ata0 and ata1; which are indicated for older systems. The log messages show that all three disks are accessed in UDMA 33 mode and are seen as having **16** heads. However, I must miss something obvious here (yawn) how can I specify the LBA mode for my third disk ? Is it automagically set ??? I fear I can corrupt part of my filesytems: my /usr lives on my third IDE disk (formerly accessed in LBA mode.) Another problem. I get "isa0: unexpected tag 14" while booting. What am I missing ? There are other questions: e.g. X authentication fails. Pam.conf and ttys are all right, though. Before attacking all of them (grepping -r the d***ed wd disks and recompiling the related ports ...), I would like to be in a position to recompile things in /usr without running any risks to destroy that filesystem. In this way, I will also be able te remake the world once more ... I thank you very much in advance for any help. Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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 -CURRENT. Sorry for these omissions :-( I should really go to bed *sigh* Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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." I chose MD5 when installing FreeBSD-3.3-Release, whence I upgraded to -STABLE and finally to -CURRENT. Sorry for these omissions :-( I should really go to bed *sigh* Best regards, Salvo Yeah, join the club. Read some of my screw-ups -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter:Where the hell am I? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message