Re: -CURRENT breakage in usr.sbin/mptable?
On Fri, 23 Mar 2001, Bruce A. Mah wrote: Hi Bruce-- A recent commit of yours to src/usr.sbin/mptable/Makefile had the commit message: Fixed style bugs (use normal formatting for assignment, and don't override the correct default for MAN1). Are you sure this is right? The default MANSECT for src/usr.sbin is 8, not 1, but mptable.1, well, lives in section 1. Oops. It was only right for 2-3 years after I first changed it until a couple of days ago. Alfred has committed a fix. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Re: Whatever happened to CTM?
On 2001-03-21 14:59 +0200, Mark Murray [EMAIL PROTECTED] wrote: Just an idea: How about a CVSUP via HTTPS server (just as a means to tunnel CVSUP through a HTTPS proxy ...) ? Most probably a CVSUP daemon bound to port 443 would do (there are programs that tunnel arbitrary data through a HTTPS proxy, though I admit this is cheating ;-) You should be able to do it with SSH (assuming that you can get out with ssh!) No, if I could get out with SSH, there was no problem ... The firewall rules are very strict: The only way to send and receive bytes through the firewall is the HTTP CONNECT method as offered by a HTTPS proxy. And even that method is further restricted to prevent misuse. $ ssh -v -l yourname otherhost.example.com -L5559:cvsup.example.com:5559 Then doing a cvsup with the server set to 127.0.0.1 will work. Yes, I know about this, and have been using similar setups on several occasions. The information may be useful to others, with less restrictive firewall setups. But I can't even connect fully transparently through even a single TCP port, only by means of a HTTPS capable application gateway ... (I'm not willing to go into too much detail here. I'm responsible for the firewall policy, and I just can't break or bend the rules enforced by me on a large company, just because its *me* this time, who absolutely needs that direct TCP connection ;-) I know that misusing 443/tcp for CVSup is not much better than attempts by some commercial software companies to tunnel everything over 80/tcp. In the end, firewalls as we know them will only be able to protect against the most primitive (header level) attacks, the protection against malicious data sent over such a connection will have to be provided by the endpoints (and I have been demanding SSL with client and server certificates for most of the B2B INTERNET services, at work). Anyway: If CTM was to ever be given up (it's good to read, that Ulf will get his CTM box connected again, soon), then there should be a alternate access method, that works through tightly configured firewalls. And CVsup via SSL might be a good candidate ... Regards, STefan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
Anyway: If CTM was to ever be given up (it's good to read, that Ulf will get his CTM box connected again, soon), then there should be a alternate access method, that works through tightly configured firewalls. And CVsup via SSL might be a good candidate ... Hmm. Look at sslproxy and sslwrap in the ports. They may just work for you. It shouldn't be too difficult to set up the other side - after all, there is a need :-) M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel link problems with ata driver
For the past couple weeks I have been unable to build a kernel for my laptop. I keep getting undefined symbols. The problem started with the split of the ata driver by different bus attachments. My laptop only has ISA and not PCI so I don't include PCI in the kernel config file. The errors and kernel configuration are included below. Jim Bloom [EMAIL PROTECTED] linking kernel ata-all.o: In function `ata_service': ata-all.o(.text+0x1332): undefined reference to `ata_dmastatus' ata-all.o: In function `ata_change_mode': ata-all.o(.text+0x1dc1): undefined reference to `ata_dmainit' ata-disk.o: In function `ad_attach': ata-disk.o(.text+0x36c): undefined reference to `ata_dmainit' ata-disk.o(.text+0x39d): undefined reference to `ata_dmainit' ata-disk.o: In function `ad_start': ata-disk.o(.text+0xa14): undefined reference to `ata_dmaalloc' ata-disk.o: In function `ad_transfer': ata-disk.o(.text+0xbf4): undefined reference to `ata_dmasetup' ata-disk.o(.text+0xd14): undefined reference to `ata_dmastart' ata-disk.o: In function `ad_interrupt': ata-disk.o(.text+0xf13): undefined reference to `ata_dmadone' ata-disk.o(.text+0x1029): undefined reference to `ata_dmainit' ata-disk.o(.text+0x1092): undefined reference to `ata_dmainit' ata-disk.o: In function `ad_service': ata-disk.o(.text+0x1518): undefined reference to `ata_dmastart' ata-disk.o: In function `ad_timeout': ata-disk.o(.text+0x177f): undefined reference to `ata_dmadone' ata-disk.o(.text+0x17b8): undefined reference to `ata_dmainit' ata-disk.o: In function `ad_reinit': ata-disk.o(.text+0x18fe): undefined reference to `ata_dmainit' ata-disk.o(.text+0x1929): undefined reference to `ata_dmainit' *** Error code 1 machine i386 cpu I486_CPU cpu I586_CPU ident LAPTOP maxusers32 #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options INVARIANTS options INVARIANT_SUPPORT # options MUTEX_DEBUG options WITNESS options MATH_EMULATE#Support for x87 emulation options INET#InterNETworking options INET6 #IPv6 communications protocols options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options IPSEC_DEBUG #debug for IP security options FFS #Berkeley Fast Filesystem options MFS #Memory Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options IPFIREWALL #firewall options IPDIVERT#divert sockets options DDB #kernel debugger # Obsolete option # options MD_NSECT=1 device isa # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc device atkbd device psm device vga # syscons is the default console driver, resembling an SCO console device sc # Floating point support - do not disable. device npx # Power management support (see LINT for more options) device apm # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic # Serial (COM) ports device sio # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip# TCP/IP over parallel device ppi # Parallel port interface device # ISA Ethernet NICs. device ed device miibus # Pseudo devices - the number indicates how many units to allocated. device loop# Network loopback device ether # Ethernet support device sl 1 # Kernel SLIP device ppp 1 # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc)
upgrade tcpdump in -current?
Are there any plans on upgrading tcpdump to e.g. 3.6.2, which has better support for e.g. NFS over IPv6? Greetings, Mark Huizer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel link problems with ata driver
It seems Jim Bloom wrote: For the past couple weeks I have been unable to build a kernel for my laptop. I keep getting undefined symbols. The problem started with the split of the ata driver by different bus attachments. My laptop only has ISA and not PCI so I don't include PCI in the kernel config file. Are you sure your /sys/conf/files file is up to date ? Have you removed your /sys/compile/YOURKERNEL dir before a new config ? -Sren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
fixit floppy full during make release
Does anyone have some free space that they can borrow the fixit floppy? Created /R/stage/floppies/boot.flp Regular and MFS boot floppies made. touch release.8 Making fixit floppy. 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/md0c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 384 i/g) super-block backups (for fsck -b #) at: 32 /mnt: write failed, file system is full cpio: write error: No space left on device *** Error code 1 # John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel link problems with ata driver
It seems Jim Bloom wrote: For the past couple weeks I have been unable to build a kernel for my laptop. I keep getting undefined symbols. The problem started with the split of the ata driver by different bus attachments. My laptop only has ISA and not PCI so I don't include PCI in the kernel config file. Are you sure your /sys/conf/files file is up to date ? Have you removed your /sys/compile/YOURKERNEL dir before a new config ? I see this problem too. Removing /sys/compile/MYKERNEL didn't help. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel link problems with ata driver
It seems Maxim Sobolev wrote: It seems Jim Bloom wrote: For the past couple weeks I have been unable to build a kernel for my laptop. I keep getting undefined symbols. The problem started with the split of the ata driver by different bus attachments. My laptop only has ISA and not PCI so I don't include PCI in the kernel config file. Are you sure your /sys/conf/files file is up to date ? Have you removed your /sys/compile/YOURKERNEL dir before a new config ? I see this problem too. Removing /sys/compile/MYKERNEL didn't help. OK, I found the problem, I just committed the fix. -Sren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Kernel panic: resource_list_alloc: resource entry is busy
This from CVSup shortly before midnight (PST); I recall that I got the update to sys/kern/kern_intr.c rev. 1.50 (to pin down the time a little better). I was able to re-boot with the kernel from /boot/kernel.old OK; once I did that, I re-built the kernel after adding "options DDB", and I then re-created the panic. An outline of the traceback (sorry; I don't have a serial console on the laptop... yet) is: Debugger(c0337e03) at Debugger+0x44 panic(c0338d20,c167810c,4,0,c047f6c4) at panic+0x70 resource_list_alloc(c1683a00,c1679d00,c168eb80,4,c167810c) at resource_list_alloc+0xc8 isa_alloc_resource(c1679d00,c168eb80,4,c167810c,f8c) at isa_alloc_resource+0xcd bus_alloc_resource(c168eb80,4,c167810c,f8c,f95) at bus_alloc_resource+0x5d opti_detect(c168eb80,c1678100) at opti_detect+0xaa [abbreviating beyond this point for now; my hands are getting tired -- dhw] mss_detect( mss_probe( device_probe_child( device_probe_and_attach( isa_probe_children( configure( mi_startup() at mi_startup+0x68 begin() at begin+0x29 The addition of DDB is the first change I've needed to make since getting -CURRENT running on the machine a couple of weeks ago, and I've been CVSuping daily and rebuilding both -STABLE and -CURRENT daily. I don't happen to have a copy of the kernel config on a different machine, so I'll need to boot it normally to supply that; sorry. But given the above, unless something changed that would require a change to the kernel config within the last day or so, I'd have thought it would have been expected to not panic :-} There are some other things I'd like to do with the machine (build today's -STABLE, for example), but I can leave it "broken" for debugging for a while easily enough. The panic appears to come faily early in the boot process (resource allocation, I'd guess :-}), and it appears eminently reproducable, so I'm willing to play with it, fetch more code, or whatever. It's a 750/600 MHx P3 w/ 256 MB RAM, so I should be able to try changes reasonably quickly. Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: spin lock panic ...
On Fri, 23 Mar 2001, John Baldwin wrote:
On 24-Mar-01 The Hermit Hacker wrote:
On Fri, 23 Mar 2001, John Baldwin wrote:
On 24-Mar-01 The Hermit Hacker wrote:
Over the past few days, I reformatted my computer clean, installed
4.2-RELEASE onto her and just finished upgrading to the latest 5.x kernel
and world ... went to ports/x11/XFree86-4 and did a 'make install' ...
after awhile, it panic'd as below:
panic: spin lock sched lock held by 0xcb332840 for 5 seconds
cpuid = 1; lapic.id = 0100
Debugger("panic")
CPU1 stopping CPUs: 0x0001... stopped.
Now, I do have DDB enabled in the kernel ... but, for the life of me, I
can't seem to find any docs on the keystroke required to drop into it :(
'man ddb' doesn't document it that I can find, nor does LINT ...
Uhh, if it panic'd, it should already be in ddb at a db prompt assuming you
have DDB in your kernel.
didn't ... last line was as above ... I've even tested my DDB to make sure
I can get to the db prompt after alfred reminded me of the ctl-alt-esc to
get there, and it works ...
Well, that meants it most likely deadlocked trying to get into the debugger. I
haven't seen any deadlocks like this in months though.
I swear, my compuer is just so special :) it hasn't happened since
... re started the X compile, it finished fine and installed .. *shrug*
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Kernel panic: resource_list_alloc: resource entry is busy
I see the same here with a GENERIC kernel. Martin Martin Blapp, [EMAIL PROTECTED] Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make world stops during i4b compilation
Hi, anyone has this problem too? (..) cc -elf -shared -nostdlib hack.c -o hack.So rm -f hack.c sh /usr/src/sys/conf/newvers.sh ORANJE cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/../include -I/usr/src/sys/contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -fno-builtin -mpreferred-stack-boundary=2 vers.c linking kernel i4b_ipr.o: In function `i4biprattach': i4b_ipr.o(.text+0x1d2): undefined reference to `ether_ifattach' i4b_isppp.o: In function `i4bispppattach': i4b_isppp.o(.text+0x179): undefined reference to `ether_ifattach' *** Error code 1 Stop in /usr3/obj/usr/src/sys/ORANJE. *** Error code 1 Compiling the GENERIC kernel however works fine.. hmmm. Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel panic: resource_list_alloc: resource entry is busy
Date: Sat, 24 Mar 2001 09:15:29 -0800 (PST) From: David Wolfskill [EMAIL PROTECTED] This from CVSup shortly before midnight (PST); I recall that I got the update to sys/kern/kern_intr.c rev. 1.50 (to pin down the time a little better). OK; I re-booted it under -STABLE, so I can report a bit more about the context. Yesterday, the thought occurred to me that it might be handy to record the start time for the CVSup (as well as the end time, so: CVSup ended at Wed Mar 21 23:53:49 PST 2001 CVSup ended at Thu Mar 22 23:51:54 PST 2001 CVSup started at Fri Mar 23 23:47:01 PST 2001 CVSup ended at Fri Mar 23 23:53:40 PST 2001 (and I had built booted -CURRENT successfully yesterday; I append /var/log/messages from that boot after my .sig.) And the following shows the CVS activity from the working sources to the failing ones (I elided the "cvs update:" lines): Script started on Sat Mar 24 05:27:55 2001 dhcp-135[1] cd /C/usr/src dhcp-135[2] cvs update -d ? PATCHES U bin/getfacl/getfacl.1 U bin/setfacl/setfacl.1 U contrib/gcc.295/except.c U contrib/gcc.295/expr.c U contrib/gcc.295/expr.h U contrib/gcc.295/varasm.c U etc/Makefile U etc/primes U etc/mtree/BSD.x11-4.dist U games/fortune/datfiles/fortunes U gnu/usr.bin/tar/tar.c U include/arpa/inet.h U include/rpc/rpc.h U lib/libc/gen/Makefile.inc U lib/libc/gen/__xuname.c U lib/libc/gen/uname.c U lib/libc/net/inet.3 U lib/libc/net/inet_addr.c U lib/libc/net/inet_lnaof.c U lib/libc/net/inet_makeaddr.c U lib/libc/net/inet_neta.c U lib/libc/net/inet_netof.c U lib/libc/net/inet_network.c U lib/libc/rpc/key_call.c U lib/libc/rpc/rpc_soc.3 U lib/libc/rpc/rpc_soc.c U lib/libfetch/fetch.3 U lib/libfetch/ftp.c U lib/libposix1e/acl_add_perm.3 U lib/libposix1e/acl_clear_perms.3 U lib/libposix1e/acl_copy_entry.3 U lib/libposix1e/acl_create_entry.3 U lib/libposix1e/acl_delete_perm.3 U lib/libposix1e/acl_get_permset.3 U lib/libposix1e/acl_get_qualifier.3 U lib/libposix1e/acl_get_tag_type.3 U lib/libposix1e/acl_set_permset.3 U lib/libposix1e/acl_set_qualifier.3 U lib/libposix1e/acl_set_tag_type.3 U libexec/ypxfr/ypxfr_extern.h U release/Makefile U release/texts/HARDWARE.TXT U secure/lib/libtelnet/Makefile U share/man/man9/module.9 U sys/compat/linux/linux_misc.c RCS file: /cvs/freebsd/src/sys/dev/an/if_aironet_ieee.h,v retrieving revision 1.3 retrieving revision 1.4 Merging differences between 1.3 and 1.4 into if_aironet_ieee.h M sys/dev/an/if_aironet_ieee.h RCS file: /cvs/freebsd/src/sys/dev/an/if_an.c,v retrieving revision 1.15 retrieving revision 1.16 Merging differences between 1.15 and 1.16 into if_an.c M sys/dev/an/if_an.c RCS file: /cvs/freebsd/src/sys/dev/an/if_anreg.h,v retrieving revision 1.5 retrieving revision 1.6 Merging differences between 1.5 and 1.6 into if_anreg.h M sys/dev/an/if_anreg.h U sys/dev/ata/atapi-all.c U sys/dev/ata/atapi-all.h U sys/dev/ata/atapi-cd.c U sys/dev/cnw/if_cnw.c U sys/dev/sound/isa/mss.c U sys/dev/sound/isa/mss.h U sys/dev/sound/pcm/ac97.c ? sys/i386/conf/LAPTOP_30W U sys/ia64/ia64/interrupt.c U sys/ia64/ia64/mp_machdep.c U sys/ia64/include/clock.h U sys/ia64/include/param.h U sys/kern/kern_intr.c U sys/kern/kern_lockf.c U sys/kern/kern_prot.c U sys/kern/kern_xxx.c U sys/kern/vnode_if.pl U sys/net/if_spppsubr.c U sys/netinet/in.h U sys/pc98/i386/machdep.c U sys/pc98/pc98/npx.c U sys/sys/types.h U sys/sys/utsname.h U sys/ufs/ffs/ffs_alloc.c U usr.bin/fetch/fetch.1 U usr.bin/fetch/fetch.c U usr.sbin/mptable/Makefile U usr.sbin/pkg_install/info/info.h U usr.sbin/pkg_install/info/main.c U usr.sbin/pkg_install/info/perform.c U usr.sbin/pkg_install/info/pkg_info.1 U usr.sbin/pkg_install/info/show.c U usr.sbin/pkg_install/lib/deps.c U usr.sbin/pkg_install/lib/exec.c U usr.sbin/pkg_install/lib/lib.h U usr.sbin/pkg_install/lib/match.c U usr.sbin/pkg_install/lib/msg.c U usr.sbin/pkg_install/lib/pen.c U usr.sbin/pkg_install/lib/str.c U usr.sbin/ppp/Makefile U usr.sbin/ppp/defs.h U usr.sbin/ppp/main.c U usr.sbin/ppp/systems.c U usr.sbin/sysinstall/config.c U usr.sbin/sysinstall/index.c U usr.sbin/sysinstall/install.c U usr.sbin/sysinstall/installUpgrade.c U usr.sbin/sysinstall/label.c U usr.sbin/sysinstall/menus.c U usr.sbin/sysinstall/sysinstall.8 U usr.sbin/sysinstall/wizard.c U usr.sbin/sysinstall/help/html.hlp U usr.sbin/sysinstall/help/options.hlp U usr.sbin/sysinstall/help/shortcuts.hlp dhcp-135[3] ^Dexit I had a PCcard in it, as usual -- a Cisco/Aironet 340 (an driver; the "messiness" around sys/dev/an up there is because I had been testing (for some time) the code that Archie committed). Here's a uni-diff of GENERIC vs. my kernel config. (I cheated a little: in my real config, I commented stuff (like SCSI-related things) out; for this exercise, I deleted the lines, then made the diff, so the result would be shorter clearer.) --- GENERIC Fri Mar 16 12:22:15 2001 +++ LAPTOP_30W Sat Mar 24 10:54:09 2001 @@ -15,21 +15,29 @@ # device lines is also present in the NOTES configuration file. If you are # in doubt as to the purpose or
Re: upgrade tcpdump in -current?
On Sat, Mar 24, 2001 at 03:19:54PM +0100, Mark Huizer wrote: Are there any plans on upgrading tcpdump to e.g. 3.6.2, which has better support for e.g. NFS over IPv6? Bill Fenner was working on this. I don't know what happened to it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world stops during i4b compilation
Ok, I did an ediff against NOTES. Perhaps it was the "1" argument to device loop1 #Network loopback device that was missing. I'll try again. Hmmm Seems odd. If you get a recurrence, you might want to share a diff between GENERIC and what you're using. Now it compiles. I had to put in a "device ether" line into my config to compile a kernel with i4b (IDSN) drivers. And this on box without ethernet card. Is this a bug or a feature? Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ICH2-M IDE controller
Hi All,
Is anyone looking at supporting the Intel ICH2-M IDE controller?
This controller is basically the same as the ICH2 controller except it has
extra powermanagment features as it's the for portable computers (hence
the M=mobile). I'm currently using the attached patch which runs
flawlessly on my laptop. However, I'm just an amature code hacker and
hence can't guarentee I haven't missed something between the chipsets.
The other question I have is why in ata-dma.c is there the fall through to
the ICH chipset? It seems to prevent any drive actually using ATA100/UDMA5
features.
Cheers,
--
* Benjamin Close
diff -u ./ata-dma.c fred/ata-dma.c
--- ./ata-dma.c Fri Mar 16 02:06:25 2001
+++ fred/ata-dma.c Sun Mar 25 10:33:52 2001
@@ -107,6 +107,7 @@
switch (scp-chiptype) {
+case 0x244a8086: /* Intel ICH2-M */
case 0x244b8086: /* Intel ICH2 */
if (udmamode = 5) {
int32_t mask48, new48;
@@ -150,7 +151,8 @@
ata_printf(scp, device,
"%s setting UDMA4 on ICH%s chip\n",
(error) ? "failed" : "success",
- (scp-chiptype == 0x244b8086) ? "2" : "");
+ (scp-chiptype == 0x244b8086) ? "2" :
+ (scp-chiptype == 0x244a8086) ? "2-M" :"");
if (!error) {
mask48 = (1 devno) + (3 (16 + (devno 2)));
new48 = (1 devno) + (2 (16 + (devno 2)));
diff -u ./ata-pci.c fred/ata-pci.c
--- ./ata-pci.c Tue Mar 20 00:01:58 2001
+++ fred/ata-pci.c Sun Mar 25 10:30:58 2001
@@ -110,6 +110,9 @@
case 0x24118086:
return "Intel ICH ATA66 controller";
+case 0x244a8086:
+ return "Intel ICH2-M ATA100 controller";
+
case 0x244b8086:
return "Intel ICH2 ATA100 controller";
panic: resource_list_alloc
just upgraded my tree and did a reinstall ... trace is:
resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at resource_list_alloc+0xd3
isa_alloc_resource() @ +0xd0
bus_alloc_resource() @ +0x5f
opti_detect @ +0x99
mss_detect @ +0x52
mss_probe @ +0x30a
device_probe_child @ +0xca
device_probe_and_attach @ +0x41
isa_probe_children @ +0xde
configure @ +0x32
mi_startup @ +0x6e
begin @ +0x29
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
PROFESSIONAL WEBSITES FOR $800 OR LESS-GAURANTEED!!!!
Do you own a small business and need a website? Or do you need a website to promote a party, event or any other major function? If so, please visit DT-GRAPHIX at http://www.dtgraphix.bigstep.com. We specialize in both HTML and FLASH sites. Thank you! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent interface/routing changes breaks on-demand PPP
On Fri, Mar 23, 2001 at 23:11:56 +, Brian Somers wrote: 1. Ppp is in -auto mode (or a ``set mode auto'' has been done). Here, ppp configures the interface as soon as it sees the ``set ifaddr'' line and never undoes that configuration. An ``add'' with a fixed IP number would never have worked if it's before the ``set ifaddr''. If it's after the ``set ifaddr'', nothing should ever remove it (as the interface will stay configured). 2. Ppp is not in -auto mode. Here, ppp won't assign the interface address 'till IPCP is up. Any attempt to ``add'' a route with a static IP number in ppp.conf should fail. So, the recent routing changes shouldn't have made a difference. Anyone know what I'm missing ? Andre, what does your ppp.conf look like and how are you running ppp ? ppp in -auto mode, "add" is after "set ifaddr" In which case your interface should stay configured despite the link coming down and your route should *not* be deleted. I'll see if I can reproduce this here (I need to upgrade a machine first). This was happening because ppp was deleting then re-adding the interface address when IPCP came up, causing the new routing code to nuke the static route. I've added an optimisation to stop this from happening, so your configuration should work ok again with src/usr.sbin/ppp/iface.c 1.17. -- Andrey A. Chernov http://ache.pp.ru/ -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rc.conf duplicating defaults/rc.conf
Once upon a time, before I knew better, I copied defaults/rc.conf to
rc.conf and edited it to my needs.
Therefore I had many lines in rc.conf which were unnessecary, because
they just repeated the defaults.
I have thrown together this script, which just outputs the needed lines
in rc.conf.
If VERBOSE is set, it also prints
##= Is default: Somelabel="somevalue"
if rc.conf and defaults/rc.conf agree on the value of Somelabel
##- Default: Somelabel="defaultvalue"
if rc.conf and defaults/rc.conf disagree on the value of Somelabel.
Btw, why can't I run this as a bang-script?
Typing ./defcheck just produces:
awk: cmd. line 1: ./defcheck
awk: cmd. line 1: ^ syntax error
- - - - filename: defcheck
#!/usr/bin/awk
#
# Quick hack to check if rc.conf unnessecary duplicate
# lines in defaults/rc.conf
#
# Assume all lines are in format label="value"
#
# Prints lines in rc.conf which are not in defaults/rc.conf
# If VERBOSE==1 below, also prints defaults.
#
# usage:
# cd /etc; awk -f defcheck
#
# Other files in defaults may be checked:
# cd /etc; awk -f defcheck -v CHECK=otherfile.conf
#
# Leif Neland
# [EMAIL PROTECTED]
# 25.marts.2001
#
BEGIN {
if (CHECK=="") {
CHECK="rc.conf"
}
VERBOSE=0;
### Read defaults into array
DEFAULT="defaults/"CHECK;
FS="#";
while (getline DEFAULT 0) {
m=split($1,a,"\"");
if (m==3) {linie[sprintf("%s\"%s\"",a[1],a[2])]=1;
default[a[1]]=a[2];}
}
##
while (getline CHECK 0)
{
flag=1;
m=split($1,a,"\"");
if (m==3) {l=sprintf("%s\"%s\"",a[1],a[2]);
if (l in linie) {
if (VERBOSE) print "##= Is default: ",l;
flag=0;
} else {
if (VERBOSE a[1] in default) {print "##- Default "a[1]"\""default[a[1]]"\""};
}
}
if (flag) {print};
}
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: panic: resource_list_alloc
On 25-Mar-01 The Hermit Hacker wrote:
just upgraded my tree and did a reinstall ... trace is:
resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
resource_list_alloc+0xd3
isa_alloc_resource() @ +0xd0
bus_alloc_resource() @ +0x5f
opti_detect @ +0x99
This is the second such one I've seen in opti_detect. I'm guessing that 'mms'
is a sound driver? If so, can you try taking it out of your kernel to see if
that is what is causing the panic?
mss_detect @ +0x52
mss_probe @ +0x30a
device_probe_child @ +0xca
device_probe_and_attach @ +0x41
isa_probe_children @ +0xde
configure @ +0x32
mi_startup @ +0x6e
begin @ +0x29
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary:
scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
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: panic: resource_list_alloc
doing so right now ... one quick/stupid question ... how does one
'reinstall' a new kernel so that you don't lose the /boot/kernel.old (aka
backup that worked)? I've been moving files around before installing the
rebuilt kernel, but that doesn't sound very efficient ... :)
thanks ..
On Sat, 24 Mar 2001, John Baldwin wrote:
On 25-Mar-01 The Hermit Hacker wrote:
just upgraded my tree and did a reinstall ... trace is:
resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
resource_list_alloc+0xd3
isa_alloc_resource() @ +0xd0
bus_alloc_resource() @ +0x5f
opti_detect @ +0x99
This is the second such one I've seen in opti_detect. I'm guessing that 'mms'
is a sound driver? If so, can you try taking it out of your kernel to see if
that is what is causing the panic?
mss_detect @ +0x52
mss_probe @ +0x30a
device_probe_child @ +0xca
device_probe_and_attach @ +0x41
isa_probe_children @ +0xde
configure @ +0x32
mi_startup @ +0x6e
begin @ +0x29
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary:
scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
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/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: panic: resource_list_alloc
removing pcm fixes the panic, it appears ...
On Sat, 24 Mar 2001, John Baldwin wrote:
On 25-Mar-01 The Hermit Hacker wrote:
just upgraded my tree and did a reinstall ... trace is:
resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
resource_list_alloc+0xd3
isa_alloc_resource() @ +0xd0
bus_alloc_resource() @ +0x5f
opti_detect @ +0x99
This is the second such one I've seen in opti_detect. I'm guessing that 'mms'
is a sound driver? If so, can you try taking it out of your kernel to see if
that is what is causing the panic?
mss_detect @ +0x52
mss_probe @ +0x30a
device_probe_child @ +0xca
device_probe_and_attach @ +0x41
isa_probe_children @ +0xde
configure @ +0x32
mi_startup @ +0x6e
begin @ +0x29
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary:
scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
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/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: panic: resource_list_alloc
On Sat, Mar 24, 2001 at 11:24:47PM -0400, The Hermit Hacker wrote: doing so right now ... one quick/stupid question ... how does one 'reinstall' a new kernel so that you don't lose the /boot/kernel.old (aka make reinstall -or- make kernel-reinstall removing pcm fixes the panic, it appears ... Yep! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: resource_list_alloc
Try "make reinstall". I have been doing quite a bit of this since my kernel panics before it ever gets all the way up. The last good kernel I have is about a month old. Actually, I moved /boot/kernel.old to another name in case I accidentally did an install instead of a reinstall. I don't want to leave my machine unable to boot. Jim Bloom [EMAIL PROTECTED] The Hermit Hacker wrote: doing so right now ... one quick/stupid question ... how does one 'reinstall' a new kernel so that you don't lose the /boot/kernel.old (aka backup that worked)? I've been moving files around before installing the rebuilt kernel, but that doesn't sound very efficient ... :) thanks .. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: panic: resource_list_alloc
On 25-Mar-01 The Hermit Hacker wrote:
doing so right now ... one quick/stupid question ... how does one
'reinstall' a new kernel so that you don't lose the /boot/kernel.old (aka
backup that worked)? I've been moving files around before installing the
rebuilt kernel, but that doesn't sound very efficient ... :)
thanks ..
# cd /sys/compile/FOO
# build like normal
# make reinstall
Also, if you want to be super careful, keep a /boot/kernel.good lying around
that has a known working kernel in it.
On Sat, 24 Mar 2001, John Baldwin wrote:
On 25-Mar-01 The Hermit Hacker wrote:
just upgraded my tree and did a reinstall ... trace is:
resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
resource_list_alloc+0xd3
isa_alloc_resource() @ +0xd0
bus_alloc_resource() @ +0x5f
opti_detect @ +0x99
This is the second such one I've seen in opti_detect. I'm guessing that
'mms'
is a sound driver? If so, can you try taking it out of your kernel to see
if
that is what is causing the panic?
mss_detect @ +0x52
mss_probe @ +0x30a
device_probe_child @ +0xca
device_probe_and_attach @ +0x41
isa_probe_children @ +0xde
configure @ +0x32
mi_startup @ +0x6e
begin @ +0x29
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary:
scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
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/
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary:
scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
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: panic: resource_list_alloc
On 25-Mar-01 The Hermit Hacker wrote:
removing pcm fixes the panic, it appears ...
David O`Brien just confirmed it on his box as well.
On Sat, 24 Mar 2001, John Baldwin wrote:
On 25-Mar-01 The Hermit Hacker wrote:
just upgraded my tree and did a reinstall ... trace is:
resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
resource_list_alloc+0xd3
isa_alloc_resource() @ +0xd0
bus_alloc_resource() @ +0x5f
opti_detect @ +0x99
This is the second such one I've seen in opti_detect. I'm guessing that
'mms'
is a sound driver? If so, can you try taking it out of your kernel to see
if
that is what is causing the panic?
mss_detect @ +0x52
mss_probe @ +0x30a
device_probe_child @ +0xca
device_probe_and_attach @ +0x41
isa_probe_children @ +0xde
configure @ +0x32
mi_startup @ +0x6e
begin @ +0x29
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary:
scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
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/
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary:
scrappy@{freebsd|postgresql}.org
--
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: Problem with tun device and trafshow/tcpdump?
I found this message in one of my inboxs - I forgot to reply :*) I believe this was fixed last October (at BSDCon)... can you confirm ? Hi everyone. Ok apologies first to anyone who has been asked this question before, I've searched the mail lists and cannot find anything like this recently. The problem is when using user ppp and some kind of traffic monitor program like trafshow or tcpdump. There are three problems I've noticed: 1, When using trafshow there's no incoming packets seen at all. 2, When using tcpdump or trafshow there's no name resolution on any packets shown. 3, When using tcpdump, incoming packets can been seen on the tun device, except incoming icmp. Can anyone suggest a fix for this? I was also told that 4.0-RELEASE is affected by this. Thanks for your time. Steve. -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rc.conf duplicating defaults/rc.conf
In the last episode (Mar 25), Leif Neland said: Btw, why can't I run this as a bang-script? Typing ./defcheck just produces: awk: cmd. line 1: ./defcheck awk: cmd. line 1: ^ syntax error - - - - filename: defcheck #!/usr/bin/awk Try #! /usr/bin/awk -f -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current kernel build broken in sc0
I get this when I add the following lines to my kernel build options SC_NORM_ATTR=(FG_GREEN|BG_BLACK) options SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN) options SC_KERNEL_CONS_ATTR=(FG_LIGHTRED|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_BLACK|BG_RED) [snip make depend] genassym.c /kern/link_aout.c /usr/src/sys/kern/subr_diskmbr.c /usr/src/sys/libkern/divdi3.c /usr/src/sys/libkern/moddi3.c /usr/src/sys/libkern/qdivrem.c /usr/src/sys/libkern/ucmpdi2.c /usr/src/sys/libkern/udivdi3.c /usr/src/sys/libkern/umoddi3.c param.c vnode_if.c hints.c config.c /usr/src/sys/i386/i386/genassym.c In file included from /usr/src/sys/dev/fb/vga.c:34: opt_syscons.h:2: unterminated string or character constant opt_syscons.h:2: possible real start of unterminated constant In file included from /usr/src/sys/dev/syscons/schistory.c:33: opt_syscons.h:2: unterminated string or character constant opt_syscons.h:2: possible real start of unterminated constant In file included from /usr/src/sys/dev/syscons/scmouse.c:29: opt_syscons.h:2: unterminated string or character constant opt_syscons.h:2: possible real start of unterminated constant -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current kernel build broken in sc0
On Sat, Mar 24, 2001 at 10:35:58PM -0600, Michael C . Wu scribbled: | I get this when I add the following lines to my kernel build | options SC_NORM_ATTR=(FG_GREEN|BG_BLACK) | options SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN) | options SC_KERNEL_CONS_ATTR=(FG_LIGHTRED|BG_BLACK) | options SC_KERNEL_CONS_REV_ATTR=(FG_BLACK|BG_RED) | | [snip make depend] | genassym.c | /kern/link_aout.c /usr/src/sys/kern/subr_diskmbr.c /usr/src/sys/libkern/divdi3.c |/usr/src/sys/libkern/moddi3.c /usr/src/sys/libkern/qdivrem.c |/usr/src/sys/libkern/ucmpdi2.c /usr/src/sys/libkern/udivdi3.c |/usr/src/sys/libkern/umoddi3.c param.c vnode_if.c hints.c config.c |/usr/src/sys/i386/i386/genassym.c | In file included from /usr/src/sys/dev/fb/vga.c:34: | opt_syscons.h:2: unterminated string or character constant | opt_syscons.h:2: possible real start of unterminated constant | In file included from /usr/src/sys/dev/syscons/schistory.c:33: | opt_syscons.h:2: unterminated string or character constant | opt_syscons.h:2: possible real start of unterminated constant | In file included from /usr/src/sys/dev/syscons/scmouse.c:29: | opt_syscons.h:2: unterminated string or character constant | opt_syscons.h:2: possible real start of unterminated constant | Sorry, forgot to mention that it was fresh src/ cvsupped three hours ago. -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: resource_list_alloc
just upgraded my tree and did a reinstall ... trace is: resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at resource_list_alloc+0xd3 isa_alloc_resource() @ +0xd0 bus_alloc_resource() @ +0x5f opti_detect @ +0x99 mss_detect @ +0x52 mss_probe @ +0x30a device_probe_child @ +0xca device_probe_and_attach @ +0x41 isa_probe_children @ +0xde configure @ +0x32 mi_startup @ +0x6e begin @ +0x29 can you try http://people.freebsd.org/~cg/mssfix.diff.gz ? -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: resource_list_alloc
From: "Cameron Grant" [EMAIL PROTECTED] Date: Sun, 25 Mar 2001 05:58:53 +0100 can you try http://people.freebsd.org/~cg/mssfix.diff.gz ? Yup. Works -- thanks! (Same kernel config that I had been using: I didn't disable sound.) Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: resource_list_alloc
On Sun, Mar 25, 2001 at 05:58:53AM +0100, Cameron Grant wrote: can you try http://people.freebsd.org/~cg/mssfix.diff.gz ? Fixed my panics too. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ICH2-M IDE controller
I think there are a few chips like that, that cannot do ATA100, but only vaguely remember hearing about it. - Original Message - From: "Benjamin Close" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, March 24, 2001 6:49 PM Subject: ICH2-M IDE controller Hi All, Is anyone looking at supporting the Intel ICH2-M IDE controller? This controller is basically the same as the ICH2 controller except it has extra powermanagment features as it's the for portable computers (hence the M=mobile). I'm currently using the attached patch which runs flawlessly on my laptop. However, I'm just an amature code hacker and hence can't guarentee I haven't missed something between the chipsets. The other question I have is why in ata-dma.c is there the fall through to the ICH chipset? It seems to prevent any drive actually using ATA100/UDMA5 features. Cheers, -- * Benjamin Close To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/etc/exports: 192.168.5 = 192.168.0.5
Bug or pilot error? My network is 192.168.5.0 I used to have im my /etc/exports: /var -alldirs -maproot=root: -network 192.168.5 -mask 255.255.255.0 But after the portmapper change, I couldn't mount, was getting permission denied. showmount -e showed 192.168.5 was being interpreted as 192.168.0.5 Changing -network to 192.168.5.0 fixed it, naturally, but the 192.168.5 used to work. Is this change intentional, or is 192.168.5 supposed to work? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /etc/exports: 192.168.5 = 192.168.0.5
Leif Neland wrote: Bug or pilot error? My network is 192.168.5.0 I used to have im my /etc/exports: /var -alldirs -maproot=root: -network 192.168.5 -mask 255.255.255.0 But after the portmapper change, I couldn't mount, was getting permission denied. showmount -e showed 192.168.5 was being interpreted as 192.168.0.5 Changing -network to 192.168.5.0 fixed it, naturally, but the 192.168.5 used to work. Is this change intentional, or is 192.168.5 supposed to work? Leif My buest guess is that this is because it is now using something like inet_addr() for decoding the address instead of some roll-your-own code. FWIW, this zero fill is a standard part of the system: peter@daintree[11:24pm]~src/sys/pci-142 ping 192.168.5 PING 192.168.5 (192.168.0.5): 56 data bytes .. peter@daintree[12:13am]~src/sys/pci-143 ping 127.1 PING 127.1 (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.068 ms .. This is far more prolific in IPv6. Eg: "ping ::1" is localhost. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
