Re: Can't delete IPV6 addresses with ifconfig
> I'd like to know what goes on behind the mask. > > I sifted through /etc/rc.d and so on but it's not very clear. See sysctl net.inet6.ip6.auto_linklocal -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't delete IPV6 addresses with ifconfig
On Fri, 15 Feb 2008, Hajimu UMEMOTO wrote: > Hi, > > > On Fri, 15 Feb 2008 10:53:27 +1030 > > "Daniel O'Connor" <[EMAIL PROTECTED]> said: > > doconnor> Any idea what creates the link local address at startup? > (Mainly to doconnor> satisfy my curiosity :) > > Put ipv6_enable="YES" into your /etc/rc.conf Yeah but I need to reboot to have it work it's magic.. I'd like to know what goes on behind the mask. I sifted through /etc/rc.d and so on but it's not very clear. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
atheros and interrupt storm 7.0-RC*
ath0: mem 0xec00-0xec00 irq 16 at device 8.0 on pci0 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:19:5b:66:e4:2f ath0: mac 7.9 phy 4.5 radio 5.6 interrupt storm detected on "irq16:"; throttling interrupt source interrupt storm detected on "irq16:"; throttling interrupt source interrupt storm detected on "irq16:"; throttling interrupt source interrupt storm detected on "irq16:"; throttling interrupt source interrupt storm detected on "irq16:"; throttling interrupt source interrupt storm detected on "irq16:"; throttling interrupt source interrupt storm detected on "irq16:"; throttling interrupt source interrupt storm detected on "irq16:"; throttling interrupt source interrupt storm detected on "irq16:"; throttling interrupt source interrupt storm detected on "irq16:"; throttling interrupt source FreeBSD xxx 7.0-RC2 FreeBSD 7.0-RC2 #3: Fri Feb 8 15:57:45 BRT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/xxx_7 i386 this happens sice forever :( thanks matheus -- We will call you cygnus, The God of balance you shall be ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Rebuilding World Problems
Quoting Kevin Oberman <[EMAIL PROTECTED]>: Date: Wed, 13 Feb 2008 13:25:04 -0800 From: "Chris H." <[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] Quoting Gavin Spomer <[EMAIL PROTECTED]>: > Thanks, this was very helpful. First of all I would just like to > admit that I only gave /usr/src/UPDATING a quick glance. Shame on me; > it might have solved most (if not all) of my problem if I had read > more thoroughly. > > Surprisingly I grokked most of your cheatsheet and looked at a few > man pages to figure out most of the rest. Haven't tried it all yet. I > was wondering about the "mount -u /". Is it really necessary to mount > the root partition prior to mounting all of them in the next step? Absolutely. Think about it for a momment. Given that EVERYTHING (save swap) is mounted off of root ( / ). So it becomes quite impossible to mount /usr/ if / hasn't already been mounted. In other words; if / hasn't been mounted it doesn't exist for usr/ to mount from it. :) Absolutely not. You are stretching the logic a bit too far on this. I'll admit I am baffled by why imp added this to UPDATING. If you have a valid fstab file, it will have a line (usually the first non-comment line) that specifies the partition as (1) ufs and (2) rw. As a result, 'mount -a -t ufs' will remount / as read-write before trying to mount any other file systems. In over a decade of using FreeBSD (since early V3 days), I have never bothered to specify the explicit remount of /. > > I don't really understand the "swapon -a". When is it necessary and > when is it not? As a rule, it is already available after boot. So executing swapon -a is often considered overkill. /But/ absolutely no harm will come of doing it, and it /may/ be necessary. So this just insures you have an "event free" journey. :) Actually, swap is not enabled in single-user mode. It is enabled very early in the startup sequence going to multiuser, but, for obvious reasons, it can't be enabled until dumpon has run. It also starts after initrandom, geli, gbde, encswap, and ccd, although most people don't have all of these enabled. If you are upgrading a system with limited memory and don't start swap, you may run out of RAM and the upgrade will freeze. Not good. Even if it odes not freeze, memory fragmentation could significantly slow progress. In most systems the installworld and mergemaster will never touch swap and the step has no impact, but it never hurts. > > Also, UPDATING has "adjkerntz -i" just before "mergemaster -p". I > looked at the man page for adjkerntz and am still uncertain if I need > to do this. I run an ntpd client, if that makes any difference. Again, just a precaution. Think "safe", or "event free". :) Not at all. Many systems run with a hardware (BIOS) clock set to local time. Your system will run with this time until ntpd can reset it near the end of the init sequence. Many files may be created with broken timestamps during this interval. You can easily check by entering the command 'date' after the system reaches the single-user prompt. If the time printed is correct, there is no need for the 'adjkerntz -i'. If the time is an hour or more off, it is needed. If you live in the UK or any other country in the 0 offset time zone (not many) and it's not summer time, this is not an issue. > > I think the documentation is an excellent reference for people who > already, moderately know FreeBSD. I am not even a true newbie as I > have a CS degree and have been a Linux admin for 2 years. Even so I > often have a hard time with the complexity of FreeBSD. I recognize > the value of understanding the fine-grain "nuts and bolts" of a > system, but even so I wonder if FreeBSD over-complicates some things? This is the "UNIX way". It breaks everything into small bits of useful stuff. There-by providing the "nuts & bolts" to build, or accomplish almost /anything/ with little, or no effort. Linux kind of "missed the boat" on this one. But even Linus T. indicates that Linux is not UNIX. I'd have to say, it's more a "feels like UNIX" than anything else. Sorry, but this is not Linus' doing. for better or worse. He provides a kernel, not an operating system. Red Hat, Suse, Mandriva, Ubuntu, Debian, et. al. provide operating systems that use Linus' kernel and use the name Linux. To sum things up; given that I've been using BSD since long before FreeBSD even existed. I can't imagine how anyone would consider using anything /but/ *BSD. It is /infinitely/ flexible, which only adds to it's power. While - as you mentioned, it seems complicated to a new user. One must remember, after all, that it is a /server/ and perhaps, not best suited to an average "desktop" user. But, if given the time, will become your best friend - /really/. :) I, too, have been using BSD for a bit longer than FreeBSD has existed, having used it while supporting the UC Davis Department of Applied Sciences back in the 1970s. Not that the CSRG BSD days are relevant to much of this as
Re: Rebuilding World Problems
Quoting Gavin Spomer <[EMAIL PROTECTED]>: Hallelujah! My "world" is rebuilt! Thanks to Chris, "[EMAIL PROTECTED]", Kevin and Jim for educating me and pointing me in the right direction. Will definitely research further and continue to have a blast with FreeBSD on my test server. It very well could be that I will be using FreeBSD for my production servers by next Fall. :D EXCELLENT! Welcome aboard! :) --Chris H - Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't delete IPV6 addresses with ifconfig
> > Yes, after I created a link local address for fxp0 it worked fine. > > I had to do so manually though - I am not sure what is responsible for=20 > making them. I just rebooted it and it seems OK now though.. > > Any idea what creates the link local address at startup? (Mainly to=20 > satisfy my curiosity :) My border gateway has: ipv6_enable="YES" ipv6_prefix_tx0="2001:0470:1F00:0820 fd92:7065:0b8e:" ipv6_gateway_enable="YES" rtadvd_enable="YES" rtadvd_interfaces="tx0" I've also use a tunnel broker to get external connectivity called from /etc/dhclient_exit_hooks /usr/local/bin/perl -T /etc/tunnelbroker-update-0.07b.pl & /etc/dhclient_exit_hooks also configures the 6to4 relay so that traffic to 6to4 addresses gets dumped to IPv4 as soon as possible. # #Configure 6 to 4 relay # octets=`echo $new_ip_address | sed 's/\./ /g'` ifconfig stf0 inet6 2002:`printf %02x%02x:%02x%02x $octets`:::1 \ prefixlen 16 alias deprecated link0 route add -inet6 2002:: -prefixlen 16 ::1 route change -inet6 2002:: -prefixlen 16 ::1 -ifp stf0 The laptop has: ipv6_enable="YES" Both have firewalls, etc. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't delete IPV6 addresses with ifconfig
Hi, > On Fri, 15 Feb 2008 10:53:27 +1030 > "Daniel O'Connor" <[EMAIL PROTECTED]> said: doconnor> Any idea what creates the link local address at startup? (Mainly to doconnor> satisfy my curiosity :) Put ipv6_enable="YES" into your /etc/rc.conf Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED],jp.}FreeBSD.org http://www.imasy.org/~ume/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't delete IPV6 addresses with ifconfig
On Fri, 15 Feb 2008, Mark Andrews wrote: > > Now to work out how to get rtadv going :) > > bsdi# ps ax | grep rtadv > 181 ?? Is 0:09.44 rtadvd tx0 > 36505 p1 S+ 0:00.01 grep rtadv > bsdi# Yes, after I created a link local address for fxp0 it worked fine. I had to do so manually though - I am not sure what is responsible for making them. I just rebooted it and it seems OK now though.. Any idea what creates the link local address at startup? (Mainly to satisfy my curiosity :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: dmesg : no output on 1 of 2 7-stable boxes
Oliver Fromme wrote: > Hello Julian, > > I'm sorry this is a late reply, but I noticed your post > on the freebsd-stable list just now. > > One of 2 laptops running 7-stable shows nothing with dmesg, (other is OK). > Did you try "dmesg -a"? Thanks Oliver, Yes, but after posting I think, (Been a while can't remember), Symptom stopped after "cd /usr/local/lib; mv wine wine.MV" (a bad port !). It was filling console buf with junk. > The dmesg buffer is a circular buffer containing both > kernel output and console output. However, "dmesg" > displays only the kernel output. If there was lots of > console output, it filled all of the dmesg buffer, > so "dmesg" displays nothing (all of the kernel output > was overwritten by console output). "dmesg -a" will > display everything, i.e. kernel + console output. Some of that description could usefuly be added to `man dmesg` ? Might some commiter wnat to hack a few words in ? Or do we neeed a formal send-pr (that a commiter would rephrase likely anyway, so best skip the send-pr ? ). > If "dmesg -a" doesn't print anything either, I'm afraid > I have no idea what might be wrong. Well, you could try > "sysctl -b kern.msgbuf" which will retrieve the raw > contents of the dmesg buffer. > > >- I tried loader.confkern.msgbuf=64000 > > I think it must be a multiple of the pages size, i,e, > 4K = 4096 on FreeBSD/i386. I usually set it to 65536 > or 131072. Ah! Certainly plausible re. 2 base N. On 7.0PRERELEASE I see kern.msgbuf= sundry text diagnostsics so seems inappropriate to set that var to a number. I see kern.consmsgbuf_size: 8192 so tried in /boot/loader.conf kern.consmsgbuf_size=4096 but even reducing size failed to vary size (enlarging had earlier failed) Some clue in sys/kern/tty_cons.c:666 I See kern.msgbuf_clear: Clear kernel message buffer kern.msgbuf: Contents of kernel message buffer Puzzled on syntax to set size in loader.conf ? -- Julian Stacey. BSD Unix Linux Net Consultant, Munich. http://berklix.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.0-PRERELEASE Fatal Trap 12 with sysctl and acpi
I'm having some trouble with a SuperMicro SuperServer 6022L-6 that
previously ran 7.0-BETA4 without problems. Today, I updated this machine to
7.0-PRERELEASE and now it will not fully boot unless I disable ACPI. A quick
search of the PR database didn't turn up anything similar with sysctl and ACPI.
I can boot to single user mode, but if I issue sysctl -a while there, it
also crashes.
I have two vmcore files, one where I booted to single user mode and issued
sysctl -a, the other when it was attempting to boot normally.
When running sysctl -a in single user mode, the last three lines before the
crash are (transcribed by hand, no serial console available):
dev.pcib.3.%location: handle=\_SB_.PCI3
dev.pcib.3.%pnpinfo: _HID=PNP0A03 UID=3
dev.pcib.3.%parent: acpi0
=
Kernel config is GENERIC, with ULE scheduler and "options ASR_COMPAT"
=
[EMAIL PROTECTED] /usr/obj/usr/src/sys/TEST]# uname -a
FreeBSD test1.hpcisp.com 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Thu Feb
14 14:08:02 EST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST i386
=
[EMAIL PROTECTED] /usr/obj/usr/src/sys/TEST]# kgdb kernel.debug
/var/crash/vmcore.1
Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address = 0x2043455c
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0743036
stack pointer = 0x28:0xe8cb3a0c
frame pointer = 0x28:0xe8cb3a38
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 67 (sysctl)
trap number = 12
panic: page fault
cpuid = 3
Uptime: 6s
Physical memory: 2035 MB
Dumping 65 MB: 50 34 18 2
#0 doadump () at pcpu.h:195
195 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt
#0 doadump () at pcpu.h:195
#1 0xc073aa38 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc073acf1 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:563
#3 0xc0a1fd00 in trap_fatal (frame=0xe8cb39cc, eva=541279580) at
/usr/src/sys/i386/i386/trap.c:899
#4 0xc0a1ff70 in trap_pfault (frame=0xe8cb39cc, usermode=0,
eva=541279580) at /usr/src/sys/i386/i386/trap.c:812
#5 0xc0a208ed in trap (frame=0xe8cb39cc) at
/usr/src/sys/i386/i386/trap.c:490
#6 0xc0a07bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc0743036 in sysctl_sysctl_next_ls (lsp=Variable "lsp" is not
available.
) at /usr/src/sys/kern/kern_sysctl.c:630
#8 0xc07430f6 in sysctl_sysctl_next_ls (lsp=Variable "lsp" is not
available.
) at /usr/src/sys/kern/kern_sysctl.c:618
#9 0xc0743133 in sysctl_sysctl_next_ls (lsp=Variable "lsp" is not
available.
) at /usr/src/sys/kern/kern_sysctl.c:630
#10 0xc0743133 in sysctl_sysctl_next_ls (lsp=Variable "lsp" is not
available.
) at /usr/src/sys/kern/kern_sysctl.c:630
#11 0xc0743196 in sysctl_sysctl_next (oidp=0xc0b53280, arg1=0xe8cb3c1c,
arg2=4, req=0xe8cb3ba4)
at /usr/src/sys/kern/kern_sysctl.c:651
#12 0xc0743aa2 in sysctl_root (oidp=Variable "oidp" is not available.
) at /usr/src/sys/kern/kern_sysctl.c:1306
#13 0xc0743bde in userland_sysctl (td=0xc5479660, name=0xe8cb3c14,
namelen=6, old=0xbfbfe4e8, oldlenp=0xbfbfe598, inkernel=0,
new=0x0, newlen=0, retval=0xe8cb3c10, flags=0) at
/usr/src/sys/kern/kern_sysctl.c:1401
#14 0xc0744812 in __sysctl (td=0xc5479660, uap=0xe8cb3cfc) at
/usr/src/sys/kern/kern_sysctl.c:1336
#15 0xc0a202b8 in syscall (frame=0xe8cb3d38) at
/usr/src/sys/i386/i386/trap.c:1035
#16 0xc0a07c40 in Xint0x80_syscall () at
/usr/src/sys/i386/i386/exception.s:196
#17 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
=
dmesg is attached, but it is from a non-acpi boot.
=
Anyone have any ideas on what might be the cause or a possible fix?
I'll keep the crash dumps around. This is a test box that I'm researching
7.0 on for possible production use on similar hardware. There is no planned
usage yet, and no other plans for this box, so anything goes in terms of
possible debugging.
If I get some time next week I might try a binary search of commits between
BETA4 and now, to pinpoint where it stopped working.
Thanks,
Jim
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-PRERELEASE #1: Thu Feb 14 14:08:02 EST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST
Timecounter "i8254"
Re: Can't delete IPV6 addresses with ifconfig
> --nextPart1526557.1B05VYlNaf > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > On Thu, 14 Feb 2008, Hajimu UMEMOTO wrote: > > doconnor> Anyone know the right way to do this? :) > > > > sudo ifconfig fxp0 inet6 2002:792d:8527::1:1 -alias > > Ahah, thanks, that works. > > Now to work out how to get rtadv going :) bsdi# ps ax | grep rtadv 181 ?? Is 0:09.44 rtadvd tx0 36505 p1 S+ 0:00.01 grep rtadv bsdi# > > =2D-=20 > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > --nextPart1526557.1B05VYlNaf > Content-Type: application/pgp-signature; name=signature.asc > Content-Description: This is a digitally signed message part. > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.4 (FreeBSD) > > iD8DBQBHtDZS5ZPcIHs/zowRAj9bAJ9ujJF6n0o+zyXgKyQwvx0saglqzwCfdML8 > F3e7nxGQXyYruOWythI/V3g= > =iphe > -END PGP SIGNATURE- > > --nextPart1526557.1B05VYlNaf-- -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "ad0: TIMEOUT - WRITE_DMA" type errors with 7.0-RC1
On Tue, Feb 12, 2008 at 01:03:35AM +0100, Torfinn Ingolfsen wrote: > On Mon, 11 Feb 2008 13:00:57 +0100 > [EMAIL PROTECTED] (Remco van Bekkum) wrote: > > > here? It's on an amd64, Asus m2a-vm with ati xp600, AMD BE-2350 CPU, > > 2GB 800MHz RAM. > > FWIW, I have the almost the same motherboard (m2a-vm hdmi) with an AMD > Phenom 9500 and 4GB RAM[1]. Different disk, though. The (single) disk > drive has worked without problems so far. I'm using standard ufs2 > filesystems on that disk. I'm running RELENG_7: > [EMAIL PROTECTED] uname -a > FreeBSD kg-vm.kg4.no 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #6: Sat Jan > 26 20:58:51 CET 2008 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 > [EMAIL PROTECTED] atacontrol list > ATA channel 0: > Master: acd0 ATA/ATAPI revision 0 > Slave: no device present > ATA channel 2: > Master: ad4 Serial ATA II > Slave: no device present > ATA channel 3: > Master: no device present > Slave: no device present > ATA channel 4: > Master: no device present > Slave: no device present > ATA channel 5: > Master: no device present > Slave: no device present > > > References: > 1) http://tingox.googlepages.com/asus_m2a-vm_hdmi_freebsd > -- > Regards, > Torfinn Ingolfsen > Thanks, here some more detailed info from me: xaero# dmesg | grep atapci atapci0: port 0xfc00-0xfc07,0xf800-0xf803,0xf400-0xf407,0xf000-0xf003,0xec00-0xec0f mem 0xfe02f000-0xfe02f3ff irq 22 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci0 ata3: on atapci0 ata4: on atapci0 ata5: on atapci0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe400-0xe40f at device 20.1 on pci0 ata0: on atapci1 xaero# atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 2: Master: ad4 Serial ATA II Slave: no device present ATA channel 3: Master: ad6 Serial ATA II Slave: no device present ATA channel 4: Master: ad8 Serial ATA II Slave: no device present ATA channel 5: Master: ad10 Serial ATA II Slave: no device present xaero# uname -a FreeBSD xaero.spacemarines.us 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Sun Feb 10 16:07:39 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 I'm using bios 1603, and a seasonic 330W PSU. The errors appear to happen at random, heavy I/O doesn't trigger it. I can rebuild world without problems, so I guess the CPU is ok. The memory has been tested and showed no errors. What's left is cables and mainboard. But how error-prone are sata cables? Considering that I've got 50% failing... Okay, maybe that should "prove" that the mainboard is faulty :) -Remco ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Promise driver/support
is there support for this Promise card? [EMAIL PROTECTED]:4:14:0: class=0x010400 card=0x0374105a chip=0x8350105a rev=0x00 hdr=0x00 vendor = 'Promise Technology Inc' class = mass storage subclass = RAID thanks, danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't delete IPV6 addresses with ifconfig
On Thu, 14 Feb 2008, Hajimu UMEMOTO wrote: > doconnor> Anyone know the right way to do this? :) > > sudo ifconfig fxp0 inet6 2002:792d:8527::1:1 -alias Ahah, thanks, that works. Now to work out how to get rtadv going :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: Can't delete IPV6 addresses with ifconfig
On Thu, 14 Feb 2008, Mark Andrews wrote: > > --nextPart1996860.fztbeObibp > > Content-Type: text/plain; > > charset="utf-8" > > Content-Transfer-Encoding: quoted-printable > > Content-Disposition: inline > > > > Hi, > > I am experimenting with IPv6 and I can't seem to remove an IPv6 > > address=20 from an interface, eg I have.. > > [midget 22:11] ~ >ifconfig fxp0 > > fxp0: flags=3D8943 > > mtu=20 1500 > > options=3Db > > inet 10.0.2.1 netmask 0xff00 broadcast 10.0.2.255 > > inet 10.0.2.3 netmask 0x broadcast 10.0.2.3 > > inet 10.0.2.4 netmask 0x broadcast 10.0.2.4 > > inet 10.0.2.7 netmask 0x broadcast 10.0.2.7 > > inet6 2002:792d:8527::1:1 prefixlen 64 > > ether 00:02:b3:32:2c:51 > > media: Ethernet 100baseTX > > status: active > > > > But I can't remove it, viz.. > > [midget 22:11] ~ >sudo ifconfig fxp0 -alias 2002:792d:8527::1:1/64 > > ifconfig: 2002:792d:8527::1:1/64: bad value > > [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1/64 > > ifconfig: 2002:792d:8527::1:1/64: bad value > > [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1 > > ifconfig: 2002:792d:8527::1:1: bad value > > [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1=20 > > prefixlen 64 > > ifconfig: 2002:792d:8527::1:1: bad value > > [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::/64 > > ifconfig: 2002:792d:8527::/64: bad value > > > > Anyone know the right way to do this? :) > > ifconfig fxp0 -alias inet6 2002:792d:8527::1:1 This doesn't work, what Hajimu suggested does though. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: Can't delete IPV6 addresses with ifconfig
On Thu, 14 Feb 2008, Daniel O'Connor wrote: Hi, I am experimenting with IPv6 and I can't seem to remove an IPv6 address from an interface, eg I have.. But I can't remove it, viz.. [midget 22:11] ~ >sudo ifconfig fxp0 -alias 2002:792d:8527::1:1/64 ifconfig: 2002:792d:8527::1:1/64: bad value [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1/64 ifconfig: 2002:792d:8527::1:1/64: bad value [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1 ifconfig: 2002:792d:8527::1:1: bad value [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1 prefixlen 64 ifconfig: 2002:792d:8527::1:1: bad value [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::/64 ifconfig: 2002:792d:8527::/64: bad value Anyone know the right way to do this? :) yes, man ifocnfig says ifconfig [-L] [-k] [-m] interface [create] [address_family] [address [dest_address]] [parameters] The following parameters may be set with ifconfig: -alias Remove the network address specified. This would be used if you ... Conclusion: -alias is a "parameter" and belongs to the end after the address. The it works for IPv4 is "pure luck". /bz -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't delete IPV6 addresses with ifconfig
Hi, > On Thu, 14 Feb 2008 22:27:34 +1030 > "Daniel O'Connor" <[EMAIL PROTECTED]> said: doconnor> Hi, doconnor> I am experimenting with IPv6 and I can't seem to remove an IPv6 address doconnor> from an interface, eg I have.. doconnor> [midget 22:11] ~ >ifconfig fxp0 doconnor> fxp0: flags=8943 mtu doconnor> 1500 doconnor> options=b doconnor> inet 10.0.2.1 netmask 0xff00 broadcast 10.0.2.255 doconnor> inet 10.0.2.3 netmask 0x broadcast 10.0.2.3 doconnor> inet 10.0.2.4 netmask 0x broadcast 10.0.2.4 doconnor> inet 10.0.2.7 netmask 0x broadcast 10.0.2.7 doconnor> inet6 2002:792d:8527::1:1 prefixlen 64 doconnor> ether 00:02:b3:32:2c:51 doconnor> media: Ethernet 100baseTX doconnor> status: active doconnor> But I can't remove it, viz.. doconnor> [midget 22:11] ~ >sudo ifconfig fxp0 -alias 2002:792d:8527::1:1/64 doconnor> ifconfig: 2002:792d:8527::1:1/64: bad value doconnor> [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1/64 doconnor> ifconfig: 2002:792d:8527::1:1/64: bad value doconnor> [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1 doconnor> ifconfig: 2002:792d:8527::1:1: bad value doconnor> [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1 doconnor> prefixlen 64 doconnor> ifconfig: 2002:792d:8527::1:1: bad value doconnor> [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::/64 doconnor> ifconfig: 2002:792d:8527::/64: bad value doconnor> Anyone know the right way to do this? :) sudo ifconfig fxp0 inet6 2002:792d:8527::1:1 -alias ^ Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED],jp.}FreeBSD.org http://www.imasy.org/~ume/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't delete IPV6 addresses with ifconfig
> --nextPart1996860.fztbeObibp > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > Hi, > I am experimenting with IPv6 and I can't seem to remove an IPv6 address=20 > from an interface, eg I have.. > [midget 22:11] ~ >ifconfig fxp0 > fxp0: flags=3D8943 mtu=20 > 1500 > options=3Db > inet 10.0.2.1 netmask 0xff00 broadcast 10.0.2.255 > inet 10.0.2.3 netmask 0x broadcast 10.0.2.3 > inet 10.0.2.4 netmask 0x broadcast 10.0.2.4 > inet 10.0.2.7 netmask 0x broadcast 10.0.2.7 > inet6 2002:792d:8527::1:1 prefixlen 64 > ether 00:02:b3:32:2c:51 > media: Ethernet 100baseTX > status: active > > But I can't remove it, viz.. > [midget 22:11] ~ >sudo ifconfig fxp0 -alias 2002:792d:8527::1:1/64 > ifconfig: 2002:792d:8527::1:1/64: bad value > [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1/64 > ifconfig: 2002:792d:8527::1:1/64: bad value > [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1 > ifconfig: 2002:792d:8527::1:1: bad value > [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1=20 > prefixlen 64 > ifconfig: 2002:792d:8527::1:1: bad value > [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::/64 > ifconfig: 2002:792d:8527::/64: bad value > > Anyone know the right way to do this? :) ifconfig fxp0 -alias inet6 2002:792d:8527::1:1 > =2D-=20 > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > --nextPart1996860.fztbeObibp > Content-Type: application/pgp-signature; name=signature.asc > Content-Description: This is a digitally signed message part. > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.4 (FreeBSD) > > iD8DBQBHtCy15ZPcIHs/zowRAp4GAKCiDBhK5KnMRXAtHN9J9pJwbr9vTQCeLHtF > H6WuTRDWwPdfOggg4inmxbw= > =UEHW > -END PGP SIGNATURE- > > --nextPart1996860.fztbeObibp-- -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't delete IPV6 addresses with ifconfig
> But I can't remove it, viz.. > [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1/64 > ifconfig: 2002:792d:8527::1:1/64: bad value Try ifconfig fxp0 inet6 delete 2002:792d:8527::1:1 I think you need the address family in there and no netmask on the end. That certainly stops the error for me here. -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't delete IPV6 addresses with ifconfig
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 14 Feb 2008 22:27+1030, Daniel O'Connor wrote: > [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1 > ifconfig: 2002:792d:8527::1:1: bad value Have you tried: sudo ifconfig fxp0 delete inet6 2002:792d:8527::1:1 - -- - -- Trond Endrestøl | [EMAIL PROTECTED] Patron of The Art of Computer Programming| FreeBSD 6.2-S & Pine 4.64 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHtC5xbYWZalUoElsRAkXXAJ97xso/N94EE1EaQ4m7hHsIkRJJYgCfSTFV QTMPguKKLtHZWFd2oPTk4LA= =a5p3 -END PGP SIGNATURE-___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Can't delete IPV6 addresses with ifconfig
Hi, I am experimenting with IPv6 and I can't seem to remove an IPv6 address from an interface, eg I have.. [midget 22:11] ~ >ifconfig fxp0 fxp0: flags=8943 mtu 1500 options=b inet 10.0.2.1 netmask 0xff00 broadcast 10.0.2.255 inet 10.0.2.3 netmask 0x broadcast 10.0.2.3 inet 10.0.2.4 netmask 0x broadcast 10.0.2.4 inet 10.0.2.7 netmask 0x broadcast 10.0.2.7 inet6 2002:792d:8527::1:1 prefixlen 64 ether 00:02:b3:32:2c:51 media: Ethernet 100baseTX status: active But I can't remove it, viz.. [midget 22:11] ~ >sudo ifconfig fxp0 -alias 2002:792d:8527::1:1/64 ifconfig: 2002:792d:8527::1:1/64: bad value [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1/64 ifconfig: 2002:792d:8527::1:1/64: bad value [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1 ifconfig: 2002:792d:8527::1:1: bad value [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::1:1 prefixlen 64 ifconfig: 2002:792d:8527::1:1: bad value [midget 22:27] ~ >sudo ifconfig fxp0 delete 2002:792d:8527::/64 ifconfig: 2002:792d:8527::/64: bad value Anyone know the right way to do this? :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: broken buildkernel (scsi_low and -Os) and duplicate manpages
David Naylor wrote: > It is a strange problem, normal installworld works fine, but somehow > the duplicate manpages result in a failure when installing with > DESTDIR=, here are some possible reasons: > > 1) I use tmpfs when using DESTDIR (could be tmpfs does something strange) > 2) Base system (compiled and installed) is compiled using -O2??? What is the exact CFLAGS setting that you use? Do you use -O2 (or -Os) without -fno-strict-aliasing? In general, having a CFLAGS=... line in /etc/make.conf is not a good idea. In most cases it does more harm than good. That might be the case here, too. I suggest you remove the CFLAGS line, rm -r /usr/obj (and make sure /usr/src is fresh) and start over. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Documentation is like sex; when it's good, it's very, very good, and when it's bad, it's better than nothing." -- Dick Brandon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: broken buildkernel (scsi_low and -Os) and duplicate manpages
On 13/02/2008, Rong-En Fan <[EMAIL PROTECTED]> wrote: > On Wed, Feb 13, 2008 at 10:52:50AM +0100, Christian Brueffer wrote: > > On Wed, Feb 13, 2008 at 11:15:29AM +0200, David Naylor wrote: > > > Hi, > > > > > > When doing an installworld DEST=? it fails twice when trying to > > > install duplicate man pages: > > > 1) lib/ncurses/ncurses: tputs.3 > > > 2) share/man/man9: rman_fini.9 > > > > > > > The rman_fini.9 one was a mistake, I've just fixed it. Thanks! rafan@ > > (CCed) did the last few ncurses updates. Rong-En, could you take a look > > at the tputs.3 issue? > > > Interesting, I actually use installworld w/ DESTDIR, but it does not > fail. Nevertheless, I have just removed the duplicate one (actually, > both curs_terminfo and curs_termcap has tputs.3. As we use termcap > in base, so I just removed the one links to curs_terminfo). It is a strange problem, normal installworld works fine, but somehow the duplicate manpages result in a failure when installing with DESTDIR=, here are some possible reasons: 1) I use tmpfs when using DESTDIR (could be tmpfs does something strange) 2) Base system (compiled and installed) is compiled using -O2??? It could just be the digital gremlin, that lives in my house (he has already claimed a harddrive and laptop adapter... :-) David ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
