Re: Dual console don't work
Bernd Walter wrote: I use -h -D in /boot.config Today I wanted to boot with monitor and keyboard. All I got was the first stage of the news boot loader on vga and seriel. The prompt itself goes only on seriel so there wasn't a chance to switch the console back to vga without a terminal. This is deliberate, FWIW. The old bootblocks privately define RB_DUAL, and you won't find it in sys/reboot.h with the other flags like RB_SINGLE, RB_SERIAL, etc. For compatibility, the new bootblocks honor the -D option, as far as their own behavior goes. But they don't pass RB_DUAL, as one of the howto flags, on to either the kernel or /boot/loader. So -D is preserved only as a backward-compatibility option (and therefore applies only to stage two of the bootstrap), and /boot/loader knows nothing about it. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: btokup().. patch to STYLE(9) (fwd)
-Original Message-
From: Mikhail Teterin [SMTP:m...@misha.cisco.com]
Sent: Monday, February 01, 1999 9:41 PM
To: curr...@freebsd.org
Subject: Re: btokup().. patch to STYLE(9) (fwd)
=Whilst the official codebase may be under the control of a select
=group of committers, the code should be capable of being understood
by
=anyone who is reasonably proficient with C.
Depends on your definition of reasonably, Mr. Special Counselor...
[ML]
I see no cause for name calling.
A Reasonably Proficient programmer is the one who
writes correct code. The one who writes maintainable
correct code is Very Proficient. The one who writes
well-documented maintainable correct code is a target
for a marriage proposal :)
Sadly, few proficient programmers program exclusively
in C/C++. Most of us have bills to pay and switch on
a drop of a hat from C to PL/I to COBOL to VisualBASIC
to Perl to FORTRAN to YouNameIt to ...
And, guess what, none of these languages have the same
operator precedence as C/C++. But they all have
parentheses. Knowledge of operator precedence as a
metric of programming proficience--ludicrous. My brain
would turn to pretzel if I had to know all the precedence
rules in all the languages that I daily have to use.
So, yes, I do use parentheses relying on assocciativity
only around addition/multiplication. Logical expressions
are handled differently in every language--some of them
do not even have short-circuiting logical operators--thus,
they will be parenthesized.
An example that was being thrown around would look like
this in my code:
/* the reason for branching */
if ( (a * b - c * d) (e / f) ) {
true_part();
}
else {
false_part();
more_false_part();
}
You will have noticed that I put braces around single
statements. This has no performance penalty--a reasonable
compiler will not create a stack frame--and helps in
maintenance.
/* copy null-terminated b to a */
for (pa = a, pb = b; (*pa = *pb) != 0; ++pa, ++pb) {
/* NOTHING */
}
Same thing here--okay, so it is a bit more verbose than
absolutely neccessary. The advantage is that the people
who are not absolutely acquainted with the syntactical
finesse of the language *can* read it and can actually
*modify* it without undue hassle.
That's what is being tirelessly debated for the last several days.
[ML] Hopefully we will come to agreement about a
reasonable metric for programmer proficiency (and
when I am at that, I can also hope for a jackpot in
lottery :)
/Marino
-mi
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Misterious message...
I'm running recent 4.0 (updated today) and when booting have an message: lo0 XXX: driver didn't set ifq_maxlen Is it dangerous or not? Sincerely, Maxim To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Persistent files under /usr/obj
do a chflags -R noschg /usr/obj before you rm it Uh no... do the 'rm' first, tolerate the few warnings, _then_ do the chflags and then another 'rm'. It's faster on my stopwatch anyway :) /* Flamebait mode on: */ Now, shouldn't we really have a target in our makefile for this, like: make REALLYCLEAN /* Flamebait mode off: */ Due to a harddisk crash I may not have received all the mails in this thread, and may therefore have missed someone else asking this question and getting a real good answer. --- Erik H. Bakke Habatech AS e...@habatech.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: btokup().. patch to STYLE(9) (fwd)
Peter Jeremy peter.jer...@auss2.alcatel.com.au wrote: Someone wrote: You are not supposed to understand this. I'd suggest that there's a vast difference in the intended audience of the code containing the above comment and FreeBSD. Not to mention a 20+ year gap in time. Whilst the official codebase may be under the control of a select group of committers, the code should be capable of being understood by anyone who is reasonably proficient with C. If understanding the kernel requires that you be a guru-level expert in C, then people won't bother. FreeBSD will wind up being a small collection of people trying to outdo each other in obtuseness. Don't be silly. FreeBSD is much more complicated than V6 for a whole lot of reasons that are independent of who gets to read the code and who gets to change it. Just as a starting point, the kernel has about a million lines of code compared to V6's ten thousand lines; Lions' comment about 1 lines being a comfortable amount of code for one person to understand comes to mind. The x86 architecture is vastly more complicated and baroque than the PDP11. We now have paging and networking and SMP and a whole lot of other sophisticated stuff that were completely beyond V6. The magic of swtch() is written in assembler, not C. On the other hand, what we have that the early Unix community didn't have is the Internet. We can collaborate with email, we can browse the code history with CVS, and generally benefit from a far greater level of support. Tony. -- f.a.n.finch d...@dotat.at f...@demon.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 3c589 doesn't work?
I'm using a 3c589C in a Fujitsu Lifebook 765dx, went from -release to -current about a week ago, no problem here. Aren't you supposed to use the zp driver for the 3c589 series? That's what I'm using at least. - Jason Tatem What you want is irrelevant. VC3, Inc. What you have chosen is at hand! tat...@vc3.com --Spock, Star Trek VI - On Mon, 1 Feb 1999, Alex Le Heux wrote: Hi, Is there any reason why the 3c589 in my laptop stopped working after I upgraded it to -current? During boot it now only tells me: Initializing PC-card drivers: ed Instead of 3.0-RELEASE, which says: Initializing PC-card drivers: ed ep Any ideas? Alex -- Gezeur. Ik heb gewoon al lekker met mijn zoon achter de pjoeter gezeten en hem M$ Publisher uitgelegd. Hij vond het heel interessant. Marcel en Erin To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: btokup().. patch to STYLE(9) (fwd)
Ladavac Marino once stated:
= =Whilst the official codebase may be under the control of a select
= =group of committers, the code should be capable of being understood
= by
= =anyone who is reasonably proficient with C.
=
= Depends on your definition of reasonably, Mr. Special Counselor...
= [ML]
= I see no cause for name calling.
I'm sorry, I did not mean name calling. I was making a joke
refering to the America's infamous senior public official talking
to a certain Special Counsel (or Independent Counsel).
= And, guess what, none of these languages have the same
= operator precedence as C/C++. But they all have
= parentheses. Knowledge of operator precedence as a
= metric of programming proficience--ludicrous. My brain
= would turn to pretzel if I had to know all the precedence
= rules in all the languages that I daily have to use.
I must admit, that this is the first reasonable argument I observe
in a few days of this Battle of Giants. Mostly it looks like:
-- I think, the code must be readable, therefore, we must allow
for X.
-- No, I think, the readability is very important, therefore X
should be disallowed.
= /* the reason for branching */
= if ( (a * b - c * d) (e / f) ) {
= true_part();
= }
= else {
= false_part();
= more_false_part();
= }
= You will have noticed that I put braces around single
= statements. This has no performance penalty--a reasonable
= compiler will not create a stack frame--and helps in
= maintenance.
I'd say, I do not like this :) My first move is to remove the un-needed braces
or put `else' onto the same line as the closing brace before it (I program in
TCL
a lot). But we all 've read enough of this already.
The discussion is no longer interesting because of its subject, but rather
because of its style. And this is a whole different branch of science...
-mi
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
make world failure (2 days in a row)
Hi, The following says it all... Thanks, John === ru cd /usr/doc/ru ; make afterdistribute DESTDIR=/R/stage/trees/bin === ru/FAQ cd /usr/doc/ru/FAQ ; make install DESTDIR=/R/stage/trees/doc SHARED=copies install -c -o root -g wheel -m 444 FAQ*.html /R/stage/trees/doc/usr/share/doc/ru/FAQ if [ -f /usr/doc/ru/FAQ/FAQ.ln ]; then (cd /R/stage/trees/doc/usr/share/doc/ru/FAQ; sh /usr/doc/ru/FAQ/FAQ.ln); fi install -c -o root -g wheel -m 444 FAQ.roff /R/stage/trees/doc/usr/share/doc/ru/FAQ === zh cd /usr/doc/zh ; make afterdistribute DESTDIR=/R/stage/trees/bin === zh/FAQ cd /usr/doc/zh/FAQ ; make install DESTDIR=/R/stage/trees/doc SHARED=copies install -c -o root -g wheel -m 444 FAQ*.html /R/stage/trees/doc/FAQ usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 3c589 doesn't work?
On Tue, 2 Feb 1999, Jason Tatem wrote: I'm using a 3c589C in a Fujitsu Lifebook 765dx, went from -release to -current about a week ago, no problem here. Aren't you supposed to use the zp driver for the 3c589 series? That's what I'm using at least. pccard (compiled in the kernel, without zp) uses ep for 3c589 cards.. without pccard zp is used. And well my 3c589D works both ways. Though I could not get a 3c589B card working , but that was with 2.2.5 PAO dont know if that card still doesnt work.. /Khaled, Telia Network Services Mail: kha...@telia.net Cell: 070-6785492 Work: 08-4567281 :hacker: /n./ [originally, someone who makes furniture with an axe] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 3c589 doesn't work?
Actually, you should use the pccard driver. The zp doesn't support multicast and a couple of other things aren't as clean. Used to work fine over here, although I haven't tried it recently. Cheers, Chris On Tue, Feb 02, 1999 at 08:07:12AM -0500, Jason Tatem wrote: I'm using a 3c589C in a Fujitsu Lifebook 765dx, went from -release to -current about a week ago, no problem here. Aren't you supposed to use the zp driver for the 3c589 series? That's what I'm using at least. -- Be careful of reading health books, you might die of a misprint. -- Mark Twain [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
GUI for cdrecord
does anybody know of a decent GUI for cdrecord that works on -current? XCDRoast is pretty hardcoded for linux. -- Jim Joseph Email: j...@phoenix.net The rule is, jam to-morrow and jam yesterday, but never jam today. -- Lewis Carroll To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 3c589 doesn't work?
I loaded the generic pccard support + ep driver, and that works fine so far using -current from about middle of last week. - Jason Tatem What you want is irrelevant. VC3, Inc. What you have chosen is at hand! tat...@vc3.com --Spock, Star Trek VI - On Tue, 2 Feb 1999, Christian Kuhtz wrote: Actually, you should use the pccard driver. The zp doesn't support multicast and a couple of other things aren't as clean. Used to work fine over here, although I haven't tried it recently. Cheers, Chris On Tue, Feb 02, 1999 at 08:07:12AM -0500, Jason Tatem wrote: I'm using a 3c589C in a Fujitsu Lifebook 765dx, went from -release to -current about a week ago, no problem here. Aren't you supposed to use the zp driver for the 3c589 series? That's what I'm using at least. -- Be careful of reading health books, you might die of a misprint. -- Mark Twain [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Scsi chatty'ness can be good..
Hopefully this isn't becoming a democracy, but just in case, the verbose reporting is a valued feature here. -- Geoff Buckingham Demon Internet To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem)
On Mon, 1 Feb 1999, Matthew Dillon wrote: :So, never do stupid things as root; that's always my moto. Well, so I did :something stupid as root, but it wasn't inherrently *that* stupid, at :least not stupid enough to require a hard boot :). Below is the source :... :Except I decided to test that feature that overrides the device filename :(normally /dev/audit). Instead, I chose /dev/mem. Don't do that (ouch). :The machine began to churn -- ok, so the buffer expands as necessary :without limit, which is something that will go away once I actually write :... :swap_pager_getswapspace: failed : :from the kernel. And needless to say, it loops fairly tightly and we :... Uh. Mm.. Hmm :-) i = read(fd, size, sizeof(size)); ... malloc(bufsize * sizeof(char)) i = read(fd, buf, bufsize); When you are reading /dev/mem, 'size' can turn out to be anything. You are then allocating 'size' bytes ( which could be some insane value ). Finally, you try to read() from /dev/mem into the buffer the same insane value. The system is almost certainly trying to kill this process, but it can't because the process is stuck in an uninterruptable system read() of an insane amount of data. I don't think there is anything to 'fix' here. The system is making the best of a bad situation. Perhaps, though, we could test for signal 9 within the insanely huge read() loops and pop out. I did a signal test inside /dev/urandom (probably yet to be committed, but Bruce said he was going to.) There's no reason we can't do one here, but we may have to break read()s of /dev/mem to smaller chunks to allow for this. Maybe there is a better way to break out of a running system call, and have it return immediately, but I haven't seen one. -Matt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem)
On Mon, 1 Feb 1999, Matthew Dillon wrote: :So this probably works for non-root users on files like /dev/zero that can :produce as much data as you might be interested in, suggesting a fun :denial of service attack for the bored and/or insane. Presumably the datasize limit can be used restrict the size of the process. Matt, Does datasize limit the number of backed pages, or the amount of address space used by a process? I.e., can I grow myself a large chunk of address space using mmap to the same region of a file, and then read into that large chunk (presumably larger than the cache size if I want to be nasty)? If datasize only affects backed pages, then we can still do nasty large copies; if it affects address space, then nasty large copies are limited to the size of the writable address space (if using readv) or the size of the largest contiguous writable space (if using read). Robert N Watson rob...@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon Universityhttp://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem)
:Matt, : :Does datasize limit the number of backed pages, or the amount of address :space used by a process? I.e., can I grow myself a large chunk of address :space using mmap to the same region of a file, and then read into that :large chunk (presumably larger than the cache size if I want to be nasty)? :If datasize only affects backed pages, then we can still do nasty large :copies; if it affects address space, then nasty large copies are limited :to the size of the writable address space (if using readv) or the size of :the largest contiguous writable space (if using read). : : Robert N Watson : :rob...@fledge.watson.org http://www.watson.org/~robert/ :PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C The 'datasize' limit does not effect mmap(), only brk/sbrk. So, in fact, I believe you can bypass the datasize limit by allocating anonymous memory using mmap(). This is probably a bug. We should either limit the mmap()able space to about the same size as the data segment limit, or keep track of the amount of anonymous mapped memory and count that in the datasize limit. Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Dual console don't work
:Bernd Walter wrote: : : I use -h -D in /boot.config : Today I wanted to boot with monitor and keyboard. : All I got was the first stage of the news boot loader on vga and seriel. : The prompt itself goes only on seriel so there wasn't a chance to switch : the console back to vga without a terminal. : :This is deliberate, FWIW. The old bootblocks privately define :RB_DUAL, and you won't find it in sys/reboot.h with the other :flags like RB_SINGLE, RB_SERIAL, etc. : :For compatibility, the new bootblocks honor the -D option, as far :as their own behavior goes. But they don't pass RB_DUAL, as one :of the howto flags, on to either the kernel or /boot/loader. : :So -D is preserved only as a backward-compatibility option (and :therefore applies only to stage two of the bootstrap), and /boot/loader :knows nothing about it. : :-- :Robert Nordier Is there a replacement for this functionality with the new bootloader? I was trying to get duel consoles working on a rack mount machine a week or two ago and met with utter failure. It was quite annoying. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Scsi chatty'ness can be good..
Geoff Buckingham wrote: Hopefully this isn't becoming a democracy, but just in case, the verbose reporting is a valued feature here. I'm pretty sure it's never going to go... The worst that seems to be threatened is that it's made an option (which is fine by me, I'd leave it turned on... All the time G)... I think one of the major advantages of *nix / linux is that it is so verbose... Maybe a new topic for -chat? G -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Scsi chatty'ness can be good..
I think one of the major advantages of *nix / linux is that it is so verbose... Maybe a new topic for -chat? G NT is just as verbose (when using the Checked build) if not more- you just don't see it because it's being dumped out a debug serial port. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
problem with vr0
I have problem with my newly bought D-link DFE530TX on my -current (which is very new). I have tested my NIC using the master/slave mode program came with my NIC with my room mate. And the results show the NIC work correctly. The most strange thing is that I can see the ethernet address of the other ip, see the following infomation. But I can't get the interface to work at all. Also, I tested replacing my de0 (which connects the outside world) with vr0. It doesn't work at all, but I can still get the ethernet address of other nodes shown in the routing table. Here are some output which might be useful to determine the problem. # dmesg | grep vr0 vr0: VIA VT3043 Rhine I 10/100BaseTX rev 0x06 int a irq 12 on pci0.19.0 vr0: Ethernet address: 00:80:c8:ef:82:09 vr0: autoneg complete, link status good (half-duplex, 10Mbps) vr0: selecting MII, 10Mbps, half duplex # ifconfig vr0 vr0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.100.2 netmask 0xff00 broadcast 192.168.100.255 ether 00:80:c8:ef:82:09 media: 10baseT/UTP (10baseT/UTP half-duplex) supported media: autoselect 100baseTX full-duplex 100baseTX half-duplex 100baseTX 10baseT/UTP full-duplex 10baseT/UTP 10baseT/UTP half-duplex # netstat -rn Routing tables Internet: DestinationGatewayFlags Refs Use Netif Expire default140.112.240.254UGSc 100 de0 127.0.0.1 127.0.0.1 UH 1 120 lo0 140.112.240/24 link#1 UC 00 de0 140.112.240.59 0:80:c8:46:1e:d4 UHLW5 1359 lo0 140.112.240.60 0:80:c8:69:96:3c UHLW5 178 de0 1114 140.112.240.2540:0:1d:ce:d3:7dUHLW 110 de0839 140.112.240.255ff:ff:ff:ff:ff:ff UHLWb 01 de0 192.168.100link#2 UC 00 vr0 192.168.100.1 0:80:c8:ef:3c:3f UHLW0 15 vr0 1158 192.168.100.2 0:80:c8:ef:82:9UHLW03 lo0 192.168.100.255ff:ff:ff:ff:ff:ff UHLWb 01 vr0 # ipfw list ipfw: getsockopt(IP_FW_GET): Protocol not available To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Dual console don't work
Matthew Dillon wrote: :Bernd Walter wrote: : : I use -h -D in /boot.config : Today I wanted to boot with monitor and keyboard. : All I got was the first stage of the news boot loader on vga and seriel. : The prompt itself goes only on seriel so there wasn't a chance to switch : the console back to vga without a terminal. : :This is deliberate, FWIW. The old bootblocks privately define :RB_DUAL, and you won't find it in sys/reboot.h with the other :flags like RB_SINGLE, RB_SERIAL, etc. : :For compatibility, the new bootblocks honor the -D option, as far :as their own behavior goes. But they don't pass RB_DUAL, as one :of the howto flags, on to either the kernel or /boot/loader. : :So -D is preserved only as a backward-compatibility option (and :therefore applies only to stage two of the bootstrap), and /boot/loader :knows nothing about it. : :-- :Robert Nordier Is there a replacement for this functionality with the new bootloader? I was trying to get duel consoles working on a rack mount machine a week or two ago and met with utter failure. It was quite annoying. Support for multiple consoles in /boot/loader is planned but not implemented yet. Mike should be able to put a timeframe on this. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: problem with vr0
Of all the gin joints in all the towns in all the world, Chia-liang Kao had to walk into mine and say: I have problem with my newly bought D-link DFE530TX on my -current (which is very new). I have tested my NIC using the master/slave mode program came with my NIC with my room mate. And the results show the NIC work correctly. The most strange thing is that I can see the ethernet address of the other ip, see the following infomation. But I can't get the interface to work at all. AG!!! I really don't want to get mad at you personally, but this is really starting to annoy me. Virtually every time anybody reports a problem, the only thing they ever say is it doesn't work. WHAT DOESN'T WORK EXACTLY!?! Describe the problem(s)!! Show us examples!! Show us error messages!! Does it catch fire?! Does it spit pea soup at you and speak in tongues?! Does it lie around the house all day and refuse to cut its hair and get a job!? WHAT!! You have not explained exactly what is going wrong. You have not explained what it is that you're trying to do which isn't working. You have not explained how you came to the conclusion that the card isn't working. Show us what happens if you type 'ping 192.168.100.1'. Don't attempt to paraphrase the error messages: quote them exactly. Does ping not illustrate the problem accurately? Fine: choose another example and show us the results. -Bill -- = -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu Work: wp...@ctr.columbia.edu | Center for Telecommunications Research Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City = It is not I who am crazy; it is I who am mad! - Ren Hoek, Space Madness = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
de0 XXX: driver didn't set ifq_maxlen
Just built a kernel from code cvsup'd last night. I get the following messages now during boot: de0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen Everything otherwise seems to be working. Are these messages indicative of a problem? Thanks -- Neal Westfall mailto:nwest...@odc.net http://www.odc.net/~nwestfal/ FreeBSD: The Power To Serve!http://www.freebsd.org/ $Id: dot.signature,v 1.2 1998/12/30 08:23:13 nwestfal Exp nwestfal $ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: de0 XXX: driver didn't set ifq_maxlen
In message pine.lnx.4.04.9902021128470.9384-100...@vorlon.odc.net, Neal Westf all writes: Just built a kernel from code cvsup'd last night. I get the following messages now during boot: de0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen Everything otherwise seems to be working. Are these messages indicative of a problem? No, the XXX: in general means Somebody should do something about this, but it is probably not a problem. The maintainers for the respective drivers will hopefully take notice and fix this buglet soon. -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: btokup().. patch to STYLE(9) (fwd)
Julian Elischer jul...@whistle.com writes: Now if I'm working on some piece of code and feel that it could do with some parens then surely KNF should be flexible enough to allow them.. I don't know how many bugs have ben revealed by adding parens and braces.. I know that one of the first things I do when looking for a bug is add as many as I can in parts of the code that are suspect. It's amazing how often it shows up the problem. As someone who has made one (1) contribution to the FreeBSD kernel, I say, go ahead and use parentheses to your heart's content. My one contribution was a patch to the kernel and Linux emulator to allow the Linux version of Allegro Common Lisp 4.3 to run under FreeBSD. :-) :-) -Fred Gilhamgil...@csl.sri.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
4GB of RAM?!
Hi all, Has anyone yet tried running -current on a Xeon with 4GB RAM installed? We're about to place an order for a Quad Xeon and would like to have 4GB of RAM installed if it is feasible and/or possible to make this work with -current. Thanks for the help, Tom To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
New boot blocks not installed on 3.0-STABLE (02/01/1999 snap)
Okay, I did an update install with 3.0-STABLE (the snap from yesterday), but the new boot blocks weren't installed, so the old boot loader keeps complaining that the kernel is the wrong format (obviously, bootloader, it's an ELF kernel). Any way to get the new boot blocks onto the drive from the kernel/mfs root disks or the fixit floppy? Thanks, Stephen Kiernan ste...@tis.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Dual console don't work
Is there a replacement for this functionality with the new bootloader? I was trying to get duel consoles working on a rack mount machine a week or two ago and met with utter failure. It was quite annoying. Support for multiple consoles in /boot/loader is planned but not implemented yet. Mike should be able to put a timeframe on this. It requires a few minutes worth of code work, support for RB_DUAL as a real boot option, and a test environment. Please contact me if you're serious about this (I've had about four flakes so far). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
[no subject]
subscribe freebsd-current To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re:
Jayson Kastens wrote: subscribe freebsd-current mailto:majord...@freebsd.org?body=subscribe freebsd-current :) -- When the people talk about troubles, the word Microsoft is the most frequently used one. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New boot blocks not installed on 3.0-STABLE (02/01/1999 snap)
Steve Kiernan wrote: Okay, I did an update install with 3.0-STABLE (the snap from yesterday), but the new boot blocks weren't installed, so the old boot loader keeps complaining that the kernel is the wrong format (obviously, bootloader, it's an ELF kernel). Any way to get the new boot blocks onto the drive from the kernel/mfs root disks or the fixit floppy? No need to. Pass /boot/loader to your old boot blocks, and it will boot normally. Then install your new bootblocks. -- Daniel C. Sobral(8-DCS) d...@newsguy.com She just looked at him over the rotating pencil like, how slow can a mammal be and still have respiratory functions? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re:
Jayson Kastens wrote: subscribe freebsd-current mailto:majord...@freebsd.org?body='subscribe freebsd-current' :) -- When the people talk about troubles, the word Microsoft is the most frequently used one. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
4.0-19990130-SNAP - ld.so not installed
Hi, I just installed the 0130 snap. The install process did not install /usr/libexec/ld.so ... I ran a make world which built and installed correctly: -- Installing legacy rtld -- cd /usr/src/libexec/rtld-aout; /usr/obj/usr/src/tmp/usr/bin/make -DNOMAN install install -c -s -o root -g wheel -m 555 -fschg -C ld.so /usr/libexec So I back-tracked to where the snap is generated. The make release process is correctly building and installing this into the snap area: /snap/release/usr/libexec/ld.so /snap/release/usr/obj/aout/usr/src/libexec/rtld-aout/ld.so but it doesn't appear to make it into the /snap/release/R/ftp area. Is this the expected/correct behavior? or am I missing something? Thanks! John To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Linux devel doesn't work with glibc libs
When trying to link, it complains about libc.os.6 vs libc.so.5. This makes life rather difficult when trying to test glide programs against my version of the /dev/3dfx driver. Can someone commit the RedHat dev system (. egcs )? Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Overview of the FreeBSD boot process, 3.1 and later
I'm in the process of preparing a document describing the FreeBSD boot process in the new age. At the moment, there's some emphasis on the loader, and probably an uneven level of detail elsewhere. Commentary is invited. http://www.freebsd.org/~msmith/FTL/bootstrap.txt -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
ppbus0: VLSI Vision Ltd PPC2 Camera MEDIA CPIA_1-20
While looking at the output from dmesg, I noticed the following which I don't remember having seen before. (Of course I might not have had the camera hooked up to this system while running FreeBSD before ;-) Probing for PnP devices on ppbus0: ppbus0: VLSI Vision Ltd PPC2 Camera MEDIA CPIA_1-20 This is actualy a Zoom/Video Cam PPC which I use under Win98 from time to time. Any chance of getting working images from this device under FreeBSD-current? How would I go about this? This system is not currently very current (Jan 14, 1999 / no pun intended) but I'm cvsup'ing as I type this... Stephen L. Palmer slpal...@netscape.net More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
How do I query system temperature probes ?
I seem to have all the hardware required for querying the temperature probes in the system (At least I can do it from the BIOS). How can I query this info ? I assume I need controller smbus0 and controller intpm0 in my kernel. But do I also need device smb0 at smbus? and/or any of the following: # ici2c network interface # iic i2c standard io # iicsmb i2c to smb bridge. Allow i2c i/o with smb commands. Once I have all this stuff in my kernel, what commands do I use to query the probes ?? My system is FreeBSD 4.0-CURRENT (of CTM 3722 - but will soon be really -CURRENT) Extract from dmesg: chip0: Host to PCI bridge (vendor=8086 device=7180) rev 0x03 on pci0.0.0 chip1: PCI to PCI bridge (vendor=8086 device=7181) rev 0x03 on pci0.1.0 chip2: Intel 82371AB PCI to ISA bridge rev 0x01 on pci0.7.0 ide_pci0: Intel PIIX4 Bus-master IDE controller rev 0x01 on pci0.7.1 chip3: Intel 82371AB Power management controller rev 0x01 on pci0.7.3 -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax:+61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: problem with vr0
I'm really sorry about this, Bill. I'll be very careful and make a recheck before sending out problem report next time. And really thank you for shouting at me instead of leaving my problem along. I did a `ping 192.168.100.1', and there is no response and no messages at all. I think the most interesting part of this is that I can see both of the lights on the hub blinking when I ping 192.168.100.1; while only the light of the other side blinks when he pings me. So we're starting to doubt the problem is the receiving function of my side. And we test again with `trafshow'. Then I found he does receive my packet and replies when I ping him, while I can only see the packets I sent out but no packets from his side. But sometimes it works for a tiny second, like the following: # traceroute i1 traceroute to i1 (192.168.100.1), 30 hops max, 40 byte packets 1 i1 (192.168.100.1) 0.720 ms * * * From: Bill Paul wp...@skynet.ctr.columbia.edu * Date: Tue, 2 Feb 1999 14:20:11 -0500 (EST) * * You have not explained exactly what is going wrong. You have not * explained what it is that you're trying to do which isn't working. * You have not explained how you came to the conclusion that the card * isn't working. Show us what happens if you type 'ping 192.168.100.1'. * Don't attempt to paraphrase the error messages: quote them exactly. * Does ping not illustrate the problem accurately? Fine: choose another * example and show us the results. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How do I query system temperature probes ?
In message 36b7ced1.96d4b...@dsto.defence.gov.au, Matthew Thyer wrote: Extract from dmesg: chip0: Host to PCI bridge (vendor=8086 device=7180) rev 0x03 on pci0.0.0 chip1: PCI to PCI bridge (vendor=8086 device=7181) rev 0x03 on pci0.1.0 chip2: Intel 82371AB PCI to ISA bridge rev 0x01 on pci0.7.0 ide_pci0: Intel PIIX4 Bus-master IDE controller rev 0x01 on pci0.7.1 chip3: Intel 82371AB Power management controller rev 0x01 on pci0.7.3 Commited code on pcisupport.c from 1.88 to 1.89 will break it. If intpm.h is not included,chipset probe code is used instead of the driver probe code. Takanori Watanabe a href=http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html; Public Key/a Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A P.S I have forgotten to enclose unused variable in #undef ENABLE_ALART with #ifdef ENABLE_ALART - #endif ,so the variable may deleted when it was commited. And currently ENABLE_ALART code will not work properly. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Heads up: comitted optimization to vm_map_insert()
I've comitted an optimization to vm_map_insert() after initial tests seemed to indicate that it works. Basically it allows OBJT_SWAP objects to be optimized in addition to OBJT_DEFAULT objects already optimized in certain specific cases. However, a followup test that I had never run before had a temporary seg-fault ( i.e. it didn't repeat when I re-ran the test ). I think the seg fault may have revealed a new bug and is not related to the optimization I comitted, so I haven't backed out the commit. I am not 100% sure though, and I am testing this now. If anyone notices weird seg-faulting that didn't occur before tonight, please notify me! -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: problem with vr0
Of all the gin joints in all the towns in all the world, Chia-liang Kao had to walk into mine and say: I'm really sorry about this, Bill. I'll be very careful and make a recheck before sending out problem report next time. And really thank you for shouting at me instead of leaving my problem along. Shouting is my specialty. I get a lot of practice. I did a `ping 192.168.100.1', and there is no response and no messages at all. I think the most interesting part of this is that I can see both of the lights on the hub blinking when I ping 192.168.100.1; while only the light of the other side blinks when he pings me. What kind of hub is this? So we're starting to doubt the problem is the receiving function of my side. And we test again with `trafshow'. Then I found he does receive my packet and replies when I ping him, while I can only see the packets I sent out but no packets from his side. But sometimes it works for a tiny second, like the following: # traceroute i1 traceroute to i1 (192.168.100.1), 30 hops max, 40 byte packets 1 i1 (192.168.100.1) 0.720 ms * * Are you using any unusual networking tricks, like network address translation or firewalling or IP aliasing? People tend to forget to mention things like that. There are some things I'm curious about: - What does netstat -in show? Are there any input errors? Are there any input packets? (If the input packet counter keeps incrementing then it has to be receiving something.) - Do you see any suspicious messages when you do a dmesg to look at the kernel message buffer? The vr driver should report receive errors if it encounters any. - If you run tcpdump on the vr0 interface (tcpdump -n -e -i vr0) can you see the traffic from the other host? Try the following: # arp -d 192.168.100.1 # tcpdump -n -e -i vr0 # ping -c 5 192.168.100.1 Show us the output. -Bill -- = -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu Work: wp...@ctr.columbia.edu | Center for Telecommunications Research Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City = It is not I who am crazy; it is I who am mad! - Ren Hoek, Space Madness = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: problem with vr0
* From: Bill Paul wp...@skynet.ctr.columbia.edu * Date: Wed, 3 Feb 1999 00:24:27 -0500 (EST) * * I did a `ping 192.168.100.1', and there is no response and no messages * at all. I think the most interesting part of this is that I can see * both of the lights on the hub blinking when I ping 192.168.100.1; * while only the light of the other side blinks when he pings me. * * What kind of hub is this? It's a nonaccredited 5-port 10Bast-T hub which we used to connect outside world via another interface (my de0 and his ed0). And when we're trying to use this hub for internal connection only via both of our newly bought dfe530s, we're in trouble. * Are you using any unusual networking tricks, like network address * translation or firewalling or IP aliasing? People tend to forget to * mention things like that. There are some things I'm curious about: No, that's why I typed a `ipfw list' in the very first mail which indicates I have no firewall configuration in my kernel at all. * - What does netstat -in show? Are there any input errors? Are there * any input packets? (If the input packet counter keeps incrementing * then it has to be receiving something.) * There are some Ipkts but very few as you can see in the following. # netstat -in Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll de0 1500 Link 00.80.c8.46.1e.d4 313987 3411118717 185 2651 de0 1500 140.112.240/2 140.112.240.59313987 3411118717 185 2651 vr0 1500 Link 00.80.c8.ef.82.09 16 015804 0 0 vr0 1500 192.168.100 192.168.100.2 16 015804 0 0 * - Do you see any suspicious messages when you do a dmesg to look at the * kernel message buffer? The vr driver should report receive errors if * it encounters any. Not at all, only `vr0: promiscuous mode enabled' when starting tcpdump. * - If you run tcpdump on the vr0 interface (tcpdump -n -e -i vr0) can * you see the traffic from the other host? Try the following: * * # arp -d 192.168.100.1 * # tcpdump -n -e -i vr0 * # ping -c 5 192.168.100.1 * * Show us the output. PING 192.168.100.1 (192.168.100.1): 56 data bytes 14:32:35.481753 0:80:c8:ef:82:9 ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.1 tell 192.168.100.2 14:32:36.486348 0:80:c8:ef:82:9 ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.1 tell 192.168.100.2 14:32:36.486561 0:80:c8:ef:3c:3f 0:80:c8:ef:82:9 0806 60: arp reply 192.168.100.1 is-at 0:80:c8:ef:3c:3f 14:32:36.486625 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 192.168.100.1: icmp: echo request 14:32:37.496739 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 192.168.100.1: icmp: echo request 14:32:38.506383 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 192.168.100.1: icmp: echo request 14:32:39.516717 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 192.168.100.1: icmp: echo request --- 192.168.100.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss and here is the result of the same test done on 192.168.100.1 (with the target changed to 192.168.100.2): ping -c 5 192.168.100.2 PING 192.168.100.2 (192.168.100.2): 56 data bytes 14:36:01.999162 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:03.008614 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:04.018622 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:05.028656 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:06.038664 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:14.106056 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0800 142: 192.168.100.1.1090 192.168.100.255.111: udp 100 14:36:14.106075 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0800 142: 192.168.100.1.1090 192.168.100.255.111: udp 100 --- 192.168.100.2 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: KLD confusion..
Take the following scenario: compiled in: module A kldstat -v shows module 'A' kldload A damned thing succeeds. That's correct. There's a fundamental problem here in that there's a confusion between file names and module names. This is a basic flaw in the way that KLD was implemented (no offense to Doug; it was initially meant to be a better LKM, not necessarily a whole new ball of wax). I've taken about four different runs at a right way of doing this subsequently. I think that, with some help and advice from Doug and Peter, I'm on the right track now, but there's no hope of it being ready for 3.1. this is handleable by just not loading 'A' but what about the following: kldload 'B' where B is defined to have a dependency on 'A' and 'A' is already loaded.. A get's loaded again.. leading to REALLY strange behaviour if the kernel is talking to one copy of A and B is talking to the other. That's definitely not correct behaviour, but again it's because the dependancy is implemented as a NEEDED reference to a *file*, not a module. I've had a look at the code, but I think this would be a 20 minute thing for the right person, rather than a 2 day thing for me... It's been about 2 months for me so far, so I guess either I'm not the right person, or it's not that easy. I can't see a right way of fixing it short of completely separating files and modules. Here's another scenario guaranteed to flummox the current code; link A and B together in a single file, name it after A. Then have C, which depends on B, and try to load that. It's going to look for a file named after B... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
