Re: dc0: watchdog timeout
At Mon, 23 Oct 2000 22:46:26 -0400 (EDT), Andrew Gallatin [EMAIL PROTECTED] wrote: Anybody else seeing 'dc0: watchdog timeout' since SMPng integration? Yes I have. I have this several times before SMPng integration at a high load situation. But, since the integration, it occurs frequently. links. I don't have tulip cards in any PCs, so it is hard for me to tell if this is an alpha issue or an if_dc driver issue.. FreeBSD 5.0-CURRENT #15: Sat Sep 23 07:12:39 JST 2000 CPU: Pentium II/Pentium II Xeon/Celeron (451.03-MHz 686-class CPU) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 dc0: Intel 21143 10/100BaseTX port 0x10100-0x1017f mem 0x41353100-0x4135317f irq 10 at device 9.0 on pci0 dc0: interrupting at ISA irq 10 dc0: Ethernet address: 00:00:f8:07:b6:45 miibus0: MII bus on dc0 dcphy0: Intel 21143 NWAY media interface on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: ADMtek AL981 10/100BaseTX port 0xd400-0xd4ff mem 0xe780-0xe78000ff irq 16 at device 15.0 on pci0 dc0: Ethernet address: 00:90:cc:a2:fa:82 miibus0: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto -- Motomichi Matsuzaki [EMAIL PROTECTED] Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release breakage on today's -current
Maybe kernel image for kern.flp is a little bit larger than a 1.44MB floppy. *** linking BOOTMFS textdata bss dec hex filename 2613503 196388 130744 2940635 2cdedb BOOTMFS install -c -m 555 -o root -g wheel -fschg BOOTMFS /R/stage/kernels mv /R/stage/kernels/BOOTMFS /R/stage/image.kern/kernel Setting up /boot directory for kern floppy /R/stage/image.kern/kernel: 54.9% -- replaced with /R/stage/image.kern/kernel.gz sh -e /usr/src/release/scripts/doFS.sh /R/stage/floppies/kern.flp /R/stage /mnt 1440 /R/stage/image.kern 8 fd1440 disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 6. Warning: 1216 sector(s) in last cylinder unallocated /dev/rvnn1c:2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32 cpio: write error: No space left on device *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. *** FYI: You can also fetch (last 50 lines of) logfile via: URL:ftp://current.jp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-CURRENT-20001024-JPSNAP.log "finger [EMAIL PROTECTED]" will also provide you the same result. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 5. At this time, remove ALL MFS filesystems from /etc/fstab. They can be hand mounted after bootup or via a local rc startup script. You can leave them in, with option "noauto", and mount them later with "mount -a -t mfs". -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
Garrett Rooney writes: On Tue, Oct 24, 2000 at 04:49:40AM +0700, Alexey Dokuchaev wrote: Well, would not be this stepping aside from BSD startup sequence, which we all know and love? Having dozens of small files instead of pair of big ones always frustrates me when I have to work with linux. and at the very least, with a number of smaller files, assuming they're named well, you can find what you're looking for faster, and not have to dig though the one monolithic script to find out how sometihng is working. Well, we *already* have over a dozen /etc/rc.* files on -current. And we *don't* have the advantage of a consistent interface to control all the functions in /etc/rc. If you break things up, then if you need to restart the mail server, just go "/etc/rc.d/sendmail restart". dhcpd? "/etc/rc.d/sendmail/dhcpd restart". Etc. Of course, for consistency ports should be tweaked to use have the same provides/requires setup, and use rc.subr instead of the homegrown hacks. Which brings up the real downside of doing this - you have to parse rc.subr and rc.conf for *every* one of those scripts. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
One of the reasons for the numbers in the SysVR4 arena is to set the order of execution so programs which other depend upon are executed first. How does the NetBSD solve this problem. Very coolly. The main rc script runs a script named `rcorder' to generate the proper order. rc.shutdown also uses `rcorder' but reverses the ordering. Two examples are included below to show what `rcorder' uses to generate the list. These NetBSD rc files also provide "start", "stop", "restart", "status", etc. commands to assist the sysadmin. Again, *very* slick and still quite BSD-like. [ ... ] # PROVIDE: ypbind # REQUIRE: ypserv One thing that surfaced frequently in a discussion of a similar system was hard vs. soft requirements. Specifically, I can run sendmail without a syslogd running, so it is not a hard requirement, but I would prefer that it be there so that I can log things. There is a similar non-requirement for bind to start sendmail, if you have it configured to not probe interfaces, which is a good idea for dial-on-demand configurations, but to provide service to a remote system, it needs bind around. So along with "PROVIDE" and "REQUIRE", there's a need for "WANT"; it could be used as a tie-breaker for circular dependency lists, if such occur. Similarly, there is a need for a "config", as well as a "start", "stop", "restart", and "Status". For well written software, this would end up being a NOOP, since it would not cache config data, but would instead obtain it each time (an example of bad caching is sendmail source host name caching, when an ISP supports DNSUPDAT based on RADIUS audit events: if the machine claims to be named something different than the ISP assigned DNS name such that forward and reverse mappings don't match, the ISP will reject attempts to relay email from valid customers). Yeah, in a perfect world, everyone would have a static IP address, and sendmail would have a knob to make it do a gethostbyaddr() for each time that it wanted to say "HELO", etc., etc.. Oh... and the PROVIDE/REQUIRE/WANT lists really, really want to be "per service name" rather than per program name, so I could, for example, have a service that depends on "smtpserv", and not care if it was sendmail or qmail or whatever, only that there was a protocol aware program sitting on the SMTP port, waiting for a connection. Terry Lambert [EMAIL PROTECTED] --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe
Re: new rc.network6 and rc.firewall6
I like the concept of them quite a bit. I think it definitely shows some thought on how to keep the advantages of each system. I would support a move toward a system like this. One thing that would be nice is a database somewhere of which of services from /etc/rc.d are running. I think this is what "status" is for... Terry Lambert [EMAIL PROTECTED] --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
Well, would not be this stepping aside from BSD startup sequence, which we all know and love? Having dozens of small files instead of pair of big ones always frustrates me when I have to work with linux. Install a binary package that needs to be started when the system is booted and needs to be shutdown when the system is shutdown. Now consider yourself as a software vendor, such as "Oracle" or "Lucent", trying to easily distribute database software or a WinModem binary-only third-party licensed codec for FreeBSD. Despite its age, "sed" is not your friend. Terry Lambert [EMAIL PROTECTED] --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, 24 Oct 2000, Terry Lambert wrote: Well, would not be this stepping aside from BSD startup sequence, which we all know and love? Having dozens of small files instead of pair of big ones always frustrates me when I have to work with linux. Install a binary package that needs to be started when the system is booted and needs to be shutdown when the system is shutdown. That's what /usr/local/etc/rc.d/ was for for years! Put all your application-specific scripts there, but leave base-system monotilithic startup alone :-) -- WBR, DAN Fe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
Well, we *already* have over a dozen /etc/rc.* files on -current. And we *don't* have the advantage of a consistent interface to control all the functions in /etc/rc. If you break things up, then if you need to restart the mail server, just go "/etc/rc.d/sendmail restart". dhcpd? "/etc/rc.d/sendmail/dhcpd restart". Etc. Actually, the point is that writing TONS of scripts to get your work done (that's what Linux world does) always pissed me off. You have a shell script that is in fact a wrapper for another shell script, and like this in turn it goes on and on and on again. Icky! :-) I don't like how Linux smells. Why can't I simply write kill -1 `cat /var/run/sendmail.pid`? I don't consider it being sagnificantly longer than writing /etc/rc.d/sendmail restart. After all, if your typing speed is good enough, it doesn't really matter whether you type in 30 or 20 chars. -- JMHO, DAN Fe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
Alexey Dokuchaev writes: Well, we *already* have over a dozen /etc/rc.* files on -current. And we *don't* have the advantage of a consistent interface to control all the functions in /etc/rc. If you break things up, then if you need to restart the mail server, just go "/etc/rc.d/sendmail restart". dhcpd? "/etc/rc.d/sendmail/dhcpd restart". Etc. Actually, the point is that writing TONS of scripts to get your work done (that's what Linux world does) always pissed me off. You have a shell script that is in fact a wrapper for another shell script, and like this in turn it goes on and on and on again. Icky! :-) I don't like how Linux smells. Well, I don't like Linux much either. On the other hand, I hate dealing with a lots of little things all of which are just slightly different from each other even more - and the latter is what you get from /etc/rc. Why can't I simply write kill -1 `cat /var/run/sendmail.pid`? I don't consider it being sagnificantly longer than writing /etc/rc.d/sendmail restart. After all, if your typing speed is good enough, it doesn't really matter whether you type in 30 or 20 chars. You can still do that. However, do you know how to get everything listed in /etc/defaults/rc.conf to reread it's config file? With the approach being advocated, the answer is "yes" - even if you don't know whether or not the daemon in question *has* a config file. That's the thing I like about all those scripts (SysV, linux, whatever) - I didn't have to deal with cruft like that. Yeah, for some things, this means you wind up running a script that's a wrapper for the vendor-provided script to make it meet your standards. If you really hate that, ignore the vendors script and talk directly to the application - but they get little enough use that I'd rather use the vendor's API and let it be wasteful. After all, if they got a lot of use, having different interface wouldn't be a problem. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
The following patch brings the floppy size down enough to fix the problem. One is a leftover from the config file syntax change. Also, I don't know how useful INET6 is to a GENERIC kernel on todays' networks (faith gif are already removed). Index: dokern.sh === RCS file: /mirror/ncvs/src/release/scripts/dokern.sh,v retrieving revision 1.37 diff -r1.37 dokern.sh 43c43 -e '/apm0/d' \ --- -e '/apm/d' \ 46a47 -e '/INET6/d' \ 65c66 -e '/apm0/d' \ --- -e '/apm/d' \ 68a70 -e '/INET6/d' \ I'll commit this later today unless I hear objections. -John - Makoto MATSUSHITA's Original Message - Maybe kernel image for kern.flp is a little bit larger than a 1.44MB floppy. *** linking BOOTMFS text data bss dec hex filename 2613503196388 130744 2940635 2cdedb BOOTMFS install -c -m 555 -o root -g wheel -fschg BOOTMFS /R/stage/kernels mv /R/stage/kernels/BOOTMFS /R/stage/image.kern/kernel Setting up /boot directory for kern floppy /R/stage/image.kern/kernel:54.9% -- replaced with /R/stage/image.kern/kernel.gz sh -e /usr/src/release/scripts/doFS.sh /R/stage/floppies/kern.flp /R/stage /mnt 1440 /R/stage/image.kern 8 fd1440 disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 6. Warning: 1216 sector(s) in last cylinder unallocated /dev/rvnn1c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32 cpio: write error: No space left on device *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. *** FYI: You can also fetch (last 50 lines of) logfile via: URL:ftp://current.jp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-CURRENT-20001024-JPSNAP.log "finger [EMAIL PROTECTED]" will also provide you the same result. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
jwd Also, I don't know how useful INET6 is to a GENERIC kernel on jwd todays' networks (faith gif are already removed). It is mandatory for FreeBSD installation via IPv6 network (via network devices; using gif(4) pseudo interface is a rare case, so it should be removed). Please keep INET6 option as it is. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 09:51:32PM +0900, Makoto MATSUSHITA wrote: It is mandatory for FreeBSD installation via IPv6 network (via network devices; using gif(4) pseudo interface is a rare case, so it should be removed). Please keep INET6 option as it is. I agree with this sentiment.. please leave INET6 support in the GENERIC kernel. I'm sure there are better things to disable, like MFS, SYSV*, P1003_P1B and friends, and ICMP_BANDLIM. -- Will Andrews [EMAIL PROTECTED] - Physics Computer Network wench To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
will I'm sure there are better things to disable, like MFS, SYSV*, will P1003_P1B and friends, and ICMP_BANDLIM. MFS is required; don't forget we have mfsroot.flp :-) -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 10:27:50PM +0900, Makoto MATSUSHITA wrote: MFS is required; don't forget we have mfsroot.flp :-) Oh yeah... time to drink some more caffeinated pop and wake up.. -- Will Andrews [EMAIL PROTECTED] - Physics Computer Network wench To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
will I'm sure there are better things to disable,
How about removing /boot/boot[12] from floppies ?
--- src/release/Makefile.oldMon Oct 23 23:53:50 2000
+++ src/release/MakefileTue Oct 24 22:38:15 2000
@@ -821,7 +821,7 @@
mv ${RD}/kernels/BOOTMFS ${RD}/image.${FSIMAGE}/kernel
@echo "Setting up /boot directory for ${FSIMAGE} floppy"
@mkdir -p ${RD}/image.${FSIMAGE}/boot
- @cp /boot/boot[12] /boot/loader ${RD}/image.${FSIMAGE}/boot
+ @cp /boot/loader ${RD}/image.${FSIMAGE}/boot
@[ -r ${RD}/kernels/BOOTMFS.${FSIMAGE}.hints ] \
sed -e '/^hint/s/^/set /' -e '/^#/d' \
${RD}/kernels/BOOTMFS.${FSIMAGE}.hints \
Only 8kbytes, but does reduce its size.
-- -
Makoto `MAR' MATSUSHITA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
XFree86 3.3.6_3 build dies on -current
I built and installed -current on a laptop yesterday (10/23/00), and went to build XFree86 3.3.6_3 today from the ports directory. It built fine, but when you run make install, it dies, complaining of syntax errors in machine/endian.h: In file included from /usr/include/sys/wait.h:93, from vgaHW.c:44: /usr/include/machine/endian.h:72: syntax error before `__uint16_swap_unit32' /usr/include/machine/endian.h:72: syntax error before `__x' snip I've not seen this reported before, nor a work around. I was only building the VGA and SVGA servers and took the defaults on every thing else. Patrick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 3.3.6_3 build dies on -current
In file included from /usr/include/sys/wait.h:93, from vgaHW.c:44: /usr/include/machine/endian.h:72: syntax error before `__uint16_swap_unit32' /usr/include/machine/endian.h:72: syntax error before `__x' snip I've not seen this reported before, nor a work around. I don't know which is "the right thing" but adding '#include sys/types.h' in front of either the '#include sys/wait.h' in vgaHW.c or in front of the '#include machine/endian.h' in /usr/include/sys/wait.h should fix your blues. I'm guessing one is the fix and the other is a workaround, but don't know which is which =) . I'm not up to speed on include rules... DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 3.3.6_3 build dies on -current
"Rogier R. Mulhuijzen" wrote: In file included from /usr/include/sys/wait.h:93, from vgaHW.c:44: /usr/include/machine/endian.h:72: syntax error before `__uint16_swap_unit32' /usr/include/machine/endian.h:72: syntax error before `__x' snip I've not seen this reported before, nor a work around. I don't know which is "the right thing" but adding '#include sys/types.h' in front of either the '#include sys/wait.h' in vgaHW.c or in front of the '#include machine/endian.h' in /usr/include/sys/wait.h should fix your blues. I'm guessing one is the fix and the other is a workaround, but don't know which is which =) . I'm not up to speed on include rules... sys/types.h is already defined in front of sys/wait.h in vgaHW.c :( Patrick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 3.3.6_3 build dies on -current
Rogier R. Mulhuijzen wrote: In file included from /usr/include/sys/wait.h:93, from vgaHW.c:44: /usr/include/machine/endian.h:72: syntax error before `__uint16_swap_unit32' /usr/include/machine/endian.h:72: syntax error before `__x' snip I've not seen this reported before, nor a work around. I don't know which is "the right thing" but adding '#include sys/types.h' in front of either the '#include sys/wait.h' in vgaHW.c or in front of This is correct. the '#include machine/endian.h' in /usr/include/sys/wait.h should fix This is not correct. your blues. I'm guessing one is the fix and the other is a workaround, but don't know which is which =) . I'm not up to speed on include rules... -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 08:59:36AM +, Terry Lambert wrote: Oh... and the PROVIDE/REQUIRE/WANT lists really, really want to be "per service name" rather than per program name, so I could, for example, have a service that depends on "smtpserv", and not care if it was sendmail or qmail or whatever, only that there was a protocol aware program sitting on the SMTP port, waiting for a connection. i believe, from the quick look i took at this last night, that this is the way it is done, at least for mail servers, as there seems to be provisions for both sendmail and postfix (well, i remember postfix specifically, and i assume sendmail was there). -- garrett rooney my pid is inigo montoya. [EMAIL PROTECTED] you kill -9 my parent process. http://electricjellyfish.net/prepare to vi. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, 24 Oct 2000 08:15:12 -0500, Will Andrews [EMAIL PROTECTED] said: I agree with this sentiment.. please leave INET6 support in the GENERIC kernel. I'm sure there are better things to disable, like MFS, SYSV*, P1003_P1B and friends, and ICMP_BANDLIM. Um, let's only disable things that give us a useful amount of space back. (We may just be screwed at this point.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Review: offsetof/struct.h/fldoff patch.
Please test review this patch: http://phk.freebsd.dk/patch/offsetof.patch - Define offsetof() in sys/types.h for the kernel and in stddef.h for userland. #ifdef the definition in stddef.h and sys/types.h so that we don't need N identical definitions in machine/ansi.h but still allow for a MD definition there should need be. Use offsetof() instead of fldoff() Remove nested include of struct.h from sys/queue.h Remove local definitions of offsetof(). Deprecate struct.h - Files affected: Index: include/stddef.h Index: include/struct.h Index: sys/alpha/alpha/machdep.c Index: sys/dev/aac/aac.c Index: sys/dev/aac/aacvar.h Index: sys/dev/mly/mly.c Index: sys/dev/sym/sym_hipd.c Index: sys/dev/wds/wd7000.c Index: sys/i386/i386/machdep.c Index: sys/ia64/ia64/machdep.c Index: sys/kern/sysv_sem.c Index: sys/kern/uipc_usrreq.c Index: sys/net/if_stf.c Index: sys/netinet/in_gif.c Index: sys/netinet6/frag6.c Index: sys/netinet6/icmp6.c Index: sys/netinet6/in6_gif.c Index: sys/netinet6/in6_proto.c Index: sys/netinet6/raw_ip6.c Index: sys/netkey/key.c Index: sys/pc98/i386/machdep.c Index: sys/sys/queue.h Index: sys/sys/types.h -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pccard_ether wouldn't kill dhclient when card is removed
patch for revision 1.20:
--- /etc/pccard_ether Thu Oct 19 16:24:35 2000
+++ pccard_etherWed Oct 25 01:27:05 2000
@@ -46,7 +46,7 @@
interface=$1
shift
-startstop=$2
+startstop=$1
shift
case ${startstop} in
@@ -101,7 +101,7 @@
;;
# Stop the interface
*)
- /sbin/ifconfig $device delete
+ /sbin/ifconfig ${interface} delete
stop_dhcp
;;
esac
--
Motomichi Matsuzaki [EMAIL PROTECTED]
Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Review: offsetof/struct.h/fldoff patch.
Poul-Henning Kamp wrote: Please test review this patch: http://phk.freebsd.dk/patch/offsetof.patch - Define offsetof() in sys/types.h for the kernel and in stddef.h for userland. #ifdef the definition in stddef.h and sys/types.h so that we don't need N identical definitions in machine/ansi.h but still allow for a MD definition there should need be. Use offsetof() instead of fldoff() Remove nested include of struct.h from sys/queue.h Remove local definitions of offsetof(). Deprecate struct.h Tell people who get the message what to replace fldoff() with... - -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 --- X_.---._/ presently in: Budapest v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/share/examples/drivers make_device_driver.sh
Julian Elischer wrote: Over the last 3 yearrs or so I've been ignoring the device interface. but now I think it's stabilised to a point where it's worth learning about its new form. So I decided that the best way to try understand the newbus stuff (and other associated stuff) was to try use it, and I've been meaning to update these samples for a long time. This hasn't been very easy due to the lack of a high-level overview to the new stuff (Oh how I miss the days when a quick read through about 3 files told you how all the device interface worked.. of course it didn't work all that WELL but it was at least easy to comprehend) Anyhow Having scanned various files (e.g. joy.c, vn.c, if_ed.c isahint.c pnpparse.c etc.) and looked at some man (9) pages, I still don't know lots (like how do I get the damned interupts registered) but at least it LOOKs like it might create a reasnably modern ISA driver. I'd certainly like to get suggestions on how to do bits better so that I can make this a sample skeleton generator that is actually USEFUL again. Bit's I'm not sure about yet include: how do I handle non-PNP isa devices.. did I get it right? where do I add the 'hints' information? can I add it to somewhere in this file, or must I edit the main hints file (wouldn't really work for modules)? How should I register the interrupt handler? Am I deriving the softc from the dev-t in the correct manner? do split the functionality between probe and attach correctly? does the same softc persist between the two? I'm still reading but comments from the new device-meisters might save a lot of pain and confusion. If the high-level overview I've been lookign for exists somewhere but I just haven't found it, then please let me know before I mke an even bigger fool of myself..! julian julian 2000/10/24 09:45:58 PDT Modified files: share/examples/drivers make_device_driver.sh Log: First effort at bringing these up-to-date. This creates a skeleton ISA device driver. I don't pretend that it's fully correct or even opitimal but it at least creates (and compiles) a 'clean' ISA driver. Hopefully PCI/PCCARD/etc. support will be added when I understand it. Unlike the old version this just creates a module. The old one tried to create a new kernel with the driver to be tested. Revision ChangesPath 1.7 +280 -291 src/share/examples/drivers/make_device_driver.sh -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 --- X_.---._/ presently in: Budapest v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, 24 Oct 2000 07:55:42 -0400 "John W. De Boskey" [EMAIL PROTECTED] said: jwd The following patch brings the floppy size down enough to fix jwd the problem. One is a leftover from the config file syntax jwd change. Also, I don't know how useful INET6 is to a GENERIC jwd kernel on todays' networks (faith gif are already removed). Please don't remove INET6. IPv6 only install is usual thing at least around me. :-) Though the person who installs FreeBSD via IPv6 is relatively few so far, IPv6 enabled installer is important for IPv6 deployment. I heared recent NetBSD's installer has IPv6 capability, too. This is demand of these days. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
The solution is very simple. Put a statically linked Perl in /sbin, and write the startup system in Perl. For user convenience, it should have a Gnome interface and a PostgreSQL backend, so we should also put X and pgsql in /sbin. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Review: offsetof/struct.h/fldoff patch.
Please test review this patch: http://phk.freebsd.dk/patch/offsetof.patch I believe that several drivers include stddef.h to get offsetof. I think most of these files are flagged by "/* for offsetof */". -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
/me hands Chris SARCASM and /SARCASM DocWilco At 13:50 24-10-2000 -0400, you wrote: The solution is very simple. Put a statically linked Perl in /sbin, and write the startup system in Perl. For user convenience, it should have a Gnome interface and a PostgreSQL backend, so we should also put X and pgsql in /sbin. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Review: offsetof/struct.h/fldoff patch.
In message [EMAIL PROTECTED], "Justin T. Gibbs" wri tes: Please test review this patch: http://phk.freebsd.dk/patch/offsetof.patch I believe that several drivers include stddef.h to get offsetof. I think most of these files are flagged by "/* for offsetof */". Right, in fact there are many such, and they should be cleaned up as well, but right now I want to keep this patch at a manageable impact. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
In message [EMAIL PROTECTED] =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= writes: : In very recent -current, my entropy file writted and readed sucessfully, : but I got the same fortune quote again and again right after reboot! : : It means that anything writted to /dev/random not reseed it but _reset_ it : to the same default state. I see the opposite. I see that without writing to the /dev/random device I get a cons is an object that cares fortune 99+% of the time on my first login. With it, I see more decently random fortunes (but I haven't done a statistical analysis of them to see how random things are). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
In message [EMAIL PROTECTED] Leif Neland writes: : Hi there, : : I've done a very recent week's make world(S) on -current, making : and installing world and kernel go fine, but all hang on boot, : with no error codes or msgs. : : Solution: Due to changes in the random/entropy stuff, you have to reboot : the machine with "shutdown -r now" or Ctrl-alt-del, not "reboot". : : (Why do we have a separate reboot command? Couldn't it just be an alias : for shutdown -r now?) reboot should be a seprate command. It should, however, cause the shutdown scripts to run unless it is run -f. shutdown implies sending all messages to all users of NFS filesystems, which isn't desirable in many cases. At least that's why my fingers type reboot to this day: On sunos 4.0 (really Solbourne OS/MP 4.0D) in a large company these messages would scare more people than they informed... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
In message [EMAIL PROTECTED] "David O'Brien" writes: : At BSDcon Luke M showed me what the NetBSD 1.5 rc files look like. : They've moved them all to /etc/rc.d/ and made them very granular (as : SVR4, but w/o leading numbers in the filenames). The NetBSD : implementation also solved all the issues people have brought up in the : past -- dependacies, etc... : : We should just move to using their rc code. I agree. I've been using them for a while on my dog slow Windows CE machine. There were some minor issues when they were first committed to NetBSD on some platforms (due to a too early use of ps and some brokeness in ps on pmax, for example), but these were quickly resolved. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
In message [EMAIL PROTECTED] Bill Vermillion writes: : One of the reasons for the numbers in the SysVR4 arena is to : set the order of execution so programs which other depend upon : are executed first. How does the NetBSD solve this problem. The scripts themselves have the ordering dependencies. The startup system runs them in the proper order. I don't know if this is pre-computed or redone each boot. Turns out to be fairly cheap to do. I'd check, but my netbsd box is currently off the net since I've not setit back up after BSDcon. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please review: PC-Card melody beep code.
In message [EMAIL PROTECTED] Tony Finch writes: : I tried this on 4.1.1-STABLE with two pccards: a D-Link DE660 and a : Lucent Wavelan card. The de card workedd fine, but the success melody : beep for the wi card was several times slower than it should be. I can : get more information if you need it. I've noticed this on the unpackted -current as well. Something in wi keeps timeouts from firing quickly enough, or at least that's my guess. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail related changes
In message [EMAIL PROTECTED] "Akinori MUSHA" writes: : Would you add an UPDATING entry for this? Many people have been : reporting problems with the local mailer not knowing these changes. It is on my queue of things to add to UPDATING as I find the time. I'll try to get to it quickly. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My Cardbus and Xircom Realport Ethernet II 10/100 experience...
In message 006d01c03d2e$36cf0220$[EMAIL PROTECTED] "Ron Klinkien" writes: : According to files in /usr/src/sys/dev/xe/* the card is supported by the xe : driver. The cardbus version of the Xircom cards use the dc driver. Was it compiled into your kernel? I've used the ethernet old card successfully. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release breakage - dokern.sh patch 2
Ok, folks want INET6. It's back.. It's been pointed out to me by "Thomas D. Dean" [EMAIL PROTECTED] that the 'le' driver does not work. Can someone provide additional information about why it's in GENERIC? Other candidates I've been pointed to include the removal of /boot/boot[12] and NFS (which I seem to remember Jordan axing at one point before we went to a 2 disk set). So, the 2nd try at the patch is below. Comments welcome. -John Index: dokern.sh === RCS file: /mirror/ncvs/src/release/scripts/dokern.sh,v retrieving revision 1.37 diff -r1.37 dokern.sh 40a41 -e '/ le/d' \ 43c44 -e '/apm0/d' \ --- -e '/apm/d' \ 63c64,65 sed -e '/pty/d' \ --- sed -e '/ le/d' \ -e '/pty/d' \ 65c67 -e '/apm0/d' \ --- -e '/apm/d' \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs when boot
In message [EMAIL PROTECTED] "Matthew N. Dodd" writes: : On Mon, 23 Oct 2000, Brian O'Shea wrote: : I am also having this problem. If you interrupt it (with ^\ to send : SIGQUIT), ldconfig generates a core. Then ldconfig will hang while : setting a.out ldconfig path: : : ^C also works. : : ^T is generally useful if you suspect something is hanging on bootup but : don't know what it is. We also found at bsdcon that lots of keystrokes would also make the system boot. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
In message [EMAIL PROTECTED] "Matthew N. Dodd" writes: : On Mon, 23 Oct 2000, Brandon D. Valentine wrote: : Well if you're that stubborn there's no reason that the "new" layout : could not be compiled into a monolithic script. In fact perhaps you : could be the one to step forward and write the code to compile that : script. ;-) : : Indeed, given the slowdowns NetBSD enountered when switching to the new : system due to all of the shell processes being created. which slowdowns were these? Even on older pmax system the boot time wasn't increased too much, once they fixed a couple of bugs in the NetBSD/pmax port... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
In message [EMAIL PROTECTED] "Jacques A. Vidrine" writes: : By the way, the author of this stuff (Luke Mewburn) says he'll post a : summary of the design and implementation issues to this list in a few : days. I talked to Luke at BSDcon about many issues. He's very keen on increasing the cooperation between the two projects. If we find issues with /etc/rc.d(NetSBD), then I'm fairly sure that he'd be willing to work with us on them. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
In message [EMAIL PROTECTED] "John W. De Boskey" writes: : The following patch brings the floppy size down enough to fix : the problem. One is a leftover from the config file syntax : change. Also, I don't know how useful INET6 is to a GENERIC : kernel on todays' networks (faith gif are already removed). apm is a good one to remove. INET6 is needed for many Japanese installs since IPv6 is very large there due to ARIN giving them such a small range of IPv4 numbers. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
In message [EMAIL PROTECTED] "John W. De Boskey" writes: : It's been pointed out to me by "Thomas D. Dean" : [EMAIL PROTECTED] that the 'le' driver does : not work. Can someone provide additional information : about why it's in GENERIC? Likely because it compiles and the devices are rare enough that not too many people have noticed. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 03:59:20PM +0900, Makoto MATSUSHITA wrote: Maybe kernel image for kern.flp is a little bit larger than a 1.44MB floppy. I just diked out more bits. Lets see if that will give us enough space on tonights snapshot build. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 08:15:12AM -0500, Will Andrews wrote: I'm sure there are better things to disable, like MFS, SYSV*, P1003_P1B and friends, and ICMP_BANDLIM. Only SYSVMSG is removed for the i386 case. SYS* for the Alpha. I'm assuming the SYS* left compiled in on the i386 is for X? Does P1003_P1B and ICMP_BANDLIM actually add code, or just set defaults, etc? If someone beats me to it, please compile GENERIC and GENERIC w/o ICMP_BANDLIM (and then again without P1003_P1B) and let us know how much space savings they would provide. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 03:32:16PM +0200, John Hay wrote: Why not remove NFS? That is what I do here when the snap floppy gets too big. How many people install using NFS? (And can't easily change to ftp.) Many. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dc0: watchdog timeout
Motomichi Matsuzaki writes: At Mon, 23 Oct 2000 22:46:26 -0400 (EDT), Andrew Gallatin [EMAIL PROTECTED] wrote: Anybody else seeing 'dc0: watchdog timeout' since SMPng integration? Yes I have. I have this several times before SMPng integration at a high load situation. But, since the integration, it occurs frequently. I just switched out my tulip for an Intel EtherExpress Pro100B. I've had the machine sitting in a while 1 loop, rebuilding a debug kernel (which frequently triggered the dc0 watchdog reset). No problems after 3 hours, so I'm considering it "safe" It must be either a driver issue or something to do with tulips being sensative to not being serviced in a reasonable amount of time.. Cheers, Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 10:44:31PM +0900, Makoto MATSUSHITA wrote: How about removing /boot/boot[12] from floppies ? Committed! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 12:43:16PM -0600, Warner Losh wrote: apm is a good one to remove. We used to, but we were trying to remove `apm0' from GENERIC. I've fixed to just `apm'. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 16:14 +0700, Alexey Dokuchaev wrote:
On Tue, 24 Oct 2000, Terry Lambert wrote:
Well, would not be this stepping aside from BSD startup
sequence, which we all know and love? Having dozens of
small files instead of pair of big ones always frustrates
me when I have to work with linux.
Install a binary package that needs to be started when the
system is booted and needs to be shutdown when the system is
shutdown.
That's what /usr/local/etc/rc.d/ was for for years! Put all
your application-specific scripts there, but leave base-system
monotilithic startup alone :-)
What if I don't employ bind but use something else (djbdns or
homebrew software) instead? Where do I put those in into the
startup sequence? When /usr/local/etc/rc.d/*.sh are run it could
be too late since on the way there a few services died due to DNS
errors.
What about other "essential" services like foreign file systems
("unnatural" things like coda?) or mail transfer agents likely to
be used / needed before other things happen but not available in
the base? What if I want to load some UPS daemon quite early?
How do I implement hardcoded ARP tables short after NIC setup and
right before services' startup? What about other hacks one had
to introduce into /etc/rc*? Think of the ipf "workaround" in PR
20202. It could have been as easy as adding one more file or
replacing the ipfw counterpart. At the moment it is about having
someone stuff the code into some other environment. Without easy
moving around in case it's wrongly placed (think of 30 lines
deleted and 30 lines added - without the chance to easily see if
they're still the same and just have moved - against one line
deleted and one line added - more obviously documenting a moved
invocation).
Plugging (dropping) in just another script and have it register
its sequence number somewhere (or replacing an existing one) is
always easier than modifying a huge pile of code.
And think about undoing those additions (insertions) upon
removal: deleting a single file is really trivial compared to
identifying and removing a chunk in a big file. And changing
your mind about what to do and how to do it for a certain service
won't interfere with all the other stuff.
I don't like thinking back of the situation, where I had to start
a (usually not running) NFS server and a NFS client for remote
installworlds. Eyeballing nested rc scripts, comparing them
against the rc.conf settings and typing all those by hand and not
missing something is really not what you want to have when you
actually have other worries to take care of. And then again -
how do I kill this damned special daemon in a clear way? Of
course every one of them has a way and if you're lucky it's only
five ways for seven services, but that's still too much of a
complexity for a simple human mind with its given restrictions.
Think of the run-parts layout in the cronjob directories and the
advantages are (should be) really obvious. The "clutter" with
the symlinks in Linux come from the notion of having runlevels,
BTW. For BSD (simple straight bootup, endless run and simple
straight shutdown, with a little change sometimes as new services
are needed or not needed any longer) there should either be no
links and a sequence description or just one pile of "numbered
links" besides the "basename'd, plain working" scripts.
BTW: When I wouldn't like those many single files I would
honestly think about combining all the source code into one or at
most two files. :) What are all those header files good for if
not for causing the preprocessor to parse them over and over for
no real gain after the first time? This analogy might
demonstrate best what modularity is able to gain, and that
devoting processing power for tedious routine jobs can free human
resources for other jobs at a more abstract level (i.e. closer to
solving "the real" problem instead of unnecessarily fiddling with
boring details and introducing dull new errors).
virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76
Gerhard Sittig true | mail -s "get gpg key" [EMAIL PROTECTED]
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
We used to, but we were trying to remove `apm0' from GENERIC. I've fixed to just `apm'. Might it be a good idea to make a INSTALL kernel config and a GENERIC config? INSTALL goes on the floppies and has just enough for all the different sorts of installations. GENERIC has almost LINT proportions so newbies don't have to try and make their own kernel. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
Hi. At Tue, 24 Oct 2000 12:15:09 -0700, David O'Brien [EMAIL PROTECTED] wrote: Other candidates I've been pointed to include the removal of /boot/boot[12] and NFS IMO NFS needs to stay. It is *very* useful to many (including me). I vote for 'remove NFS away'. Yes, there are many people using NFS install, but it is site-specific. There are no services distributing FreeBSD via NFS in public. In such site-specific situation, you can make your *specific* floppies with NFS and without INET6 or some. IMHO, making install-floppies should be more easy. -- Motomichi Matsuzaki [EMAIL PROTECTED] Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
On Wed, Oct 25, 2000 at 04:48:14AM +0900, Motomichi Matsuzaki wrote: Other candidates I've been pointed to include the removal of /boot/boot[12] and NFS IMO NFS needs to stay. It is *very* useful to many (including me). I vote for 'remove NFS away'. Yes, there are many people using NFS install, but it is site-specific. And INET6 isn't site specific. It certainly is everywhere but maybe .jp. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 09:42:54PM +0200, Rogier R. Mulhuijzen wrote: We used to, but we were trying to remove `apm0' from GENERIC. I've fixed to just `apm'. Might it be a good idea to make a INSTALL kernel config and a GENERIC config? Nope, the two would be quickly out of sync. What make you think the person that forgot to change `apm0' to `apm' in dokern.sh would have remembered to have made the change in an INSTALL kernel config? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
Before removing NFS, I'd remove the new `ncv', `nsp', and `stg' drivers. Not to mention the `vpo' Parellel port Zip drive device. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 2. Make sure your kernel includes: devicerandom # Entropy device Are you implying the random.ko module is broken? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 05:05:49AM +0700, Alexey Dokuchaev wrote: Still, it would be better if I could choose between "classical" and "new" startup layout, say, somewhere at the installation stage. Supporting two very different schemes is a support nightmare. And giveing good test coverage with our current resources would also be a problem. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 04:49:40AM +0700, Alexey Dokuchaev wrote: Having dozens of small files instead of pair of big ones always frustrates me when I have to work with linux. Maybe, but the greatly increased functionality makes it worth it. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 04:23:40PM +0700, Alexey Dokuchaev wrote: Why can't I simply write kill -1 `cat /var/run/sendmail.pid`? What about deamons that don't understand `kill -HUP'? Sendmail didn't until very reciently. ``/etc/rc.d/some-deamon restart'' does the right thing reguardless how involved that might be. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On 24-Oct-00 David O'Brien wrote: On Tue, Oct 24, 2000 at 09:42:54PM +0200, Rogier R. Mulhuijzen wrote: We used to, but we were trying to remove `apm0' from GENERIC. I've fixed to just `apm'. Might it be a good idea to make a INSTALL kernel config and a GENERIC config? Nope, the two would be quickly out of sync. What make you think the person that forgot to change `apm0' to `apm' in dokern.sh would have remembered to have made the change in an INSTALL kernel config? Because they are more obvious in that they are in the same place (same directory) whereas dokern.sh is stuffed away in src/release/scripts/. Besides, when doing the 3rd floppy idea, using a custom INSTALL kernel config is going to be the way to go. Just as soon as we can get Peter to finish his latest round of config changes. :) -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
At Tue, 24 Oct 2000 13:08:26 -0700, David O'Brien [EMAIL PROTECTED] wrote: I vote for 'remove NFS away'. Yes, there are many people using NFS install, but it is site-specific. And INET6 isn't site specific. It certainly is everywhere but maybe .jp. I think INET6 is a grobal and public feature, because there are some IPv6 servers. IPv6 networks (6bone) WORKS, and you can get full FreeBSD distribution via IPv6 network if you have connectibity to world-wide 6bone. Not site-specific, IPv6 servers open to the world. Again. There is no public NFS servers for distributing FreeBSD as I know. You can't get any FreeBSD, even if you sends NFS packets to the Internet. Can I and anybody access your favorite NFS servers? -- Motomichi Matsuzaki [EMAIL PROTECTED] Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
It didn't work without the device line when I tested it last week(Thursday/Friday). -John - David O'Brien's Original Message - On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 2. Make sure your kernel includes: device random # Entropy device Are you implying the random.ko module is broken? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Fw: My Cardbus and Xircom Realport Ethernet II 10/100 experience...
Nice work those pccard stuff... Ahum I ment cardbus stuff.. ;-) Anyway my Xircom Realport II Cardbus 10/100 Mb card works ok now It's one of those red double height ones with a RJ45 jack built into it... Maybe something to mention in the docs to use the dc driver with it. Ron. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
will I'm sure there are better things to disable, like MFS, SYSV*, will P1003_P1B and friends, and ICMP_BANDLIM. MFS is required; don't forget we have mfsroot.flp :-) The name is historical; we use md(4) not MFS. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
- David O'Brien's Original Message - On Tue, Oct 24, 2000 at 02:36:44PM -0400, John W. De Boskey wrote: the 'le' driver does not work. Can someone provide additional information about why it's in GENERIC? Get confirmation that it does not work (one user isn't suffient in my book as there could be many issues which could make it ``not work'' for one person). That's part of what this mail is/was for. Other candidates I've been pointed to include the removal of /boot/boot[12] and NFS IMO NFS needs to stay. It is *very* useful to many (including me). I haven't removed it. But it is an option. I was a very heavy user of NFS, but it didn't matter to jkh when he removed it last time. The switch to ftp isn't hard. P.S. PLEASE trim the CC line. It has gotten redictulously long. To the point some might consider not sending a single message on this thread, else they'll get their mailbox flooded from then on. I copied those folks who responded to my original mail. Standard curtesy. I did not copy you on this. -John -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
BSDcon Was: Re: current hangs when boot
On Tue, 24 Oct 2000, Warner Losh wrote:
We also found at bsdcon that lots of keystrokes would also make the
system boot.
Warner
For those of us that couldn't go, has anybody posted pictures from the con
yet? ...any kind of pictures - not just ones of keyboard bashing...
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
You need to put random_load="YES" into /boot/loader.conf. Optionally, you can load random.ko during the boot process. John W. De Boskey wrote: It didn't work without the device line when I tested it last week(Thursday/Friday). - David O'Brien's Original Message - On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 2. Make sure your kernel includes: devicerandom # Entropy device Are you implying the random.ko module is broken? -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fw: My Cardbus and Xircom Realport Ethernet II 10/100 experience...
In message 016501c03dfa$e7951780$[EMAIL PROTECTED] "Ron Klinkien" writes: : Maybe something to mention in the docs to use the dc driver with it. We need a good way to list known supported cards (not just pccard or cardbus) in a driver's man page. Warner Maybe an idea to create a new man section for supported hardware info, that way you can store this kind of info for all kinds of drivers, scsi, video etc.. eg. man dc 4 gives general info about dc driver man dc 'x' gives list of supported hardware for this driver. You only have to include an pointer for the user in the original man page, and list it under the SEE ALSO line. Just my 1 eurocent... Ron. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
[redirected to just -current; I'm not sure what this has to do with -net] I agree. I've been using them for a while on my dog slow Windows CE machine. There were some minor issues when they were first committed to NetBSD on some platforms (due to a too early use of ps and some brokeness in ps on pmax, for example), but these were quickly resolved. So, who wants to do a proof-of-concept implementation for -current which integrates with our existing rc.conf mechanism? In order to obey POLA, we should at least have the separate scripts switch off the same knobs whenever possible. It's something I'd be willing to do, I guess. I have some history with the rc.foo files. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
The scripts themselves have the ordering dependencies. The startup system runs them in the proper order. I don't know if this is pre-computed or redone each boot. I'm really curious about this, myself. One of the reasons the SYSV scripts have the numeric prefix is so that you know exactly what order things will be started in. With the NetBSD stuff, this is not immediately obvious though I guess one could have a top level rc file with an explicit ordering similar to our various subdir Makefiles, but that also gives you another location to edit when dropping in a new startup file. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 02:58:08PM -0700, Jordan Hubbard wrote: The scripts themselves have the ordering dependencies. The startup system runs them in the proper order. I don't know if this is pre-computed or redone each boot. I'm really curious about this, myself. One of the reasons the SYSV scripts have the numeric prefix is so that you know exactly what order things will be started in. With the NetBSD stuff, this is not immediately obvious though I guess one could have a top level rc file with an explicit ordering similar to our various subdir Makefiles, but that also gives you another location to edit when dropping in a new startup file. well, assuming you specify all the necessary dependencies, does it really matter what the specific order is? i mean i always thought of the numbers in SYSV script names as a hack to preserve dependencies, rather than a way to preserve a specific order. the order only needs to exist to preserve dependencies, unless i'm missing something. -- garrett rooney my pid is inigo montoya. [EMAIL PROTECTED] you kill -9 my parent process. http://electricjellyfish.net/prepare to vi. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
Only SYSVMSG is removed for the i386 case. SYS* for the Alpha. I'm assuming the SYS* left compiled in on the i386 is for X? That is correct. It's not mandatory, but it emits a scary-looking error message when X starts up and a lot of folks were commenting on it, so I put it (SYSVSHM) back in. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 02:58:08PM -0700, Jordan Hubbard wrote: The scripts themselves have the ordering dependencies. The startup system runs them in the proper order. I don't know if this is pre-computed or redone each boot. I'm really curious about this, myself. One of the reasons the SYSV scripts have the numeric prefix is so that you know exactly what order things will be started in. With the NetBSD stuff, this is not immediately obvious though I guess one could have a top level rc file with an explicit ordering similar to our various subdir Makefiles, but that also gives you another location to edit when dropping in a new startup file. and, to reply a second time to this message, it is recomputed at each boot... the rc and rc.shutdown scripts both run rcorder to do it, with rc.shutdown reversing the order. -- garrett rooney my pid is inigo montoya. [EMAIL PROTECTED] you kill -9 my parent process. http://electricjellyfish.net/prepare to vi. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 02:58:08PM -0700, Jordan Hubbard thus spoke: The scripts themselves have the ordering dependencies. The startup system runs them in the proper order. I don't know if this is pre-computed or redone each boot. I'm really curious about this, myself. One of the reasons the SYSV scripts have the numeric prefix is so that you know exactly what order things will be started in. With the NetBSD stuff, this is not immediately obvious though I guess one could have a top level rc file with an explicit ordering similar to our various subdir Makefiles, but that also gives you another location to edit when dropping in a new startup file. This was my thought also. I put the TCP/IP scripts at 99 to make sure that any slow network initialization is done. Since they all start with S - for example S99tcp - moving it to s99tcp will keep it from starting, and the Knnname in the same directory is used to stop things when moving from that run level. It's one of the things I like about the Sys V /etc/rcn.d directory structure, as you can easily fine tune it to fit your needs. Just a look at the files and you know the order. Bill -- Bill Vermillion - bv @ wjv . com -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
Jordan Hubbard writes: [redirected to just -current; I'm not sure what this has to do with -net] I agree. I've been using them for a while on my dog slow Windows CE machine. There were some minor issues when they were first committed to NetBSD on some platforms (due to a too early use of ps and some brokeness in ps on pmax, for example), but these were quickly resolved. So, who wants to do a proof-of-concept implementation for -current which integrates with our existing rc.conf mechanism? In order to obey POLA, we should at least have the separate scripts switch off the same knobs whenever possible. I'm in the midst of trying to install NetBSD so I can look at this. If no one else steps forward to do it, I can put together a patch. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs when boot
On Tue, Oct 24, 2000 at 12:38:41PM -0600, Warner Losh wrote: In message [EMAIL PROTECTED] "Matthew N. Dodd" writes: : On Mon, 23 Oct 2000, Brian O'Shea wrote: : I am also having this problem. If you interrupt it (with ^\ to send : SIGQUIT), ldconfig generates a core. Then ldconfig will hang while : setting a.out ldconfig path: : : ^C also works. : : ^T is generally useful if you suspect something is hanging on bootup but : don't know what it is. We also found at bsdcon that lots of keystrokes would also make the system boot. Which reminds me of the Sun software problem report that had as the engineering reply: "Don't hit on the keyboard like a wild monkey" .. :-) -- Wilko Bulte Arnhem, the Netherlands [EMAIL PROTECTED] http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
On Tue, Oct 24, 2000 at 02:36:44PM -0400, John W. De Boskey wrote: Ok, folks want INET6. It's back.. It's been pointed out to me by "Thomas D. Dean" [EMAIL PROTECTED] that the 'le' driver does not work. Can someone provide additional information That is correct. See kern/19219. I've verified this on a DEC le card. That is also as far as I got.. about why it's in GENERIC? To annoy people? ;) -- Wilko Bulte Arnhem, the Netherlands [EMAIL PROTECTED] http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
On Wed, Oct 25, 2000 at 04:48:14AM +0900, Motomichi Matsuzaki wrote: Hi. At Tue, 24 Oct 2000 12:15:09 -0700, David O'Brien [EMAIL PROTECTED] wrote: Other candidates I've been pointed to include the removal of /boot/boot[12] and NFS IMO NFS needs to stay. It is *very* useful to many (including me). I vote for 'remove NFS away'. Yes, there are many people using NFS install, but it is site-specific. The same argument goes for IPV6. In other words: it all depends on your viewpoint. IMHO, making install-floppies should be more easy. Yes!!! -- Wilko Bulte Arnhem, the Netherlands [EMAIL PROTECTED] http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
So, who wants to do a proof-of-concept implementation for -current which integrates with our existing rc.conf mechanism? In order to obey POLA, we should at least have the separate scripts switch off the same knobs whenever possible. It's something I'd be willing to do, I guess. I have some history with the rc.foo files. :) I'm rather new to -current, but I'd be willing to be junior hacker on this project. I'm rather fond of shell script hacking and other languages come easily to me too. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 3.3.6_3 build dies on -current
Patrick Gardella wrote: I built and installed -current on a laptop yesterday (10/23/00), and went to build XFree86 3.3.6_3 today from the ports directory. It built fine, but when you run make install, it dies, complaining of syntax errors in machine/endian.h: In file included from /usr/include/sys/wait.h:93, from vgaHW.c:44: /usr/include/machine/endian.h:72: syntax error before `__uint16_swap_unit32' /usr/include/machine/endian.h:72: syntax error before `__x' snip XFree86 4.0.1 has the same problem. The following patch solves it for 4.0.1 (relative to .../xc/include): --- Xarch.h Sat Jun 17 11:40:56 2000 +++ /home/marcel/Xarch.hTue Oct 24 15:15:58 2000 @@ -49,9 +49,7 @@ #endif #endif #elif defined(CSRG_BASED) -#if defined(__NetBSD__) || defined(__OpenBSD__) #include sys/types.h -#endif #include machine/endian.h #elif defined(linux) #if defined __STRICT_ANSI__ I'm going to build 3.3.6 anyway, because 4.0.1 coredumps on my new notebook, so I'll try to make a patch as well. If someone can make a PR out of this thread, then we're all happy; especially jmz. -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
On Tue, Oct 24, 2000 at 04:49:41PM -0400, John W. De Boskey wrote: IMO NFS needs to stay. It is *very* useful to many (including me). I haven't removed it. But it is an option. I was a very heavy user of NFS, but it didn't matter to jkh when he removed it last time. The switch to ftp isn't hard. Ultimately that is a call for JKH. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
Again. There is no public NFS servers for distributing FreeBSD as I know. You can't get any FreeBSD, even if you sends NFS packets to the Internet. Can I and anybody access your favorite NFS servers? I think this misses the point. Not everyone installs FreeBSD from public servers and, in fact, there is a large percentage of FreeBSD users who have *never* installed FreeBSD from a public server and never will due to various firewall / corporate policy issues. Instead, they transfer the bits to an intermediate server or mount the installation CD and export it, doing all installs over NFS or anon FTP (internal use only) from there. Believe me, if we were to put out a serious call to kill NFS from the installation boot images, you'd very quickly hear from all of those people and they would be screaming. We need to exhaust all other possibilities before we even contemplate that option. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
[Why is -current on the cc line twice? One instance removed] I haven't removed it. But it is an option. I was a very heavy user of NFS, but it didn't matter to jkh when he removed it last time. The switch to ftp isn't hard. Well, that's not quite accurate. It did matter, it just seemed like you were the one lone voice calling for it at the time. I very quickly learned otherwise and, what do you know, it came back. :) NFS is a big, bloated and obvious candidate for removal and I'd be very happy to see it go away forever (not just from the boot floppy, but everywhere :-) but that's not likely to happen, now is it? :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
At Wed, 25 Oct 2000 00:28:41 +0200, Wilko Bulte [EMAIL PROTECTED] wrote: IMO NFS needs to stay. It is *very* useful to many (including me). I vote for 'remove NFS away'. Yes, there are many people using NFS install, but it is site-specific. The same argument goes for IPV6. In other words: it all depends on your viewpoint. Again. NFS is site-specific service. IPv6 is world-wide service. Indeed, world-wide NFS is capable, but is somewhat ridiculous idea. And more, IPv6 is network layer feature, and NFS is session and higher layer feature like FTP, HTTP, AFS and so on. If IPv6 is disabled in IPv6-only environment, any of FTP, HTTP, NFS does not work. Disabling NFS causes minor impact compared with that, because switching to FTP is very easy, as already pointed out. NFS is for convenience, IPv6 is for life. The same argument goes for device drivers. Device drivers of storage devices are also for their lives. -- Motomichi Matsuzaki [EMAIL PROTECTED] Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
On Tue, 24 Oct 2000, David O'Brien wrote: On Tue, Oct 24, 2000 at 04:23:40PM +0700, Alexey Dokuchaev wrote: Why can't I simply write kill -1 `cat /var/run/sendmail.pid`? What about deamons that don't understand `kill -HUP'? Sendmail didn't until very reciently. ``/etc/rc.d/some-deamon restart'' does the right thing reguardless how involved that might be. Though I see your point, actually, many UNIX books, including some pretty old ones, refer to sending HUP signal as standard way of restarting/resetting daemons. ./danfe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
and, to reply a second time to this message, it is recomputed at each boot... the rc and rc.shutdown scripts both run rcorder to do it, with rc.shutdown reversing the order. Ah, OK, sorry - I must have missed this the first time around. I'll have to investigate the workings of rcorder then. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
I'm in the midst of trying to install NetBSD so I can look at this. If no one else steps forward to do it, I can put together a patch. I've had several replies, so why don't we all look into this a bit and see which one of us actually manages to have enough steam to do it after the analysis period is over. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
Believe me, if we were to put out a serious call to kill NFS from the installation boot images, you'd very quickly hear from all of those people and they would be screaming. We need to exhaust all other possibilities before we even contemplate that option. Are there maybe other large pieces which could use something like NFS_NOSERVER is to NFS? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
msmith The name is historical; we use md(4) not MFS. I should read md(4) manpage... sorry. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sysinstall's console keymap menu
Hi Jordan,
How about this patch to display keymap menu correctly with 80 column
width console?
# If someone have a good idea to abbrevate "(accent)" string,
# I'd like to trim this word to reduce left column width of this menu.
--
Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc.
[EMAIL PROTECTED] // FreeBSD Project
Index: menus.c
===
RCS file: /home/ncvs/src/release/sysinstall/menus.c,v
retrieving revision 1.279
diff -u -r1.279 menus.c
--- menus.c 2000/10/14 21:02:31 1.279
+++ menus.c 2000/10/25 01:49:44
@@ -1430,13 +1430,13 @@
{ " Brazil CP850", "Brazil CP850 keymap", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=br275.cp850" },
{ " Brazil ISO (accent)","Brazil ISO keymap (accent keys)",
dmenuVarCheck, dmenuSetKmapVariable, NULL, "keymap=br275.iso.acc" },
{ " Brazil ISO", "Brazil ISO keymap",dmenuVarCheck, dmenuSetKmapVariable,
NULL, "keymap=br275.iso" },
- { " Croatian ISO", "Croatian ISO keymap", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=hr.iso" },
+ { "Croatian ISO","Croatian ISO keymap", dmenuVarCheck,
+dmenuSetKmapVariable, NULL, "keymap=hr.iso" },
{ "Danish CP865","Danish Code Page 865 keymap", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=danish.cp865" },
{ " Danish ISO", "Danish ISO keymap",dmenuVarCheck, dmenuSetKmapVariable,
NULL, "keymap=danish.iso" },
{ "Estonian ISO", "Estonian ISO keymap", dmenuVarCheck, dmenuSetKmapVariable,
NULL, "keymap=estonian.iso" },
{ " Estonian ISO 15", "Estonian ISO 8859-15 keymap", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=estonian.iso15" },
{ " Estonian CP850", "Estonian Code Page 850 keymap",dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=estonian.cp850" },
- { " Finnish CP850","Finnish Code Page 850 keymap", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=finnish.cp850" },
+ { "Finnish CP850","Finnish Code Page 850 keymap",dmenuVarCheck,
+dmenuSetKmapVariable, NULL, "keymap=finnish.cp850" },
{ " Finnish ISO", "Finnish ISO keymap", dmenuVarCheck, dmenuSetKmapVariable,
NULL, "keymap=finnish.iso" },
{ " French ISO (accent)", "French ISO keymap (accent keys)", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=fr.iso.acc" },
{ " French ISO", "French ISO keymap",dmenuVarCheck, dmenuSetKmapVariable,
NULL, "keymap=fr.iso" },
@@ -1447,8 +1447,8 @@
{ "Icelandic (accent)", "Icelandic ISO keymap (accent keys)",dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=icelandic.iso.acc" },
{ " Icelandic", "Icelandic ISO keymap", dmenuVarCheck, dmenuSetKmapVariable,
NULL, "keymap=icelandic.iso" },
{ " Italian","Italian ISO keymap", dmenuVarCheck, dmenuSetKmapVariable,
NULL, "keymap=it.iso" },
- { "Latin American", "Latin American ISO keymap", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=lat-amer" },
{ "Japanese 106","Japanese 106 keymap", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=jp.106" },
+ { "Latin American", "Latin American ISO keymap", dmenuVarCheck,
+dmenuSetKmapVariable, NULL, "keymap=lat-amer" },
{ "Norway ISO", "Norwegian ISO keymap", dmenuVarCheck, dmenuSetKmapVariable,
NULL, "keymap=norwegian.iso" },
{ "Polish ISO", "Polish ISO keymap",dmenuVarCheck, dmenuSetKmapVariable,
NULL, "keymap=pl_PL.ISO_8859-2" },
{ " Portuguese (accent)","Portuguese ISO keymap (accent keys)",
dmenuVarCheck, dmenuSetKmapVariable, NULL, "keymap=pt.iso.acc" },
@@ -1468,13 +1468,13 @@
{ " Swiss German CP850", "Swiss German Code Page 850 keymap", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=swissgerman.cp850" },
{ "U.K. CP850", "United Kingdom Code Page 850 keymap", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=uk.cp850" },
{ " U.K. ISO", "United Kingdom ISO keymap", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=uk.iso" },
- { " U.S. CapsLock-Ctrl","United States standard with Caps Lock acting
as left Control", dmenuVarCheck, dmenuSetKmapVariable, NULL, "keymap=us.pc-ctrl" },
+ { " U.S. CapsLock-Ctrl","United States standard (Caps as L-Control)",
+ dmenuVarCheck, dmenuSetKmapVariable, NULL, "keymap=us.pc-ctrl" },
{ " U.S. Dvorak","United States Dvorak keymap", dmenuVarCheck,
dmenuSetKmapVariable, NULL, "keymap=us.dvorak" },
{ " U.S. Dvorak (left)", "United States left handed Dvorak keymap",
dmenuVarCheck, dmenuSetKmapVariable, NULL, "keymap=us.dvorakl" },
{ " U.S. Dvorak (right)","United States right handed Dvorak keymap",
dmenuVarCheck, dmenuSetKmapVariable, NULL, "keymap=us.dvorakr" },
- { " U.S. Emacs", "United States standard optimized for EMACS use",
dmenuVarCheck, dmenuSetKmapVariable, NULL, "keymap=us.emacs" },
+ { " U.S.
Re: -current hangs during boot (UPDATING entry)
On Mon, 23 Oct 2000, John W. De Boskey wrote: I'm beginning to think we need an updating entry. 1. Make sure /dev/random exists 'cd /dev sh MAKEDEV std' Unless you are using devfs. 2. Make sure your kernel includes: devicerandom # Entropy device Or the appropriate line in /boot/mumble.conf 3. Make sure /etc/rc is at rev 1.237 or higher. 4. Make sure /etc/rc.shutdown is at rev 1.13 or 1.15 5. At this time, remove ALL MFS filesystems from /etc/fstab. They can be hand mounted after bootup or via a local rc startup script. A better solution would be to increase the granularity of the file system mounts so that the MFS systems were mounted after the entropy gathering. There are a couple of reasons I changed the ordering on the two reseeding attempts, one of the big ones was that for the "manual" reseed (i.e., no entropy file) we want more parts of the system mounted so that we have more potential entropy gathering tools. Rest sounds good... Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? 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
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. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: smp instability
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 . -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: 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: new rc.network6 and rc.firewall6
At 2:58 PM -0700 10/24/00, Jordan Hubbard wrote: The scripts themselves have the ordering dependencies. The startup system runs them in the proper order. I don't know if this is pre-computed or redone each boot. I'm really curious about this, myself. One of the reasons the SYSV scripts have the numeric prefix is so that you know exactly what order things will be started in. With the NetBSD stuff, this is not immediately obvious though I guess one could have a top level rc file with an explicit ordering similar to our various subdir Makefiles, but that also gives you another location to edit when dropping in a new startup file. One should have some other script that you could run, which would look thru all the rc files and just list which order they will be run at startup (or at shutdown). That way you could find out the order for a given set of scripts without having to actually startup or shutdown... (I have no idea how netbsd does it, I'm just saying that I would think some other script should be provided which could list out the proper order without actually running any of the scripts...) --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute 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
Re: new rc.network6 and rc.firewall6
On Tue, Oct 24, 2000 at 11:04:55PM -0400, Garance A Drosihn wrote: One should have some other script that you could run, which would look thru all the rc files and just list which order they will be run at startup (or at shutdown). That way you could find out the order for a given set of scripts without having to actually startup or shutdown... (I have no idea how netbsd does it, I'm just saying that I would think some other script should be provided which could list out the proper order without actually running any of the scripts...) since i've been playing with the tools a little in my copious spare time, you could determine that using the rcorder tool that they actually use to get the order in the rc script. just run 'rcorder /etc/rc.d/*' and it'll output the order they should start up in. reverse that order for shutdown. this system looks more and more swank every time i look at it. -- garrett rooney my pid is inigo montoya. [EMAIL PROTECTED] you kill -9 my parent process. http://electricjellyfish.net/prepare to vi. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
