Subscribe
Please add me to this list Chuck To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The Matrix screensaver, v.0.2
On Sun, 22 Aug 1999, Ollivier Robert wrote: According to Narvi: "Falling letters like in the movie with red bills" Pill :) That very important... The screensaver triggered me to see the movie again. A. I love it. Yeah, it's gotta be the perfect hacker's movie. Maybe we *should* go approach the producers? I have gone to that movie several times, and I keep on enjoying it, so this is GOOD PR for them. +--- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On Sun, 22 Aug 1999, Rodney W. Grimes wrote: On Sun, 22 Aug 1999, Ollivier Robert wrote: According to Narvi: "Falling letters like in the movie with red bills" Pill :) That very important... The screensaver triggered me to see the movie again. A. I love it. Yeah, it's gotta be the perfect hacker's movie. Maybe we *should* go approach the producers? I have gone to that movie several times, and I keep on enjoying it, so this is GOOD PR for them. Good idea, the approach for approval to distrubute this presented to the marketing department has a strong leverage on the legal department, in that they can't just take the easy road of saying ``no'' when the marketing department is going ``yes, yes.. this would be good for revenue''. OK, then, I'll do it "with unofficial but general approval of many FreeBSDers" (which is what I'll tell the folks). Too bad I don't live in LA anymore, I used to know the right folks to go to. +--- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
bootparamd changed for use with inetd
Hi,
I've dug through the archives and found no mention of this subject. Are there any
political/technical reasons why bootparamd was not set up to work with inetd? If the
answer is no, I've included a patch for /usr/src/usr.sbin/bootparamd/bootparamd/main.c
that allows it to work this way. I was also wondering if it would be more correct to
put
it in libexec under the name rpc.bootparamd if this patch were accepted?
This does not break the ability to run it standalone.
here is an example inetd.conf line I use:
bootparamd/1 dgram rpc/udp wait root /usr/libexec/rpc.bootparamd rpc.bootparamd
and under current naming sceme it would be:
bootparamd/1 dgram rpc/udp wait root /usr/sbin/bootparamd bootparamd
It accually boots my sparc10 just fine. In fact I can boot the sparc over 10T from my
FBSD
box faster than it boots from local disk :-) -- any theories on why?
---
Chuck Gagnon ([EMAIL PROTECTED])
--- cut here -- cut here -- cut here ---
begin 644 patch-aa
M+2TM(UA:6XN8RYOFEG"49R:2!*=6X@,3(@,#DZ,S@Z-3D@,3DY.`HK*RL@
M;6%I;BYC"51U92!!=6@(#,@,#`Z,#@Z,CD@,3DY.0I`0"`M,C8L,3`@*S(V
M+#$V($!`"B`C:6YC;'5D92`\WES+W-O8VME="YH/@H@(VEN8VQU94@/'-Y
MR]S=%T+F@^"B`C:6YC;'5D92`\WES+W1Y5S+F@^"BLC:6YC;'5D92`\
MWES+W=A:70N:#X*("-I;F-L=61E(#QN971I;F5T+VEN+F@^"B`C:6YC;'5D
M92`\87)P82]I;F5T+F@^"B`C:6YC;'5D92`B8F]O='!AF%M7W!R;W0N:"(*
M(`HK:6YT(9R;VU?:6YE=0@/2`Q.R`@("`@+RH@W1AG1E9"!FF]M(EN
M971D(#\@*B\**VEN="!C;]S961O=VX@/2`R,#L@("`@("\J(AO=R!L;VYG
M('1O('=A:70@8F5F;W)E(=O:6YG(1OFUA;G0@*B\**VEN="!S:6YC96QA
MW1R97$@/2`P.PHK:6YT('-T871?:7-?:6YI="`](#$["BL*(EN="!D96)U
M9R`](#`["B!I;G0@9]L;V@/2`P.PH@=6YS:6=N960@;]N9R!R;W5T95]A
M91R(#T@+3$["D!`("TS."PX,B`K-#0L,3Y($!`"B`*(5X=5R;B`@=F]I
M9"!B;V]T%R86UPF]G7S$H*3L*('-T871I8R!V;VED('5S86=E(%]?4"@H
M=F]I9"DI.PHK=F]I9"!C;5A;G5P*"D["BMV;VED('5P9%T97-T870H*3L*
M(`H@:6YT"B!M86EN*%R9V,L(%R9W8I"B!I;G0@87)G8SL*(-H87(@*BIA
MF=V.PH@PHM"5-60UA04E0@*G1R86YS#L*+0EI;G0@:3L*+0ES=')U8W0@
M:]S=5N="`J:4["BT)W1R=6-T('[EMAIL PROTECTED]"6-H87(@8SL*+0HM
M"7=H:6QE("@H8R`](=E=]P="AAF=C+"!AF=V+")DW(Z9CHB*2D@(3T@
M+3$I"BT)("!S=VET8V@@*,I('L*+0D@(-AV4@)V0G.@HM"2`@("!D96)U
M9R`](#$["BT)("`@()R96%K.PHM"2`@8V%S92`GBZ"BT)("`@("`@:68@
M*"!IV1I9VET*"`J;W!T87)G*2D@PHM"0ER;W5T95]A91R(#T@:6YE=%]A
M91R*]P=%R9RD["BT)"6)R96%K.PHM"2`@("`@('T@96QS92!["BT)"6AE
M(#T@9V5T:]S=)Y;F%M92AO'1AFI.PHM"0EI9B`H:4I('L*+0D)("`@
M8F-O'DH:4M/FA?861DBP@*-H87(@*BDFF]U=5?861DBP@VEZ96]F
M*')O=71E7V%D9'(I*3L*+0D)("`@8G)E86L["BT)"7T@96QS92!["BT)"2`@
M(5RG@H,2P@(FYO('-U8V@@:]S="`ER(L(%R9W9;:5TI.PHM"0E]"BT)
M("`@("`@?0HM"2`@8V%S92`G9BZ"BT)("`@()O;W1P9FEL92`](]P=%R
M9SL*+0D@("`@8G)E86L["BT)("!C87-E("=S)SH*+0D@("`@9]L;V@/2`Q
M.PHK("!35D-84%)4("ITF%NW`["BL@(EN="!I+"!S.PHK("!S=')U8W0@
M:]S=5N="`J:4["BL@('-TG5C="!S=%T()U9CL**R`@8VAAB!C.PHK
M("!I;G0@V]C:R`](#`["BL@(EN="!PF]T;R`](#`["BL@('-TG5C="!S
M;V-K861DE]I;B!FF]M.PHK("!I;G0@9G)O;6QE;CL**PHK("!I9B`H87)G
M8R`]/2`R*0HK("`@(-L;W-E9]W;B`](%T;VDH87)G=ELQ72D["BL@(EF
M("AC;]S961O=VX@/#T@,"D**R`@("!C;]S961O=VX@/2`R,#L**PHK("!W
M:EL92`H*,@/2!G971O'0H87)G8RP@87)G=BPB9'-R.F8Z(BDI("$]("TQ
M*0HK("`@('-W:71C:"`H8RD@PHK("`@(-AV4@)V0G.@HK("`@("`@95B
M=6@/2`Q.PHK("`@("`@8G)E86L["BL@("`@8V%S92`GBZ"BL@("`@("!I
M9B`H(ES9EG:70H("IO'1AFI*2!["BL@("`@("`@(')O=71E7V%D9'(@
M/2!I;F5T7V%D9'(H;W!T87)G*3L**R`@"6)R96%K.PHK("`@("`@?2!E;'-E
M('L**R`@"6AE(#T@9V5T:]S=)Y;F%M92AO'1AFI.PHK("`):68@*AE
M*2!["BL@(`D@("!B8V]P2AH92T^:%]A91R+"`H8VAAB`J*29R;W5T95]A
M91R+"!S:7IE;V8HF]U=5?861DBDI.PHK("`)("`@8G)E86L["BL@(`E]
M(5LV4@PHK("`)("`@97)R"@Q+"`B;F\@W5C:"!H;W-T("5S(BP@87)G
M=EMI72D["BL@(`E]"BL@("`@("!]"BL@("`@8V%S92`G9BZ"BL@("`@("!B
M;V]T9I;4@/2!O'1AF["BL@("`@("!BF5A:SL**R`@("!C87-E("=S
M)SH**R`@("`@(1O;]G(#T@,3L**R`@("`@()R96%K.PHK("`@(1E9F%U
M;'0Z"BL@("`@("!U[EMAIL PROTECTED]("`@('T**PHK("!I9B`H('-T870H8F]O
M='!F:6QE+"`F8G5F("D@*0HK("`@(5RB@Q+"`B)7,B+"!B;V]T9I;4I
M.PHK"BL@("\J"BL@("H@4V5E(EF(EN971D('-T87)T960@=7,**R`@*B\*
M*R`@9G)O;6QE;B`]('-IF5O9BAFF]M*3L**R`@:68@*=E='-O8VMN86UE
M*#`L("AS=')U8W0@V]C:V%D9'(@*BDF9G)O;2P@)F9R;VUL96XI(#P@,"D@
MPHK("`@(9R;VU?:6YE=0@/2`P.PHK("`@('-O8VL@/2!24$-?04Y94T]#
M2SL**R`@("!PF]T;R`]($E04%)/5$]?5410.PHK("!]"BL**R`@:
Re: PNP ids missing in sio.c
On Sat, 4 Sep 1999, Doug Rabson wrote: On Fri, 3 Sep 1999, Steve Price wrote: Can anyone think of a good reason why I can't migrate the old PNP ids to the new sio.c? I just rebooted my box with a fresh kernel and much to my shagrin (sp?) my USR PNP modem didn't work anymore. The following patch got it working again. The reason I didn't move the old ids wholesale is that the old system matched against the vendor id (which is bogus for multifunction cards). The new system matches with the logical device id which is often different from the vendor id. Some simple single function cards use the same id for both (as yours does) but I can't tell this without seeing the pnpinfo output. Now that we can't use the pnp command from 'boot -c', what has (if anything) replaced it? I seem to be remember this being discussed recently but I'll be darned if I can find it in the mailing list archives. The pnp command should no longer be needed (crossed fingers) since the new code automatically detects devices and assigns resources to them. Does the sio driver know about PCI? Can it run PCI sio cards, like those sold by SIIG? -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd.Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message ---+--- Chuck Robey| Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770| picnic.mat.net: FreeBSD/i386 (301) 220-2114 | jaunt.mat.net : FreeBSD/Alpha ---+--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ports/13729: strip(1) exits with an error on script file - causessevere portability problems
On Mon, 13 Sep 1999 [EMAIL PROTECTED] wrote: This kind of thing, where there is no bug ... where the subject is a request for a new feature, isn't this kind of thing the wrong way for folks to be using the trouble reporting system? Or is this the way we want it to happen? It seems to me that allowing such use of gnats makes it miserably hard for folks to close some PRs. Number: 13729 Category: ports Synopsis: strip(1) exits with an error on script file - causes severe portability problems Confidential: no Severity: serious Priority: medium Responsible:freebsd-ports State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Mon Sep 13 09:30:01 PDT 1999 Closed-Date: Last-Modified: Originator: Patrick Powell Release:3.2-Release, 4-Current Organization: Astart Technologies Environment: Description: strip(1) fails with an error when asked to strip shell scripts. This behavior is documented as follows: DESCRIPTION GNU strip discards all symbols from the object files objfile. The list of object files may include archives. At least one object file must be given. strip modifies the files named in its argument, rather than writing modified copies under different names. In many install scripts for code you have: $(INSTALL) -s ^^^ -s specified for ALL installable executable objects including perl scripts, shell, scripts, etc. This requires a huge amount of effort when porting to FreeBSD because you now have to determine which executables can or cannot be stripped. I strongly recommend you do a test in the strip code for ALLOWABLE magic numbers, strip those, and ignore the rest.I How-To-Repeat: strip a shell script - you get an error. More seri Fix: 1. modify man page to indicate that strip only works on object files or executable files, and ignores others 2. modify action so that it checks to see if it has an allowable item to strip and then does it. In the strip code, find the place where it checks for 'magic numbers' of allowable executables, and rather than exiting with a non-zero error code, simply exit with a 0 error code or continue to the next file to strip. Release-Note: Audit-Trail: Unformatted: To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-ports" in the body of the message ---+--- Chuck Robey| Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, Unix and 213 Lakeside Drive Apt T-1 | carpentry. It's all in the design! Greenbelt, MD 20770| picnic.mat.net: FreeBSD/i386 (301) 220-2114 | jaunt.mat.net : FreeBSD/Alpha ---+--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Loss of Functionality with newpnp
On Sun, 26 Sep 1999, Mike Smith wrote: This is only partially related, but I still can't even boot a kernel with the pnp0 controller enabled. It just hangs after probing the soundcard. You seem to have accidentally deleted all of the details related to this bug report from your email before sending it. Please try again. Mike, I'm checking into this on my own, so this isn't a question, but you might want to know that I have a Turtle Beach PCI audio card, setup with controller pnp0 and device pcm0, and getting about the same responses. Things have stopped working (the mixer totally). This is just data if you wanted it. I can see the answer isn't laying at your fingertips, so I will continue to read code. Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Linux emulation
I just tried to use my copy of WordPerfect 8 to decode an rtf document, like I've done before the signal change, and boy was I surprised. The machine locked up for 10 seconds, then spontaneously rebooted. Anyone else have this experience with Linux emulation? Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
COMMAND_SET ?
I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled, and I found something called a COMMAND_SET, and I can't figure out what it means. Any takers? Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The eventual fate of BLOCK devices.
On Tue, 12 Oct 1999, David Scheidt wrote: On Tue, 12 Oct 1999, Kirk McKusick wrote: I would like to take a step back from the debate for a moment and ask the bigger question: How many real-world applications actually use the block device interface? I know of none whatsoever. All the filesystem utilities go out of their way to avoid the block device and use the raw interface. Does anyone on this list know of any programs that need/want the block interface? If there are none, or It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated disk devices. There may be other RDBMSes that do this. Informix, should a miracle occur and they decide to suport FreeBSD, definitely want the same. Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The eventual fate of BLOCK devices.
On Tue, 12 Oct 1999, Warner Losh wrote: In message [EMAIL PROTECTED] David Scheidt writes: : It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated : disk devices. There may be other RDBMSes that do this. EVERY RDBMS that I've ever seen or had to make work with my drivers has been on the raw partition. This is because the database writers DO NOT LIKE OR TRUST the buffer cache due to its non-deterministic nature of disk writing. Are you sure that Sybase uses BLOCK devices and not CHAR devices? Gawd, now that I think of it, about my Informix post, you're right, they use a raw partition, and their own buffering. Warner Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: linux emulation broken..
On Thu, 14 Oct 1999, Kenneth Wayne Culver wrote: This is weird, I use linux netscape and word perfect all the time, and the only problems I see are memory leaks I knew were there (in the applications, not FreeBSD) I had equal problems a little while back. Make sure you have the linux_base port installed, it has a far more up to date set of libs. On Thu, 14 Oct 1999, Marc van Woerkom wrote: (im)perfect. I was using the linux version of netscape, until recently when it began hanging for long periods of time during network or disk activity. Calling up linux-netscape-4.61 causes my system to freeze for a couple of seconds, then it reboots. This is either related to some recent changes, or my system being not in a consistent state. Regards, Marc 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 ---- Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
On Sat, 23 Oct 1999, Matthew Dillon wrote: I found a copy of the C version of trek73 in my Amiga archives. This is the trek73 originally written in HP-2000 Basic that was rewritten by Dave Pare and Chris Williams in C and seriously enhanced by a bunch of people including me in my early college years circa 1985. I don't think any of the authors would mind if it went into /usr/games, but tracking them down is close to impossible since ucbvax no longer exists. If nobody knows different, I would like to clean it up (fairly easy since it's already in C) and commit it in. I've included the docs below. Remembering from ancient history, didn't this make the rounds to just about anyone who wanted to learn code? I think it was even in a DEC games book. I think putting this into games is safe, but there's another trek in games already ... I haven't played trek in a looong time, is this one better in some way than the one already there? If it doesn't get into /usr/games, anyhow, it can certainly go into ports. Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
lsof broken
It's broken trying to work with the name cache, and dies because it can't find the name NCACHE. Where is this guy? Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: linux emulation broken.. (solution)
On Mon, 25 Oct 1999, Chris Csanady wrote: I *know* someone else said it wasn't so, but just 3 weeks ago I had this very problem, with word perfect, and it works just fine now. Are you sure you have a really up to date linux_base port installed? It was recently changed, a *lot* of new libs added, and I'd really like an answer on this, whether I'm right or wrong. Well, I found a solution to my problems with running linux-netscape and word perfect. It looks like it was not the linux emulation code that was at fault. I recently installed a real redhat 6.1, and mounted it on /compat/linux. Now all is well--so I can only assume it is some weird interaction between the linux_base port and my system. Maybe it is related to using XFree86 3.9.15, but I don't have the time to test that theory right now. Certainly not a great solution, but if things are broke for you this at least works. No, like I said, when I *really* updated my Linux libs (and the linux_base port had very newly updated libs when I posted this) my problems evaporated, which is why I urged others to do it. I don't know why it didn't work for you, but at least it's done for you now. Chris Csanady Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CTM-deltas generation sptopped ?
On Thu, 4 Nov 1999, Peter Jeremy wrote: On 1999-Nov-03 23:58:00 +1100, [EMAIL PROTECTED] wrote: There are no new CTM-deltas on 'ctm.freebsd.org' at least 22 hours. The last e-mail delta I have is cvs-cur.5804, which arrived here at 0808UTC (about 5 hours before your message). I would have expected to receive 5805 (or at least an initial part) about 5 hours ago now, so I suspect something is wrong. I stopped reading the list for a few days (letting my mail pile up) while I handled a panic situation at the University, sorry. I can't traceroute or ping the source of ctm's, and I have mail out to the owner of the system. Now that I'm aware, I will follow this as fast as I can. Peter Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CTM-deltas generation sptopped ?
On Fri, 5 Nov 1999, Chuck Robey wrote: On Thu, 4 Nov 1999, Peter Jeremy wrote: On 1999-Nov-03 23:58:00 +1100, [EMAIL PROTECTED] wrote: There are no new CTM-deltas on 'ctm.freebsd.org' at least 22 hours. The last e-mail delta I have is cvs-cur.5804, which arrived here at 0808UTC (about 5 hours before your message). I would have expected to receive 5805 (or at least an initial part) about 5 hours ago now, so I suspect something is wrong. I stopped reading the list for a few days (letting my mail pile up) while I handled a panic situation at the University, sorry. I can't traceroute or ping the source of ctm's, and I have mail out to the owner of the system. Now that I'm aware, I will follow this as fast as I can. Replying to my own mail, I want to give an update: the machine that generates ctm has crashed, and the vinum volume doesn't fsck cleanly on startup. It's not a disaster, this can all be fixed, nothing critical *could* have been lost, because I've copies of everything critical right here. The likelihood, tho, is that it'll be a couple days at least until ctm comes back up, because I think I'm going to have to recreate it. Be patient, I'll announce when it gets back up. Oh, yeah, anoncvs is down too, same reasons, same response. Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
console problem
I've been on vacation for the last week, so I haven't been watching -current like a good boy should, but I've suddenly been seeing a serious problem, and it *might* not have been reported, and seeing as code freeze is almost here, it's worth risking a bit of embarrassment, I guess. Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. It seems to come on more quickly if I do something serious, like a buildkernel. Happened once on startup, but even though rc hadn't finished, I WAS able to ssh into the box and shut it down (indicating to me that rc had finished, just no response from the console). Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
On Sun, 1 Dec 2002, Manfred Antar wrote: Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. It seems to come on more quickly if I do something serious, like a buildkernel. Happened once on startup, but even though rc hadn't finished, I WAS able to ssh into the box and shut it down (indicating to me that rc had finished, just no response from the console). Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. I'm seeing the same here and the same on a serial console. Kernel from Friday 29 Nov. 8pm PST sources works So it happened sometime after that Manfred OK, did two full rebuilds,once using ssh, once using x. The one using ssh was fine, the one using X did hang the console, but the only way to notice that was because the PC speaker hangs while sounding off. I read the commitlogs, the only one that seemed at all connected with the console was this one (a weak link, admittedly): begin commit message imp 2002/11/29 16:49:43 PST Modified files: sys/kern subr_bus.c Log: devd kernel improvements: 1) Record all device events when devctl is enabled, rather than just when devd has devctl open. This is necessary to prevent races between when a device arrives, and when devd starts. 2) Add hw.bus.devctl_disable to disable devctl, this can also be set as a tunable. 3) Fix async support. Reset nonblocking and async_td in open. remove async flags. 4) Free all memory when devctl is disabled. Approved by: re (blanket) Revision ChangesPath 1.117 +38 -21src/sys/kern/subr_bus.c ===end commit message== I cc'ed Warner on this. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
On Mon, 2 Dec 2002, Vallo Kallaste wrote: Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. It seems to come on more quickly if I do something serious, like a buildkernel. Happened once on startup, but even though rc hadn't finished, I WAS able to ssh into the box and shut it down (indicating to me that rc had finished, just no response from the console). Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. It's interesting that you seem to have almost same machine as I have. Tyan Thunder with SCSI and ATA disks, SMP and the only difference seems to be memory size, 1GB vs. 512MB. Not counting network interfaces and such. I've also lost console after rebuild yesterday. The kernel from Nov. 29 works. Mine (console) not locks up but is simply missing from the start. Otherwise system is up and running. I don't think it's coincidence, something is broken and related to the Tyan mobos we have. Are you using the on-board video? I have an extra video card, and had to reflash the board because before reflash, I used to have this problem. It went away after reflash, and your references to the mobo reminded me. Tonight, I'll see if the video just goes back to the onboard card. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
On Mon, 2 Dec 2002, Manfred Antar wrote: Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. It seems to come on more quickly if I do something serious, like a buildkernel. Happened once on startup, but even though rc hadn't finished, I WAS able to ssh into the box and shut it down (indicating to me that rc had finished, just no response from the console). Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. It's interesting that you seem to have almost same machine as I have. Tyan Thunder with SCSI and ATA disks, SMP and the only I have the same problem here on an Intel PR440FX dual pentium-pro MB. Manfred It's not the fact that I have an extra, unused on-board video (checked). Also, when the video output stops, the console still works fine for input (keyboard never stops working normally). Also, I can successfully start X just fine. It's just the vty's output that is stopped (all vtys, alt-Fn has no effect on output, only input). It's not wiped, just no further changes. I tried issuing a vidcontrol; before lockup, color change works fine, after, no effect. It's acting as if the mapping in memory to the video buffer has changed. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0-DP2 boot failure on a 440GX motherboard
On Tue, 3 Dec 2002, Arun Sharma wrote: On Wed, Nov 20, 2002 at 05:35:53PM -0800, Arun Sharma wrote: On Wed, Nov 20, 2002 at 04:36:58PM -0800, Arun Sharma wrote: This is a dual Pentium III motherboard, with 2 x PIII at 850 MHz. 5.0-DP1 worked just fine on this machine. However, with DP2, I get a garbled console (Everything is ok till the Timecounter.. message). Sometimes the CD manages to boot and get into sysinstall, but hangs shortly thereafter. Even the sysinstall output is garbled. boot -v output captured from a serial console attached. I have debugged this some more. I'm able to boot, if I boot from serial console and am careful not to tickle the vga driver too much i.e. interact with the machine over the network or over the serial console. The moment I try to do anything on vga consoles, I get a hang. Is this a hard hang, or is the vga output frozen (and keyboard still works, X still works, ssh still works) like I've been reporting? Another observation: even when booting from the serial console, when the vga driver probes/attaches the hardware, I see garbage written on my vga console. I tested that 11/25 kernel also has this problem. The problem didn't happen with DP1. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: console problem
On Wed, 4 Dec 2002, Long, Scott wrote: This problem and the general 'console freeze' problem, and possibly even the 'floppy doesn't work anymore' problem should be fixed. The problem was with the ahc and ahd drivers corrupting the callout list used to trigger timeouts in the kernel. Pardon me for taking this long to answer, but the surest method of proving the fix was a sufficient torture test. It's quite finished now, and this is indeed a fix. I'm curious how you got to looking into the ahc driver for an ostensible syscons bug ... just perusing commit logs? Scott -Original Message- From: Holm Tiffe [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 7:27 AM To: [EMAIL PROTECTED] Subject: Re: console problem Chuck Robey wrote: I've been on vacation for the last week, so I haven't been watching -current like a good boy should, but I've suddenly been seeing a serious problem, and it *might* not have been reported, and seeing as code freeze is almost here, it's worth risking a bit of embarrassment, I guess. Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). I see the hanging Speaker problem on an Asus A7V with an Athlon 2000+ and 256 Megs of RAM, so it seems not SMP related, nor Tyan related. Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher Partnerfax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de 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 Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Touchpad support in -current for Sony Vaio GRX-670
Seems the 670 needs a slight addition to psm.c for its
touchpad. Can this be committed?
I'm using Yahoo because the mailing list doesn't like
my real address. Please excuse the formatting.
*** /usr/src/sys/isa/psm.c Thu Dec 12 21:35:39
2002
--- psm.c Fri Nov 29 01:49:22 2002
***
*** 2880,2885
--- 2880,2886
{ 0x80374d24, IBM PS/2 mouse port
},/*IBM3780,ThinkPad */
{ 0x81374d24, IBM PS/2 mouse port
},/*IBM3781,ThinkPad */
{ 0x0490d94d, SONY VAIO PS/2 mouse
port},/*SNY9004,Vaio*/
+ { 0x0390d94d, SONY VAIO PS/2 mouse
port},/*SNY9003,VaioGRX670*/
{ 0 }
};
__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
dri-devel - HEADS-UP
To those of you running the radeon.ko dri module from the ports (ports/graphics/dri-devel) IF YOU'RE RUNNING CURRENT then you might want to listen up. I just did a rebuild of the system for the first time in about 6 days, and my system rebooted immediately when XFree86 attempted loading the radeon.ko. I always rebuild and reinstall the modules when I do the kernel, but I also always take extra care to copy the ports version of radeon.ko over the one built/installed during the modules build, so I am completely certain that I was using the one from the ports. I reverified that on reboot. While I'm not totally certain it was the dri-devel, I rebuilt it again (it used the same sources as before from ports, on the new kernel sources from /usr/src/sys) and next time, used that to load. Result this time was just fine. I did check, the module binary had changed size (gotten a bit smaller). I don't know for sure if that is from a change in the compiler or a change in kernel sources (probably both). I'd previously built the dri-devel port with the gcc 3.2 compiler, it's in a new rev now. The moral is, I think you need to rebuild/reinstall dri-devel if you're running FreeBSD-current. If anyone can either show I'm wrong, or verify my experience, if you'd post your results you'd be doing everyone a favor. I won't mind being proven wrong. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vaio ACPI and PCCARD problems
--- Pete Carah [EMAIL PROTECTED] wrote: This is a Vaio R505ES. Looks as if acpi is both totally necessary and doesn't work right. snip psm doesn't work (fails probe too). Complains about unable to allocate irq. You might try this. I have a Sony Vaio GRX-670 and the touch pad didn't work. Took me a while to track down this one line change ;) Don't know if the R505ES has the same issue... __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com psm.diff Description: psm.diff
Linux Emulation Panic
Two panics produced when using Linux emulation on a machine CVSUP'ed two hours ago. Both very easy to produce. Am I the only one running Linux emulation on -current? Or is something wacked-ifed with this machine? Thanks, Chuck McCrobie [EMAIL PROTECTED] 1. cd /usr/ports/emulators/linux_base ; make install (hand-typed, sorry for typo's) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x08:0xc4670534 stack pointer = 0x10:0xdcb45c98 frame pointer = 0x10:0xdcb45c9c 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 = 1516 (glibc_post_upgrade) kernel: type 12 trap, code=0 Stopped at stackgap_init+0x14: mol 0x2c(%eax),%edx db trace stackgrap_init(dcv45cd0,c047d023,c4360c78,c4361540,dcb45ce0) at stackgap_init+0x14 linux_execve(c4361540,dcb45d10,dcb45cfc,dcb45d00,3) at linux_execve+0x17 syscall(2f,2f,2f,8048816,bfbfea50) at syscall+0x2aa Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (11, Linux ELF, linux_execve), eip=0x80486c2, esp=0xbfbfea2c, ebp=0xbfbfea38 2. kldload linux ; /compat/linux/sbin/ldconfig sorry, no panic information for this one __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Sony VAIO GRX-670 Touchpad Support in -current
Should this be a send-pr or can someone commit it from here? Thank you, Chuck McCrobie [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com psm.c.diff Description: psm.c.diff
Re: which(1), rewritten in C?
On Thu, 2 Mar 2000, Alfred Perlstein wrote: * Dan Papasian [EMAIL PROTECTED] [000302 18:17] wrote: While this may sound crazy, I was tired of 'which' taking a long time to complete on my 486 dx4/100 when it was under extereme pressure, so I rewrote it in C :) ...snip NOTE: This version of which has exactly the same behavior. Also, the above test was not performed when the box was under load.. and on slower machines/under load, the differences are of course, more noticable. You may all go ahead and call me crazy now. ...I've got the fear of posting the source, but what the heck, getting nitpicked is good education :) http://bugg.strangled.net/which.c Any flames^Wthoughts? It doesn't seem to handle multiple arguments. File a PR and fix the issues and I'll look at getting it into post 4.0. Hey Alfred, what Perl program is he talking about? Which is a builtin for csh and tcsh (my shells). Or is he talking about some other 'which'? -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: which(1), rewritten in C?
On Thu, 2 Mar 2000, Laurence Berland wrote: Which is also a perl script, which sh uses (since it's not a builtin there). It does the same thing as the which that's built in to bash and tcsh and csh Oh, then it does it dynamically? That must be why it's slow. OK, thanks. Chuck Robey wrote: On Thu, 2 Mar 2000, Alfred Perlstein wrote: * Dan Papasian [EMAIL PROTECTED] [000302 18:17] wrote: While this may sound crazy, I was tired of 'which' taking a long time to complete on my 486 dx4/100 when it was under extereme pressure, so I rewrote it in C :) ...snip NOTE: This version of which has exactly the same behavior. Also, the above test was not performed when the box was under load.. and on slower machines/under load, the differences are of course, more noticable. You may all go ahead and call me crazy now. ...I've got the fear of posting the source, but what the heck, getting nitpicked is good education :) http://bugg.strangled.net/which.c Any flames^Wthoughts? It doesn't seem to handle multiple arguments. File a PR and fix the issues and I'll look at getting it into post 4.0. Hey Alfred, what Perl program is he talking about? Which is a builtin for csh and tcsh (my shells). Or is he talking about some other 'which'? -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CTM deltas
On Sat, 11 Mar 2000 [EMAIL PROTECTED] wrote: The latest CTM delta for -CURRENT on ftp.freebsd.org is 4257 (March 6). Because all of the mirrors for CTM are in countries other than the US, would there be any differences between the deltas they have and the ones that ftp.freebsd.org should have? (I don't understand this crypto thing all too well.) Also, is there some reason that CTM deltas aren't on the FTP servers? The deltas stop at 4257 on one of the mirrors in Taiwan too, and I can't contact either of the other two Taiwanese mirrors or the South African mirror listed on http://www.freebsd.org/handbook/mirrors-ctm.html (the one in Germany is fine, and has all the deltas through 4265 at this point). So many points to address here ... 1) please, bring ctm problems to the attention of [EMAIL PROTECTED] If you think they are general in nature, you can use ctm-announce, which is a public list. Don't use current, they're mostly uninterested in CTM stuff. 2) Archive site has changed, try ftp.freesoftware.com. You *should* have read that on logging into ftp.freebsd.org. 3) I don't see the numbers you see. On current, the latest delta is cvs-cur.6161.gz. I checked the src-3 one also, in case you maybe meant that, it's also a long way off of 4257. I think you must have your numbers messed up; please recheck them. 4) As long as you're not talking about Mark Murray's CTM of int'l crypto, there's only *one* source of ctm deltas, and I'm it. They are all now signed with GNU's gpg, and any you get are identically the same. Doesn't matter where you pick them up from. Most folks get them from the mailing lists from [EMAIL PROTECTED] 5) Just checked with the new ftp site; ftp.freesoftware.com isn't correctly mirroring ctm deltas. The other sites are OK. I'll get right on that, thanks for pointing me at it. The last ctm delta that ftp.freesoftware.com has is a week or two old: cvs-cur.6147.gz. Any more questions, send them to [EMAIL PROTECTED], not this list. Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
On Wed, 29 Mar 2000, Matthew Dillon wrote: time make -j 20 buildworldbuild FreeBSD-current using 4.0 kernel 4745.607u 1673.646s 1:29:07.45 120.0% 1323+1599k 8237+251565io 1615pf+0w time make -j 20 buildworldbuild FreeBSD-current using 5.0 kernel 4696.987u 1502.278s 1:10:34.17 146.4% 1359+1641k 10889+4270io 1779pf+0w Difference: 19 minutes, or a 21% improvement. Bob Bishop got 7% with an earlier patch (hopefully his system is no longer locking up and he can repeat his test with the current stuff). Goddamn. That's significant! Congratulations, Matt. Did it again! Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0?
On Sun, 2 Apr 2000, Thomas T. Veldhouse wrote: Are there any plans to merge perl-5.6.0 into current? I don't have any plans for using it currently, but I curious. Hmm. What with the nightmarish build structure of perl, I'm sure that reading this is just going to wreck Mark's day. In light of that, and in the absence of both any real software that needs the upgrade, and lack of confidence in a really squeaky new release, why don't we all grant Mark a little slack on this, at least for a while. Else we're going to have a drooling Mark on our hands :-) Unless, of course, you want to do it *for* Mark? Thanks, Tom Veldhouse [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0?
On Mon, 3 Apr 2000, Christopher Masto wrote: On Sun, Apr 02, 2000 at 05:56:22PM -0400, Chuck Robey wrote: On Sun, 2 Apr 2000, Thomas T. Veldhouse wrote: Are there any plans to merge perl-5.6.0 into current? I don't have any plans for using it currently, but I curious. Hmm. What with the nightmarish build structure of perl, I'm sure that reading this is just going to wreck Mark's day. In light of that, and in the absence of both any real software that needs the upgrade, and lack of confidence in a really squeaky new release, why don't we all grant Mark a little slack on this, at least for a while. I've been running Perl 5 since before it was included with FreeBSD, and I've never noticed anything nightmarish about the build process. I tried 5.6 a couple of days ago, and it built and tested out of the box. It's the way that perl builds itself. Isn't perl the only thing we build that *doesn't* use make alone to guide the build process? Isn't perl the only thing in the tree that uses itself to build it's manpages? Have you looked at the make files for perl, say the one in gnu/usr.bin/perl/perl? It works *real* slickly, but it sure wouldn't have been easy to piece together. Maybe you misinterpreted what I said to mean "the build is screwed up". I think the job done was great, but I wouldn't want to get the job of modifying it, say moving it's local library location. ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installworld to /some/where/...
On Thu, 6 Apr 2000, Yu Guo/PEK/Lotus wrote: Just do a make DESTDIR=/mnt/installdir installworld Or remotely mount /usr/obj and /usr/src, and do 15 make installworlds on 15 machines. In fact, I'm not totally sure that first method works, because I think that perl, at least, records the name of DESTDIR during the 'make buildworld' so moving DESTDIR only in installworld, that might bomb later when you ran it. In fact, I think that will happen, and to cc1 (of gcc) also, because the 'specs' get set during buildworld, don't they? The above would only be safe, I think, if you did the make buildworld with the same DESTDIR. Anyone know if that's true? Hi, Is it possible to do an installworld not to / of existing system, but to, say, subdirs somewhere, which could be mountpoints for another disk? Something like: /mnt/installdir/ /mnt/installdir/compat /mnt/installdir/etc /mnt/installdir/usr /mnt/installdir/var /mnt/installdir/ The reason I'm asking is that I'm looking for a method to easily clone/upgrade a bunch of servers without having to do 'make world' on all of them. I'm not satisfied either with using dd - the machines are not identical, there are some bits and pieces of config specific to each machine. So far the best method was to do a make world, but it becomes more and more a nuisance and waste of time... Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ 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 ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Fri, 14 Apr 2000, Joe Greco wrote: In other words, if we're going to be replacing sendmail with an alternative MTA, I'd prefer postfix over qmail, and I believe I can marshall some pretty strong arguments for that position. Perhaps it's time to revisit something I proposed several years ago. Remove Sendmail from the base system - or, at least, make it a "package" that is removable with the package management tool. Then be able to add another mailer (or an updated Sendmail) in its place. Ideally, Sendmail would be available as a package for installation as part of the base system, just like games or info or proflibs. I would love to see this happen with other components of the system as well, such as BIND. While it is fantastic that FreeBSD comes out of the box so fully functional, it does make it a bit of a pain for those of us who intend to build servers - we have to disable the original before installing a new package. :-/ I always keep hearing the same line. You guys *know* perfectly well how to do it, and it's not a big thing to you, you even admit it's only "a bit of a pain". To most of the rest of the world, it's a huge thing, and they don't have the least clue how to do it. If you guys want so desperately to make things 1% easier, why have I never seen anyone bring out a parallel "sparse" FreeBSD? It wouldnt' be a large thing to do, and you who keep on asking for it, you know that very well. Just have a reasonable bit of compassion for everyone else. That's not to say the huge hurt it would do to FreeBSD to all reviewers and the public at large, just to save you "a bit of a pain". ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Sat, 15 Apr 2000, Joe Greco wrote: Uh, Chuck, can you tell me how many BIND and Sendmail advisories there have been in the last five years? Wouldn't it be nice if we could just tell newbies, "hey, yeah, that Sendmail has a known security issue, pkg_delete it and then add this new one here". Or would you prefer to explain to someone who doesn't "have the least clue how to do it" how to upgrade BIND and Sendmail to the latest? The concept is beneficial from _many_ angles, not just the one I gave. Despite my tendency to promote the traditional BSD distribution style, that does not mean that I feel that everything in FreeBSD should arrive as it did on the 4.4BSD tape. I think that the ability to be able to select modules for inclusion or exclusion would be particularly useful. If you want to pick another one and by default install that, fine. If you want to force new users to read all about mailers just to get their first mail working, no, that's just too much, Joe, you're asking too much of folks. If you've got a bone to pick with sendmail, that's ok, but you have to pick a better one. If you can't decide on the best one, then how in the heck do you expect Joe Public to do better? ALWAYS provide sensible default values, not a bunch of expert questions. ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Sat, 15 Apr 2000, Joe Greco wrote: Chuck, Please go back and read what I _wrote_. Your response assumes I made I've got your message, I quoted it fully in my first response. You asked to "Remove Sendmail from the base system", and that's a direct quote, Joe. statements that I certainly did not, and suggests to me that you missed every third word in my previous messages. :-( In particular, I advocated including Sendmail in the base system in a manner that would allow it to be trivially removed (or, alternatively, not including it but making it a selectable package, like X11). No, you said remove it, or at least make it removeable. I responded that you can't just remove it. Go to your sent mail message folder, I'm not making this up. I said don't remove it (not "don't make it removeable"). You're the one who's sticking new words in. This could, for example, be done in the very same way that we currently do loads of other crap, like /usr/games, proflibs, etc. More ideally, it would be done in a format compatible with the package management system, so that one could simply "pkg_delete" Sendmail and install a new one. Am I getting through now? :-) You asked in your mail to remove it, I said you can't leave ordinary users without a good default. Your context in what you said was that it was a minor pain to have to remove the default mailer. I stand by what I said. You changed your message, and if you want, I can send your message back to you. If you argue *only* that some easier method be arranged so that mailers can be swapped out, that I fully approve of. I never said otherwise, and I don't like much the way you changed things. In fact, what the heck, here's your original message, cut out of my reply (where I quoted all of your part of the exchange): Perhaps it's time to revisit something I proposed several years ago. Remove Sendmail from the base system - or, at least, make it a "package" that is removable with the package management tool. Then be able to add another mailer (or an updated Sendmail) in its place. Ideally, Sendmail would be available as a package for installation as part of the base system, just like games or info or proflibs. I would love to see this happen with other components of the system as well, such as BIND. While it is fantastic that FreeBSD comes out of the box so fully functional, it does make it a bit of a pain for those of us who intend to build servers - we have to disable the original before installing a new package. :-/ ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup crash
On Wed, 19 Apr 2000, Alexander N. Kabaev wrote: Actually, it seems that Java borrowed a whole lot of ideas from Modula-3. And C++ experience can even hurt instead helping when switching to Java. Java inherits some parts of C++ syntax but is based on rather different design. That statement, about "C++ experience can even hurt instead helping when switching to Java" is pretty specious. I've heard it said that knowing C ruins you for learning C++, and your statement holds about the same amount of water. If you think the latter is right, you might believe the former, but I sure don't buy it, it sounds awfully conceited. C++ and Java are *quite* similar. There are differences, and personally, I think Java is quite a bit better for them, but they aren't based on radically different designs, and quite often, code parts will look identical. Yes, there are differences, and Yes, some of those differences are major, but they are from the same tree, and knowing C++ isn't going to hurt you one bit in learning Java ... it'll just make you appreciate Java all the more. One think I like about Modula-3, I have to agree, is that it has some of the nicer features or Java. I think interfaces are great, and I have very dire opinions about the quality of most template code (from C++). ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone have OpenSSH + X11-fwd working?
On Fri, 21 Apr 2000, Warner Losh wrote: In message [EMAIL PROTECTED] "Andrew Reilly" writes: : Have you got "X11Forwarding yes" Ahem. "ForwardX11 yes" is what's documented and is known to work. While this whole thing is being discussed, does anyone know of either a configuration variable or environmental variable that ssh reads, that will give the same effect as the -q flag, so that I can stop seeing those stupid warnings about the size of the key being off by one? Thanks. ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Archive pruning
I want to bring up a suggestion. I just want a little bit of argument on it ... and if you're violently opposed, just say so, that's fine. I want to suggest that, once a year, we go thru the cvs archive, and prune away all history more than 3 (or maybe 2, maybe 4) years old. This could be done without too much pain, I think, in a script. The purpose is to put some kind of cap on growth of the FreeBSD source archive. While folks do sometimes go hunting for hugely old materials in the tree, I normally couldn't care less (when browsing) about history that old. Do we really need 5 year old history? Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Mon, 24 Apr 2000, David O'Brien wrote: On Mon, Apr 24, 2000 at 08:15:45PM -0400, Chuck Robey wrote: I want to bring up a suggestion. I just want a little bit of argument on it ... and if you're violently opposed, just say so, that's fine. I'm "violently opposed". :-) While folks do sometimes go hunting for hugely old materials in the tree, I've often traced files back to the begining of FreeBSD time (and then continued in the CSRG SCCS tree). I've done this numerious times, especially the contributed sources like GCC and GNU grep. Do we really need 5 year old history? Yes. OK. Thanks, I wanted some opinions, and I guess I have enough to satisfy me. ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Mon, 24 Apr 2000, Bakul Shah wrote: Do we really need 5 year old history? That really depends on your point of view. "Those who cannot remember the past are condemned to repeat it" -- Santayana "The only thing we learn from history is that we learn nothing from history." -- Hegel I am with Hegel in the very long term but what is the rush about pruning? Set a cron job to ask this in the year 2037! In the short term it is valuable to trace back the genesis of various features/bugs. With cvs annotate you can even find out who put in a feature or bug and bug that person about it (as I was just this past week about something I had written over four years back). The networking code is so convoluted that having all the history (which we don't) can be very valuable in unravelling all the development strands. Well, I wasn't talking about a harsh pruning, but I haven't seen much support for the idea, so maybe it better drop. The idea came when I was making room for vmware ... boy, I wish that the new generation of 18G Ultra160 disks would come out already ... the only reasonably priced one is the Seagate, but it could be aptly nicknamed the "data furnace" from just how hot it runs. I need more disk! ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Tue, 25 Apr 2000, Richard Wackerbarth wrote: On Tue, 25 Apr 2000, you wrote: I told myself I wouldn't get into this debate with you again, Richard, but you're not listening. The vast majority (all? I might have missed one) of the other respondants Actually, I didn't start this. Someone else brought up the idea. I did. I wanted to test the opinions. I said I had enough responses, about 40 messages ago. Damn, people, if you're *really* tired of hearing from Richard on this, for god's sake control your keyboards, they're running amuck! Let's see if you guys can just let it die, ok? The quiet majority that might benefit are not very likely to speak up when they are told some is impossible. Quiet majority hehe! Right Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Sat, 29 Apr 2000, gh wrote: For an opinion from a reasonably new-comer and non-developer, I think at least the main source tree should remain *completely* complete. As someone mentioned, why not have "lite" mirrors? Oh, for god's sake, PLEASE let this drop! I don't want to insult a newcomer, but you've picked a very poor thing to comment on. Try another, maybe one that's a bit fresher. ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: a better idea for package dependencies
On Tue, 9 May 2000, David O'Brien wrote: On Mon, May 08, 2000 at 06:30:17PM -0400, Kenneth Wayne Culver wrote: Actually, it has to do with the pkg_ commands, which I believe are built when you make world... yes. and aren't part of the ports, And are only used for Ports. Thus their behavior defines the behavior of the Ports Collection. Thus it is a Ports issue. IF the pkg_* utils were ports, how would you install them?? Oh, will you get off it? Finally someone posts something about a *technical* issue, it's got at least some reasonable claim to be on the list (it's sure involving sysinstall, if obliquely) and it's not giving a lot of noise. There must be better things to complain about. I could offer you maybe a dozen if you're not feeling particularly investigatory right now. Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make(1) patches to bypass quietness prescribed by @-prefixedcommands in Makefiles
On Sun, 14 May 2000, Will Andrews wrote:
Hi all,
Some time ago I was complaining about how there is no way to force make(1)
to display the commands executed by @-prefixed commands in Makefiles. So I
went around and talked to a few people and one guy clued me in on how I
would add something like this (sorry, I don't remember the name right now
as this was a few weeks ago..).
This option is useful for people with complex Makefile hierarchies who
cannot simply insert a `@${ECHO} "SOMEVAR = ${SOMEVAR}"` as needed in their
Makefiles or remove all the @'s in their Makefiles. In particular, I would
use this feature to debug ports.
Attached is the patch. If I can get permission, I'd like to commit this to
code on -current, with a possible MFC in a few weeks (?). I'd like to hear
any complaints about this code, including any style(9) mistakes, whether
this option would be considered bloat, and whether the variable name
``beLoud'' is appropriate in this context. ;-)
Oh, what a nice present! Thanks!
Thanks,
----
Chuck Robey| Interests include C Java programming, FreeBSD,
[EMAIL PROTECTED] | electronics, communications, and signal processing.
New Year's Resolution: I will not sphroxify gullible people into looking up
fictitious words in the dictionary.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make(1) patches to bypass quietness prescribed by @-prefixedcommands in Makefiles
On Sun, 14 May 2000, Will Andrews wrote: On Sun, May 14, 2000 at 01:25:16PM -0600, Lyndon Nerenberg wrote: I like the idea, but the -l flag conflicts with a different usage for SVR4 derived makes (on at least AIX, Irix, and Solaris): -l load Specifies that no new jobs (commands) should be started if there are others jobs running and the load average is at least load (a floating-point number). With no argument, removes a previous load limit. Compatibility with those other makes is pretty low to begin with, but it doesn't hurt, I guess, to allow for this. -dl is ok with me. I just wouldn't consider the compatibility thing a real issue if it weren't this easy to satisfy. Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
vmware
I fianlly have vmware2 working on my current box, but I have noticed a couple things in my log, and I wanted to ask about them. Here's a little bit at the end: sio1: 3 more silo overflows (total 1268) /dev/vmmon: Vmx86_DestroyVM: unlocked pages: 359971, unlocked dirty pages: 217740 I guess I can understand the large number of silo overflows. I noticed that I can't seem to get any mails when I have vmware working, and I wish that wasn't so. The part that really worries me, tho, is the virtual memory warning. I was doing a lot of Windows software installation (which dragged on *really* slowly), but is there anything to be worried about in that warning above? Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: Destabilization due to SMP development
On Wed, 21 Jun 2000, Mark Murray wrote: Has anyone given any thought to what it would take to create an open source version of something similar to perforce? ;-) Clearly you have. :-). We await your submissions with baited breath... I have mixed feelings about that. The Perforce people have been willing for FreeBSD to use it free. They're really nice about that, it seems more than a bit discourteous to try to copy it. If you'd asked to duplicate MSWord, they're a unethical monopolist, I wouldn't have any scruples attacking them, but I don't like attacking folks who've been displaying towards free software such a friendly attitude. Makes me (and I sure support free software!) feel like a predator when you go after folks who've been doing good. I think, if you want it fixed, you should go fix cvs. Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Config problems
I am getting a config error with the new gethints.pl stuff: unrecognized config token 1 This is with a newly cvsupped system, and I checked the version of gethints.pl: ROOT:/usr/src/sys/i386/conf:472 cvs status gethints.pl === File: gethints.pl Status: Up-to-date Working revision:1.4 Sun Jun 18 01:43:22 2000 Repository revision: 1.4 /home/ncvs/src/sys/i386/conf/gethints.pl,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) So I think that's right. My config file before had worked just fine, but as a test, I went thru it and really tried to make it squeaky clean, but it didn't seem to get rid of that error. I don't know if this message indicates a fatal problem or just is a leftover printf, there's damned little in the way of info in it. I don't know, maybe that error message is referring to line 1 of my config file? Here's the start of the config file: machine i386 cpu I586_CPU cpu I686_CPU ident CH maxusers64 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O If that doesn't do it, I'm attaching the entire config file to this mail. Sure would appreciate a hint; I'm not a perl hacker, but if I gotta become one to puzzle this out, it's going to take me an long extra while trying to get me a new kernel. Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Config problems
On Sun, 25 Jun 2000, Kenneth Wayne Culver wrote: Hey chuck, except for the SMP stuff, your config looks mostly like mine (I only have a cpu line for i686) Let me know if there's anything I can do to help though. I'm about ready to post again, so this is good timing. I got the totally vague warning from gethints.pl to quiet by making my disk section look much like the NOTES file. I then ran it by a brand new config, and out spewed more than 25 errors. The entire section on wiring down disks fails, and also all the stuff on npx, even tho that part was copied verbatim from NOTES. I have an Adaptec dual channel controller on my motherboard, and I have 3 disks and 2 cdroms, which I want to wire down. There's lines in the NOTES examples whose meanings just make no sense to me. Let me do a bit of quoting: [from NOTES] hint.scbus.0.at="ahc0" hint.scbus.1.at="ahc1" hint.scbus.1.bus="0" hint.scbus.3.at="ahc2" hint.scbus.3.bus="0" hint.scbus.2.at="ahc2" hint.scbus.2.bus="1" hint.da.0.at="scbus0" hint.da.0.target="0" hint.da.0.unit="0" hint.da.1.at="scbus3" hint.da.1.target="1" hint.da.2.at="scbus2" hint.da.2.target="3" hint.sa.1.at="scbus1" hint.sa.1.target="6" What does ``hint.scbus.1.bus="0"'' mean? Do I have to stick a number after the "device ahc" and "device scbus" lines (the NOTES file doesn't). Are there any other oddities I ought to know of? Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Config problems
cons stuff device vga0at isa? port ? device sc0 at isa? device sio0at isa? port IO_COM1 irq 4 device sio1at isa? port IO_COM2 irq 3 device ppc0at isa? port? irq 7 drq 3 device ppbus0 device lpt0at ppbus? device plip0 at ppbus? device ppi0at ppbus? device pps0at ppbus? # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 device fxp0 pseudo-device loop pseudo-device vn pseudo-device ether pseudo-device snp 4 #Snoop device - to look at pty/vty/etc.. pseudo-device tun 1 pseudo-device pty 128 pseudo-device streams pseudo-device gzip# Exec gzipped a.out's pseudo-device bpf 4 device pass0 #CAM passthrough driver device pass1 #CAM passthrough driver device pass2 #CAM passthrough driver device pass3 #CAM passthrough driver # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # PS/2 mouse device psm0at atkbdc? irq 12 Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs-cur.6450.gz Fatal error: Bytecount too large.
On Sun, 2 Jul 2000, Julian Stacey wrote: Stefan Esser wrote: On 2000-07-01 16:35 -0500, Stephen Hocking [EMAIL PROTECTED] wrote: again. However, when I attempt to apply cvs-cur.6450.gz I get the above err You have to increase the value of MAX_SIZE in /usr/src/usr.sbin/ctm/ctm/ctm.h to at least 12MB (i.e. 1024*1024*12). This has been fixed in -current (to 20M B) and is awaiting a MFC. Not sure whether the fix went in before cvs-cur.6450, but I think so. In that case just recompile and install ctm. The patch below solves it on 3.4-RELEASE : Date: Wed, 21 Jun 2000 09:18:26 -0400 (EDT) From: Chuck Robey [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: cvs-cur Message-ID: [EMAIL PROTECTED] .. Index: /usr/src/usr.sbin/ctm/ctm/ctm.h === RCS file: /usr/cvs/src/usr.sbin/ctm/ctm/ctm.h,v retrieving revision 1.14 diff -u -3 -r1.14 ctm.h - --- /usr/src/usr.sbin/ctm/ctm/ctm.h 1999/08/28 01:15:59 1.14 +++ /usr/src/usr.sbin/ctm/ctm/ctm.h 2000/06/15 20:25:55 @@ -26,7 +26,7 @@ #include sys/time.h #define VERSION "2.0" - -#define MAXSIZE (1024*1024*10) +#define MAXSIZE (1024*1024*20) Yeah. I committed it to currect myself, Julian. Tomorrow, I'll do the MFC. It was about 2 weeks ago, when a big patch blew up the ctm machine. I announced it pretty widely on the ctm list, I'm really sorry you missed it and had to do that work again. #define SUBSUFF ".ctm" #define TMPSUFF ".ctmtmp" Julian - Julian Stacey http://bim.bsn.com/~jhs/ Kostenlos: FreeBSD 3200 packages, sources, Netscape, WordPerfect StarWriter. RaucherKrebsNebel erregt meinen allergischen Kopfschmerz: Schnupftabak Nutzen! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Annoucning DragonFly BSD!
On Thu, 17 Jul 2003, Gregory Sutter wrote: To drag this back to more interesting topics, I'm not yet convinced that branching off 4.X is a good thing. I see all the mound of work to make things work with mutexes, and it still seems like a good thing, and something that CAN be still leveraged, even in a messaging prardigm. I'll admit I might be wrong, but I'd sure appreciate a bit of discussion about it. I *like* the mutex idea, at base, and I really hate to lose the work. On 2003-07-17 08:57 -0700, Julian Elischer [EMAIL PROTECTED] wrote: On Thu, 17 Jul 2003, Julian Stacey wrote: Matthew Dillon [EMAIL PROTECTED] appeared to write: Announcing DragonFly BSD! http://www.dragonflybsd.org/ - A new kernel - OK - maybe it'll cross fertilise others, but couldn't it run with an exisiting /usr/src ? Free Net or Open. Mat had his commit bit unfairly removed.. what would YOU do? Look, let's not go there again--the past is the past. The current situation is that Matt is using his skills and perspective to branch FreeBSD in an interesting direction. We all know he can do it, so instead of repoliticizing the discussion by harping on how he was treated unfairly, which we know is a subject fraught with disagreement, let's just focus on the work that Matt is doing to further the improvement of BSD technology. OK? Greg Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Annoucning DragonFly BSD!
On Thu, 17 Jul 2003, Brian Reichert wrote: On Thu, Jul 17, 2003 at 08:56:56PM -0400, Chuck Robey wrote: On Thu, 17 Jul 2003, Gregory Sutter wrote: To drag this back to more interesting topics, I'm not yet convinced that branching off 4.X is a good thing. Gosh, if only there were a DragonFly BSD mailing list, so we _can_ keep on topic somewhere. :) If follks would keep the traffic down, I could host it, but I only have a DSL link, it's not enough for a lot of traffic. If no one does it by Friday night, I'll host one myself. Until then folks, please bear with us, we haven't anywhere else to go to. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Annoucning DragonFly BSD!
On Thu, 17 Jul 2003, Larry Rosenman wrote: I have a 768/768 DSL line, and mailman all set up. I also have the disk space. Let me know if you are interested. I'm happy with it, but right now, until we get a bit more organized, we only need one yea vote: Matt's. I *don't* want to inconvenience his plans any (especially not when I'm really sure I don't understand them all yet). Is Larry's offer OK with you, Matt? We need off the FreeBSD lists, before complaints start up. We can advertise later, if it's necessary. LER --On Thursday, July 17, 2003 21:10:26 -0400 Chuck Robey [EMAIL PROTECTED] wrote: On Thu, 17 Jul 2003, Brian Reichert wrote: On Thu, Jul 17, 2003 at 08:56:56PM -0400, Chuck Robey wrote: On Thu, 17 Jul 2003, Gregory Sutter wrote: To drag this back to more interesting topics, I'm not yet convinced that branching off 4.X is a good thing. Gosh, if only there were a DragonFly BSD mailing list, so we _can_ keep on topic somewhere. :) If follks would keep the traffic down, I could host it, but I only have a DSL link, it's not enough for a lot of traffic. If no one does it by Friday night, I'll host one myself. Until then folks, please bear with us, we haven't anywhere else to go to. - --- Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. - --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DragonFly lists are on the DragonFly site...
On Fri, 18 Jul 2003, Nigel Weeks wrote: http://www.dragonflybsd.org/Main/forums.cgi Has both newsgroups and mailing lists on it... Gotcha, I didn't see them (was busy reading the tech stuff). I figure the kernel list is the right one. Thanks. At least the newsgroups work - they've been a hard slog reading them, though... -Original Message- From: Larry Rosenman [mailto:[EMAIL PROTECTED] Sent: Friday, 18 July 2003 11:33 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; Julian Elischer Subject: Re: Annoucning DragonFly BSD! I have a 768/768 DSL line, and mailman all set up. I also have the disk space. Let me know if you are interested. LER --On Thursday, July 17, 2003 21:10:26 -0400 Chuck Robey [EMAIL PROTECTED] wrote: On Thu, 17 Jul 2003, Brian Reichert wrote: On Thu, Jul 17, 2003 at 08:56:56PM -0400, Chuck Robey wrote: On Thu, 17 Jul 2003, Gregory Sutter wrote: To drag this back to more interesting topics, I'm not yet convinced that branching off 4.X is a good thing. Gosh, if only there were a DragonFly BSD mailing list, so we _can_ keep on topic somewhere. :) If follks would keep the traffic down, I could host it, but I only have a DSL link, it's not enough for a lot of traffic. If no one does it by Friday night, I'll host one myself. Until then folks, please bear with us, we haven't anywhere else to go to. -- --- --- Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. -- --- --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [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] Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Linux Emulation Panic
Thank you. That was it. Booted from /boot/cvsup/kernel, loaded modules from /boot/kernel/*. Now, if I can just figure out read-conf and friends in loader. It seems I have to manually: loader unload loader set kernel=cvsup loader set kernelname=/boot/cvsup/kernel loader set module_path=/boot/cvsup loader boot I want to have two different kernels - one I know works (older -current) and the latest cvsup of -current. Then, I would like to: loader some-command-to-load-alternate-configuration I suppose that's read-conf, but that doesn't seem to like me :( I have: /boot/cvsup.conf as: unload kernel=cvsup kernelname=/boot/cvsup/kernel module_path=/boot/cvsup then I use: loader read-conf cvsup.conf but the changes don't take effect. Oh well, maybe some more experimentation later... Thanks, Chuck McCrobie --- Kenneth Culver [EMAIL PROTECTED] wrote: What exactly were you running? I use linux emulation on -CURRENT right now for mozilla and a few other packages, and havn't had any panics... you might have your kernel modules out of sync with your kernel. Ken On Mon, 13 Jan 2003, Chuck McCrobie wrote: Two panics produced when using Linux emulation on a machine CVSUP'ed two hours ago. Both very easy to produce. Am I the only one running Linux emulation on -current? Or is something wacked-ifed with this machine? Thanks, Chuck McCrobie [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: AC97 sound problems with current
--- John Hay [EMAIL PROTECTED] wrote: | There is a calibration step in the driver to determine the clock rate of th | e | AC97 link. What you are seeing is the calibration step failing and setting | a | bogus ac97 link rate. I took a cursory look a couple of weeks back and it | smelt like the timecounter initialization point changed, but haven't gotten | | around to looking closer and fixing the driver. It's definitely nothing to do with the timecounter - quick test on other h/w along similar lines. I don't access to an ich board to test on - it's probably obvious, but I'm not seeing it just now with visual inspection... It doesn't look like it is the timecounters. I just added some printfs and it looks like this: pcm0: measured ac97 link rate at 51200 Hz t1 1.098359, t2 1.098363 ociv 0, nciv 1, bytes 8192 tsc1 445813142, tsc2 445821922, diff 8780 The tsc values are just from rdtsc(), I added tsc1 = rdtsc() just above the first microtime() and tsc2 just after the last. My machine is a 1.8G P4 (ICH2), so the timecounter values seem correct. I have kernel around the middle of Feb that gets the value right and one from March 4 that gets it all wrong. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] I also see this problem. On my machine, I dumped the t1 and t2 variables - there's only about 3 microsecond difference!. It seems the calibration loop is entered, but that CIV is immediately updated to the next index, thus getting out of the loop after about 3-4 microseconds. I thought something with the setup of the registers or maybe a blocksize issue, but I'm getting out of my element here. I can try various testing and debug code if needed. Chuck McCrobie [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FXP breakage
--- Pete Carah [EMAIL PROTECTED] wrote: This may be just my infamous vaio acting up again, but since the recent commit to fxp driver (Monday?) I get a panic on device probe (page fault in kernel mode). That and the way the pccbb act up (always return 0 for event and status register reads, and don't reset pending interrupt on event reg write) make me think that something is awry with the way acpi/pci allocate memory for the device windows. I know there is something funny with the aml/asl since almost everything ends up on irq 9 also... I also sometimes see the lock order problem with pcm but mostly just missing interrupts (choppy sound that comes out slow but in the right order). PCM is responding to display interrupts... -- Pete I wondered what that crash was on boot-up. Sometimes it does boot though! Anyway... I also have almost everything on IRQ9. I'm not sure its FreeBSD - I think its the Vaio :( Just checked Windows 2000 and it lists USB, video, network, firewire, audio _ALL_ on IRQ9. Perhaps your pcm problems come from the interrupt not being delivered at all - try moving a USB mouse while your audio is playing. I have a hacky-hack to make my vaio's audio play normally. I noticed that since the audio and usb share an interrupt, moving a USB mouse gets the pcm interrupt handler called - which results in normal sound. Sorry, I don't have my own web page address handy - I never go there ;) I'll send it privately. Chuck McCrobie [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: keyboard problems with X
On Sun, 30 Jul 2000 [EMAIL PROTECTED] wrote: The problem I am seeing is that the keyboard isnt even seen. Its useable up until about midway through the boot process, then it goes dead/locks up. The boot continues fine and the machine is up. The mouse is usable in X but not the keyboard. Cant even switch virtual consoles. Is it useable or not, outside of X? Can you single-user boot and get the keyboard working? I am not clear if it's an X problem or a system problem. You said you updated your source tree yesterday. If that was from a recent build, then I don't know, but I'm very curious, just how old was your previous build? The config changed really radically maybe 2 months ago, so maybe your config file is hosed? steve I have, like when I'm running tail on something, and then I try to ctrl-c out of it, the whole console locks solid, and I have to reboot. (although if I was connected to an ethernet, I think I could probably ssh in and reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the lockmgr problems that were reported earlier. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 30 Jul 2000 [EMAIL PROTECTED] wrote: Hi, I updated my source tree yesterday (and kernel) and am having some problems with my keyboard under X. Has anyone else noticed anything strange. steve -- Steve Heistand [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: keyboard problems with X
On Sun, 30 Jul 2000, Kenneth Wayne Culver wrote: My problems are with a previous build of late last week. And my problem isn't with X. My problem only happens when you start "tail" on some file, then try to exit. It locks the console solid... neither the mouse nor the keyboard work. Sorry, Ken, I was looking at his problem. I havne't the vaguest notion where your's comes out of. I might suggest doing a ktrace/kdump and see if maybe something is grabbing the keyboard that you aren't aware of. BTW, notice the new address ... I wanted connectivity NOW, and maybe didn't have the greatest imagination as per domain name, but at least my new dsl is up. I just wish it hadn't taken my voice line to do it. ---- Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'interrupt-level buffer overflows' for sio device?
FYI, this is very likely not caused by the heavy weight interrupt threads, but rather because the interrupt threads can't be run because the giant lock is held by a process running in the kernel. Once we get drivers to have their own locking and pulled out from under the giant lock this problem should deminish greatly. Before we can do this there are various infrastructure pieces which must be made mp safe, such as the lockmanger. Chuck To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Where has cvs-cur gone?
On Tue, 10 Oct 2000, Stephen Hocking wrote: Last one I can find in the FTP repository is cvs-cur.6772.gz. Where are the more recent ones? I'm sorry, I have been recovering from recent surgery again, and just got back to reading email. The vinum volume that ctm resides on has disappeared, and all the usual suspects are being rounded up seriously, it looks like Ulf (who physically controls that machine) took them offline for some reason, I don't know why, I have an email off to him about it. Least I won't have to use that "recovering from surgery" excuse anymore. This last surgery, it finally worked! No more time in the body shop anymore!! yea!! Now I can get back to my main hobby (harrassing BSD folks bwahahahhah) I just got in touch with Ulf (just now). ctm-repair now in progress. Stephen ---- Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED]| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
smp instability
I'm having rather extreme problems with stability on my dual PIII setup. I know this is to be expected, but it's gotten so extreme on my system, I can't spend more than a few minutes before it locks up. Is there any chance that I could make things better by using a sysctl to tell the box it's now a single-cpu system? I can't read man pages at the moment (I'm composing this on my Sparc Ultra-5) so if this might work, and someone knows the exact command to use, I'd appreciate a bit of help. Otherwise, I'm going to have to go to a lot of trouble to move back to a pre-SMPNG system, and I sure don't want to do that. Thanks Chuck (who doesn't even have his .sig now!) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: smp instability
On Tue, 24 Oct 2000, John Baldwin wrote: On 25-Oct-00 Chuck Robey wrote: I'm having rather extreme problems with stability on my dual PIII setup. I know this is to be expected, but it's gotten so extreme on my system, I can't spend more than a few minutes before it locks up. Is there any chance that I could make things better by using a sysctl to tell the box it's now a single-cpu system? I can't read man pages at the moment (I'm composing this on my Sparc Ultra-5) so if this might work, and someone knows the exact command to use, I'd appreciate a bit of help. You can use kernel.old to compile a UP kernel. I always keep a UP kernel around just in case. Also, when did your SMP box become unstable? There was a known problem with SMP boxes when the vm page zero'ing during the idle loop was first turned on that has since been fixed with the latest commit to vm_machdep.c yesterday. Symptoms were frequent kernel panic 12's with interrupts disabled . No kernel panics, just lockups. I saw the startup problems (having to hit a lot of control-C's to get booted) and I had two kinds of lockup problems, one a complete machine freeze (still pings, but that's all) and also a strange one where an entire mounted filesystem would disappear. I can back up to my kernel.gd I keep around, but I have to get me an older mountd, netstat, ps (and others) before that older kernel is good, and it was from before the /boot/kernel thing (I hated that idea, and still do). I'm going to try the sysctl route first, see if that works. I won't be able to report reliable results until the morning (if it lasts all night, it's a huge fix). As it stands now, no way can I do any compiling. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: smp instability
On Tue, 24 Oct 2000, Mike Meyer wrote: Chuck Robey writes: I'm having rather extreme problems with stability on my dual PIII setup. I know this is to be expected, but it's gotten so extreme on my system, I can't spend more than a few minutes before it locks up. Is there any chance that I could make things better by using a sysctl to tell the box it's now a single-cpu system? I can't read man pages at the moment (I'm composing this on my Sparc Ultra-5) so if this might work, and someone knows the exact command to use, I'd appreciate a bit of help. Try "sysctl -w machdep.smp_active=0". It's not clear how much good this will do since you'll still be running an SMP kernel. Please let us know how that works. With less than a full hour's history, I haven't exactly heavily tested it, but it only lasted 10 minutes last time, and my system is still kicking currently. Regarding that control-C needed on booting thing: when I log in, my call to fortune needs to be interrupted also, so I immediately went and tried a "ktrace fortune". I didn't need to kdump, because doing that ktrace seems to have somehow cleared the control-C thing on all that kicked it off before (not just fortune alone). My system is really repeatable on that, so if it's not yet fixed, and you have other things to try on it, I'd be willing (if my system stays up!) In the meantime, I think that "sysctl -w machdep.smp_active=0" might actually work for me (I did it in single user so the multiuser startup would be cleaner). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
lpd panic
I'm finally having enough time again to look at FreeBSD again, so I went back and I'm looking at my port complaints. In looking at a2ps, after I reinstalled it fresh (so if it'd been changed I would see those) I see it seems to be going ok, but I pick up a kernel panic whilst printing. The process active at the time is (irq7:lpt0), the trace shows it's dying in fork_trampoline. I have a two processor machine in a very recent (hours old) current, and the panic is a "supervisor read, page not present". If this is familiar to anyone, please give me a shout (note I *am* running a smp kernel). If I get no reply, I guess I'm going to see about tracing this thing back. Thanks. ---- Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: lpd panic
On Sun, 26 Nov 2000, Mark Murray wrote: seems to be going ok, but I pick up a kernel panic whilst printing. Ditto. Also on a dual-cpu machine, also a really recent CURRENT. Well, I can catch the panic in gdb, but I'm not sure how to proceed. The active processes (for me) are irq7:lpt0, irq7:ppc0, and gs (ghostscript, being driven from my apsfilter installation). What's the right way to access the stacks of these processes, so that I can look at their stack frames, and get some idea if they're interfering with one another? Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
getting back to current
I've just finished going thru another medical session, this one took about 5 months, and because of the extended time spent away, I'm running 4.5 (I've been running current since 1.1, this feels really odd). I need a little bit of help (or advice, maybe) to get me back to current. I just finished cvsupping, and the main sources built just fine. I installed a new config (static, the libs are now too old) and fixed all the changes in my config file, so now my kernel file configs but it doesn't build (breaks in 'make depend', I think in genassym). I'm guessing that this is only one of a string of incompatibilities, in jumping from 4.5 back to current. I could drag myself thru fixing the bugs I'm hitting, but I was wondering if I could get someone to use my config file (on freefall, APRIL and APRIL.hints, in ~chuckr/) and build me a kernel and a set of modules. I'm asking this because my health isn't yet back fully, and I would like to shortcut this a bit. [my FreeBSD machine is april.chuckr.org, hence the config filename]. I'm not sure what changes have occurred in kernel/module installation, but *you'd* have to be really sure about that, because I wouldn't want someone to scrag their system whilst doing me a favor. If you're not certain, please don't even offer, I'd hate to be the cause of your system meltdown. I appreciate any consideration I get ... Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: getting back to current
On Sun, 30 Jun 2002, Doug Barton wrote: Chuck Robey wrote: I've just finished going thru another medical session, this one took about 5 months, and because of the extended time spent away, I'm running 4.5 (I've been running current since 1.1, this feels really odd). I need a little bit of help (or advice, maybe) to get me back to current. Glad to hear you're feeling better. :) The bad news is that this is a really terrible time to upgrade to -current. The KSE mark III update just went in, so things are very unstable right now. Clearing out about 50,000 old mails today ... need to update myself. Much thanks for the heads-up. I'm OK with instability, I'm used to that, as long as it works at least a bit. I just finished cvsupping, and the main sources built just fine. I installed a new config (static, the libs are now too old) and fixed all the changes in my config file, so now my kernel file configs but it doesn't build (breaks in 'make depend', I think in genassym). I'm guessing that this is only one of a string of incompatibilities, in jumping from 4.5 back to current. At this point, the only way to build -current on a -stable system is make buildworld; make buildkernel. Make sure that KERNCONF is defined in /etc/make.conf. You'll probably want to read -current and cvs-all for a while before you finish the upgrade though HTH, Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Recommended MP development machines...
On 3 Jul, Peter Wemm wrote: Chuck Robey wrote: On Wed, 3 Jul 2002, David O'Brien wrote: On Wed, Jul 03, 2002 at 07:43:22PM -0700, George V. Neville-Neil wrote: I know everyone says they all work but i'd like some recommendations on MP machines for -CURRENT work. I'll be ordering one this week. There is but _1_ dual system to get -- Tyan Thunder K7 (code name Guinness) . http://www.tyan.com/products/html/thunderk7.html. It comes in multiple flavors, but mine is the dual-channel Ultra160, dual-3com 10/100, 5-64bit PCI, 1 AGP version. You can cheap out and not get the non-SCSI S2462NG model. Match this bad-boy up with a pair of fast Athlon `MP' (not `XP') CPU's and it is a totally solid system. Various FreeBSD committers also have this system. There is a newer [more economic] version called the Thunder K7X. http://www.tyan.com/products/html/thunderk7x.html more economic is a poor way to describe it, seeing as it has all the features, plus (1) an updated version of the AMD mp chipset and (2) a fixed onboard usb port. The K7 had a broken on-board usb (the AMD chipset had a PCI contention bug for the usb port, so the tin back panel of the board blocked out the usb, and the K7 came with a PCI usb card, which ate up one of your PCI slots. The K7X has a repaired on-board usb, so you get that PCI slot back. Hm. Do you have any details on this? I've had occasional strange USB-related things happen on this box. Of course, it runs -current which puts me into the USB danger-zone enough as it is.. but what happens when this bug is triggered? I just finished buying the K7X myself, so I did quite a bit of research before rejecting the Asus board, and the K7. This included reading about a half dozen reviews I located via google and tomshardware. I'm quite certain of my facts (and my head is abuzz with lots more board trivia about them) but it's going to take a little bit for me to run down the source of the PCI comment. I'll do that, wait a bit for it. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 -- Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Recommended MP development machines...
On 3 Jul, Peter Wemm wrote: Chuck Robey wrote: On Wed, 3 Jul 2002, David O'Brien wrote: On Wed, Jul 03, 2002 at 07:43:22PM -0700, George V. Neville-Neil wrote: I know everyone says they all work but i'd like some recommendations on MP machines for -CURRENT work. I'll be ordering one this week. There is but _1_ dual system to get -- Tyan Thunder K7 (code name Guinness) . http://www.tyan.com/products/html/thunderk7.html. It comes in multiple flavors, but mine is the dual-channel Ultra160, dual-3com 10/100, 5-64bit PCI, 1 AGP version. You can cheap out and not get the non-SCSI S2462NG model. Match this bad-boy up with a pair of fast Athlon `MP' (not `XP') CPU's and it is a totally solid system. Various FreeBSD committers also have this system. There is a newer [more economic] version called the Thunder K7X. http://www.tyan.com/products/html/thunderk7x.html more economic is a poor way to describe it, seeing as it has all the features, plus (1) an updated version of the AMD mp chipset and (2) a fixed onboard usb port. The K7 had a broken on-board usb (the AMD chipset had a PCI contention bug for the usb port, so the tin back panel of the board blocked out the usb, and the K7 came with a PCI usb card, which ate up one of your PCI slots. The K7X has a repaired on-board usb, so you get that PCI slot back. Hm. Do you have any details on this? I've had occasional strange USB-related things happen on this box. Of course, it runs -current which puts me into the USB danger-zone enough as it is.. but what happens when this bug is triggered? Sorry it took so long, the web site I originally found it on has apparently disappeared. This link, however, describes the problem neatly: http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/24472.pdf Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
current.freebsd.org
is that machine dead? Is it still the source of current snaps? I need to re-install (having booting problems between old version of FreeBSD and new one, easiest fix is just to re-install) and I want to know where to go for a snap of current. Anyone got one? Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current.freebsd.org
On Sun, 7 Jul 2002, David W. Chapman Jr. wrote: On Sun, Jul 07, 2002 at 11:28:30PM -0400, Chuck Robey wrote: is that machine dead? Is it still the source of current snaps? I need to re-install (having booting problems between old version of FreeBSD and new one, easiest fix is just to re-install) and I want to know where to go for a snap of current. Anyone got one? Have you tried the jp site? It should be on the list of the ftp sites from sysinstall. Last I checked you could ftp install via ftp from the jp site that hosted the latest snaps. Nope. I checked ftp,ftp2, and ftp3.jp.freebsd.org, and the best they had was a copy of the old 5.0DP1 release. That's months old now, I don't want to install that unless I must. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current.freebsd.org
On Sun, 7 Jul 2002, David O'Brien wrote: On Sun, Jul 07, 2002 at 11:28:30PM -0400, Chuck Robey wrote: is that machine dead? It's dead Jim. I've asked [EMAIL PROTECTED] to CNAME current and releng4 to the .jp snap server. Perhaps a reminder to hostmaster by someone else would help. Ohhhkay. The .jp site I found stopped making snaps on 6/21. Seeing as current only stabilized in the last day or so, I think first I'll write them and ask if it's going to start back up again. Manfred Antar told me about ftp.kddlabs.co.jp, which is the good site. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current.freebsd.org
On Mon, 8 Jul 2002, David O'Brien wrote: On Mon, Jul 08, 2002 at 12:32:21AM -0400, Chuck Robey wrote: Ohhhkay. The .jp site I found stopped making snaps on 6/21. Seeing as current only stabilized in the last day or so, I think first I'll write them and ask if it's going to start back up again. They never stopped, `make release' has been broken. Just like current.freebsd.org there are holes in snapshots. :-P current.freebsd.org works again now (it's been pointed at the Japanese site, which has up-to-date snaps available). Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Whatever happened to CTM?
On Wed, 21 Mar 2001, Stephen McKay wrote: unfortunatly my provider cut me off and I just got some access back, but not for the location the ctm machine is located at. At this time I do not know yet when it will have access again. Surely FreeBSD Inc (or whatever it is that owns the freebsd.org machines) could spring for a box. Assuming Ulf is still keen, it shouldn't be too hard for him to remote administer it. I've already announced this on the ctm-announce list, but in case some aren't subscribed, a new host has been located for ctm, and I expect it won't take too long to get it back up, hopefully by this weekend sometime. If Ulf's reading this, giving me a change to recover some files from the old host would be appreciated, if it's possible. I've mailed Ulf separately twice, but gotten no response. If the files just aren't any longer available, I will have to make do, it would make at least one item easier, is all. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (bsd)patch vs ports
On Wednesday, November 27, 2013 11:21:58 AM Andriy Gapon wrote: When building ports on head I sometimes see messages like the following during a patch phase: === Applying FreeBSD patches for firefox-25.0_1,1 No such line 262 in input file, ignoring === Applying NSS patches No such line 194 in input file, ignoring No such line 658 in input file, ignoring No such line 52 in input file, ignoring No such line 45 in input file, ignoring Is this a cause for concern? Do those messages mean that potentially important patches are not actually applied? Well.. If it compiles, then no, those patches were probably not important. Security fixes are usually done upstream by the vendor. Honestly, it appears that someone left old patch files, and those patches may no longer be needed for firefox to compile on FreeBSD. break19 ___ 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: Heavy I/O blocks FreeBSD box for several seconds
On Jul 7, 2011, at 3:51 PM, Hartmann, O. wrote: This is quibbling. On heavy loads on networ, disk et cetera, isn't there always and also a CPU bound load? No. Properly written software blocks when waiting on network or disk I/O, and doesn't sit there spinning in a busy-wait consuming CPU until it actually gets more work to do. See select(2), kqueue(2), and friends. Regards, -- -Chuck ___ 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: Console problem with ALT-F# keys
Hi--
On Aug 25, 2011, at 5:56 PM, Pegasus Mc Cleaft wrote:
I am running FreeBSD 9.0-BETA1 r225125 compiled with LLVM on a Xeon
processor (CPUTYPE=core2 and CFLAGS= -mmmx -msse -msse2 -msse3 -O2
-fno-strict-aliasing -pipe)
The FreeBSD kernel doesn't use MMX or SSE by explicit design choice. See
sys/conf/kern.mk:
# [ ... ] Explicitly prohibit the use of SSE and other SIMD
# operations inside the kernel itself. These operations are exclusively
# reserved for user applications.
#
.if ${MACHINE_ARCH} == i386 ${CC} != icc
CFLAGS+=-mno-align-long-strings -mpreferred-stack-boundary=2 \
-mno-mmx -mno-3dnow -mno-sse -mno-sse2
INLINE_LIMIT?= 8000
.endif
Trying to override the default compiler flags to force it to use MMX/SSE is
simply not going to work.
Regards,
--
-Chuck
___
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: Problems booting 9.0-BETA1 memstick
On Sep 1, 2011, at 12:00 PM, Matt Thyer wrote: Shouldn't we use MBR partitioning instead of GPT for the memstick image ? They aren't exclusive. Anything which doesn't understand GPT should fall back to the 'protective' MBR kept inside the GPT format... Regards, -- -Chuck ___ 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: HEADS UP: ports/ and 10.0-CURRENT
Hi-- On Sep 27, 2011, at 11:50 AM, Gleb Kurtsou wrote: It's more exciting than that. FreeBSD = 10 is already seized by Apple :) http://www.google.com/codesearch#search/q=__FreeBSD__%5CW%2B10type=cs MacOS X doesn't define __FreeBSD__ either in CPP macros or the system headers: % touch foo.h; cpp -dM foo.h | grep __FreeBSD__ % cpp --version i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Regards, -- -Chuck ___ 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: System headers with clang?
On Oct 11, 2011, at 6:59 AM, Larry Rosenman wrote: We will NOT support clang as the compiler for lsof unless the system headers work the same way as gcc's do. That apparently means you won't support clang then, because it's not intended to be (or ever going to be) fully bug-for-bug compatible with GCC. In this case, at least, clang is reporting legitimate issues which should be fixed, even if folks continue to build lsof with GCC from now until the end of days. To echo a word someone else just used, I'm baffled as to why you would hold such a position. Regards, -- -Chuck ___ 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
make installworld fails on releng9
I had some issues while running make installworld after I sync'd to the latest releng9, on my RC1 install. Now, it appears to failed, while trying to create some links, chfn chsh ypchpass ypchfn ypchsh. These are supposed to be hardlinked to /usr/bin/chpass, except that, since the other files already exist, and are immutable, make installworld was unable to do anything, so I wound up removing the immutable flag on these files and re- running make installworld. I didn't see any mention of this little.. issue, in UPDATING, or in the - current mailing list (yes, I know, 9.0 is no longer technically, current, but since it isn't released yet, I figure it's close enough) -- Chuck Burns ___ 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: make installworld fails on releng9
On Saturday, October 29, 2011 1:13:58 AM Benjamin Kaduk wrote: Are you running installworld in single-user mode? What is the value of kern.securelevel? -Ben Kaduk Yes, I was running in single-user mode, and kern.securelevel was never modified, and is currently showing as -1 Also, I am running zfs root, if that makes a difference -- Chuck Burns We have the right as individuals to give away as much of our own money as we please in charity; but as members of Congress we have no right to appropriate a dollar of the public money. - Davy Crockett ___ 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: /sys/amd64/conf/DEFAULTS
On Tuesday, November 08, 2011 02:12:58 PM Niclas Zeising wrote: From my understanding of things, the DEFAULTS kernel configuration file is automatically included into the build by config(8). There is no need to include it into the generic using the include statement. It was first added 6 years ago, on October 27 2005. Regards! Not sure if you already know this, or not but another thing to keep in mind, if a module is not mentioned, or is commented out, then it will still be built, just not included into the monolithic kernel. If you were already aware of this, then my apologies. Chuck ___ 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: MAXLOGNAME + /etc/group + chkgrp invalid character @
On Nov 8, 2011, at 3:47 PM, Dan The Man wrote: In the daily cron Daily run output email always get the following: Verifying group file syntax: chkgrp: /etc/group: line 3: '@' invalid character chkgrp expects group names to consist of characters in isalnum(). Could we modify system to support email addresses as usernames. Sure, that's why FreeBSD comes with source code. You can modify anything you like. :-) However, if you want to use a domain-aware login mechanism, Kerberos is in the base system, and SASL and LDAP are available in ports. You're not going to break anything allowing @ into the list of characters which pw(8) likes, but the flatfile passwd and group files are not hierarchical the way domain-aware network identity systems are. A secondary issue is that there is rarely a one-to-one relationship between email addresses and users; many email addresses are aliases which expand either to a different username, or even to multiple users. From my testing it works fine, even with Daily run output complaining I can still su to user i added in wheel group. We'd need to fix ckkgrp source, adduser source, and making move to: #define MAXLOGNAME 256 in /usr/src/sys/sys/param.h You can do that also, but I think you'll break compatibility with NIS/YP. You might not care, but don't be surprised if you find that folks aren't willing to adopt this change back into FreeBSD-- I've seen a few people wanting to increase MAXLOGNAME since 2003 or so. Regards, -- -Chuck ___ 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: MAXLOGNAME + /etc/group + chkgrp invalid character @
Hi--
On Nov 8, 2011, at 4:32 PM, Dan The Man wrote:
On Tue, 8 Nov 2011, Chuck Swiger wrote:
On Nov 8, 2011, at 3:47 PM, Dan The Man wrote:
In the daily cron Daily run output email always get the following:
Verifying group file syntax:
chkgrp: /etc/group: line 3: '@' invalid character
chkgrp expects group names to consist of characters in isalnum().
K so thats a simple fix where it does that check.
usr.sbin/chkgrp/chkgrp.c, line ~117:
for (cp = f[0] ; *cp ; cp++) {
if (!isalnum(*cp) *cp != '.' *cp != '_' *cp != '-'
(cp f[0] || *cp != '+')) {
warnx(%s: line %d: '%c' invalid character, gfn, n, *cp);
e++;
}
}
Add a *cp != '@' clause to the if statement.
Could we modify system to support email addresses as usernames.
Sure, that's why FreeBSD comes with source code.
You can modify anything you like. :-)
However, if you want to use a domain-aware login mechanism, Kerberos is in
the base system, and SASL and LDAP are available in ports. You're not going
to break anything allowing @ into the list of characters which pw(8)
likes, but the flatfile passwd and group files are not hierarchical the way
domain-aware network identity systems are.
A secondary issue is that there is rarely a one-to-one relationship between
email addresses and users; many email addresses are aliases which expand
either to a different username, or even to multiple users.
Wish you would elaborate abit more here, what I have found is email addresses
tend to make the best usernames, people can remember them :)
They are unique, and you solve 2 problems right away:
a) they can actually remember their username
b) they aren't having to pick through a million different taken usernames
they have to pick on their own, which is frusterating way people often do
signups.
If you've got a database of millions of users, you're definitely functioning in
a different realm than what /etc/passwd and /etc/group were designed for. :-)
Anyway, the idea is that you should be able to define multiple hierarchy levels
for your identity database, which NIS+, NetInfo, Kerberos, and LDAP
(kinda-sorta) can support. This lets you define an identity either at the root
level, which is visible everywhere, or in subdomains from root, which means the
identity is valid only within that subdomain but not in other subdomains-- and
johndoe in one subdomain can be entirely different than johndoe in some
other domain. (If you want johndoe the same everywhere, you'd define it at
root instead.)
That's just a bare-bones explanation, but a more complete one would likely
approach book-length. :-)
You might not care, but don't be surprised if you find that folks aren't
willing to adopt this change back into FreeBSD-- I've seen a few people
wanting to increase MAXLOGNAME since 2003 or so.
I've talked to many sys admins as well, that are all modifying the code to
the kernel for a decade now on every new make buildworld, would be nice to
see it mainstream.
Sure, you can find examples or counterexamples if you look for 'em...
Regards,
--
-Chuck
___
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: Use of newest version number such as 10.0 instead of current
On Friday, November 11, 2011 07:29:46 AM Mehmet Erol Sanliturk wrote: -(snipped stuff)- This is preventing testing and / or using efforts . I know , it is possible to rename local link names , but everyone is not so much knowledgeable . Thank you very much . Mehmet Erol Sanliturk Quite honestly, if someone isn't that knowledgeable, then they probably shouldn't be running current. In fact, the handbook even states that. I don't really see an issue here. -current is a bleeding edge development release, that must be built from source, and SHOULD always point to the latest source code. If you are using pkg_add -r pkgname to install software, on anything but release versions, you should expect breakage. If you do not wish to build from source, then you should probably stick to release versions. Chuck Burns ___ 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: Use of newest version number such as 10.0 instead of current
On Friday, November 11, 2011 08:17:52 AM you wrote: -snip- My sentence is NOT about Current , but 9.0 RC1 . Perhaps , you will NOT say , if a person is NOT knowledgeable , he should NOT use 9.0 RC1 . If you use a proper RC, then pkg_add will work until a new RC, and since there is no binary upgrade path for anything other than releases, you will need to reinstall, with the newly released RC. -snip- Up to now , my most disappointed situation is that , there is NO any tendency to lower required expertise level to use FreeBSD . Such an approach is confining FreeBSD to a small number of elite users when compared to millions of Linux users let alone hundred millions of some other operating systems which they are approaching to billions when version users are summed in spite of paying money also . GhostBSD, PCBSD are two options for lower expertise and, as such, are billed as desktop versions of FreeBSD. FreeBSD itself (as well as the other BSDs) is a minimalistic OS, where you can build your own system, making it either into a server, workstation, or even into a desktop system if you so desire. If you want something with point-n-click ease of use, go use one of the two desktop-oriented versions. Both GhostBSD, and PCBSD are just a desktop environment built on top of FreeBSD. PCBSD even has a 9.0 RC out now as well, if you're into testing. PCBSD uses the kde environment, and GhostBSD uses the gnome 2.32 environment. If you want something else, feel free to create your own. There is nothing in the BSD license that prevents you from doing that. Instead of complaining that SOMEONE ELSE should do something that YOU want done, why not just do it yourself. In other words, put up, or shut up. :) Chuck Burns ___ 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: spamcop abuse of power
On Nov 17, 2011, at 5:37 AM, Dan The Man wrote: Today I had an unhappy unix student try to submit an assignment to me and could not. Spamcop has decided to go off blacklisting all yahoo/shaw etc servers worldwide. I'm seeing about 40 spams per month from Yahoo's *.bullet.mail.sp2.yahoo.com; they're almost certainly the single largest source of spammy email I get. Example Solution Postfix: remove: reject_rbl_client bl.spamcop.net from your smtpd_recipient_restrictions line until they fix their abuse issues. I probably wouldn't use any RBL for pass/fail blocking-- aside from postmaster.rfc-ignorant.org, maybe, and even that one likely needs some whitelisting if your mail system has a non-trivial # of users-- instead, consider using RBLs for scoring. Regards, -- -Chuck ___ 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: Clang as default compiler November 4th
On Fri, 14 Sep 2012 15:23:19 -0500 Brooks Davis bro...@freebsd.org wrote: On Thu, Sep 13, 2012 at 09:10:24AM -0700, Steve Kargl wrote: On Thu, Sep 13, 2012 at 09:32:12AM -0600, Ian Lepore wrote: On Wed, 2012-09-12 at 19:08 -0700, Steve Kargl wrote: In regards to my initial post in this thread, I was just trying to assess whether any benchmarks have been performed on FreeBSD for floating point generated by clang. Other than the limited testing that I've done, it appears that the answer is 'no'. We have src/tools/tests/testfloat and src/tools/regression/lib/msun. I know nothing about the former (just noticed it for the first time). The latter I think is a set of correctness tests rather than performance tests. It's quite clear that the clang proponent have not tried to run src/tools/regression/lib/msun. % setenv CC clang % make | grep warning | wc -l 1354 % make clean % make | tee make.log % head -20 make.log clang -O2 -pipe -march=opteron -O0 -lm test-cexp.c -o test-cexp test-cexp.c:49:14: warning: pragma STDC FENV_ACCESS ON is not supported, ignoring pragma [-Wunknown-pragmas] #pragma STDC FENV_ACCESSON ^ test-cexp.c:183:2: warning: expression result unused [-Wunused-value] testall(0.0, 1.0, ALL_STD_EXCEPT, 0, 1); ^~~ test-cexp.c:98:7: note: expanded from macro 'testall' test(cexp, x, result, exceptmask, excepts, checksign); \ ^ test-cexp.c:87:11: note: expanded from macro 'test' assert(((func), fetestexcept(exceptmask) == (excepts)));\ ^ /usr/include/assert.h:54:21: note: expanded from macro 'assert' #define assert(e) ((e) ? (void)0 : __assert(__func__, __FILE__, \ ^ test-cexp.c:183:2: warning: expression result unused [-Wunused-value] testall(0.0, 1.0, ALL_STD_EXCEPT, 0, 1); ^~~ test-cexp.c:99:7: note: expanded from macro 'testall' % tail -20 make.log test-trig.c:69:11: note: expanded from macro 'test' assert(((func), fetestexcept(exceptmask) == (excepts)));\ ^ /usr/include/assert.h:54:21: note: expanded from macro 'assert' #define assert(e) ((e) ? (void)0 : __assert(__func__, __FILE__, \ ^ 74 warnings generated. clang -O2 -pipe -march=opteron -O0 -lm test-fenv.c -o test-fenv test-fenv.c:82:14: warning: pragma STDC FENV_ACCESS ON is not supported, ignoring pragma [-Wunknown-pragmas] #pragma STDC FENV_ACCESS ON ^ 1 warning generated. for p in test-cexp test-conj test-csqrt test-ctrig test-exponential test-fma test-fmaxmin test-ilogb test-invtrig test-logarithm test-lrint test-lround test-nan test-nearbyint test-next test-rem test-trig test-fenv; do /usr/src/tools/regression/lib/msun/$p; done Assertion failed: (((cexp), fetestexcept((0x04 | 0x20 | 0x01 | 0x08 | 0x10)) == (0))), function test_nan, file test-cexp.c, line 211. 1..7 ok 1 - cexp zero Abort trap (core dumped) *** [tests] Error code 134 Stop in /usr/src/tools/regression/lib/msun. Prompted by this post, I did a bit of testing and it looks like we have two classes of failures that need to be investigated. First, some tests are failing with a gcc compiled world and clang compiled test code. They seem to mostly be unexpected fp exception state when testing with NaNs. I suspect that someone more knowledgeable in this area could come up with a reduced test case and explication of what clang is doing wrong pretty quickly. The second class is tests that fail when libm is compiled using clang. I've not investigate those at all. I'd tend to guess that we have a wider range of issues there. This is clearly an area we need more focus on before a switch to clang. To a point I would be OK with it delaying the switch to work these issues, but as with C99 long double support we can't let the quest for perfection delay us indefinitely. -- Brooks Also, you probably want to be sure you are running these tests against clang 3.2, not the clang that is in base, since -that- is the version that will be going live, right? -- Chuck Burns brea...@gmail.com ___ 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: [HEADSUP] Upcoming GNU sort removal
On 10/4/2012 11:26 AM, C. P. Ghost wrote: BTW, its good to see BSD-licensed tools gradually replacing GNU tools in base. Though I'd have really preferred to see resources directed towards getting XEN/Dom0 support to FreeBSD/amd64. This really needs some love, IMHO. ;-) Gabor Thanks, -cpghost. response type=sarcastic Then give it some love yourself! No one is stopping you! :) /response -- Chuck Burns brea...@gmail.com ___ 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: Fw: FreeBSD in Google Code-In 2012? You can help too!
On 10/24/2012 4:57 PM, Michael Vale wrote: -Original Message- From: Michael Vale Sent: Thursday, October 25, 2012 8:57 AM To: Adrian Chadd Subject: Re: FreeBSD in Google Code-In 2012? You can help too! oh i only replied to you, not the thread. I have some ideas though... -Original Message- From: Adrian Chadd Sent: Thursday, October 25, 2012 8:29 AM To: Michael Vale Subject: Re: FreeBSD in Google Code-In 2012? You can help too! :-) Cross-compiling ports is a big issue though. I'm going to smack people over the head about it at MeetBSD. That's a good idea, fix ports so that one can compile 32bit ports on FreeBSD amd64. If that's not what you meant, then ok.. but it's still a good idea for a task. :P -- Chuck Burns brea...@gmail.com ___ 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: polling's future [was: Re: Dynamic Ticks/HZ]
On Tuesday, November 06, 2012 12:36:46 PM Andre Oppermann wrote: On 06.11.2012 12:30, Luigi Rizzo wrote: On Tue, Nov 06, 2012 at 11:23:34AM +0100, Andre Oppermann wrote: ... Hi Luigi, do you agree on polling having outlived its usefulness in the light of interrupt moderating NIC's and SMP complications/disadvantages? yes, we should let it rest in peace. Thank you for this non-complicated answer. :-) I worry about what happens for those people who would be running FreeBSD on older equipment where polling might still make sense. Do we throw them under the bus? -- Chuck Burns ___ 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: 9.1-RC3 feels okay :-)
On 11/7/2012 10:27 AM, Warren Block wrote: On Wed, 7 Nov 2012, CeDeROM wrote: Isn't this a Xorg bug then? When I have no configuration file Hal should provide the configuration, so sooner or later the mouse should start moving... but is does not.. Do I get http://www.wonkity.com/~wblock/docs/html/aei.html correct that when I am using xorg.conf there is no need for Hal and when I am using Hal there is no need for xorg.conf? Not quite, no. xorg.conf is the configuration file for xorg-server. It can do a lot more than just identify input devices. Option AutoAddDevices Off tells xorg-server: even if hal is present and running, don't use it to detect input devices. AFAIK, hal is not used by xorg-server for anything else. All other autoconfig (video card detection, monitor detection, it even has its own built-in input device detection) is done by the xorg server itself. ___ 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 And, for the record, HAL is NOT needed in recent xorg-server, even for running without an xorg.conf file. This was not the case for a while, but with recent xorg-server, hal is NOT NEEDED even for autodetection. It has been deprecated by the linux folks for a few years now. -- Chuck Burns brea...@gmail.com ___ 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: Failed to switch consoles in 9.0-RC3
On 11/8/2012 7:40 AM, CeDeROM wrote: Hello :-) When switching from Xorg (installed from package by portinstall) to console I got this bad behavior and constantly beeping speaker. On the console, when it switched, I got this message 3 times: Failed to switch console (Invalid agrument) There are no more messages or debug information to better describe the problem sorry... Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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 Known issue. KMS prevents console switching, still. KMS is not quite ready for use, but works fine as long as you stay in Xorg -- Chuck Burns brea...@gmail.com ___ 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: sysutils/lsof Author Question (for CLANG)....
On 11/8/2012 8:17 AM, Andriy Gapon wrote: on 08/11/2012 01:00 Greg 'groggy' Lehey said the following: On Wednesday, 7 November 2012 at 16:35:22 -0600, Larry Rosenman wrote: On 2012-11-07 15:39, Greg 'groggy' Lehey wrote: On Wednesday, 7 November 2012 at 10:32:23 -0500, Benjamin Kaduk wrote: Once again, attempting to use kernel internals outside of the supported interfaces is just asking for trouble; I do not understand why this message is not sinking in over the course of your previous mails to these lists, so I will not try to belabor it further. IIRC lsof is a special case that always needs to be built with intimate knowledge of the kernel. This is VERY true. Since some of the information lsof uses has no API/ABI/KPI/KBI to get, it grovels around in the kernel. And until those interfaces are provided, I think this is legitimate. If there's anybody out there who hasn't used lsof, you should try it. It's good. Just curious why lsof can't use interfaces that e.g. fstat/sockstat/etc use? Those base utilities do not seem to experience as much trouble as lsof. BTW, it is still beyond me why VOP_WRITE could be of any interest to userland code even for such a utility as lsof. Honestly, if you do not like the way lsof does things, I'm sure patches are welcome.. -- Chuck Burns brea...@gmail.com ___ 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
