world breakage?
Sources from ~12 hours ago: === usr.bin/kdump cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/kdump.c cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c In file included from ioctl.c:79: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition In file included from ioctl.c:96: /usr/obj/usr/src/i386/usr/include/sys/cdrio.h:59: warning: `CDRIOCBLANK' redefined /usr/obj/usr/src/i386/usr/include/sys/wormio.h:102: warning: this is the location of the previous definition In file included from ioctl.c:30: /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:883: syntax error before `bus_dmamap_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1016: syntax error before `bus_dmamap_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1024: syntax error before `bus_space_tag_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1028: syntax error before `bus_addr_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1045: syntax error before `bus_dma_tag_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1136: syntax error before `bus_addr_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1273: syntax error before `bus_space_tag_t' In file included from ioctl.c:33: /usr/obj/usr/src/i386/usr/include/dev/vinum/vinumio.h:104: `MAXNAME' undeclared here (not in a function) ioctl.c: In function `ioctlname': ioctl.c:140: sizeof applied to an incomplete type ioctl.c:236: sizeof applied to an incomplete type ioctl.c:306: sizeof applied to an incomplete type ioctl.c:374: sizeof applied to an incomplete type ioctl.c:694: sizeof applied to an incomplete type ioctl.c:1074: sizeof applied to an incomplete type ioctl.c:1422: sizeof applied to an incomplete type ioctl.c:1470: sizeof applied to an incomplete type ioctl.c:1838: `dpt_perf_t' undeclared (first use in this function) ioctl.c:1838: (Each undeclared identifier is reported only once ioctl.c:1838: for each function it appears in.) ioctl.c:1874: sizeof applied to an incomplete type *** Error code 1 Stop in /usr/src/usr.bin/kdump. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: world breakage?
On Thu, Jan 27, 2000 at 09:39:10AM +0100, Dag-Erling Smorgrav wrote: Sources from ~12 hours ago: === usr.bin/kdump ... In file included from ioctl.c:79: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined Peter Wemm fixed this as src/include/Makefile rev 1.109 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-passwd
On Thu, 27 Jan 2000 00:23:23 PST, "David O'Brien" wrote: I think what you really want is: sed 's/^\([^:#@+-]*\):[^:]*:/\1:(password):/' Eeek, I don't know why I sent you that. It should have been: sed 's/^\([ +-][^+-][^:]*\):[^:]*:/\1:(password):/' Sorry about that. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
realhostname_sa bug
There was a bug in realhostname_sa() in lib/libutil and
sometime daemon using it dies, such as telnetd.
I think following patch will fix it, but now checking make
world before actually committing it.
If anyone experienced same problem, please try following
patch.
Sorry for your troubles.
Yoshinobu Inoue
Index: realhostname.c
===
RCS file: /home/ncvs/src/lib/libutil/realhostname.c,v
retrieving revision 1.4
diff -u -r1.4 realhostname.c
--- realhostname.c 2000/01/25 14:51:57 1.4
+++ realhostname.c 2000/01/27 11:37:08
@@ -122,8 +122,10 @@
port = ((struct sockinet *)addr)-si_port;
((struct sockinet *)addr)-si_port = 0;
if (!memcmp(sa, addr, sa-sa_len)) {
- strncpy(host, res-ai_canonname,
- hsize);
+ if (res-ai_canonname != 0)
+ strncpy(host,
+ res-ai_canonname,
+ hsize);
result = HOSTNAME_FOUND;
((struct sockinet *)addr)-si_port =
port;
@@ -146,8 +148,10 @@
if (IN6_IS_ADDR_V4MAPPED(in6)
!memcmp(in6-s6_addr[12], in,
sizeof(*in))) {
- strncpy(host, res-ai_canonname,
- hsize);
+ if (res-ai_canonname != 0)
+ strncpy(host,
+ res-ai_canonname,
+ hsize);
result = HOSTNAME_FOUND;
break;
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-passwd
On Thu, 27 Jan 2000 00:23:23 PST, "David O'Brien" wrote:
I think what you really want is:
sed 's/^\([^:#@+-]*\):[^:]*:/\1:(password):/'
Eeek, I don't know why I sent you that. It should have been:
sed 's/^\([ +-][^+-][^:]*\):[^:]*:/\1:(password):/'
IMNSO sed is the wrong tool here, awk can deal with the
password file much easier than sed and should handle just
about any input just so long as it doesn't add any :'s to the
lines that we are trying to mungle the password out of:
BEGIN {FS=":"; OFS=":"; ORS=""}
// {if (NF==10) {
print $1,"(password):"
for (n = 3; n =NF; n++) print $n,"";
} else
print $0;
print "\n";
Defantily works on diff, diff -u and diff -c.
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-passwd
On Thu, 27 Jan 2000 04:11:38 PST, "Rodney W. Grimes" wrote: sed 's/^\([ +-][^+-][^:]*\):[^:]*:/\1:(password):/' IMNSO sed is the wrong tool here, No arguments from me, since my awk skills are limited. However, I'll point out that sed is doing a decent job without turning into an invocation mess. The awk program you sent is much longer. Oh, and it produces absolutely no output whatsoever over here. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ASDM and linux emulation?
I would like to use an ASDM (backup software) with linux-emulation. I get the following in /var/log/messages: es-i2 /kernel: linux: syscall setresuid is obsoleted\ or not implemented (pid=41052) Jan 27 13:12:42 es-i2 /kernel: pid 41052 (dsm), \ uid 0: exited on signal 11 (core dumped) as netscape and acroread work quite good i think the core dump is related to the former failure. What is the problem with this syscall? This can be a show stopper for the server box ... I hate all this silly problems with mandrake-linux etc. -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ASDM and linux emulation?
On Thu, Jan 27, 2000 at 01:39:38PM +0100, F. Heinrichmeyer wrote: I would like to use an ASDM (backup software) with linux-emulation. I get the following in /var/log/messages: Have you tried the SCO client with the IBCS module loaded? I've been using it with great success for a while. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville [EMAIL PROTECTED] PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
subscribe freebsd-current
subscribe freebsd-current
N
'²æìr¸{û Ù[h¨èÚ£ñkyàRú+û§²æìr¸yúÞy» ýË«éíþ)í
æèw* ¶¦zË
Re: Sendmail on current
On 26 Jan 2000 20:33:31 +0100, Eric Jacoboni wrote: in CURRENT, /usr/sbin/sendmail is a symlink to /usr/sbin/mailwrapper (see man mailwrapper). No, it's a hard link. I only mention this because your explanation makes it sound like mailwrapper generates much more overhead than it really does: In CURRENT, the command 'sendmail' runs the mailwrapper program which, in turn, runs the correct ones according to /etc/mail/mailer.conf (there's an exemple in 'man mailer.conf'). Anyway, this guy's problem is just the location of mailer.conf, which you got right, so he should be fine. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sendmail on current
Sheldon Hearn [EMAIL PROTECTED] writes: On 26 Jan 2000 20:33:31 +0100, Eric Jacoboni wrote: in CURRENT, /usr/sbin/sendmail is a symlink to /usr/sbin/mailwrapper (see man mailwrapper). No, it's a hard link. I only mention this because your explanation makes it sound like mailwrapper generates much more overhead than it really does: No, not on my box (as far as i believe 'ls' and 'file' ;-) : % ls -l /usr/sbin/sendmail lrwxr-xr-x 1 root wheel 21 26 jan 23:54 /usr/sbin/sendmail - /usr/sbin/mailwrapper % file /usr/sbin/sendmail /usr/sbin/sendmail: symbolic link to /usr/sbin/mailwrapper The mailwrapper manpage also pretends it's a symlink... -- - Éric Jacoboni « No sport, cigars! » (W. Churchill) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sendmail on current
On 27 Jan 2000 15:25:55 +0100, Eric Jacoboni wrote: No, not on my box (as far as i believe 'ls' and 'file' ;-) : % ls -l /usr/sbin/sendmail lrwxr-xr-x 1 root wheel 21 26 jan 23:54 /usr/sbin/sendmail - /usr/sbin/mailwrapper My humble apologies. No more drugs for me. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipsec errors
Yoshinobu Inoue [EMAIL PROTECTED] writes: I just added debug flag check instead of changing syslog level. Could you please try the following patch to usr.sbin/inetd/inetd.c ? Ok, i had the same pbs with ipsec messages at startup (since my last make world, yesterday evening)... I've applied your patch : the messages have gone... thanks, -- Eric Jacoboni Ta mère, son mot de passe c'est « toto » ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipsec errors
level. Could you please try the following patch to usr.sbin/inetd/inetd.c ? Ok, i had the same pbs with ipsec messages at startup (since my last make world, yesterday evening)... I've applied your patch : the messages have gone... thanks, -- Eric Jacoboni Thanks, I committed it. Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ep0 incorrectly probed
I downloaded the 2000/01/25 snapshot of current today. When I booted from floppy, this message showed up: ep0: eeprom failed to come ready (5 times) and a NIC address of 0:0:0:0:0:0 was reported back. When booting this machine with 3.4-RELEASE, the correct NIC address is reported. When ifconfiging the interface, the machine hangs. The kernel knows the right ioport/irq, and works correctly with both 3.4-RELEASE and Windows 95. I didn't install CURRENT on it, since I wanted to install it by FTP... Quick info of the machine: Pentium 100 P/I-P55SP4 rev 1.4 motherboard (SiS550x chipset) 32 MB RAM 3COM 509 ISA ethernet card (BNC) Hercules Stingray 64 video Edwin Mons To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Folks, please try to spread out your cvsups a bit better....
I suspect I'm not the only mirror operator who sees a huge load spike early in the morning: --- start of forwarded message (RFC 934 encapsulation) --- From: [EMAIL PROTECTED] Apparently-To: [EMAIL PROTECTED] Subject: xyz.lcs.mit.edu daily run output Date: Thu, 27 Jan 2000 01:59:01 -0500 (EST) [deletia] xyz up 7+10:08, 0 users, load 11.77, 9.93, 6.09 [deletia] --- end --- You'll probably get better service if you cvsup at 8 AM or 10 PM (ET). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipsec errors
I'm at work now, so I can't apply the patches till I go home again (at
work I have Sun boxes and a linux box, blahh)
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems Administrator | ICQ #: 24767726 |
| and student at The | AIM: AgRSkaterq |
| The University of Maryland, | Website: (Under Construction) |
| College Park. | http://www.wam.umd.edu/~culverk/|
=
On Thu, 27 Jan 2000, Yoshinobu Inoue wrote:
Maybe there was a message on here that I overlooked, I'm not sure, but how
exactly do I get rid of them?
It is not harmful but I should have lower the syslog level,
sorry.
I'll soon fix it.
I just added debug flag check instead of changing syslog
level.
Could you please try the following patch to
usr.sbin/inetd/inetd.c ?
Thanks,
Yoshinobu Inoue
Index: inetd.c
===
RCS file: /home/ncvs/src/usr.sbin/inetd/inetd.c,v
retrieving revision 1.75
diff -u -r1.75 inetd.c
--- inetd.c 2000/01/25 14:52:10 1.75
+++ inetd.c 2000/01/27 04:41:15
@@ -1256,7 +1256,8 @@
buf = ipsec_set_policy(policy_in, strlen(policy_in));
if (buf != NULL) {
if (setsockopt(sep-se_fd, level, opt,
- buf, ipsec_get_policylen(buf)) 0) {
+ buf, ipsec_get_policylen(buf)) 0
+ debug != 0) {
syslog(LOG_ERR,
"%s/%s: ipsec initialization failed; %s",
sep-se_service, sep-se_proto,
@@ -1271,7 +1272,8 @@
buf = ipsec_set_policy(policy_out, strlen(policy_out));
if (buf != NULL) {
if (setsockopt(sep-se_fd, level, opt,
- buf, ipsec_get_policylen(buf)) 0) {
+ buf, ipsec_get_policylen(buf)) 0
+ debug != 0) {
syslog(LOG_ERR,
"%s/%s: ipsec initialization failed; %s",
sep-se_service, sep-se_proto,
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ipsec errors
I'm at work now, so I can't apply the patches till I go home again (at work I have Sun boxes and a linux box, blahh) It is OK, because Eric Jacoboni kindly tried the patch instead. I already committed it. Thanks for taking care for it. Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ascii art in hosts.allow
But...but... ITS SUCH AN EYE-SORE! all depends on what image of professionalism freebsd thinks it is trying to project. randy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: help! need kernel!
cpiazzOn Wed, Jan 26, 2000 at 07:26:30PM +0200, Alexandr Listopad wrote: cpiazz hello! cpiazz cpiazz I have Abit motherboard with ATA-66 support. cpiazz I try to install FreeBSD-CURRENT, all good when install, but after reboot cpiazz kernel boots, but ask me a root device, when I press '?', there are no cpiazz 'ad' device (this is my HDD). ;( As I understand - there are no support in cpiazz that kernel for my HDD... ;( cpiazz cpiazz As I understand there are one way to help me - create new kernel with cpiazz ata-pci0 support. cpiazz cpiazzThe boot floppies have ATA in the kernel. I installed a new system on cpiazza BP6 with the hard drive on one of the HPT366 controllers just fine cpiazzabout two weeks ago. Sorry, but I have no idea what is going on cpiazzhere.. I just wanted to say that it worked for me cpiazz cpiazzata-pci1: HighPoint HPT366 ATA-66 controller port 0xd400-0xd4ff,0xd000-0xd003, cpiazz0xcc00-0xcc07 irq 18 at device 19.0 on pci0 cpiazz... cpiazzad4: 12949MB disk IBM-DJNA-371350 at ata2 as master mode UDMA66 cpiazz cpiazzBTW, sos, if you're reading this: I like this format for reporting cpiazzthe hard drives present a lot better :-). All nice, in the install process... My disk is ad4sXX in install, but after reboot it is ad0xxx - why? Another questions in yesturdays cvsup I get full sources, but when I try to make world make says: /usr/src/tools/install.sh Can't open /usr/src/tools/install.sh *** Error code 2 ... there no tools/ dir in /usr/src - why? this is my supfile: *default host=cvsup2.ua.freebsd.org *default base=/usr/src-4.0 *default prefix=/usr/src-4.0 *default release=cvs *default tag=. *default delete use-rel-suffix doc-all src-base src-bin src-contrib src-etc src-gnu src-include src-lib src-libexec src-release src-sbin src-share src-sys src-usrbin src-usrsbin Thnaks. Regards, Listopad Alexandr ([EMAIL PROTECTED]), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: src/include/Makefile,v 1.109 is broken
On Thu, 27 Jan 2000 17:00:58 +0200, Ruslan Ermilov wrote: An attached patch seems to fix the problem. Does anybody actually understand what's really going on in this file? Everyone uses the words "seems to" and "I think" when they're proposing fixes in this file. I propose that we hold out for a fix which is accompanied by comments that explain what the hell all these oddball variables are used for and why SHARED is overridden (or used at all in the buildworld case). Ruslan, if I misunderstood your words, please don't take offense. It's just that this'll be the 5th commit in this regard without comment from Marcel, who was responsible for rewriting most of this Makefile recently. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Folks, please try to spread out your cvsups a bit better....
Today Garrett Wollman wrote: I suspect I'm not the only mirror operator who sees a huge load spike early in the morning: I plead guilty, your honor. When are the low load times. -- Jack O'NeillSystems Administrator / Systems Analyst [EMAIL PROTECTED] Crystal Wind Communications, Inc. Finger [EMAIL PROTECTED] for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages /dev/null -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: src/include/Makefile,v 1.109 is broken
On Thu, Jan 27, 2000 at 06:34:08PM +0200, Sheldon Hearn wrote: On Thu, 27 Jan 2000 17:00:58 +0200, Ruslan Ermilov wrote: An attached patch seems to fix the problem. Does anybody actually understand what's really going on in this file? Everyone uses the words "seems to" and "I think" when they're proposing fixes in this file. Disregard my "seems" word above, it really fixes the problem ;=) BTW, I has given a comment: | The idea was that `copies' should first undo all the | things `symlinks' did, but it is broken now. I propose that we hold out for a fix which is accompanied by comments that explain what the hell all these oddball variables are used for and why SHARED is overridden (or used at all in the buildworld case). Obviously, to speed up the building process. Ruslan, if I misunderstood your words, please don't take offense. It's just that this'll be the 5th commit in this regard without comment from Marcel, who was responsible for rewriting most of this Makefile recently. I was told by Alexey Zelkin that Marcel was hired by some giant company, and he asked for FreeBSD vacation for some time (though I personally did not see such a message)... -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 incorrectly probed
On Thu, 27 Jan 2000, Edwin Mons wrote: I downloaded the 2000/01/25 snapshot of current today. When I booted from floppy, this message showed up: ep0: eeprom failed to come ready (5 times) Humm... Please boot verbose and send me the output. This may require you to use a serial console. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Folks, please try to spread out your cvsups a bit better....
On Thu, Jan 27, 2000 at 10:29:13AM -0500, Garrett Wollman wrote: I suspect I'm not the only mirror operator who sees a huge load spike early in the morning: The reason for this is probably because many people like to cron cvsup early in the morning, when they're not using the computer. You're right - they need to even it out during the day. xyz up 7+10:08, 0 users, load 11.77, 9.93, 6.09 Wow, that high? I think xyz also does FTP mirror, doesn't it? -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 incorrectly probed
"Matthew N. Dodd" wrote: On Thu, 27 Jan 2000, Edwin Mons wrote: I downloaded the 2000/01/25 snapshot of current today. When I booted from floppy, this message showed up: ep0: eeprom failed to come ready (5 times) Humm... Please boot verbose and send me the output. This may require you to use a serial console. Used my Palm III as console... Regards, Edwin Mons ok boot -v SMAP type=01 base= len= 000a SMAP type=02 base= 000f len= 0001 SMAP type=01 base= 0010 len= 01f0 SMAP type=02 base= fffe len= 0002 Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-2124-CURRENT #2: Mon Jan 24 16:18:58 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/BOOTMFS Calibrating clock(s) ... TSC clock: 99451420 Hz, i8254 clock: 1192915 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 99474313 Hz CPU: Pentium/P54C (99.47-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 33554432 (32768K bytes) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x005f9000 - 0x01ffdfff, 27283456 bytes (6661 pages) config intro *** intro skipped *** avail memory = 26726400 (26100K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fc810 bios32: Entry = 0xfcd20 (c00fcd20) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xcd50 pnpbios: Found PnP BIOS data at 0xc00fdb10 pnpbios: Entry = f:610 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: Preloaded elf kernel "kernel" at 0xc05e. Preloaded mfs_root "/mfsroot" at 0xc05e0090. Intel Pentium detected, installing workaround for F00F bug md0: Preloaded image /mfsroot 2949120 bytes at 0xc030e5f8 Creating DISK md0 md1: Malloc disk Creating DISK md1 Math emulator present pci_open(1):mode 1 addr port (0x0cf8) is 0x8084 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=55111039) npx0: math processor on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 86318515 bytes/sec bzero() bandwidth = 43372657 bytes/sec pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=55111039) pcib0: Host to PCI bridge on motherboard found- vendor=0x1039, dev=0x5511, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found- vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found- vendor=0x1039J, dev=0x5513, revid=0x07 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=0 map[10]: type 1, range 32, base e800, size 3 map[14]: type 1, range 32, base e400, size 2 map[18]: type 1, range 32, base e000, size 3 map[1c]: type 1, range 32, base d800, size 2 map[20]: type 1, range 32, base d400, size 4 found- vendor=0xedd8, dev=0xa099, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[10]: type 1, range 32, base fb80, size 22 pci0: PCI bus on pcib0 isab0: SiS 85c503 PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 ata-pci0: SiS 5591 ATA-33 controller port 0xd400-0xd40f,0xd800-0xd803,0xe000-0 xe007,0xe400-0xe403,0xe800-0xe807 irq 0 at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xd400 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xd408 ata1: mask=03 status0=00 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc ata1 at 0x0170 irq 15 on ata-pci0 vga-pci0: ARK Logic 2000PV SVGA controller mem 0xfb80-0xfbbf at device 10.0 on pci0 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa0: if_ep: 3Com 3C509-BNC EtherLink III at port 0x300-0x310 irq 10 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fe0: EEPROM(SSI): 0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 40: ff
Re: ep0 incorrectly probed
Using the boot configuration screen can you disable all devices that are not installed? I suspect something is clobbering the board after it is identified. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: locking problem FreeBSD 3.4 - kermit and mgetty
On Wed, Jan 26, 2000 at 11:13:55PM +0100, Gert Doering wrote: Hi, On Tue, Jan 25, 2000 at 08:51:40PM +0100, Christoph Kukulies wrote: But as a result mgetty gets into kermit's ways such that when a modem connection is made I suddenly get a modem prompt like +FCON as if someone (mgetty) is either messing with my local or the remote modem while kermit opens the connection. The modem is in fax mode, and has established a fax connection. Have kermit send an AT+FCLASS=0 first. OK, this may be a repair but I'm wondering why that worked before and now I have to take special measures. Or is it perhaps kermit's fault? gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany [EMAIL PROTECTED] fax: +49-89-35655025[EMAIL PROTECTED] -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
strange ATA stuff (was: ep0 incorrectly probed)
"Matthew N. Dodd" wrote: Using the boot configuration screen can you disable all devices that are not installed? I suspect something is clobbering the board after it is identified. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | I tried that. It worked. Thanks a lot! Looks like the fe0 driver was the one messing it up for my ep0. Now back to the install. Another weird thing: as you could see in the boot dump, a Seagate UDMA2 drive has been detected. After sysinstall starts, I see the following messages on vty1: ad0: ad_timeout: lost disk contact - resetting ata0: resetting devices .. ata0-master: timeout waiting for command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ad0: ad_timeout: lost disk contact - resetting ata0: resetting devices .. ata0-master: timeout waiting for command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ad0: ad_timeout: lost disk contact - resetting ata0: resetting devices .. ata0-master: timeout waiting for command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ad0: ad_timeout: lost disk contact - resetting ata0-master: timeout waiting for command=ef s=fc e=00 ad0: ad_timeout: trying fallback to PIO mode ata0: resetting devices .. done and the setup continues as if nothing has happened. The drive is configured as PIO mode 4 in the BIOS (the BIOS does not support UDMA, the chipset apparently does). Any pointers? Edwin Mons To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
JFWIW, this sounds like something that I "fixed" in the old wd driver, where a device 'echoed' on the bus after it was deselected. Increasing the timeout between deselecting the device and trying to talk again to the bus was, AFAIR, the workaround then. It seems Alex wrote: OK - here's the part relevant to ata: ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcf0-0xfcff at device 1.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 ata1: mask=03 status0=00 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc Here it sees two devices, apparently you cdrom is reacting both on master AND slave addresses :( ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed But when we try to talk to it it fails... ata0-master: success setting up UDMA2 mode on PIIX4 chip But when we try to talk to it it fails... Any ideas? I'll try to come up with a patch that solves this... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: strange ATA stuff (was: ep0 incorrectly probed)
On Thu, 27 Jan 2000, Edwin Mons wrote: and the setup continues as if nothing has happened. The drive is configured as PIO mode 4 in the BIOS (the BIOS does not support UDMA, the chipset apparently does). Any pointers? Humm... Try mode 'Auto'? Dunno. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NFS /usr/src and /usr/obj?
On Wed, 26 Jan 2000, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes: I'm wondering how one can do a buildworld on a machine, and then NFS mount /usr/src and /usr/obj on a client machine and do an installworld of the freshly built sources? I've been looking in the archives without much success, and haven't figured it out by reading the makefiles yet. Can anyone shed some light on this? I've done it in the past, but not recently. Consider the alternative of mounting the destination on the compilehost and make install DESTDIR=/mnt A: What's the advantage? B: What do I mount? The root of the destination? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems installing FreeBSD 4.0 20000125-CURRENT
Hi, I installed 4.0 2125-CURRENT last night on a new box, and had several problems that I wanted to share: 1. sysinstall forgot to write my hostname to /etc/rc.conf . I had gone into the options menu and selected "DHCP"; when I picked my network interface it looked for and found a DHCP server and popped up the network configuration box with most of the fields filled in (including domain name); all I did was type in a hostname. sysinstall then added the domain name to the host name and I said "OK", but that hostname never made it into rc.conf (it booted up calling itself Amnesiac). 2. motd was full of garbage. I realize now that I should have saved it but I wasn't really thinking. 3. On the first reboot after installing, the keyboard was in a funny state. Some keys would provide multiple characters, some would do none. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I used the expert install and picked the "Install everything" option so I assumed I'd get everything =) On the plus side, being able to use DHCP rocks, and I really like how it installed the Linux packages when I picked Linux emulation. And 4.0 seems to work well with this random hardware (emachine 400), including the onboard sound and random ethernet card (linksys something). Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: With feature freeze being in place
Test IPv6 support! You've all been asking for it, test it. Is there a quick primer on getting IPv6 up and running? I built a kernel with INET6 and the ipsec stuff, and my interfaces now have IPv6 addresses, but no userland apps seem to be able to parse IPv6 addresses, e.g. "ping ::1" says "no such host". (This is 4.0-2125-CURRENT). I searched the -current mail archives but couldn't find anything that seemed relevant. Thanks, Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 incorrectly probed
In message [EMAIL PROTECTED] "Matthew N. Dodd" writes: : Using the boot configuration screen can you disable all devices that are : not installed? : : I suspect something is clobbering the board after it is identified. We've had *BAD* luck with the ex driver doing this... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: strange ATA stuff (was: ep0 incorrectly probed)
On Thu, 27 Jan 2000, Matthew N. Dodd wrote: On Thu, 27 Jan 2000, Edwin Mons wrote: and the setup continues as if nothing has happened. The drive is configured as PIO mode 4 in the BIOS (the BIOS does not support UDMA, the chipset apparently does). Any pointers? Humm... Try mode 'Auto'? Did that. Didn't make any difference. Gave the same results either way. Could be a weird harddisk - IDE controller problem. Not a real problem, though. Everything appears to work just fine. Edwin Mons To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: strange ATA stuff (was: ep0 incorrectly probed)
It seems Edwin Mons wrote: On Thu, 27 Jan 2000, Matthew N. Dodd wrote: On Thu, 27 Jan 2000, Edwin Mons wrote: and the setup continues as if nothing has happened. The drive is configured as PIO mode 4 in the BIOS (the BIOS does not support UDMA, the chipset apparently does). Any pointers? Humm... Try mode 'Auto'? Did that. Didn't make any difference. Gave the same results either way. Could be a weird harddisk - IDE controller problem. Not a real problem, though. Everything appears to work just fine. it does, its harmless, its removed from the list when this happens... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: With feature freeze being in place
Test IPv6 support! You've all been asking for it, test it. Is there a quick primer on getting IPv6 up and running? I built a kernel with INET6 and the ipsec stuff, and my interfaces now have IPv6 addresses, but no userland apps seem to be able to parse IPv6 addresses, e.g. "ping ::1" says "no such host". (This is 4.0-2125-CURRENT). Please try ping6 ::1 I searched the -current mail archives but couldn't find anything that seemed relevant. Thanks, Bill Sorry but I'll just attach some part of KAME package USAGE doc to this mail. Please check it about other tools usage. Also, usual tools, rlogin, rlogind, rsh, rshd, telnet, telnetd, ftp, ftpd, and inetd are already IPv6 capable. Wmmm, maybe I should merge ping and pin6 before code freeze... Yoshinobu Inoue -- ifconfig A link-local address is automatically assigned to each interface, when the interface becomes up for the first time. Even if you find an interface without a link-local address, do not panic. The link-local address will be assigned when it becomes up (with "ifconfig IF up"). Some network drivers allow an interface to become up even without a hardware address (for example, PCMCIA network cards). In such cases, it is possible that an interface has no link-local address even if the interface is up. If you see such situation, please disable the interface once and then re-enable it (i.e. do `ifconfig IF down; ifconfig IF up'). Pseudo interfaces (like "gif" tunnel device) will borrow IPv6 interface identifier (lowermost 64bit of the address) from EUI64/IEEE802 sources, like ethernet cards. Pseudo interfaces will be able to get IPv6 link-local address, if you have other "real" interface configured beforehand. If you have no EUI64/IEEE802 sources on the node, you may need to configure link-local address manually. Though we have last-resort code in the kernel, which generates interface identifier from MD5(hostname), it may not suitable for your usage (for example, if you configure same hostname on both sides of gif tunnel, you will be doomed). If you have a router announcing Router Advertisement, global addresses will be assigned automatically. So, neither "ifconfig" nor "prefix" is necessary for your *host*. (Please refer to "sysctl" section for configuring a host to accept Router Advertisement.) If you want to set up a router, you need to assign global addresses for two or more interfaces by "ifconfig" or "prefix". (prefix command is described at next section) If you want to assign a global address by "ifconfig", don't forget to specify the "alias" argument to keep the link-local address. # ifconfig de0 inet6 3ffe:501:808:1:200:f8ff:fe01:6317 alias # ifconfig de0 de0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80:1::200:f8ff:fe01:6317 prefixlen 64 inet 163.221.202.12 netmask 0xff00 broadcast 163.221.202.255 inet6 3ffe:501:808:1:200:f8ff:fe01:6317 prefixlen 64 ether 00:00:f8:01:63:17 media: 100baseTX status: active See also "/usr/local/v6/etc/rc.net6". prefix In IPv6 architecture, an IPv6 address of an interface can be generated from a prefix assigned to it, and a link-dependent identifier for the interface. So assigning a full IPv6 address by ifconfig is not necessary anymore, because user can only take care of prefix, by letting system take care of interface identifier. The newly added "prefix" command enables user to just assign prefixes for interfaces, and let your system automatically generate IPv6 addresses. Prefixes added by the "prefix" command is maintained in the kernel consistently with prefixes assigned by Router Advertisement(in case of hosts) and with prefixes assigned by Router Renumbering(in case of routers). Manual assignment of prefixes or change of prefix properties take precedence over ones assigned by Router Advertisement or Router Renumbering. If you want to assign a prefix(and consequently address) manually, do as follows: # prefix de0 3ffe:501:808:1:: # ifconfig de0 de0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80:1::200:f8ff:fe01:6317 prefixlen 64 inet 163.221.202.12 netmask 0xff00 broadcast 163.221.202.255 inet6 3ffe:501:808:1:200:f8ff:fe01:6317 prefixlen 64 ether 00:00:f8:01:63:17 media: 100baseTX status: active To check assigned prefix, use the "ndp" command. (See description of ndp command about its usage) # ndp -p 3ffe:501:808:1::/64 if=de0 flags=LA, vltime=2592000, pltime=604800, expire=Never No advertising router The "prefix" command also has node internal prefix renumbering ability. If you have multiple prefixes which have 3ffe:501:808:/48 at the top, and would like to renumber them to 3ffe:501:4819:/48, then use the "prefix" command with the "matchpr" argument and the "usepr" argument. Suppose that current state of before renumbering as follows:
Re: With feature freeze being in place
On Thu, 27 Jan 2000 11:03:28 -0800, Bill Fenner [EMAIL PROTECTED] said: Is there a quick primer on getting IPv6 up and running? I built a kernel with INET6 and the ipsec stuff, and my interfaces now have IPv6 addresses, but no userland apps seem to be able to parse IPv6 addresses, e.g. "ping ::1" says "no such host". (This is 4.0-2125-CURRENT). Yesterday, I tested ping6 between two hosts using link-local addresses, and it worked. The week before, however, I couldn't get a different machine to transmit packets when it had IPv6 in the kernel. I'm not sure about the relative dates involved. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
inet6 (was Re: With feature freeze being in place)
i've had ipv6 working with freenet6.net.. well, partially working, the full feature should work fine soon though. the tunneling through gif works, and i'm about to test IPSec with IPv4. more testing is in order though, so, i'll try to pass on some more info when i have it. -- jan On Thu, 27 Jan 2000, Garrett Wollman wrote: On Thu, 27 Jan 2000 11:03:28 -0800, Bill Fenner [EMAIL PROTECTED] said: Is there a quick primer on getting IPv6 up and running? I built a kernel with INET6 and the ipsec stuff, and my interfaces now have IPv6 addresses, but no userland apps seem to be able to parse IPv6 addresses, e.g. "ping ::1" says "no such host". (This is 4.0-2125-CURRENT). Yesterday, I tested ping6 between two hosts using link-local addresses, and it worked. The week before, however, I couldn't get a different machine to transmit packets when it had IPv6 in the kernel. I'm not sure about the relative dates involved. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message +-// f. johan beisser //--+ email: jan[at]caustic.org web: http://www.caustic.org/~jan "knowledge is power. power corrupts. study hard, be evil." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: With feature freeze being in place
Also, usual tools, rlogin, rlogind, rsh, rshd, telnet, telnetd, ftp, ftpd, and inetd are already IPv6 capable. Hm. rlogin and rsh attempt to connect, but my inetd isn't listening; do I have to update inetd.conf to get inetd to listen on IPv6 addresses? telnet can't parse ::1: emachine% telnet ::1 ::1: Unknown host ftp prints a very odd message: emachine% ftp ::1 ftp: No control connection for command. I guess ftp parsed ::1 as a URL. What a pain. I tried putting "::1 v6-localhost" in /etc/hosts, but telnet and ftp couldn't use v6-localhost as a name while ping6, traceroute6, rlogin and rsh could. So far, the only tools I've been able to use to emit v6 packets are ping6, traceroute6, rlogin and rsh. I don't have any other v6 machines on my network, so I've just been using loopback. Wmmm, maybe I should merge ping and pin6 before code freeze... I think it'd be very handy for the native ping (and traceroute, if possible) to be IPv4/IPv6 capable. Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 incorrectly probed
"Matthew N. Dodd" wrote: On Thu, 27 Jan 2000, Warner Losh wrote: We've had *BAD* luck with the ex driver doing this... Except that the ex driver doesn't do anything destructive in its identify method now. I'm having a hell of a time getting the ex driver to attach in PnP mode but thats another story. I think the i85295 needs some special kicking or something but I don't have the manuals yet. It doesn't seem to be assigned the resources the kernel picks out for it. This is shown by 'pnpinfo'. pnpinfo doesn't have anything to do with what the kernel thinks. It's a userland program that manually resets and reconfigures the cards.. This is an absolute disaster if you happened to be using the hardware, eg: the sound driver. After running pnpinfo, the hardware essentially "disappears". pciconf(8) does it properly, it asks the kernel via /dev/pci. pnpinfo uses /dev/io to bash on the ports directly. Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 incorrectly probed
On Fri, 28 Jan 2000, Peter Wemm wrote: pnpinfo doesn't have anything to do with what the kernel thinks. It's a userland program that manually resets and reconfigures the cards.. This is an absolute disaster if you happened to be using the hardware, eg: the sound driver. After running pnpinfo, the hardware essentially "disappears". pciconf(8) does it properly, it asks the kernel via /dev/pci. pnpinfo uses /dev/io to bash on the ports directly. Thats kinda weird seeing as how pnpinfo correctly reports the settings as detected/assigned by the kernel for all other cards. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: With feature freeze being in place
Yesterday, I tested ping6 between two hosts using link-local addresses, and it worked. The week before, however, I couldn't get a different machine to transmit packets when it had IPv6 in the kernel. I'm not sure about the relative dates involved. -GAWollman Some driver seems to have problems with INET6 support. IPv6 addresss auto configuration packet is sent just after ifconfig up, and all such work is done at splimp(). Sometime it seems to be problem for some drivers. As I heard, -fxp driver cause problem with some driver at some timing. -de driver caused some initialization problem with INET6. I have been trying to find some time to test fxp, but not successful yet. Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: With feature freeze being in place
Also, usual tools, rlogin, rlogind, rsh, rshd, telnet, telnetd, ftp, ftpd, and inetd are already IPv6 capable. Hm. rlogin and rsh attempt to connect, but my inetd isn't listening; do I have to update inetd.conf to get inetd to listen on IPv6 addresses? Yes, if tcp, please specify SNIPtcp46 SNIP or SNIPtcp6 SNIP Former accept either of IPv4 and IPv6, and latter only accept IPv6. The following 2 are same. Only accept IPv4. SNIPtcp4 SNIP SNIPtcp SNIP You can also specify following 2 entries for each of services at the same time. SNIPtcp6 SNIP SNIPtcp4 SNIP Please check inetd man page for details. telnet can't parse ::1: emachine% telnet ::1 ::1: Unknown host ftp prints a very odd message: emachine% ftp ::1 ftp: No control connection for command. telnet, ftp, and ftpd are added today.(2000/01/27 01:28:39 PST) So it might not yet be mirrored to your place. Wmmm, maybe I should merge ping and pin6 before code freeze... I think it'd be very handy for the native ping (and traceroute, if possible) to be IPv4/IPv6 capable. Bill Traceroute/traceroute6 merging is somewhat more difficult because traceroute is maintenanced under contrib. :( Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Something strange with pccard/ed0 ?
Hi, I'm currently running 4.0-CURRENT (Jan 27) on a Dell I3500 laptop with pccard and a D-LINK DE-660. All runs ok except that my card is not recognized as ed0 but as ed1. Here are my config params : =-=-=-= device card0 device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 =-=-=-= i'm using the genuine DE-660 pccard.conf entry. At startup, i get the following messages : =-=-=-== Jan 27 21:31:20 alex /kernel: pcic: management irq 10 Jan 27 21:31:20 alex /kernel: pcic0: VLSI 82C146 at port 0x3e0 iomem 0xd i rq 10 on isa0 Jan 27 21:31:20 alex /kernel: pccard0: PC Card bus -- kludge version on pcic0 Jan 27 21:31:20 alex /kernel: pccard1: PC Card bus -- kludge version on pcic0 (...) Jan 27 21:31:20 alex /kernel: pccard: card inserted, slot 0 Jan 27 21:31:28 alex /kernel: devclass_alloc_unit: ed0 already exists, using nex t available unit number Jan 27 21:31:29 alex /kernel: ed1 at port 0x240-0x25f irq 3 slot 1 on pccard1 Jan 27 21:31:29 alex /kernel: ed1: address 00:80:c8:bc:91:94, type NE2000 (16 bi t) Jan 27 21:31:29 alex /kernel: bpf: ed1 attached Jan 27 21:31:28 alex pccard:ed1: D-Link DE-660 inserted Jan 27 21:31:29 alex pccardd[44]: pccardd started =-=-=-= I don't understand this devclass_alloc_unit pb... Why does it pretend that ed0 already exists ? -- - Éric Jacoboni « No sport, cigars! » (W. Churchill) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 incorrectly probed
"Matthew N. Dodd" wrote: On Fri, 28 Jan 2000, Peter Wemm wrote: pnpinfo doesn't have anything to do with what the kernel thinks. It's a userland program that manually resets and reconfigures the cards.. This is an absolute disaster if you happened to be using the hardware, eg: the soun d driver. After running pnpinfo, the hardware essentially "disappears". pciconf(8) does it properly, it asks the kernel via /dev/pci. pnpinfo uses /dev/io to bash on the ports directly. Thats kinda weird seeing as how pnpinfo correctly reports the settings as detected/assigned by the kernel for all other cards. Hmm, I take some of that back. I'm still not 100% sure of the implications of what I'm seeing in src/contrib/pnpinfo, but it still makes me nervous. For example: Logical device #0 IO: 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 IRQ 5 0 DMA 1 0 IO range check 0x00 activate 0x01 versus: pcm0: CS423x at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 Which is right? Does the device really have all 8 IO ranges assigned to the same address? (0x534) Or is pnpinfo wrong? Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: locking problem FreeBSD 3.4 - kermit and mgetty
Hi, On Thu, Jan 27, 2000 at 07:03:38PM +0100, Christoph Kukulies wrote: But as a result mgetty gets into kermit's ways such that when a modem connection is made I suddenly get a modem prompt like +FCON as if someone (mgetty) is either messing with my local or the remote modem while kermit opens the connection. The modem is in fax mode, and has established a fax connection. Have kermit send an AT+FCLASS=0 first. OK, this may be a repair but I'm wondering why that worked before and now I have to take special measures. Or is it perhaps kermit's fault? Older mgetty versions had all class 2 modems in "class 0 mode" while waiting for incoming calls, which worked very well for some Rockwell modems, and not so well for others. With class 2.0 modems, the modem always *had* to be in fax mode. Recently, I changed the settings so that some class 2 modems are also run in "class 2 mode", so maybe that triggered the problem at your end. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany [EMAIL PROTECTED] fax: +49-89-35655025[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
1. sysinstall forgot to write my hostname to /etc/rc.conf . I had gone into the options menu and selected "DHCP"; when I picked my network interface it looked for and found a DHCP server and popped up the network configuration box with most of the fields filled in (including domain name); all I did was type in a hostname. sysinstall then added the domain name to the host name and I said "OK", but that hostname never made it into rc.conf (it booted up calling itself Amnesiac). In this case, I actually assume that the DHCP server will be providing the host name and specifically *ignore* the user-provide hostname field since our dhcp client integration is still a bit green and you'll just override the DHCP server assignment for the hostname with the user-defined one if it's written to rc.conf. 2. motd was full of garbage. I realize now that I should have saved it but I wasn't really thinking. Huh? 3. On the first reboot after installing, the keyboard was in a funny state. Urk, can't reproduce it. I need a reproducible sequence of operations before we'll have any hope of tackling this one. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. Same here. 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I guess we need to build our own XF86 distribution with the a.out libraries built or we need to somehow stuff those into a compat dist. Ugh, either option is pretty ugly. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [PATCH] Please test the PS/2 mouse driver patch
In article [EMAIL PROTECTED] you wrote: I wrote a patch for the psm driver to add support for several PS/2 mice. It is in http://www.freebsd.org/~yokota/ps2mice-24Jan2000.tar.gz. I am attaching README included in the patch. Thank you. Kazu Do you have specs on the Trackpoint PS/2 mice found on Thinkpads? The version on my 770X has a double click by "pushing hard on the trackpoint" feature. It also has the ability to do the scroll thing if you hold the middle mouse button and move the trackpoint. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Comments on this patch?
I've been running this for a while. I reversed the normal order to
make it easier to do the math w/o having to shift columns and flip
things over.
BTW, I'm getting numbers that are 2x bigger than before :-(.I had
makebuildworld down to around 1:20 at one point, but now it is 2:40.
Comments?
Warner
Index: Makefile
===
RCS file: /home/imp/FreeBSD/CVS/src/Makefile,v
retrieving revision 1.233
diff -u -r1.233 Makefile
--- Makefile2000/01/09 18:17:48 1.233
+++ Makefile2000/01/27 21:42:39
@@ -130,6 +130,19 @@
@echo " ${OBJFORMAT} make world started on ${STARTTIME}"
@echo " ${OBJFORMAT} make world completed on `LC_TIME=C date`"
@echo "--"
+#
+# Timed buildworld
+#
+timed-buildworld: upgrade_checks
+ @echo "--"
+ @echo " ${OBJFORMAT} make buildworld started on ${STARTTIME}"
+ @echo "--"
+ @cd ${.CURDIR}; ${MAKE} buildworld
+ @echo
+ @echo "--"
+ @echo " ${OBJFORMAT} make buildworld completed on `LC_TIME=C date`"
+ @echo " ${OBJFORMAT} make buildworld started on ${STARTTIME}"
+ @echo "--"
#
# Perform a few tests to determine if the installed tools are adequate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Par. gone missing
I just notice my par. port is no longer detected. A kernel built on Jan 21st fails to detect my par. port which has worked fine so far. In /var/log/messages I get the following: Jan 27 22:29:53 kern.crit trantor /kernel: ppc0: parallel port found at 0x3bc Jan 27 22:29:53 kern.crit trantor /kernel: ppc0: cannot reserve I/O port range When doing a boot -v. An older kernel booted Jan 13th showed the following : Jan 13 21:08:47 kern.crit trantor /kernel: ppc0 at port 0x3bc-0x3c3 irq 7 on isa0 Jan 13 21:08:47 kern.crit trantor /kernel: isa_compat: didn't get ports for ppc Jan 13 21:08:47 kern.crit trantor /kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode Jan 13 21:08:47 kern.crit trantor /kernel: lpt0: generic printer on ppbus 0 Jan 13 21:08:47 kern.crit trantor /kernel: lpt0: Interrupt-driven port Rebooting the older kernel brings back my port so I doubt it's a hardware problem. Any hints on tracing the reason for it not being detected ?? Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
.bash_history and permissions
Hi folks! I'm running FreeBSD 4.0 from Dec. 26 1999. This should be on the "general questions" malininglist, but I thought maybe there is something that changed from -stable to -current that does this: I'm trying to limit permissions on .bash_history. There have been users on my server that have linked .bash_history to /dev/null and then been doing some cracking, and attacking other servers. To limit this (or at least trying to control it) I tried to take out write permission for group and others, thinking that will stop the users from trying to mod- ify the file. That didn't work! Even if I did "chmod 000 .bash_history" users still could delete the file or modify it. So I thought maybe if I just change the group or the owner of the file, it would fix the problem that didn't work either...now it wouldn't log the commands to the history file anymore. So I was wondering, do any of you gurus and bofh know how to fix this? This is very imporant for me, I'd be _very_ thankful if anyone could help me fix this problem. (PS: In other's OSs i.e Solaris or Linsucks, changing the perms seemd to work, just not in FreeBSD) -- DSS/DH 1024/4064: 0x5E9EE10A/0x2486FEBE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On 27-Jan-2000 Jordan K. Hubbard wrote: | | 3. On the first reboot after installing, the keyboard was in a funny | state. | | Urk, can't reproduce it. I need a reproducible sequence of operations | before we'll have any hope of tackling this one. | | Control-alt-del definitely didn't work, so I had to power off and | reboot. This hasn't repeated itself. | | Same here. | I seem to have this problem occasionaly, the keyboard keymap gets all screwed up somehow, and the only way to get out is to hit the reset button. But I've been having the problem for a long time, and with different boxes. It happens about every 1 out of 15 reboots but randomly. I haven't been able to connect it to any event or anything, but I notice that hitting keys during boot can increase the probability of it occurring, but again, nothing reproducible. - Mike Heffner [EMAIL PROTECTED] Fredericksburg, VA ICQ# 882073 Date: 27-Jan-2000 Time: 16:47:01 - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
% %On 27-Jan-2000 Jordan K. Hubbard wrote: % | % | 3. On the first reboot after installing, the keyboard was in a funny % | state. % | % | Urk, can't reproduce it. I need a reproducible sequence of operations % | before we'll have any hope of tackling this one. % | % | Control-alt-del definitely didn't work, so I had to power off and % | reboot. This hasn't repeated itself. % | % | Same here. % | % %I seem to have this problem occasionaly, the keyboard keymap gets all screwed %up somehow, and the only way to get out is to hit the reset button. But I've %been having the problem for a long time, and with different boxes. It happens %about every 1 out of 15 reboots but randomly. I haven't been able to connect %it to any event or anything, but I notice that hitting keys during boot can %increase the probability of it occurring, but again, nothing reproducible. Right. I've seen this when I hit Enter rapidly twice at the first loader prompt. Doesn't ever happen if I wait for the second prompt. Russell %- %Mike Heffner [EMAIL PROTECTED] %Fredericksburg, VA %ICQ# 882073 %Date: 27-Jan-2000 Time: 16:47:01 %- % % %To Unsubscribe: send mail to [EMAIL PROTECTED] %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000, Garrett Wollman wrote: I have on a number of occasions had my laptop boot with a non-functional keyboard. Sometimes the keyboard is just locked; other times it generates garbage. Never managed to isolate the circumstances in which this happened (but it didn't happen with a kernel from last September or there-abouts). Haven't had it happen on a desktop or server yet. -GAWollman I've seen this on a Compaq Armada laptop recently (-current from about 1/10/2000). It only happens when I interrupt the boot process with a key press (I cannot recall whether it was in /boot/loader or in boot2). I suspect the latter, but have not yet tracked the problem down. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
Right. I've seen this when I hit Enter rapidly twice at the first loader prompt. Doesn't ever happen if I wait for the second prompt. That's my impression too -- I've seen it on my laptop when I do that (sometimes), and I may have hit enter twice rapidly on this reboot. Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Parallel port gone missing (extra info)
In message [EMAIL PROTECTED], Paul van der Zwan wrote: I just notice my par. port is no longer detected. A kernel built on Jan 21st fails to detect my par. port which has worked fine so far. In /var/log/messages I get the following: Jan 27 22:29:53 kern.crit trantor /kernel: ppc0: parallel port found at 0x3bc Jan 27 22:29:53 kern.crit trantor /kernel: ppc0: cannot reserve I/O port range When doing a boot -v. An older kernel booted Jan 13th showed the following : Jan 13 21:08:47 kern.crit trantor /kernel: ppc0 at port 0x3bc-0x3c3 irq 7 on isa0 Jan 13 21:08:47 kern.crit trantor /kernel: isa_compat: didn't get ports for ppc Jan 13 21:08:47 kern.crit trantor /kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode Jan 13 21:08:47 kern.crit trantor /kernel: lpt0: generic printer on ppbus0 Jan 13 21:08:47 kern.crit trantor /kernel: lpt0: Interrupt-driven port Rebooting the older kernel brings back my port so I doubt it's a hardware problem. Any hints on tracing the reason for it not being detected ?? Some extra info , the MB is a Chaintech 5TDM2, changing biossettings from EPP to ECP/EPP does not help. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 incorrectly probed
On Fri, 28 Jan 2000, Peter Wemm wrote: For example: Logical device #0 IO: 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 IRQ 5 0 DMA 1 0 IO range check 0x00 activate 0x01 versus: pcm0: CS423x at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 Which is right? Does the device really have all 8 IO ranges assigned to the same address? (0x534) Or is pnpinfo wrong? I dunno. Looks like pnpinfo is wrong when it comes to printing IO address ranges assigned. I do know that somehow or another the kernel PnP stuff isn't able to tell the card to use the assigned addresses but I don't get any failure messages (from the PnP code.) If you've got an Intel Etherexpress Pro/10 board you should be able to observe this. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000, Garrett Wollman wrote: On Thu, 27 Jan 2000 13:28:10 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said: 3. On the first reboot after installing, the keyboard was in a funny state. Urk, can't reproduce it. I need a reproducible sequence of operations before we'll have any hope of tackling this one. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. Same here. I have on a number of occasions had my laptop boot with a non-functional keyboard. Sometimes the keyboard is just locked; other times it generates garbage. Never managed to isolate the circumstances in which this happened (but it didn't happen with a kernel from last September or there-abouts). Haven't had it happen on a desktop or server yet. -GAWollman As another sort of me-to, I use a non-standard key board from an ols lunch-box portable. It seems to have stopped working correctly in the boot-loader/visual config, although it still works fine in single-user and above. I mention this only in that it might be a useful data point, it has never been enough of a hassle for me to try to understand exactally what is going on, I just hook up a spare 101-key keyboard. Brian Beattie| The only problem with [EMAIL PROTECTED] | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ColdFusion 4.5 RC3
I can consistantly get ColdFusion 4.5 RC3 installed on FreeBSD-current. It will not work on -stable (i didn't really mess with it too much however) i haven't gotten the Apache module to work yet (but i haven't even looked at it, so give me time) instructions are at http://users.tmok.com/~wonko/cf -wonko To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Something strange with pccard/ed0 ?
On 27 Jan 2000, Eric Jacoboni wrote: All runs ok except that my card is not recognized as ed0 but as ed1. Here are my config params : =-=-=-= device card0 device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 Thats correct. The kernel has assigned 'ed0' to the non-existent ISA card you've told it to expect. use 'device ed0' instead. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-pass
On 27-Jan-00 David O'Brien wrote: I would appreciate it if those that want things changed would please try Sheldon's `sed' expression below and report back how it worked for you. That will expose passwords of users whose entries are commented out, unfortunately. Then again, I've reverted the '-u' change on all my machines, so that doesn't apply to me all that much. Actually, since changed lines start with '+' or '-', that is going to expose passwords of changed accounts as well: diff -u foo foo2 | sed 's/^\([^:#@+-]*\):[^:]*:/\1:(password):/' --- foo Thu Jan 27 17:30:05 2000 +++ foo2Thu Jan 27 17:30:53 2000 @@ -14,8 +14,8 @@ pop:(password):68:6::0:0:Post Office Owner:/nonexistent:/sbin/nologin nobody:(password):65534:65534::0:0:Unprivileged user:/nonexistent:/sbin/nologin ftp:(password):14:5::0:0:Anonymous FTP Admin:/var/ftp:/nonexistent -majordom:*:54:54::905054400:0:Majordomo Psuedo User:/usr/local/majordomo:/sbin/nologin -www:*:80:80::0:0:Web Server SandBox:/:/sbin/nologin +majordom:wacko:54:54::905054400:0:Majordomo Psuedo +User:/usr/local/majordomo:/sbin/nologin +www:blah:80:80::0:0:Web Server SandBox:/:/sbin/nologin ccc:(password):902:902:standard:0:0:CCC CVS Repository Owner:/home/ccc:/sbin/nologin Have trouble seeing that change, btw? I find it harder to see than this: diff foo foo2 | sed 's/^\([^:]*\):[^:]*:/\1:(password):/' 17,18c17,18 majordom:(password):54:54::905054400:0:Majordomo Psuedo User:/usr/local/majordomo:/sbin/nologin www:(password):80:80::0:0:Web Server SandBox:/:/sbin/nologin --- majordom:(password):54:54::905054400:0:Majordomo Psuedo User:/usr/local/majordomo:/sbin/nologin www:(password):80:80::0:0:Web Server SandBox:/:/sbin/nologin I agree that unified diff is more readable for things like code where context matters, but for password files, where each line is its own entity and there is no meaning in context, I see it as clutter that makes it harder to read. If 'joebob' user changes his password, I really don't care that the line in the passwd file above 'joebob's account is the account for 'billybob', I just care that 'joebob' changed his password. - Forwarded message from Sheldon Hearn [EMAIL PROTECTED] - To: "David E. O'Brien" [EMAIL PROTECTED] Date: Wed, 26 Jan 2000 18:44:47 +0200 As discussed on the freebsd-current mailing list, I think you'll find that you missed out a few characters in the new class that defines the characters that should not appear at the beginning of affected lines: -sed 's/^\([] [^:]*\):[^:]*:/\1:(password):/' +sed 's/^\([^:]*\):[^:]*:/\1:(password):/' I think what you really want is: sed 's/^\([^:#@+-]*\):[^:]*:/\1:(password):/' - End forwarded message - -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ColdFusion 4.5 RC3
On Thu, Jan 27, 2000 at 05:34:01PM -0500, Brian Hechinger wrote: I can consistantly get ColdFusion 4.5 RC3 installed on FreeBSD-current. It will not work on -stable (i didn't really mess with it too much however) i haven't gotten the Apache module to work yet (but i haven't even looked at it, so give me time) instructions are at http://users.tmok.com/~wonko/cf -wonko Is this ColdFusion for Linux? Joe -- Josef KarthauserFreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 01:28:10PM -0800, Jordan K. Hubbard wrote: In this case, I actually assume that the DHCP server will be providing the host name and specifically *ignore* the user-provide hostname IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't setup to provide hostnames to the requrestor. 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I guess we need to build our own XF86 distribution with the a.out libraries built or we need to somehow stuff those into a compat dist. If you want the added to src/lib/compat, let me know ASAP. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 01:28:10PM -0800, Jordan K. Hubbard wrote: 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I guess we need to build our own XF86 distribution with the a.out libraries built or we need to somehow stuff those into a compat dist. OR we can make a [binary] port of it. This would not be hard to do. Let me know if you prefer this approach. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Comments on this patch?
BTW, I'm getting numbers that are 2x bigger than before :-(.I had makebuildworld down to around 1:20 at one point, but now it is 2:40. Which compilers for both times? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000, Bill Fenner wrote: Right. I've seen this when I hit Enter rapidly twice at the first loader prompt. Doesn't ever happen if I wait for the second prompt. That's my impression too -- I've seen it on my laptop when I do that (sometimes), and I may have hit enter twice rapidly on this reboot. Bill Hmmm, I wonder it the boot loader is doing something funny in initializing the keyboard. Maybe something changed? Brian Beattie| The only problem with [EMAIL PROTECTED] | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ColdFusion 4.5 RC3
Josef Karthauser drunkenly mumbled... Is this ColdFusion for Linux? yes. sorry about the confusion, i forgot to mention that. Allaire off-record said that they aren't happy with Linux and are seeking an alternative. i seem to be pushing them towards FreeBSD. but, keep in mind, this will be a huge shift in development for them, so if they ever do descide this, it still won't happen for a while. -brian -- ps: off-record means i will deny ever having said this even though you have proof. :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ColdFusion 4.5 RC3
On Thu, Jan 27, 2000 at 05:49:39PM -0500, Brian Hechinger wrote: Josef Karthauser drunkenly mumbled... Is this ColdFusion for Linux? yes. sorry about the confusion, i forgot to mention that. Allaire off-record said that they aren't happy with Linux and are seeking an alternative. i seem to be pushing them towards FreeBSD. but, keep in mind, this will be a huge shift in development for them, so if they ever do descide this, it still won't happen for a while. Cool, I knew that if I held out long enough I wouldn't have to install solaris :) Cold Fusion on FreeBSD - an ISP's dream :) Joe -- Josef KarthauserFreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
Garrett Wollman wrote: On Thu, 27 Jan 2000 13:28:10 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said: 3. On the first reboot after installing, the keyboard was in a funny state. Urk, can't reproduce it. I need a reproducible sequence of operations before we'll have any hope of tackling this one. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. Same here. I have on a number of occasions had my laptop boot with a non-functional keyboard. Sometimes the keyboard is just locked; other times it generates garbage. Never managed to isolate the circumstances in which this happened (but it didn't happen with a kernel from last September or there-abouts). Haven't had it happen on a desktop or server yet. -GAWollman Yeah, happens here too, every now and again. I boot straight into xdm, so it might have something to do with X, but any attempts to type in the username generate garbage. I can't switch to a text console, because Ctrl-Alt-Fx keys don't work either - all I can do is push the Big Red Button. The graphics card in my laptop is Chips Technology 6. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with an0 and ISA Aironet Card..
Of all the gin joints in all the towns in all the world, Paul Reece had to walk into mine and say: On Thu, 20 Jan 2000, Bill Paul wrote: snip Back up. You're leaving out some info. - When did you buy these cards? (The firmware rev may be an issue. knowing when you bought the card helps me figure out if your firmware is newer than mine.) Cards were purchased in the past 6 months. Revision of the card I'm using at the moment is 3.13 - I upgraded the firmware to the latest. (Win DGS under 'status' reports 3.13). You can view the firmware rev with the if_an driver (when it works) by doing ancontrol -i an0 -I. The newest PCMCIA card that I have seems to be using revision 3.10. The ISA card that I have is using 2.06. The trouble is I don't have Windows machine set up to run the firmware update utility. What I tried to do today was swap the PCMCIA module on my existing ISA card with one of the new ones with the later firmware. I did this a while back when I got our first batch of cards. However, I can't do it now. One of the problems I had with the Aironet cards initially is that they were set up so that they would operate in two modes: if you applied +5volts to the vpp1 and vpp2 pins on the PCMCIA module, it would work in PCMCIA mode such that you could get at the CIS data and configure it like any other PCMCIA card. Without the +5volts, the module would work in a special 'dumb bus' mode that would allow it to interface with the ISA and PCI bridge adapter cards that Aironet uses for their ISA and PCI cards. Basically, this allows them to make just one PCMCIA module and use it in all three kinds of cards. However the latest PCMCIA cards that we just got are different: now they always work in PCMCIA mode regardless of how vpp1 and vpp2 are set. On the one hand, this is good because it means you don't have to frob sys/pccard/pccard.c to enable the vpp voltage when the card is inserted. (My older cards will not work with FreeBSD unless I apply this tweak to the kernel.) On the other hand, this means that the newer PCMCIA cards won't work in the ISA and PCI bridge adapters. This sort of stymied my attempts to duplicate your problem here in the lab. What would be nice is if you could somehow set up a scratch box with an Aironet ISA4800 card in it that I could access remotely. I'm reasonably confident I could make it work if I could just experiment with it for a while. Unfortunately, this may not be possible depending on technical on various political constraints, especially since I need to twiddle around as root in order to examine register contents and test a new driver. pcpaul# ./testa COMMAND: 0 PARAM0: ff11 PARAM0: 0x (still no lights on card) if I run it again: pcpaul# ./testa COMMAND: 0 PARAM0: 1234 PARAM0: 0x (and still no lights). This info help at all? Well, yes. It tells me two things. First, it tells me that I made a typo on the program that I gave you. :) Second, it shows me that the card is at the I/O address that it's supposed to be, although it appears to not be responding to the 'read SSID list' command that the if_an driver issues during the probe phase. Unfortunately, as I said earlier, I need to be able to experiment on this thing in order to figure out the problem, and I can't do that unless you can somehow arrange remote access. -Bill -- = -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu Work: [EMAIL PROTECTED] | Center for Telecommunications Research Home: [EMAIL PROTECTED] | Columbia University, New York City = "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000, Bill Fenner wrote: Right. I've seen this when I hit Enter rapidly twice at the first loader prompt. Doesn't ever happen if I wait for the second prompt. That's my impression too -- I've seen it on my laptop when I do that (sometimes), and I may have hit enter twice rapidly on this reboot. Bill Hmmm, I wonder it the boot loader is doing something funny in initializing the keyboard. Maybe something changed? It doesn't do anything to the keyboard, it just calls the BIOS to find out whether keys have been pressed. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: .bash_history and permissions
In the last episode (Jan 27), Emre said: I'm running FreeBSD 4.0 from Dec. 26 1999. This should be on the "general questions" malininglist, but I thought maybe there is something that changed from -stable to -current that does this: I'm trying to limit permissions on .bash_history. There have been users on my server that have linked .bash_history to /dev/null and then been doing some cracking, and attacking other servers. To limit this (or at least trying to control it) I tried to take out write permission for group and others, thinking that will stop the users from trying to mod- ify the file. That didn't work! Even if I did "chmod 000 .bash_history" users still could delete the file or modify it. So I thought maybe if I just change the group or the owner of the file, it would fix the problem that didn't work either...now it wouldn't log the commands to the history file anymore. Are you also running a modified bash that removes the HISTFILE and HISTFILESIZE environment variables, and have you also removed /bin/sh and all other shells that don't log commands (* NOTE: do not remove /bin/sh *) ? So I was wondering, do any of you gurus and bofh know how to fix this? This is very imporant for me, I'd be _very_ thankful if anyone could help me fix this problem. (PS: In other's OSs i.e Solaris or Linsucks, changing the perms seemd to work, just not in FreeBSD) Delete permission comes from the directory, not the file. No amount of chmod'ing the file will affect it. Under FreeBSD, you can run "chflags sappnd,sunlnk .bash_history" to make the file undeletable, append-only. Under other Unixes, the user can simply do a "cp /dev/null ~/.bash_history kill -9 $$" to log out with no history file. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On 27-Jan-00 David O'Brien wrote: On Thu, Jan 27, 2000 at 01:28:10PM -0800, Jordan K. Hubbard wrote: In this case, I actually assume that the DHCP server will be providing the host name and specifically *ignore* the user-provide hostname IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't setup to provide hostnames to the requrestor. Why not check to see what the hostname is after dhclient is run and then stick that name in the network setup dialog box. If the user does edit the hostname themselves, then you can flag that event, and use that flag when writing out /etc/rc.conf to mean that the hostname variable should be set. Actually, this doesn't work all that well because the boot floppy doesn't include /bin/hostname in the crunch so /sbin/dhclient-script can't set the hostname when it is sent out by a dhcp server. 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I guess we need to build our own XF86 distribution with the a.out libraries built or we need to somehow stuff those into a compat dist. If you want the added to src/lib/compat, let me know ASAP. -- -- David([EMAIL PROTECTED]) -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Comments on this patch?
On 2000-Jan-28 10:02:06 +1100, Warner Losh [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED] "David O'Brien" writes: : BTW, I'm getting numbers that are 2x bigger than before :-(.I had : makebuildworld down to around 1:20 at one point, but now it is 2:40. ... So I'd say this is with 2.7.3 and the compiler in today's current. There's so much that has changed in the last 2.5 years so this is more like grousing rather than pointing to a problem. FreeBSD itself is significantly larger - at a guess, I'd say that 4.0-CURRENT is about 50% larger than 2.x. I suspect (though I haven't done any direct comparisons) that today's egcs is slower than 2.7.3. Also, following Marcel's work, buildworld is now far more careful about ensuring that tools it wants to use are built correctly for the environment they are going to be used in - which means that far more of the system is built multiple times during a buildworld. Overall, a 2:1 slowdown doesn't really surprise me. It would be nice if it was smaller though. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Something strange with pccard/ed0 ?
"Matthew N. Dodd" [EMAIL PROTECTED] writes: On 27 Jan 2000, Eric Jacoboni wrote: All runs ok except that my card is not recognized as ed0 but as ed1. device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 Thats correct. The kernel has assigned 'ed0' to the non-existent ISA card you've told it to expect. use 'device ed0' instead. Oops... Thanks for your help, it's ok now. -- - Éric Jacoboni « No sport, cigars! » (W. Churchill) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: .bash_history and permissions
- Original Message - From: "Emre" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 27, 2000 4:53 PM Subject: .bash_history and permissions Hi folks! I'm running FreeBSD 4.0 from Dec. 26 1999. This should be on the "general questions" malininglist, but I thought maybe there is something that changed from -stable to -current that does this: I'm trying to limit permissions on .bash_history. There have been users on my server that have linked .bash_history to /dev/null and then been doing some cracking, and attacking other servers. for x in `cut -d: -f1 /etc/passwd` do if [ ! -r ~$x/.bash_history ] then userdel -r $x fi done To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
In message [EMAIL PROTECTED] Mike Smith writes: : It doesn't do anything to the keyboard, it just calls the BIOS to find : out whether keys have been pressed. I've been seeing the hit CR twice fast problem for months. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
In message [EMAIL PROTECTED] Mike Smith writes: : It doesn't do anything to the keyboard, it just calls the BIOS to find : out whether keys have been pressed. I've been seeing the hit CR twice fast problem for months. It's always been a problem; we don't understand the mechanics of it however. Susceptibility varies widely between systems, and the best hypothesis I've been able to come up with is that there are issues with taking interrupts in vm86 mode; possibly the BIOS is being re-entered in a fashion it doesn't like. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't setup to provide hostnames to the requrestor. Seems they're set up incorrectly then. You can't be a good "network citizen" these days without a resolvable hostname that also matches your primary IP address or, among other things, you won't be able to send mail directly to anyone who practices traditional spam filtering techniques. This also isn't just pedantry because, as I noted before, specifying the hostname will currently cause it to override the DHCP hostname value even if it is specified (as it certainly is on *my* DHCP server :-) and result in broken behavior for the aformentioned mailers. If we were to fix that in our rc scripts, I could remove this assumption in sysinstall in good conscience. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
In message [EMAIL PROTECTED] Mike Smith writes: : In message [EMAIL PROTECTED] Mike Smith writes: : : It doesn't do anything to the keyboard, it just calls the BIOS to find : : out whether keys have been pressed. : : I've been seeing the hit CR twice fast problem for months. : : It's always been a problem; we don't understand the mechanics of it : however. Susceptibility varies widely between systems, and the best : hypothesis I've been able to come up with is that there are issues with : taking interrupts in vm86 mode; possibly the BIOS is being re-entered in : a fashion it doesn't like. Just wanted to make sure you acknowledged the problem. It sounded like you were saying that it wasn't a problem at all rather than the theory put forward wasn't likely the problem. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't setup to provide hostnames to the requrestor. Seems they're set up incorrectly then. You can't be a good "network citizen" these days without a resolvable hostname that also matches your primary IP address or, among other things, you won't be able to send mail directly to anyone who practices traditional spam filtering techniques. Actually, the problem here is that our dhclient doesn't pick the hostname up the first time around. If it's set in an existing lease that is just confirmed, it works, but if you're starting without a lease, you won't get a hostname set (but it will be in the lease file, so if you restart before the lease expires you're OK). This also isn't just pedantry because, as I noted before, specifying the hostname will currently cause it to override the DHCP hostname value even if it is specified (as it certainly is on *my* DHCP server :-) and result in broken behavior for the aformentioned mailers. If we were to fix that in our rc scripts, I could remove this assumption in sysinstall in good conscience. Personally I'd prefer to just fix the DHCP client so that it correctly sets the hostname as obtained from the server... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
Why not check to see what the hostname is after dhclient is run and then stick that name in the network setup dialog box. If the user does edit the hostname themselves, then you can flag that event. That would work in that one specific case with that specific dhcp server. Now change the dhcp server post-install time and watch what happens. :-) What is clearly needed is some idea of "fallback hostname" vs the one you *might* be automatically assigned by "something else" (one current value for something else being DHCP) and should probably use preferentially. Split the hostname into two variables and do the appropriate rc dance magic, off ya go. Of course, this also fails to address a more fundamental failing in our rc scripts, this being that the concept of "network identity" is currently handled in too simplistic a fashion. When dealing with the "local vs on the road" scenario, many laptop users (including myself) end up hand-editing their rc.conf files or adding some cheesy menu to the rc files which say, in effect, "choose one of the following canned configurations" and then go work the appropriate variable-setting magic. The fact that I've seen so many people re-invent this particular wheel also sends a strong hint that a better, more general, mechanism is now overdue. As the original architect of FreeBSD's rc.conf (nee /etc/sysconfig) mechanism, I can also say with some assurance that it's reached its limits. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Comments on this patch?
On Thu, Jan 27, 2000 at 02:44:27PM -0700, Warner Losh wrote: I've been running this for a while. I reversed the normal order to make it easier to do the math w/o having to shift columns and flip things over. Thanks for the patch! It'd be nice to time the buildworld only. Is there a timed installworld? (I think `make world` is the only one, but I never really cared that much for these stats anyway ;-) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Errors compiling kernel...
I recently cvsup'd the sources (around Thu Jan 27 19:30:48 EST 2000), and I'm getting these errors compiling the kernel: cc -c -mpentium -O3 -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/ata/atapi-all.c ../../dev/ata/atapi-all.c: In function `atapi_attach': ../../dev/ata/atapi-all.c:96: syntax error before `}' *** Error code 1 Stop in /usr/src/sys/compile/CUSTOM. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
3. On the first reboot after installing, the keyboard was in a funny state. Urk, can't reproduce it. I need a reproducible sequence of operations before we'll have any hope of tackling this one. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. Same here. I have on a number of occasions had my laptop boot with a non-functional keyboard. Sometimes the keyboard is just locked; other times it generates garbage. Never managed to isolate the circumstances in which this happened (but it didn't happen with a kernel from last September or there-abouts). Haven't had it happen on a desktop or server yet. I have had reports on similar lockup in both 4.0-CURRENT and 3.X. I personally have not been able to reproduce it, but now my new sand box machine exhibits this problem occasionally. The I/O access to the AT keyboard by the atkbd driver have not changed much for the last couple of years, despite massive source tree reorganization. And yes, problem reports started to pop-up since sometime around the last summer. I have not been able to track down the cause of the problem, but am suspecting possibility of the clock/timer problem. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
I seem to have this problem occasionaly, the keyboard keymap gets all screwed up somehow, and the only way to get out is to hit the reset button. But I've been having the problem for a long time, and with different boxes. It happens about every 1 out of 15 reboots but randomly. I haven't been able to connect it to any event or anything, but I notice that hitting keys during boot can increase the probability of it occurring, but again, nothing reproducible. If you hit any key while the keyboard driver is trying to initialize the keyboard, there is a good possibility that the driver will be screwed. But, it mustn't show problems if you hit the keyboard during the boot loader or after the driver is attached... Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Errors compiling kernel...
On Thu, Jan 27, 2000 at 07:31:50PM -0500, Donn Miller wrote: I recently cvsup'd the sources (around Thu Jan 27 19:30:48 EST 2000), and I'm getting these errors compiling the kernel: cc -c -mpentium -O3 -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/ata/atapi-all.c ../../dev/ata/atapi-all.c: In function `atapi_attach': ../../dev/ata/atapi-all.c:96: syntax error before `}' *** Error code 1 Soren Schmidt (sos) made some recent commits to the ATA driver. Perhaps these problems are the result. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in === makeinfo
whereintheworld.pl (thanxs Bill Fenner) shows ... What does this Perl script do? :-) See http://www.freebsd.org/~fenner/ - it parses "make world" output in a way that gives slightly better progress info than just a "tail". Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
In message [EMAIL PROTECTED] Mike Smith writes: : It doesn't do anything to the keyboard, it just calls the BIOS to find : out whether keys have been pressed. I've been seeing the hit CR twice fast problem for months. It's always been a problem; we don't understand the mechanics of it however. Susceptibility varies widely between systems, and the best hypothesis I've been able to come up with is that there are issues with taking interrupts in vm86 mode; possibly the BIOS is being re-entered in a fashion it doesn't like. I wonder if the keyboard interrupt is blocked for a prolonged period in the boot loader because of vm86, and quite a number of (up to 16 or something) scan codes are waiting in the keyboard to be received by the host computer, when the kernel is loaded. The keyboard driver atkbd tries to flush pending scan codes, left over from the boot loader, before it starts initializing the keyboard. It may be failing to flush all the pending scan codes if there are too many of them. The following patch will make the driver wait slightly longer to flush inputs. I would like to see if this makes any difference. I should come up with something better this, though... Kazu Index: atkbd.c === RCS file: /src/CVS/src/sys/dev/kbd/atkbd.c,v retrieving revision 1.22 diff -u -r1.22 atkbd.c --- atkbd.c 2000/01/20 13:32:53 1.22 +++ atkbd.c 2000/01/28 00:47:27 @@ -1085,7 +1098,7 @@ } /* flush any noise in the buffer */ - empty_both_buffers(kbdc, 10); + empty_both_buffers(kbdc, 200); /* save the current keyboard controller command byte */ m = kbdc_get_device_mask(kbdc) ~KBD_KBD_CONTROL_BITS; To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Comments on this patch?
:On Thu, Jan 27, 2000 at 02:44:27PM -0700, Warner Losh wrote: : I've been running this for a while. I reversed the normal order to : make it easier to do the math w/o having to shift columns and flip : things over. : :Thanks for the patch! It'd be nice to time the buildworld only. Is there :a timed installworld? (I think `make world` is the only one, but I never :really cared that much for these stats anyway ;-) : :-- :Will Andrews [EMAIL PROTECTED] :GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- I just use the 'time' csh/tcsh variable: time Control automatic timing of commands. If set, then any com- mand that takes more than this many cpu seconds will cause a line giving user, system, and real times and a utilization percentage which is the ratio of user plus system times to re- al time to be printed when it terminates. I set it to something relatively high, like 15 minutes. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000 16:06:31 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said: citizen" these days without a resolvable hostname that also matches your primary IP address or, among other things, you won't be able to send mail directly to anyone who practices traditional spam filtering techniques. However, there is no need to actually use the configured hostname for this purpose. `temp-4224.lcs.mit.edu' is just that, temporary -- I want my machine to know what its *real* identity is. From my perspective, when I'm installing a FreeBSD machine, the DHCP client option serves only to quick-start the installation -- the machine will eventually have a real address. It would be useful to me if sysinstall paid attention to the hostname I specified the hostname will currently cause it to override the DHCP hostname value even if it is specified (as it certainly is on *my* DHCP server :-) and result in broken behavior for the aformentioned mailers. You have your mail server set to ``authenticate'' based on the HELO? That's the only thing in the SMTP protocol that the kernel's hostname setting has any impact on. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Comments on this patch?
On Thu, Jan 27, 2000 at 04:00:40PM -0700, Warner Losh wrote: So I'd say this is with 2.7.3 and the compiler in today's current. Ah. 2.95.2 is a known speed snail. The GCC developers took this to heart and 2.96 will compile much faster. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000 16:06:31 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said: citizen" these days without a resolvable hostname that also matches your primary IP address or, among other things, you won't be able to send mail directly to anyone who practices traditional spam filtering techniques. However, there is no need to actually use the configured hostname for this purpose. `temp-4224.lcs.mit.edu' is just that, temporary -- I want my machine to know what its *real* identity is. From my perspective, when I'm installing a FreeBSD machine, the DHCP client option serves only to quick-start the installation -- the machine will eventually have a real address. It would be useful to me if sysinstall paid attention to the hostname I specified That's not correct; your DHCP configuration should reflect the hostname. Sysinstall doesn't fill in the hostname field because the crunched binary is missing the hostname(1) command. If we were to add that, it's just possible that we'd get hostnames working too. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 04:06:31PM -0800, Jordan K. Hubbard wrote: IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't setup to provide hostnames to the requrestor. Seems they're set up incorrectly then. Not at all. You can't be a good "network citizen" these days without a resolvable hostname that also matches your primary IP address or, among other things, you won't be able to send mail directly to anyone who practices traditional spam filtering techniques. I will state unequivocally that most DHCP clients use a local mail relay. And the local relay will use a "generic" hostname on the email address. Also, the DNS "name" has nothing to do with the host's name. The sites DNS admins will have both forward and reverse (A PTR) RR's. Also I will state in large shops, they don't hardcode IPs to particular machines. Thus over time a machine has many different IPs. People would not be too happy to see their hostnames change all the time, nor to be the typical "foo-bar-dhcp-134-89" that the assigned IP will resolve to. In a Winloose network, they don't care about matching machine names with DNS hostnames. This also isn't just pedantry because, as I noted before, specifying the hostname will currently cause it to override the DHCP hostname value even if it is specified (as it certainly is on *my* DHCP server :-) Yes, this behavior is ISC's ruled desire. From experience Ted Lemon and Co. knows that most shops don't handout hostnames, and when they do they are long nonsensical ones. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current is still broken as of 2000/01/27
=== libexec/getNAME cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/getNAME/ge tNAME.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -o getNAME getNAME.o gzip -cn /usr/src/libexec/getNAME/getNAME.1 getNAME.1.gz === libexec/getty cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/getty/main .c In file included from /usr/src/libexec/getty/main.c:71: /usr/src/libexec/getty/extern.h:61: conflicting types for `setflags' /usr/obj/usr/src/i386/usr/include/unistd.h:186: previous declaration of `setflag s' *** Error code 1 .. Guys, this is pretty bad! - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: Actually, the problem here is that our dhclient doesn't pick the hostname up the first time around. If it's set in an existing lease that is just confirmed, it works, but if you're starting without a lease, you won't get a hostname set (but it will be in the lease file, so if you restart before the lease expires you're OK). Are you sure? In the case I know you experience, the server changed its behavior WRT handing out hostnames. I don't doubt that such a switch mid-stream in using DHCP would confuse things. Personally I'd prefer to just fix the DHCP client so that it correctly sets the hostname as obtained from the server... Nope. Poll larger shops first on their DHCP usage. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
That's not correct; your DHCP configuration should reflect the hostname. Sysinstall doesn't fill in the hostname field because the crunched binary is missing the hostname(1) command. If we were to add that, it's just possible that we'd get hostnames working too. Actually, that's not quite true and hasn't been for awhile now: jkh@highwing- grep hostname /usr/src/release/*conf* /usr/src/release/boot_crunch.conf.generic:progs dhclient arp hostname - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: Actually, the problem here is that our dhclient doesn't pick the hostname up the first time around. If it's set in an existing lease that is just confirmed, it works, but if you're starting without a lease, you won't get a hostname set (but it will be in the lease file, so if you restart before the lease expires you're OK). Are you sure? In the case I know you experience, the server changed its behavior WRT handing out hostnames. I don't doubt that such a switch mid-stream in using DHCP would confuse things. Quite sure. I have several machines installed with the 26th snapshot that aren't setting the hostname correctly. You were present when the hostname issuing from the server problem was fixed, and the clients were still not picking them up then. Personally I'd prefer to just fix the DHCP client so that it correctly sets the hostname as obtained from the server... Nope. Poll larger shops first on their DHCP usage. Correct behaviour would be not to set the hostname unless: a) it is not already set or b) it was previously set by the DHCP client You could probably ignore b) and satisfy most people. At the moment, the hostname is _never_ set by the DHCP client _unless_ it finds a lease that is still valid. This is clearly a bug. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
