Make World fails
Hello all.. I'm attempting to upgrade from 3.2-Release to -current, got all the sources through anonymous cvs and went through the process. Ran into a glitch that was solved by updating a module,, then all went well for about 45 minutes. Then I got the error "Dont' know how to make argwatch.c" It's a part of /src/gnu/usr.bin/cvs I looked at the Makefiles and it was including two directories. Neither directory (/src/gnu/usr.bin/cvs/lib and /src/contrib/cvs/src) had the files that it is in /src/gnu/usr.bin/cvs/lib/Makefile . I checked anonymous FTP and it was the same situation. And I haven't received anythhing from the cvs-all mailing list regarding these files. What do I do to get this to finish up? Thanks, Jon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make world fails
Sorry if this is a repeat, I don't think my letter was sent... On attempting to upgrade from 3.2-RELEASE to -current, make world fails. The problem lays with /src/gnu/usr.bin/cvs. In /sr/gnu/usr.bin/cvs/lib/Makefile it's looking for files in /src/contrib/cvs/src and /src/gnu/usr.sbin/cvs/lib that do not exist. I check the ftp site, they aren't there, and i've cvs up'd the modules. On the web cvs browser, the files show up but are marked as Attic and have been removed. How do i fix this? Thanks, Jon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrade to current from 3.3-RELEASE
I had the *exact* same error a minute ago.. upgrading from 3.2-RELEASE, I tried upgrading my texinfo from 3.12 to 4.0 but that didn't do anything. :On Tue, Feb 29, 2000 at 03:25:38PM -0500, Aaron Hughes wrote: > > I cvsup upgraded my /src dir to 'release=cvs tag=.' which I believe to be > 4.0-CURRENT. > > I successfully completed a 'make -j10 buildworld', however, when I ran > make -j10 installworld' I received the following error: > > [snip] > > ===> lib/libcom_err/doc > install-info --quiet --defsection="Programming & development > tools." --defentry="* libcom_err: (com_err).A Common Error > Description Library for UNIX." com_err.info /usr/share/info/dir > install-info: unrecognized option `--defsection=Programming & development > tools.' > Try `install-info --help' for a complete list of options. > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > > [end snip] > > Anyone have any thoughts on how to get this to install corrently? > > Thanks, > Aaron > > > > - Aaron Hughes > - Manager, Network Backbone, Internet Implementation, RCN > - [EMAIL PROTECTED] > - For public PGP key: finger [EMAIL PROTECTED] > - Key fingerprint = AD 67 37 60 7D 73 C5 B7 33 18 3F 36 C3 1C C6 B8 > > > > > > 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: 3.4 -> 4.0 upgrade problems
oN tUE, mAR 07, 2000 AT 05:05:40PM +0200, Ruslan Ermilov wrote: > On Wed, Mar 08, 2000 at 01:02:29AM +1000, Idea Receiver wrote: > [...] > > btw, I have problem to make release, it kept complain about that i didnt > > set the USA_RESIDENT, however, I did! both in /etc and /etc/defaults. Can > > please someone help me out with this as well.. > > > > thanks :) > > Set USA_RESIDENT in environment rather than in /etc. Or just put USA_RESIDENT=YES in /etc/make.conf To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ad0 Time Out
I've encountered a problem when booting my -current kernel. I'd include parts of the /var/log/messages, but it does not write to it when I boot up current. I installed the -current kernel, and made the devices for ad0 and ad1 including all the slices that I need, besides making all devices. I changed the /etc/fstab from wd to ad. I manually enter my root device when it's booting. Here's the problem I have: (I bet it's because of somethign stupid i did, or did not do...) It detects ad0 and ad1 allright, but then when it tries to mount root (ad0s3a) it gives me an error like the following: ad0: WRITE timed out. It then proceeds to crash. If anybody can help me I'd appreciate that, I know I don't have a whole lot of information, but I'll provide it if anybody needs specific things.. It's just a little harder to include it when it doesn't save it to the hard drive. Thanks, Jon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Question related to FreeBSD Serial Console...
Hiya > Unfortunately, many motherboards (BIOSs?) won't initialise a PS/2 keyboard > interface unless a keyboard is connected at boot time, so if you plug in a > keyboard subsequently it won't work. Nothing the OS can do in this case (I > believe), and yes it's a PITA. Keyboard and mouse manufacturers usually give dire warnings about plugging in PS/2 devices when the machine is powered up, maybe that's the reason why. --Jon http://www.witchspace.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cannot create partition entries for /dev/ad3
Hiya > I read that too. That appears to be just about all the information about > the new devfs that there is, > short of reading the source code. If you look in /usr/share/doc (or someplace like that) there's a document describing the rationale behind devfs and its implementation - it's geared more towards programmers than end users, but I certainly found it useful. Cheers, --Jon http://www.witchspace.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sound no longer works ... ?
Hiya > I'm running: > > pcm0: mem 0xfea0-0xfeaf,0xfe00-0xfe3f irq > 9 at device 8.1 on pci0 > pcm0: > > on a Sony VAIO ... Just wondering: had you applied the IRQ rerouting patch to get your sound working? I got caught out by this when I upgraded my VAIO and ended up getting mangled sound again. --Jon http://www.witchspace.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X11 unstable under CURRENT and STABLE.
Robert Suetterlin wrote: >Hi! > > I read a few threads on the stableness of X11 under CURRENT. >Some people proposed it was more stable under STABLE. > >I can report that my X on STABLE: > XFree86 Version 4.2.1 / X Window System > (protocol Version 11, revision 0, vendor release 6600) > Release Date: 3 September 2002 > If the server is older than 6-12 months, or if your card is > newer than the above date, look for a newer version > before reporting problems. (See http://www.XFree86.Org/) > Build Operating System: FreeBSD 4.7-RC i386 [ELF] > > 4.7-RC as of September 19th. > >X crashed after killing acroread with CTRL-C. (Un)fortunately I could not >repeat this behaviour so far. > >Sincerely, Robert S. > > > > Crashes fo r me too, reporting Sigint 6, Basically whenever it is idle. Usually just running Opera and Mozilla-mail. Any Sugestions?? Cheers, Jon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Superfast clock on current.
I too have experienced this problem with -current. I'm running on a Thinkpad A21p, but with a fairly out-of-date build (September 1, 2001). This happens, I believe. because the kernel thinks the processor is running at one speed and then that speed changes to reflect different power management settings. For example, if I configure BIOS APM to clockdown the processor on battery and run full-throttle on AC power. My clock runs smoothly on battery (the condition I booted in), but when I engage the AC the clock runs a few times faster than normal. I can control this condition simply adding and removing AC power and having the BIOS APM react. It is clear: the processor speed is not held constant and this produces the behavior you mention. Some data points: Right after boot ntptimeset reports: Your clock is off by -4.4654581 seconds. (131.215.225.254) [48/47] Some minutes later: Your clock is off by -1710.9709441 seconds. (131.215.225.254) [37/36] Anyways, my dmesg is attached. -Jon Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Sat Sep 1 01:18:52 PDT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PHILEMON Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 846865184 Hz CPU: Pentium III/Pentium III Xeon/Celeron (846.87-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383f9ff real memory = 134152192 (131008K bytes) avail memory = 125894656 (122944K bytes) Preloaded elf kernel "kernel" at 0xc049. Preloaded userconfig_script "/boot/kernel.conf" at 0xc049009c. Pentium Pro MTRR support enabled Using $PIR table, 11 entries at 0xc00fdee0 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) pcic0: mem 0x5000-0x5fff irq 11 at device 2.0 on pci0 pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] pccard0: on pcic0 pcic1: mem 0x5010-0x50100fff irq 11 at device 2.1 on pci0 pcic1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] pccard1: on pcic1 fxp0: port 0x1800-0x183f mem 0xf010-0xf011,0xf012-0xf0120fff irq 11 at device 3.0 on pci0 fxp0: Ethernet address 00:10:a4:8e:87:33 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at 3.1 (no driver attached) csa0: mem 0xf000-0xf00f,0xf0122000-0xf0122fff irq 11 at device 5.0 on pci0 csa: card is Thinkpad 600X/A20/T20 pcm0: on csa0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1850-0x185f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x1860-0x187f irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 7.3 (no driver attached) orm0: at iomem 0xc-0xc,0xd-0xd17ff,0xe-0xe on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pmtimer0 on isa0 ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default IP Filter: v3.4.20 initialized. Default = block all, Logging = enabled ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 30520MB [66144/15/63] at ata0-master UDMA33 acd0: DVD-ROM at ata1-master PIO4 Mounting root from ufs:/dev/ad0s2a lock order reversal 1st 0xc8d1621c process lock @ /usr/src/sys/vm/vm_glue.c:469 2nd 0xc0b30ec0 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239
Re: Neat little DPT utils...
On Wed, 19 Jan 2000, damieon wrote:
> I administer several machines running freebsd. Most of
> them are running FreeBSD-CURRENT, and all of them have DPT SmartRAID IV
> raid controlers.
I've got a backup server here with a DPT SmartRAID IV (PM3334UW) running
3.3-STABLE from Nov 17. About 15 minutes of playing and I've got the programs
compiling cleanly, however:
root@tyberius:/usr/src/usr.sbin/dpt/dpt_ctlinfo$ ./dpt_ctlinfo
./dpt_ctlinfo ERROR: Failed to open "(null)" - Bad address
Looking at the code some more, I see:
if ( (fd = open(argv[1], O_RDWR, S_IRUSR | S_IWUSR)) == -1 ) {
(void)fprintf(stderr, "%s ERROR: Failed to open \"%s\" -
%s\n",
argv[0], argv[1], strerror(errno));
exit(1);
}
So, I'm stuck with a compiling program and I don't know what it wants as an
argument. Anything I try give me an:
root@tyberius:/usr/src/usr.sbin/dpt/dpt_ctlinfo$ ./dpt_ctlinfo /dev/da0
./dpt_ctlinfo ERROR: Failed to send IOCTL c003 - Inappropriate ioctl for
device
I'll be looking into this some more over the next couple days, but any hints
or suggestions are more than welcome. If I can get it running in this
3.3-STABLE server, then I'll steal the controller for a weekend and bang out
some -CURRENT code, although I think the necessary changes (STABLE -> CURRENT)
should be fairly minor.
---
Jon Simola <[EMAIL PROTECTED]> | "In the near future - corporate networks
Systems Administrator | reach out to the stars, electrons and light
ABC Communications | flow throughout the universe." -- GITS
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches)
In message <Pine.BSF.4.21.0001221703020.4454-10@localhost>, Alex Zepeda wro te: } On Sat, 22 Jan 2000, Rod Taylor wrote: } } > Personally, I'd like to see less stuff in the system source for } > smaller installs and lower compile time leaving it up to me to } > customize the individual stuff thats installed. Unless bzip is used } > by > 99.9% of the FreeBSD installs, I'm willing to let it } > 'auto-install itself'. } } What if we began to use bzip2 instead of gzip for things like man pages, } or releases, etc? I did that (for man pages) out of curiosity a year or two ago, and the difference was negligible. bzip2 seems to do better on bigger files as a (very) general rule than on smaller ones. } I think gzip is somewhat like compress, in that it might never go away } completely, but it's generally been superceded by (IMO) bzip2. I don't agree at all, and all you have to do is visit a few web sites and ftp sites' download areas to see why. It's just not ubiquitous, or even close. -- Jon Hamilton [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Crypto progress! (And a Biiiig TODO list)
In message <[EMAIL PROTECTED]>, Wes Peters wrote: } Lyndon Nerenberg wrote: } > } > >>>>> "Mark" == Mark Murray <[EMAIL PROTECTED]> writes: } > } > Mark> o A username may only be checked $number times per } > Mark> $timeperiod; after that, _all_ answers are silently } > Mark> converted to "no". } > } > Umm, massive DOS hole. } } Per username. If you publish your userlist, you're an idiot. The } daemon should also immediately go into "breakin evasion mode" for } all invalid usernames, answering the requests very slowly. You don't have to publish a userlist in order for some of that kind of information to leak out. Besides, by answering very slowly for invalid usernames you just gave the bad guys a way to deduce your user list anyway. -- Jon Hamilton [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ps doesn't need privileges?
In message <[EMAIL PROTECTED]>, Chris Costello wrote: } On Sun, Sep 12, 1999, Peter Wemm wrote: } > Now that I think about it, it shouldn't be too hard (TM) to finish off the } > /proc/pid/cmdline stuff so that ps didn't need to access /mem and didn't } > need setgid at all. } }What about the `e' flag? What about people who don't use /proc? Maybe I'm misreading; is the plan to make ps work (at least with most of the bells and whistles) only with /proc, or is the plan to make it an option to either strip the setgid and use proc, or to leave it and use kmem? -- Jon Hamilton [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Netscape core dump, happily :-)
On Sun, Oct 03, 1999 at 12:22:55PM +0200, Gianmarco Giovannelli wrote: > Is there anyone who is experienced Netscape crashes with 4.0-CURRENT when > the close button is pressed (not always, but very often) ? > It happens to me with 4.61 and 4.70 , it doesn't happen with 3.2-STABLE I > have at work. Yes, I've been experiencing that as well. It writes a zero length core file in my home directory and exits with signal 10: Oct 1 16:20:53 void /kernel: pid 18518 (navigator-4.61.b), uid 1000: exited on signal 10 It's incredibly annoying, but I haven't bothered to track it down in any great detail. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.pobox.com/~parise/ : Computer Science House Member To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ppp over pty: trying to detect CD
Running -current from this afternoon, I am having a strange symptom with ppp over a pty; ppp does not detect that the pty does not support carrier, and will cycle once per second waiting for CD to appear. Putting ``set cd off'' in my ppp.conf for that target fixed the problem, but I thought I'd mention it nonetheless, since that didn't used to be required. Certainly not all that big a deal, but I thought it was worth a mention. FreeBSD 4.0-CURRENT #13: Sat Dec 11 20:31:42 CST 1999 The section from my ppp.conf: vpn: set ipcpretry 1000 set lcpretry 1000 set timeout 0 set ifaddr 192.168.1.2/0 192.168.1.1/0 255.255.255.0 set cd off <- this guy fixed the problem enable lqr accept lqr set openmode passive set log phase ipcp Connect tun Command add 192.168.2.0/24 HISADDR and the syslog with debugging turned on, with no "set cd" in the config: Dec 11 20:48:20 woodstock ppp[3106]: Phase: Using interface: tun1 Dec 11 20:48:20 woodstock ppp[3106]: Phase: deflink: Created in closed state Dec 11 20:48:20 woodstock ppp[3106]: tun1: Command: vpn: add 192.168.2.0/24 HISADDR Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: wrote 140: cmd = Add, dst = 2a8c0, gateway = 101a8c0 Dec 11 20:48:20 woodstock ppp[3106]: tun1: Phase: PPP Started (direct mode). Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: Select changes time: no Dec 11 20:48:20 woodstock ppp[3106]: tun1: Phase: bundle: Establish Dec 11 20:48:20 woodstock ppp[3106]: tun1: Phase: deflink: closed -> opening Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: Input is a tty (/dev/ttyp0) Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: tty_Create: physical (get): fd = 0, iflag = 0, oflag = 2, cflag = 4b00 Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: physical (put): iflag = 201, oflag = 2, cflag = 3cb00 Dec 11 20:48:20 woodstock ppp[3106]: tun1: Phase: deflink: Connected! Dec 11 20:48:20 woodstock ppp[3106]: tun1: Phase: deflink: opening -> carrier Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: Waiting for carrier Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: Waiting for carrier [ and on and on and on ] -- Jon Hamilton [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: is it really at the end of its lifecycle?
On Wed, Dec 15, 1999 at 11:44:17AM -0800, Jordan K. Hubbard wrote: > > Call it Inuit. (rationale: Inuit feed on pinguins (right?)) > > How about PolarBear in that case? :) I was under the impression that Polar Bears are native to the North Pole and penguins are from the South Pole. Promoting a zoologically correct operating system ... -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.pobox.com/~parise/ : Computer Science House Member To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dangerously looking glitch (4.0-STABLE)
In message <[EMAIL PROTECTED]>, Maxim Sobolev wrote: } This is a multi-part message in MIME format. } --3D64CAE46133EFA188180FFD } Content-Type: text/plain; charset=koi8-r } Content-Transfer-Encoding: 7bit } } Hi, } } I've tried to track down why my own script which is cleaning non-matching } distfiles from time to time produce incorrect results (just cvsup'ed 4.0). } After some digging I've found that this bug could be easily reproduced by doi } ng } "find -exec md5" on large set of files several times consequiently, and then } comparing results. You can see that md5 checksum of the one of the files is How many in a "large set"? I tried 10 passes on my 4.0-stable machine and was not able to replicate your results, though I only have about 500 files in my distfiles. I tried the same in /usr/src, and in another area with both large and small files (393,000 total), all of which came up clean. I think you have a hardware problem somewhere :( -- Jon Hamilton [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dangerously looking glitch (4.0-STABLE)
In message <[EMAIL PROTECTED]>, Maxim Sobolev wrote: } Frank Nobis wrote: } } > On Wed, Apr 05, 2000 at 07:13:29AM -0500, Jon Hamilton wrote: } > > } > > up clean. I think you have a hardware problem somewhere :( } > } > That is very likely a hardwre problem. I have a nfs server under 3.4-S } > here running, It was easy to crash the system with much I/O over nfs } > on a 100M Ethernet connection. (I did a dump and the machine paniced) } > } > The same over a slower 10M ethernet, but it took longer to crash. } > } > Now I replaced a very old adaptec 1542cf with a 2940U. I did the same } > stress test, but got no more panics. Even a load of 80% interrupts } > didn't kill the machine. } > } > Maybe you have a similar problem. } } It is unlikely, because I've never seen this problem previously when 3.[01234 } ] } was installed on this hardware. Hardware does fail over time; just because it performed OK in the past doesn't mean that something hasn't gone bad since. I suppose it could be a problem with one of the drivers for your particular setup; is it feasable for you to try booting an older version (even from floppy) of FreeBSD and try the test again? -- Jon Hamilton [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Sun, Apr 09, 2000 at 02:44:25PM -0400, Patrick Bihan-Faou wrote: > I have integrated the source of qmail so it can be built as part > of the "world". I think that it would be nice to have an > alternative for the mailer package to be built as part of a make > world. I don't recall the particulars (it's been a while since I've managed a qmail installation), but aren't there issues with qmail's distribution license that would make integrating it into the build tree illegal? As a side note, I don't think it's all that good of an idea to add another MTA to the build tree, but I'm sure others will raise a more substantial argument than I could. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
In message <[EMAIL PROTECTED]>, Richard Wackerbarth wrote } > > Do we really need 5 year old history? } > } > Yes. } I don't disagree that we need to maintain the history. } } I do, however, question the policy that REQUIRES EVERYONE to maintain that } much history. I've been following this thread at some distance for a while, and I don't understand your definition of ``everyone''. Aside from developers, who do you feel is a good candidate to track the entire CVS repository, rather than using CVSUP or some other method to get only the tree they are interested in? I'm not trying to be snide; it's possible that I'm missing some element of your argument, but I think using the term ``everyone'' is overstating the case considerably. -- Jon Hamilton [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kerberos5 breaks buildworld in -current
GO VINCE GO! YAH Vincent Poy wrote: > On Tue, 16 Oct 2001, Valentin Chopov wrote: > > > just replace mv with cp in /usr/src/kerberos5/lib/libasn1/Makefile > > I replaced the 2 mv's in /usr/src/kerberos5/lib/libasn1/Makefile > with cp and while the lib compiles, the problem now is: > > cc -nostdinc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS > -DOLD_ENVIRON -DENV_HACK -DAUTHENTICATION -DENCRYPTION > -I/usr/src/kerberos5/libexec/telnetd/../../../crypto/telnet -DINET6 -Wall > -I/usr/src/kerberos5/libexec/telnetd/../../include > -I/usr/src/kerberos5/libexec/telnetd/../../include -DHAVE_CONFIG_H > -DKRB5_KRB4_COMPAT -DKRB4 -DINET6 -I/usr/obj/usr/src/i386/usr/include > -o telnetd global.o slc.o state.o sys_term.o telnetd.o termstat.o > utility.o authenc.o -lutil -ltermcap > /usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a > -lmp -lcrypto -lcrypt -lpam > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x44): > undefined reference to `kerberos4_init' > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x48): > undefined reference to `kerberos4_send' > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x4c): > undefined reference to `kerberos4_is' > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x50): > undefined reference to `kerberos4_reply' > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x54): > undefined reference to `kerberos4_status' > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x58): > undefined reference to `kerberos4_printsub' > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x64): > undefined reference to `kerberos4_init' > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x68): > undefined reference to `kerberos4_send' > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x6c): > undefined reference to `kerberos4_is' > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x70): > undefined reference to `kerberos4_reply' > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x74): > undefined reference to `kerberos4_status' > >/usr/obj/usr/src/kerberos5/libexec/telnetd/../../lib/libtelnet/libtelnet.a(auth.o)(.data+0x78): > undefined reference to `kerberos4_printsub' > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > Cheers, > Vince - [EMAIL PROTECTED] - Vice President __ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > WurldLink Corporation / / / / | / | __] ] > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > 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
current doesnt see ps2 port with acpi enabled on intel vc820
Hello, I have just compiled and installed -current from this morning 7AMPST, and have noticed that when acpi is enabled in loader.conf the OS does not see the ps2 mouse port. When I turn off ACPI the mouse port shows up fine. Other than not seeing the ps2 port when in ACPI enabled mode, the OS works without a hitch on my motherboard. Any ideas? IF this is a known problem please let me know, as I have been off this list for a month or so. On another note .. when doing a make distribution in /usr/src/etc, the process will fail when trying to install MAKEDEV and MAKEDEV.local into /dev both in single user and multiuser. I got around this by telling it to not install them. I have attached dmesg output from both ACPI and non ACPI enabled boots. Thanks in advance, Jon Christopherson Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Sat Dec 15 08:04:04 PST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENESIS Preloaded elf kernel "/boot/kernel/kernel" at 0xc0438000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04380a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 598476354 Hz CPU: Pentium III/Pentium III Xeon/Celeron (598.48-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 133955584 (130816K bytes) avail memory = 125849600 (122900K bytes) pnpbios: Bad PnP BIOS data checksum Pentium Pro MTRR support enabled VESA: v3.0, 16320k memory, flags:0x1, mode table:0xc03788a2 (122) VESA: NVidia Using $PIR table, 11 entries at 0xc00f2f60 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 acpi_pcib0: port 0xcf8-0xcff on acpi0 pci0: on acpi_pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 pcm0: port 0xdf00-0xdf3f irq 11 at device 7.0 on pci2 fxp0: port 0xdf80-0xdf9f mem 0xfe90-0xfe9f,0xf43ff000-0xf43f irq 10 at device 9.0 on pci2 fxp0: Ethernet address 00:a0:c9:69:49:b4 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf irq 9 at device 10.0 on pci2 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs pci2: at device 12.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xef80-0xef9f irq 11 at device 31.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 31.3 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ata-: ata0 already exists, skipping it ata-: ata1 already exists, skipping it atkbdc-: atkbdc0 already exists, skipping it fdc-: fdc0 already exists, skipping it ppc-: ppc0 already exists, skipping it sio-: sio0 already exists, skipping it sio-: sio1 already exists, skipping it sc-: sc0 already exists, skipping it vga-: vga0 already exists, skipping it pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ad0: 39082MB [79406/16/63] at ata0-master UDMA66 acd0: CDROM at ata1-master PIO4 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s1a Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Sat Dec 15 08:04:04 PST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENESIS Preloaded elf kernel "/boot/kernel/kernel" at 0xc03f4000. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 598476017 Hz CPU: Pentium III/Pentium III Xeon/Celeron (598.48-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 1339
RE: current doesnt see ps2 port with acpi enabled on intel vc820
Hello, That patch worked like a charm! Ps2 port seen fine both in acpi mode and non-acpi mode. Thanks a lot. Perhaps this should be imported to the driver in the source tree? Attached is the new dmesg output. Regards, Jon Christopherson -Original Message- From: KT Sin [mailto:[EMAIL PROTECTED]] Sent: Saturday, December 15, 2001 7:24 PM To: Jon T. Christopherson Cc: [EMAIL PROTECTED] Subject: Re: current doesnt see ps2 port with acpi enabled on intel vc820 Hi I'm seeing the same problem on my MSI bookpc. For some reasons, the psm device will fail to get an IRQ when ACPI is enabled. Can you try the attached patch and see if it helps? kt On Sat, Dec 15, 2001 at 09:16:07AM -0800, Jon Christopherson wrote: > Hello, > > I have just compiled and installed -current from this morning > 7AMPST, and have noticed that when acpi is enabled in loader.conf the OS > does not see the ps2 mouse port. When I turn off ACPI the mouse port > shows up fine. Other than not seeing the ps2 port when in ACPI enabled > mode, the OS works without a hitch on my motherboard. Any ideas? IF this > is a known problem please let me know, as I have been off this list for > a month or so. > > On another note .. when doing a make distribution in > /usr/src/etc, the process will fail when trying to install MAKEDEV and > MAKEDEV.local into /dev both in single user and multiuser. I got around > this by telling it to not install them. > > I have attached dmesg output from both ACPI and non ACPI enabled > boots. > > Thanks in advance, > > Jon Christopherson > > Copyright (c) 1992-2001 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.0-CURRENT #1: Sat Dec 15 08:04:04 PST 2001 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENESIS > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0438000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04380a8. > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 598476354 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (598.48-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > Features=0x383f9ff > real memory = 133955584 (130816K bytes) > avail memory = 125849600 (122900K bytes) > pnpbios: Bad PnP BIOS data checksum > Pentium Pro MTRR support enabled > VESA: v3.0, 16320k memory, flags:0x1, mode table:0xc03788a2 (122) > VESA: NVidia > Using $PIR table, 11 entries at 0xc00f2f60 > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI" frequency 3579545 Hz > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > acpi_cpu0: on acpi0 > acpi_button0: on acpi0 > acpi_pcib0: port 0xcf8-0xcff on acpi0 > pci0: on acpi_pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at device 0.0 (no driver attached) > pcib2: at device 30.0 on pci0 > pci2: on pcib2 > pcm0: port 0xdf00-0xdf3f irq 11 at device 7.0 on pci2 > fxp0: port 0xdf80-0xdf9f mem 0xfe90-0xfe9f,0xf43ff000-0xf43f irq 10 at device 9.0 on pci2 > fxp0: Ethernet address 00:a0:c9:69:49:b4 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ahc0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf irq 9 at device 10.0 on pci2 > aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs > pci2: at device 12.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > uhci0: port 0xef80-0xef9f irq 11 at device 31.2 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > pci0: at device 31.3 (no driver attached) > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 on acpi0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0 port 0x3f8-0x3ff irq 4 on acpi0 > sio0: type 16550A > sio1 port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > ppc0 port 0x378-0x37f irq 7 on acpi0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ata-: ata0 already exists, skipping it > ata-: ata1 already exists, skipping it > atkbdc-: atkbdc0 already exists, sk
Re: Logitech iFeel Optical USB Mouse cannot be attached.
On Sun, Dec 23, 2001 at 04:43:55AM -0800, Raman Ng wrote: > I am using Asus A7V mb, Athlon 1.1 GHz CPU, 512 Mb > RAM. Whenever the kernel > boot up, the message device_probe_and_attach: ums0 > attach returned 6. > Details can refer to the attached detail.. This > problem is similar to PR > misc/30373 and there is no one handle it at all. I > have tried FreeBSD 4.4-RELEASE, 4.5-PRERELEASE and > 5.0-CURRENT (which is cvsup a month ago) and the > problem is still persisted. http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/30373 -- Jon Parise ([EMAIL PROTECTED]) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mtree verification output format
On Tue, Oct 03, 2000 at 10:46:56AM +1000, Greg Black wrote:
> > > size (was 1234, should be 5678)
> > > cksum (was 42424242, should be 69696969)
> > >
> > >...so that it's clear what the meaning of the numbers is.
> >
> > In that case I think I would like to loose the ',' also.
>
> While you're at it, why not use single word verbs:
>
> size (got 1234 wanted 5678)
> cksum (got 42424242 wanted 69696969)
Or perhaps:
size (got 1234 expected 5678)
cksum (got 42424242 expected 69696969)
--
Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology
http://www.csh.rit.edu/~jon/ : Computer Science House Member
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: cvs servers load
On Sat, Oct 07, 2000 at 09:44:39PM +0200, Wilko Bulte wrote: > Time to put the cvsup servers on the map with ICBM coordinates maybe? I think that would actually be quite useful (or, at the very least, purely informative). -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed small change to .cshrc
On Tue, Jan 09, 2001 at 09:45:14AM -0800, Archie Cobbs wrote:
> + if ( `basename $SHELL` == "tcsh" ) then
> + bindkey ^W backward-delete-word
> + endif
I generally test for tcsh like this:
if ( $?tcsh ) then
bindkey ^W backward-delete-word
endif
--
Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology
http://www.csh.rit.edu/~jon/ : Computer Science House Member
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: correction for find(1)'s man page
In message <199901180357.taa22...@vashon.polstra.com>, John Polstra wrote: } In article <36a0fc11.8b22d...@cybercable.fr>, } Thierry Herbelot wrote: } > Hello } > } > I was reading the man page for find(1), looking for the precise option } > to follow symbolic links. } > } > This option is -follow, of course, but it is not described in the man } > page } } Huh? The correct options are the first three options described in } the man page: } -H The -H option causes the file information and file type (see }stat(2)) returned for each symbolic link specified on the command }line to be those of the file referenced by the link, not the link }itself. If the referenced file does not exist, the file informa- }tion and type will be for the link itself. File information of }all symbolic links not on the command line is that of the link }itself. What this doesn't explicitly say is that it causes find(1) to actually follow the symlink and recursively descend the target tree (if the link points to a directory); I assume that's the behavior the original poster wanted. Near the bottom of the find(1) manpage (on my -stable system), is this: Historically, the -d, -h and -x options were implemented using the pri- maries ``-depth'', ``-follow'', and ``-xdev''. These primaries always ``-h'' there should read ``-H''; -h is an unknown option to find(1). -- Jon Hamilton hamil...@pobox.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
In message , Richar d Wackerbarth wrote: } } On Wed, 10 Feb 1999, John Fieber wrote: } } > On Wed, 10 Feb 1999, jack wrote: } > } > > If /etc/rc.conf only contains changes from the defaults when } > > man something_or_other tells the user to find and edit } > > something_or_other_flags in /etc/rc.conf the entry won't be } > > there to edit. } > } > Why must it contain only changes? Is there any reason it } > couldn't be a copy of the default rc.conf on a new installation? } } Alternately, it could be a copy of the default file with every item } commented out. That would provide the clues for those who need to } edit values and still not mess up the default behavior of a new install } with old options that might have changed but were not explicitly } overridden. But then you're right back where you started. Since rc.conf isn't supposed to be touched by the install/upgrade tools, it'll get out of date (and will become a hinderance rather than a help) as default settings change, and as settings are added/deleted. -- Jon Hamilton hamil...@pobox.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: disk quota overriding
In message <97a8ca5bf490d211a94ff6c2e55d097...@s-lmh-wi-900.corpnet.at>, La davac Marino wrote: } BTW, has chown been "fixed" to the ludicrous SysV semantics that } the root and owner can chown a file? If so, the latter has to be } disabled in presence of quotas on the volume--otherwise: } } touch big_file } chmod 777 big_file } chown root:wheel big_file } cat /dev/zero >>big_file } } This joke used to work on HPUX 10.something which kept the } owner-may-chown semantics even in presence of quotas. It was not funny. } (I don't know whether HP has fixed that). Under HP-UX 9.x, the behavior you describe was the default, and it was changable by altering a kernel config parameter and relinking the kernel. The same tunable is available under 10.x, but I'm less certain what the default behavior is there. Whether quotas are enabled or not does not affect the behavior, only the kernel tunable parameter. -- Jon Hamilton hamil...@pobox.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: /var/db/pkg/.mkversion
In message <19990401052839.d11...@futuresouth.com>, "Matthew D. Fuller" wrote: } [ Yes, I'm sticking my nose in where it probably doesn't belong and } should get chopped off for it. It's a hobby ;] } } On Thu, Apr 01, 1999 at 02:36:14AM -0800, a little birdie told me } that Satoshi - the Wraith - Asami remarked } > } > The same situation arises whether the version info is in /var/db/pkg } > or /some/other/place. It has been pointed out many times in the past } > that we need something to ensure bsd.port.mk can synchronize itself } > with the rest of the system (simply because there are too many people } > who cvsup one without the other). } > } > The question is, can I ask you to make sysinstall write some kind of } > version info that can be used by bsd.port.mk to identify the age of } > the system? } } This would require a little more work on the 'back' side, but what would } be so hard about just checking $Id$ strings around the .mk files? If } not for the revision, at least for the date. I think that's asking for trouble - it'll lose if someone keeps their .mk files in their own RCS (I do this for some files; admittedly not for the .mk files, but I could see someone doing that). -- Jon Hamilton hamil...@pobox.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Annoucning DragonFly BSD!
Matthew Dillon wrote: A Packaging system is a very important piece of any distribution. Our goal will be to create a packaging system that, via VFS 'environments', causes any particular package to see only the dependancies that it depends on, and the proper version of said dependancies as well. Multiple versions of third party apps that normally conflict with each other could be installed simultaniously. The packaging-system-controlled VFS environment would also hide everything a package does not depend on, like other libraries in the system, in order to guarentee that the dependancies listed in the packaging system are in fact what the application depends on. There's no point in having a packaging system that can't detect broken and incorrect dependancies or we wind up with the same mess that we have with ports. Wouldn't it be possible to achive the same result without the VFS with well organized lib subdirs? like "usr/lib/xyzlib1.2/" and "usr/lib/xyzlib1.3/" which would maintain the install for any given version of a lib? In other words, instead of just dumping all the libs into the one place, you simply place them into sub folders instead and then link them as needed? Granted this would cause havoc for things like LD_LIBRARY_PATH. I never did like the way we dump things in the lib dir's, its messy. The VFS idea is interesting, but it like cleaning the mess by sending parts of the big mess into another dimention, making it a trans-dimentional mess (technically a larger mess). This throws away the KISS principle. To make this work the VFS environment would have to be able to run as a userland process. Otherwise we would never be able to throw in the type of flexibility and sophistication required to make it do what we want it to do, and the kernel interfacing would have to be quite robust. I want to make these environments so ubiquitous that they are simply taken for granted. Begin userland VFSs with the capability of overlaying the entire filesystem space, these environments would be extremely powerful. I suspect this ability would usefull for other things too, possibly for security lock-downs on shell users env's without chrooting them as an example. -Jon It might be possible to build this new packaging system on top of the existing ports infrastructure. It will be several months (possibly 6-12 months) before the kernelland is sufficienctly progressed to be able to imlpement the userland VFS concept so we have a lot of time to think about how to do it. -Matt Matthew Dillon <[EMAIL PROTECTED]> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: File system deadlock. GBDE(4) and/or MD(4) related.
Poul-Henning Kamp wrote: In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writ es: # touch /mnt/test.file You are probably missing: dd if=/dev/null of=/mnt/test.file bs=1m count=512 # mdconfig -a -t vnode -f /mnt/test.file -s 512M -u 1 What you have found has nothing to do with GBDE, I think it is the usual "vnode backed md(4)" deadlock. I wrote a howto that is somewhat similare to the desired steps in case anybody is interested in another way: http://www.ezunix.org/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=67&page=1 I've used gbde extensivly and have doubts about any issues. However, maybe some sanity checks in gbde would catch the problem? -Jon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH from host to jail
Pat Lashley wrote:
I'm trying to set up some jails in a 5.1R system. I've pretty much
copied a setup that was working fine in 4.8; but on 5.1 I can't seem
to SSH from the host system into one of its jails. It acts like the
packets just aren't getting through.
I would really appreciate it if somebody would send me rc.conf fragments
that are known to work for setting up a jail's IP alias and routing on
5.1.
sure, but this isn't going to fix your problem:
ifconfig_wi0="inet 192.168.0.140 netmask 255.255.255.0"
ifconfig_wi0_alias0="inet 192.168.0.131 netmask 255.255.255.255"
jail_enable="YES"
jail_list="shiba"
jail_shiba_hostname="shiba"
jail_shiba_ip="192.168.0.131"
jail_shiba_rootdir="/usr/prison/192_168_0_130/"
jail_shiba_exec="/bin/sh /etc/rc"
To fix your problem you should try to mount a devfs for the jail so the
tty device is available for sshd to open when you login. I simply added
one line to my /etc/rc.d/jail script to test for the "dev" mount-point
in jail. Like so:
[ -d "${jail_rootdir}/dev" ] && mount -t devfs ${jail_rootdir}\dev
I suppose we could avoid this little fau pax in the future by adding a
new jail specific rc.conf var like this example:
jail_shiba_devfs="/usr/prison/192_168_0_130/dev"
It could be easy to have it simply exist, or be non-null, to imply a
desire for devfs, and further checked for the existence of the
mount-point as I wrote above.
I could have a pr+patch made in 5 minutes if anybody thinks this is not
a bad idea?
-Jon
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
busdma/scsi trm(4) related panic
Hi, I've been getting what appears to be a busdma / scsi related panic for the past couple of days. This is based solely on what little info I get when it drops to the debugger - I haven't been able to get a core dump. It panics during the boot process immediately after it tries to probe my scsi devices (just a cdrom) attached to my Tekram DC-315U adapter. If I remove trm(4) from my kernel, I can boot without a panic, but if I load the trm module, and then issue `camcontrol rescan all` it will panic. Reverting /usr/src/sys/i386/i386/busdma_machdep.c to version 1.52 lets me boot and use my scsi devices without panics. Version 1.53 will panic too. This is with -current sources as of 5:57am MST (12:47UTC) on Aug. 5. FreeBSD jonnyv.kwsn.lan 5.1-CURRENT FreeBSD 5.1-CURRENT #3: Tue Aug 5 21:09:50 MST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/JONNYV i386 Here's what little info I have (apologies for typos, I had to transcribe this by hand): Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc35682f stack pointer = 0x10:0xd68fbb94 frame pointer = 0x10:0xd68fbbd8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (swi7: tty:sio clock) kernel: type 12 trap, code = 0 Stopped at _bus_dmamap_load_buffer+0x3ff: movl %ecx,0(%edx,%eax,8) $ nm -n /boot/kernel/kernel | grep c03568 c03568e0 T bus_dmamap_load If there's anything you'd like me to type at the "db>" prompt, just ask and I'll send the output. Thanks, Jon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: busdma/scsi trm(4) related panic
On Wed, 2003-08-06 at 06:42, Scott Long wrote: > I know what the problem is and I'm working on a patch right now. > > Scott Excellent. I'll be happy to test it if needed. Jon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: busdma/scsi trm(4) related panic
On Wed, 2003-08-06 at 05:00, Craig Rodrigues wrote: > On Tue, Aug 05, 2003 at 11:08:33PM -0700, Jon Kuster wrote: > > If there's anything you'd like me to type at the "db>" prompt, just ask > > and I'll send the output. > > Send the backtrace, with the 't' command. Here you go. Once again, this was hand transcribed, so sorry for any typos. -Jon db> t _bus_dmamap_load_buffer(c3fd3c40,c044660,c4193e84,24,0) at _bus_dmamap_load_buffer+0x3ff bus_dmamap_load(c3fd3c40,0,c4193e84,24,c01c9760) at bus_dmamap_load+0x6c trm_action(c406c200,c418dc00,c0130cc4,c4193e00,c4193e00) at trm_action+0x27a xpt_run_dev_sendq(c406c1c0,c4193e18,1,7,4) at xpt_run_dev_sendq+0x192 xpt_release_devq_device(c4193e00,1,1,d68fbcec,c0243b5e) at xpt_release_devq_device+0xe2 xpt_release_devq_timeout(c4193e00,c1521974,10,f8c6020d,c0131dd0) at xpt_release_devq_timeout+0x21 softclock (0,0,0,0,c1521974) at softclock+0x24e ithread_loop(c1520280,d68fbd48,0,0,c1520280) at ithread_loop+0x1c8 fork_exit(c021d770,c1520280,d68fbd48 at fork_exit+0xb1 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd68fbd7c, ebp = 0 --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: busdma/scsi trm(4) related panic
On Fri, 2003-08-08 at 23:46, Scott Long wrote: > Attached is an untested patch. Please let me know if it solves the > problem > > Scott That did the trick. Thanks! Jon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: More ULE bugs fixed.
Jeff Roberson [EMAIL PROTECTED] wrote : > On Fri, 17 Oct 2003, Bruce Evans wrote: > > How would one test if it was an improvement on the 4BSD scheduler? It > is not even competitive in my simple tests. What were your simple tests? -- Jonathan Mini <[EMAIL PROTECTED]> http://www.freebsd.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: More ULE bugs fixed.
Bruce Evans [EMAIL PROTECTED] wrote : > On Sun, 26 Oct 2003, Jon Mini wrote: > > > Jeff Roberson [EMAIL PROTECTED] wrote : > > > > > On Fri, 17 Oct 2003, Bruce Evans wrote: > > > > > > How would one test if it was an improvement on the 4BSD scheduler? It > > > is not even competitive in my simple tests. > > > > What were your simple tests? > > Er, they were in the original mail. Just do parts of buildworld with -j16 > on an SMP system. ULE was 2.4 times slower for make depend and 2.1 times > slower for make obj. Something must have been very wrong, since make obj, > especially, should be completely i/o bound so it shouldn't be affected > by the scheduler. Also, run a bunch of CPU hog processes with various > nicenesses and look at top output to check that they are given reasonable > amounts of CPU. My apologies, I just subscribed to current and only caught the tail end of this thread. -- Jonathan Mini <[EMAIL PROTECTED]> http://www.freebsd.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nss_ldap
Wasn't there a patch floating around to build a dynamic world with the placment of libc et'al in /lib ??? I'd actually like to try that patch for building a tiny fbsd image for my net4501. Thanks in advance, -Jon Disnard Dan Nelson wrote: In the last episode (Jun 27), Andrey Nepomnyaschih said: Well playing with it nss_ldap in 5.1R. I have found that ls -la Will not show the names of the owner if the owner resides in LDAP Directory only the corresponding uidNumbers. Is there a way to show the usernames instead of uidNumbers? Make sure ls is dynamically-linked. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [current] hostap+wi
Ruslan Ermilov wrote: On Sat, Jul 05, 2003 at 04:48:09PM -0400, David Gilbert wrote: [...] The hostap machine is 4.8-STABLE and the client is 5.1-RELEASE. One nice thing about the hostap is that bridge(4) works with wi(4) that is in hostap mode. Does anybody know if only Intersil cards have the hostap mode, or some Prism's also do? Well yeah. Considering Intersil makes the Prism brand of 802.11 chips. =) I'm not aware of any other chips that allow for this groovy hostap mode unless the formerly unsupported atheros chips do. I figure the idea is not unique, and the feature seems logical for vendors to build their AP's based on common hardware. -Jon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bug filing broken?
You might try to investigate the issue first. Try "http://www.dnsreport.com";, and see if any red flags appear in the MX record section, or in another area that might affect mail. Its a common technique to reject mail from domains that do not follow the RFC specs. Also, you might try to send word about this to the postmaster of freebsd.org. Best, -Jon Andrew P. Lentvorski, Jr. wrote: I tried to file a bug for one of my -CURRENT machines using send-pr and got the following result back: - The following addresses had permanent fatal errors - <[EMAIL PROTECTED]> (reason: 450 : Helo command rejected: Host not found) Presumably this means that the mailer is trying to reverse lookup my hostname, and it doesn't exist. That's true, as I have been experimenting with this stuff behind my firewall on my private net. Fine. I'll file a bug via the web interface. Go to: http://www.freebsd.org/send-pr.html The web-based bug interface is currently disabled. This is annoying. A user is already peeved that FreeBSD has a bug, and now the bug sending mechanism has a bug. In addition, the web bug submission is offline. The send to [EMAIL PROTECTED] should not have failed in the first place. Even if [EMAIL PROTECTED] needs spam protection, all of the emails coming into it have a signature which makes spam analysis incredibly easy. Please reopen FreeBSD-gnats-submit so that it accepts all input and rejects based upon content. Another idea is to rewrite send-pr so that it submits bug reports directly to a port on a server somewhere. Using port 80 and a dedicated receive server would get around firewalling issues. The alternative is to reopen the web form. However, I find send-pr much more useful (less cutting and pasting). Submitting a bug report should be the easiest, most robust and error free task the system carries out. Thanks, -a ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: (forw) proc-args (M_PARGS) leakage
> From: Peter Jeremy <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: proc-args (M_PARGS) leakage
> Date: Mon, 17 Jun 2002 13:15:03 +1000
> Message-id: <[EMAIL PROTECTED]>
> User-Agent: Mutt/1.2.5.1i
> Sender: [EMAIL PROTECTED]
>
> This is -CURRENT from 7th May so it's possible the bug has been
> fixed, though there's nothing obvious in either the CVS commit
> logs or by diffing the relevant files.
>
> Having noticed that my system is paging far more than I would have
> expected, I went looking and found that the 'proc-args' pool was
> far larger than I expected. And is growing over time:
>
> gsmx07# vmstat -m|grep proc-args
> proc-args701802 70634K 70634K 1589264 16,32,64,128,256
> [about 10 minutes delay]
> gsmx07# vmstat -m|grep proc-args;vmstat -m|grep proc-args
> proc-args702048 70652K 70652K 1589557 16,32,64,128,256
> proc-args702047 70652K 70652K 1589558 16,32,64,128,256
> gsmx07#
>
> Unfortunately, M_PARGS is not the easiest pool to track allocations
> and de-allocations. Having gone through the references to pargs_*()
> and p_args, I can't see any obvious cause of this.
This is definately failure to drop a reference.
> Whilst I'm fairly certain it's not my problem, sysctl_kern_proc_args()
> (1.136) looks dubious:
[ ... ]
> (And later code shows pa dead at this point). I don't follow this.
> pargs_drop(pa) deletes a single reference count - which matches the
> line "p->p_args = NULL;" - but I don't see anything to match the
> pargs_hold(pa) above.
You are correct, One reference too few is dropped when a proc's pargs
is changed. This would mean that every call to setproctitle(3) would
cause a leak.
Please let me know if this fixes your problem:
Index: kern_proc.c
===
RCS file: /home/ncvs/src/sys/kern/kern_proc.c,v
retrieving revision 1.136
diff -u -r1.136 kern_proc.c
--- kern_proc.c 7 Jun 2002 05:41:27 - 1.136
+++ kern_proc.c 21 Jun 2002 08:04:17 -
@@ -1024,10 +1024,9 @@
if (req->oldptr && pa != NULL) {
error = SYSCTL_OUT(req, pa->ar_args, pa->ar_length);
}
- if (req->newptr == NULL) {
- pargs_drop(pa);
+ pargs_drop(pa);
+ if (req->newptr == NULL)
return (error);
- }
PROC_LOCK(p);
pa = p->p_args;
> Additionally, whilst I'm certain it's not my problem,
> fill_kinfo_proc() copys a reference to pargs, but doesn't increment
> the reference counter (using pargs_hold()).
You are correct; this is intentional. The kinfo stuff is terribly broken
currently. Many fields, pargs being one of them, are broken. A kinfo
struct is passed to userland, so it can't hold any references to kernel
objects. Really, kinfo should contain a copy of the string, not a pargs
pointer.
--
Jonathan Mini <[EMAIL PROTECTED]>
http://www.freebsd.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Toshiba 1901-S301 and problems installing 5.0 dp2
On Wed, Nov 27, 2002 at 11:35:02PM -0500, Jason wrote: > I ama trying to install 5.0 dp2 (tried other boot disks as well, including > 4.7) on my new toshiba laptop. Each and every time it locks up at the > following 2 lines (it boots normally up to this point) > > pci0: at device 31.5 (no driver attached> > pci0: at device 31.6 (no driver attached) > > then nothing, it just sits there, 3 finger salute does not work. I have no > way to disable anything in the bios unfortunately. I had a similar problem with my Toshiba laptop (3005-S304). While I'm not currently running FreeBSD on it, I was able to get an install booted by building a custom kernel _without_ SCSI support. That was based on a suggestion I received from someone on the -mobile mailing list, but I don't recall who it was (sorry). Anyway, that got a -stable (around 4.5 or 4.6) installation started, and I was seeing the same problem as you, so hopefully that will help. -- Jon Parise ([EMAIL PROTECTED]) :: http://www.csh.rit.edu/~jon/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CPUTYPE=p4 warning needed
I didn't see any warnings in /usr/share/examples/etc/make.conf, so I thought I'd share my experience with CPUTYPE=p4. Building world with CPUTYPE=p4 results in static when playing back mpeg audio. All other audio works fine. A few cases where this is present (to show it is not application specific): 1) playing an mp3 with mpg123 2) playing an mp3 with xmms 3) playing a movie with mpeg audio in mplayer A symptom of this problem in xmms is that the spectrum analyzer is almost constantly maxed out at most every frequency. Thus, it seems that in the decoding of the audio stream the amplitude of the signal is outputed too high, resulting in some form of clipping. This clipping sounds like static. This is ignorant speculation, but maybe it will help. This problem is present when these applications are installed via packages or compiled from ports. In any case, I think it would be a good idea to include a warning in /usr/share/examples/etc/make.conf that says CPUTYPE optimizations may result in broken code. Maybe it's just my machine, but I've recompiled several times now and it's consistent (if and only if I build and install world with CPUTYPE=p4 is the problem evident). Jon Noack dmesg: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sat Dec 14 20:48:25 CST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/COMPGEEK Preloaded elf kernel "/boot/kernel/kernel" at 0xc04ff000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04ff0a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 2539102024 Hz CPU: Pentium 4 (2539.10-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febfbff real memory = 536805376 (511 MB) avail memory = 516071424 (492 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 Using $PIR table, 15 entries at 0xc00f7450 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe800-0xebff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) uhci0: port 0xdc00-0xdc1f irq 10 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Microsoft Microsoft Wheel Mouse Optical\M-., rev 1.10/1.21, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. uhub1: Philips Semiconductors hub, class 9/0, rev 1.10/1.10, addr 3 uhub1: 3 ports with 3 removable, self powered uhci1: port 0xd800-0xd81f irq 9 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci2: port 0xd400-0xd41f irq 9 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 pcib3: at device 2.0 on pci2 pci3: on pcib3 asr0: mem 0xe200-0xe3ff irq 11 at device 2.1 on pci2 asr0: major=154 asr0: ADAPTEC 2100S FW Rev. 370F, 1 channel, 256 CCBs, Protocol I2O rl0: port 0xbc00-0xbcff mem 0xefeeff00-0xefee irq 12 at device 9.0 on pci2 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:20:ed:40:16:0c miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0xb800-0xb83f irq 11 at device 10.0 on pci2 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xff00-0xff0f,0-0x3,0-0x7,0-0x3,0-0x7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 31.3 (no driver attached) acpi_button1: on acpi0 fdc0: cmd 3 failed at out byte 1 of 3 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: cmd 3 failed at out byte 1 of 3 orm0: at iomem 0xcc000-0xd1fff,0xc-0xcbfff on isa0 pmtimer0 on isa0 fdc0: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec acpi_cpu: CPU throttl
Pre-filled RAM disk.
Wotcha! I work for Arm for my sins, and in my spare time I’ve been playing with FreeBSD. In my day job I work with the CPU core validation team, and one of the things we do is take the hardware design of a new core and run it on a machine called an emulator. This emulator isn’t the same thing as QEMU, nor is it just an FPGA, it’s something in the middle - you compile the hardware design and download it to the emulator, and it can then run programs on your design at about 1MHz. Which is lovely. Our main bread and butter is to take such a design and get it to boot Arm Linux, a very cut down version, and then run some tests hosted in the Linux environment. These tests would typically thrash the snot out of some particular aspect of the architecture, such as memory sharing amongst multiple processor cores. Now, we would like to use other operating systems that behave differently to Linux, there are some obvious candidates that I’m not going to talk about for legal reasons, but one that was suggested was using FreeBSD under emulation. So, what is needed is someway of telling the operating system that it is going to use a ram disk for its root filesystem, and that the ram disk is going to be at a fixed physical address in the memory map. That way we can pre-load root from a file in the emulation environment. In the Linux environment we would package the kernel, it’s DRB and the root filesystem memory image inside a light-weight bootloader wrapper, load that at the right offset into the emulator’s memory map, and twang the virtual reset line of the emulated processor. There’s some magic jiggery pokery to get console output from what the OS thinks is an AMBA UART, but that’s about size of it. So, what does FreeBSD have to offer in the way of ramdisk functionality? Jon. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pre-filled RAM disk.
On Sep 20, 2017, at 10:35 PM, Ian Lepore wrote: > > On Wed, 2017-09-20 at 21:23 -0600, Warner Losh wrote: >> On Wed, Sep 20, 2017 at 9:16 PM, Warner Losh wrote: >> >>> On Wed, Sep 20, 2017 at 8:50 PM, Jon Brawn wrote: >>> >>>> >>>> Wotcha! >>>> >>>> >>>> So, what does FreeBSD have to offer in the way of ramdisk >>>> functionality? >>>> >>> Yes. >>> >>> See MD_ROOT and friends. >>> >> The MFS_IMAGE kernel option has replaced this. >> >> Warner > > And the documentation (such as it is) for MFS_IMAGE is in the md(4) > manpage. In a nutshell, it's a mechanism that lets you compile an > existing filesystem image directly into the kernel and it is mounted as > a memory filesystem at boot time. Hopefully being contained within the > kernel will make the problem of loading it at a fixed physical address > go away for you. > > -- Ian > I really need to bring more of my work problems to this list, obviously. Thanks folks! Jon. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: GNU LICENSING
Hi I was wondering how to apply to the gnu licensing and how to sign and commit to the licensing laws.. Would you mind telling me how to assign to one please?? And one other thing in the license of most gnu licensing they go on to mention the 'AS IS' commitment but I don't fully understand, as well could you give me five minutes of you busy time to explain please?? My regards MR jon ruse I do donate to the fsf donation station if that is anything meaning?? Sent from my iPhone > On 12 Sep 2014, at 23:46, "freebsd-current-requ...@freebsd.org" > wrote: > > Send freebsd-current mailing list submissions to >freebsd-current@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit >http://lists.freebsd.org/mailman/listinfo/freebsd-current > or, via email, send a message with subject or body 'help' to >freebsd-current-requ...@freebsd.org > > You can reach the person managing the list at >freebsd-current-ow...@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-current digest..." > Today's Topics: > > 1. Re: CDC-WDM driver (4G modems) (PseudoCylon) > 2. Re: panic: resource_list_alloc: resource entry is busy > (Marcin Cieslak) > 3. Re: panic: resource_list_alloc: resource entry is busy > (John Baldwin) > 4. Re: panic: resource_list_alloc: resource entry is busy > (Marcin Cieslak) > 5. shells/bash port, add a knob which symlinks to /bin/bash ? > (Craig Rodrigues) > 6. Re: shells/bash port, add a knob which symlinks to /bin/bash > ? (Bryan Drewery) > 7. Re: shells/bash port, add a knob which symlinks to /bin/bash > ? (Baptiste Daroussin) > 8. RE: shells/bash port, add a knob which symlinks to /bin/bash > ? (Rang, Anton) > 9. RE: shells/bash port, add a knob which symlinks to /bin/bash > ? (Benjamin Kaduk) > 10. Re: panic: resource_list_alloc: resource entry is busy > (John Baldwin) > 11. Re: shells/bash port, add a knob which symlinks to /bin/bash > ? (Alfred Perlstein) > 12. Re: panic: resource_list_alloc: resource entry is busy > (Marcin Cieslak) > 13. Re: shells/bash port, add a knob which symlinks to /bin/bash > ? (Garrett Cooper) > 14. RE: shells/bash port, add a knob which symlinks to /bin/bash > ? (Daniel Eischen) > 15. Re: shells/bash port, add a knob which symlinks to /bin/bash > ? (Lyndon Nerenberg) > 16. Re: shells/bash port, add a knob which symlinks to /bin/bash > ? (Craig Rodrigues) > 17. Re: shells/bash port, add a knob which symlinks to /bin/bash > ? (Subbsd) > 18. Re: shells/bash port, add a knob which symlinks to /bin/bash > ? (Brooks Davis) > > > > > > > > > > > > > > > > > > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Programmatically cache line
> On Jan 4, 2018, at 4:03 AM, David Chisnall wrote: > > On 3 Jan 2018, at 22:12, Nathan Whitehorn wrote: >> >> On 01/03/18 13:37, Ed Schouten wrote: >>> 2018-01-01 11:36 GMT+01:00 Konstantin Belousov : >>>>>>> On x86, the CPUID instruction leaf 0x1 returns the information in >>>>>>> %ebx register. >>>>>> Hm, weird. Why don't we extend sysctl to include this info? >>>> For the same reason we do not provide a sysctl to add two integers. >>> I strongly agree with Kostik on this one. Why add stuff to the kernel, >>> if userspace is already capable of extracting this? Adding that stuff >>> to sysctl has the downside that it will effectively introduce yet >>> another FreeBSDism, whereas something generic already exists. >>> >> >> Well, kind of. The userspace version is platform-dependent and not always >> available: for example, on PPC, you can't do this from userland and we >> provide a sysctl machdep.cacheline_size to userland. It would be nice to >> have an MI API. > > On ARMv8, similarly, sometimes the kernel needs to advertise the wrong size. > A few big.LITTLE cores have 64-byte cache lines on one cluster and 32-byte on > the other. If you query the size from userspace while running on a 64-byte > cluster, then issue the zero-cache-line instruction while migrated to the > 32-byte cluster, you only clear half the size. Linux works around this by > trapping and emulating the instruction to query the cache size and always > reporting the size for the smallest cache lines. ARM tells people not to > build systems like this, but it doesn’t always stop them. Trapping and > emulating is much slower than just providing the information in a shared > page, elf aux args vector, or even (often) a system call. > > To give another example, Linux provides a very cheap way for a userspace > process to enquire which core it’s running on. Some more recent > high-performance mallocs use this to have a second-layer per-core cache after > the per-thread cache for free blocks. Unlike the per-thread cache, the > per-core cache does need a lock, but it’s very unlikely to be contended (it > will only be contended if either a thread is migrated in between checking and > locking, so acquires the wrong CPU’s lock, or if a thread is preempted in the > middle of middle of the very brief fill operation). The author of the > SuperMalloc paper tried doing this with CPUID and found that it was slower by > a sufficient margin to almost entirely offset the benefits of the extra layer > of caching. > > Just because userspace can get at the information directly from the hardware > doesn’t mean that this is the most efficient or best way for userspace to get > at it. > > Oh, and some of these things are useful in portable code, so having to write > some assembly for every target to get information that the kernel already > knows is wasteful. > > David This idea of Arm big.LITTLE systems having cache lines of different lengths really, really bothers me - how on earth is the cache coherency supposed to work in such a system? I doubt the usual cache coherency protocols would work - probably need a really MESSY protocol to deal with this config :-) Jon. smime.p7s Description: S/MIME cryptographic signature
Re: Intel CPU design flaw - FreeBSD affected? Information from Arm
Wotcha! My employer, Arm, have made the following website available to help with deciding what to do about this security issue. http://www.arm.com/security-update <http://www.arm.com/security-update> Note: I am not writing here as a representative of Arm, and cannot provide further information about this issue. I would encourage you to read all the pages and the white paper thoroughly to best understand this issue as it relates to working with Arm processors. Jon. smime.p7s Description: S/MIME cryptographic signature
Re: USB stack
19e3 at VOP_CREATE_APV+0xd3 > Jan 7 12:06:15 blubee kernel: #8 0x80b4a53d at vn_open_cred+0x2ad > Jan 7 12:06:15 blubee kernel: #9 0x80b42e92 at kern_openat+0x212 > Jan 7 12:06:15 blubee kernel: #10 0x80f16d2b at amd64_syscall+0x79b > Jan 7 12:06:15 blubee kernel: #11 0x80ef5b7b at Xfast_syscall+0xfb > > > Is the slow transfers user error? Wotcha! I don’t see any read or write performance figures anywhere? Also, is this CURRENT? If so, aren’t all the debug / warning features that are turned on by default in CURRENT at the moment going to have an effect on throughput? Especially if you’re writing through a filesystem where directory and file accesses will each require a lock to be taken, if only for a short while? If you want to get closer to the true USB speed of the device, stop mounting it and copying files to the filesystem, but instead just dd data onto and off of the device directly, and measure how fast that goes. Remember to backup your data from the card first… Jon. smime.p7s Description: S/MIME cryptographic signature
Re: USB stack
> On Jan 7, 2018, at 5:44 PM, Jon Brawn wrote: > > >> On Jan 6, 2018, at 10:18 PM, blubee blubeeme wrote: >> >> On Sun, Jan 7, 2018 at 12:11 PM, Warner Losh wrote: >> >>> >>> >>> On Sat, Jan 6, 2018 at 8:56 PM, blubee blubeeme >>> wrote: >>> >>>> I ask does FreeBSD usb stack actually implements USB spec 2.0 or greater >>>> and the topic gets derailed...? >>>> >>> >>> Yes, it does. >>> >>> >>>> Are you guys saying that 7-8MB/s is USB speeds? >>>> >>> >>> I've gotten up to 24MB/s for maybe a decade. That's not possible with USB >>> 1.x. More recently, I've maxed out the writes on a USB stick at about >>> 75MB/s (the fastest it will do), which isn't possible with USB 2.0... I've >>> not tried USB3 with an SSD that can do more >>> >>> Warner >>> >>> >>>> On Thu, Jan 4, 2018 at 6:44 PM, O'Connor, Daniel >>>> wrote: >>>> >>>>> >>>>> >>>>>> On 4 Jan 2018, at 09:23, Gary Jennejohn wrote: >>>>>>> What is an "LG v30"? >>>>>>> >>>>>> It's a smartphone from LG and only supports USB2 speed. The reported >>>>>> transfer rate is no big surprise. >>>>> >>>>> OK thanks. >>>>> >>>>> -- >>>>> Daniel O'Connor >>>>> "The nice thing about standards is that there >>>>> are so many of them to choose from." >>>>> -- Andrew Tanenbaum >>>>> GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C >>>>> >>>>> >>>> ___ >>>> freebsd-current@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org >>>> " >>>> >>> >>> I just connected a Transcend StorageJet 1TB hdd not a mobile phone >> --- >> Jan 7 11:56:56 blubee kernel: umass0 on uhub0 >> Jan 7 11:56:56 blubee kernel: umass0: > Transcend, class 0/0, rev 3.00/80.00, addr 4> on usbus0 >> Jan 7 11:56:56 blubee kernel: umass0: SCSI over Bulk-Only; quirks = 0x0100 >> Jan 7 11:56:56 blubee kernel: umass0:3:0: Attached to scbus3 >> Jan 7 11:56:56 blubee kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 >> Jan 7 11:56:56 blubee kernel: da0: Fixed Direct >> Access SPC-4 SCSI device >> Jan 7 11:56:56 blubee kernel: da0: Serial Number W9328YZN >> Jan 7 11:56:56 blubee kernel: da0: 400.000MB/s transfers >> Jan 7 11:56:56 blubee kernel: da0: 953869MB (1953525168 512 byte sectors) >> Jan 7 11:56:56 blubee kernel: da0: quirks=0x2 >> Jan 7 12:06:08 blubee kernel: lock order reversal: >> Jan 7 12:06:08 blubee kernel: 1st 0xfe07c26336c0 bufwait (bufwait) @ >> /usr/src/sys/vm/vm_pager.c:374 >> Jan 7 12:06:08 blubee kernel: 2nd 0xf80148c425f0 zfs (zfs) @ >> /usr/src/sys/dev/md/md.c:952 >> Jan 7 12:06:08 blubee kernel: stack backtrace: >> Jan 7 12:06:08 blubee kernel: #0 0x80acfa03 at >> witness_debugger+0x73 >> Jan 7 12:06:08 blubee kernel: #1 0x80acf882 at >> witness_checkorder+0xe02 >> Jan 7 12:06:08 blubee kernel: #2 0x80a41b8e at >> lockmgr_lock_fast_path+0x1ae >> Jan 7 12:06:08 blubee kernel: #3 0x81094309 at VOP_LOCK1_APV+0xd9 >> Jan 7 12:06:08 blubee kernel: #4 0x80b4ac36 at _vn_lock+0x66 >> Jan 7 12:06:08 blubee kernel: #5 0x80611d32 at mdstart_vnode+0x442 >> Jan 7 12:06:08 blubee kernel: #6 0x806102ce at md_kthread+0x1fe >> Jan 7 12:06:08 blubee kernel: #7 0x80a2d654 at fork_exit+0x84 >> Jan 7 12:06:08 blubee kernel: #8 0x80ef5e0e at fork_trampoline+0xe >> Jan 7 12:06:15 blubee kernel: lock order reversal: >> Jan 7 12:06:15 blubee kernel: 1st 0xfe07c41d5dc0 bufwait (bufwait) @ >> /usr/src/sys/kern/vfs_bio.c:3562 >> Jan 7 12:06:15 blubee kernel: 2nd 0xf8002bb31a00 dirhash (dirhash) @ >> /usr/src/sys/ufs/ufs/ufs_dirhash.c:281 >> Jan 7 12:06:15 blubee kernel: stack backtrace: >> Jan 7 12:06:15 blubee kernel: #0 0x80acfa03 at >> witness_debugger+0x73 >> Jan 7 12:06:15 blubee kernel: #1 0x80acf882 at >> witness_checkorder+
INTRNG
Wotcha Gang! In my travels through the arm64 GENERIC config file I came across the option ‘INTRNG’, and wondered what it was: INTeRrupt Next Generation? INTeger Random Number Generator? IN TRaiNinG? INTerrupt Random Number Generator? INdependent TRaiNinG? So, please put me out of my misery, what does INTRNG stand for, and what are its implications when selected vs not selected? Cheers! Jon. smime.p7s Description: S/MIME cryptographic signature
lock order reversal
Wotcha! So, I’ve been using FreeBSD 12-CURRENT at various svn releases for a while now, and I get quite a few “lock order reversal” dumps. The one I’ve got on my screen at the moment is for ufs / bufwait / ufs: root@brax:/usr/src/stand # lock order reversal: 1st 0xfd0003ec17e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2602 2nd 0x410efa20 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:282 3rd 0xfd00b83ca7e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2602 stack backtrace: #0 0x003b59d4 at witness_debugger+0x64 #1 0x0032bd34 at __lockmgr_args+0x6ac #2 0x005c6af0 at ffs_lock+0x88 #3 0x00679eb0 at VOP_LOCK1_APV+0xac #4 0x00426fa8 at _vn_lock+0x64 #5 0x00417550 at vget+0x78 #6 0x00409fdc at vfs_hash_get+0xec #7 0x005c2b94 at ffs_vgetf+0x44 #8 0x005b96a8 at softdep_sync_buf+0x9f4 #9 0x005c7834 at ffs_syncvnode+0x26c #10 0x005a1b5c at ffs_truncate+0x6b0 #11 0x005ce3cc at ufs_direnter+0x778 #12 0x005d64bc at ufs_makeinode+0x4b8 #13 0x005d2b90 at ufs_create+0x38 #14 0x00677168 at VOP_CREATE_APV+0xac #15 0x0042691c at vn_open_cred+0x264 #16 0x0041fc84 at kern_openat+0x208 #17 0x0064b59c at do_el0_sync+0x8bc Is there something I should be doing to help debug these? Jon. smime.p7s Description: S/MIME cryptographic signature
