Re: Make pccard.ether working if there is already a dhclient running
I have now fixed the remaining issues.
Comments are welcome.
Martin
--
Simplify the pccard dhcp handling a lot. There are now
many configurations which have a NIC on board, and
pccard slots. If a dhclient is running on the internal
nic, the user was forced to kill a running dhclient
manually.
If a pccard is included at startup time, /etc/rc.d/dhclient
start does include it into the startup list for dhcp devices.
That means you can you then dhcp on the internal and the
pccard device.
If the card is plugged in later, a running dhclient (working
for the internal interface only) is killed, and restarted,
but with the interface name of the new pccard.
Here is my example config which works really fine now:
ifconfig_sis0="DHCP"
pccard_ifconfig=DHCP
removable_interfaces="an0 wi0"
--- etc/pccard_etherThu Jun 26 04:44:08 2003
+++ etc/pccard_etherSat Aug 9 14:31:58 2003
@@ -12,11 +12,32 @@
pidfile="/var/run/dhclient.${interface}.pid"
elif [ -s /var/run/dhcpc.${interface}.pid ]; then
pidfile="/var/run/dhcpc.${interface}.pid"
+ elif [ -s /var/run/dhclient.pid ]; then
+ eval _active_list=\"`/bin/ps -x | \
+ /usr/bin/grep dhclient | \
+ /usr/bin/grep -v grep | \
+ /usr/bin/sed -e 's|^.*dhclient||'`\"
+
+ _aprefix=
+ for _if in _active_list ; do
+ _test_if=`ifconfig ${_if} 2>&1`
+ case "$_test_if" in
+ "ifconfig: interface $_if does not exist")
+ ;;
+ *)
+ _dhcplist="${_dhcplist}${_aprefix}${_if}"
+ [ -z "$_aprefix" ] && _aprefix=' '
+ ;;
+ esac
+ done
+
+ pidfile="/var/run/dhclient.pid"
else
return
fi
kill `cat ${pidfile}`
rm -f ${pidfile}
+ sh `/etc/rc.d/dhclient start`
}
start_dhcp() {
@@ -35,7 +56,7 @@
pidfile="/var/run/dhclient.${interface}.pid"
dhclient_flags="${dhclient_flags} -pf ${pidfile}"
fi
- ${dhclient_program} ${dhclient_flags} ${interface}
+ ${dhclient_program} ${dhclient_flags} $_dhcplist ${interface}
else
echo "${dhclient_program}: DHCP client software not available"
fi
--- etc/network.subrSat Aug 9 11:48:47 2003
+++ etc/network.subrSat Aug 9 14:10:59 2003
@@ -299,6 +299,24 @@
esac
done
+ case ${pccard_ifconfig} in
+ [Dd][Hh][Cc][Pp])
+ for _if in ${removable_interfaces} ; do
+ _test_if=`ifconfig ${_if} 2>&1`
+ case "$_test_if" in
+ "ifconfig: interface $_if does not exist")
+ ;;
+ *)
+ _dhcplist="${_dhcplist}${_aprefix}${_if}"
+ [ -z "$_aprefix" ] && _aprefix=' '
+ ;;
+ esac
+ done
+ ;;
+ *)
+ ;;
+ esac
+
case "$type" in
nodhcp)
echo $_nodhcplist
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acpica/acfreebsd.h bug with boot code (stand.h)
Andrey Chernov wrote: /usr/src/sys/contrib/dev/acpica/acfreebsd.h includes ctype.h which is incompatible with its redefinition in /usr/include/stand.h As result we got: ===> i386/libi386 cc -O -pipe -march=pentium3 -ffreestanding -DCOMPORT=0x3f8 -DCOMSPEED=9600 -DTERM_EMU -I/usr/src/sys/boot/i386/libi386/../../common -I/usr/src/sys/boot/i386/libi386/../btx/lib -I/usr/src/sys/boot/i386/libi386/../../../contrib/dev/acpica -I/usr/src/sys/boot/i386/libi386/../../.. -I. -I/usr/src/sys/boot/i386/libi386/../../../../lib/libstand/ -ffreestanding -mpreferred-stack-boundary=2 -c /usr/src/sys/boot/i386/libi386/biosacpi.c In file included from /usr/src/sys/contrib/dev/acpica/acfreebsd.h:165, from /usr/src/sys/boot/i386/libi386/biosacpi.c:33: /usr/include/ctype.h:88: syntax error before "int" *** Error code 1 Please fix it somehow. Things that include stand.h should not include ctype.h. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca VIVO Centro Oeste Norte Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] When the saleman's car broke down, he walked to the nearest farmhouse to ask if he could stay the night. The farmer agreed to put him up. "I live alone," he continued, "you can have the bedroom at the top of the stairs, to the right." "Oh, never mind," the disappointed salesman said. "I think I'm in the wrong joke." ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Strange fstype in bsdlabel output
traitor:~% mount /dev/da0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/da0s1f on /localhome (ufs, local, soft-updates) /dev/da0s1e on /usr (ufs, local, soft-updates) /dev/da0s1d on /var (ufs, local, soft-updates) /dev/md0 on /tmp (ufs, local, nodev, nosuid, soft-updates) procfs on /proc (procfs, local) linprocfs on /usr/compat/linux/proc (linprocfs, local) fdescfs on /dev/fd (fdescfs) traitor:~% dumpfs /dev/da0s1d | grep UFS magic 11954 (UFS1)timeWed Aug 6 10:34:03 2003 traitor:~% dumpfs /dev/da0s1e | grep UFS magic 11954 (UFS1)timeWed Aug 6 10:26:10 2003 traitor:~% dumpfs /dev/da0s1f | grep UFS magic 11954 (UFS1)timeWed Aug 6 10:19:16 2003 traitor:~% bsdlabel da0s1 # /dev/da0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 26214404.2BSD 2048 16384 16392 b: 2097152 262144unused0 0 c: 355517820unused0 0 # "raw" part, don't edit d: 1048576 2359296unused0 0 e: 12582912 3407872unused0 0 f: 19560998 15990784unused0 0 traitor:~% Why are d,e,f designated as `unused'? Shouldn't they be `4.2BSD' instead? -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ jos at catnook.com_/_/ _/_/_/ require 'std/disclaimer' ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB da(4) quirks deprecated
On Fri, 8 Aug 2003, Andrew Thompson wrote: > On Fri, 2003-08-08 at 03:13, Nate Lawson wrote: > > On Fri, 8 Aug 2003, Andrew Thompson wrote: > > > umass0: SigmaTel, Inc. USBMSC Audio Player, rev 1.10/0.01, addr 3 > > > umass0: Get Max Lun not supported (IOERROR) > > > da0 at umass-sim0 bus 0 target 0 lun 0 > > > da0: Removable Direct Access SCSI-4 device > > > da0: 1.000MB/s transfers > > > da0: 125MB (256001 512 byte sectors: 64H 32S/T 125C) > > > umass0: BBB reset failed, IOERROR > > > umass0: BBB bulk-in clear stall failed, IOERROR > > > umass0: BBB bulk-out clear stall failed, IOERROR > > > umass0: BBB reset failed, IOERROR > > > umass0: BBB bulk-in clear stall failed, IOERROR > > > umass0: BBB bulk-out clear stall failed, IOERROR > > > and so on > > > > Looks pretty standard. Here is more info on the possible quirks: > > http://www.root.org/~nate/freebsd/quirks.html > > > > If I were you, I'd look first into adding one for RS_NO_CLEAR_UA in > > sys/dev/usb/umass.c. See other quirks like this to get an idea. It's > > also possible that the problem is "NO_SYNC_CACHE" in > > sys/cam/scsi/scsi_da.c. > > I have tried RS_NO_CLEAR_UA, NO_GETMAXLUN, NO_START_STOP, > NO_TEST_UNIT_READY, DA_Q_NO_SYNC_CACHE and DA_Q_NO_6_BYTE without any > luck. > > Any other quirks to try? Let's see the new dmesg. As per my previous reply, I'm not confident your quirk was having any effect. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PCM freezes the box
On Thu, 7 Aug 2003 [EMAIL PROTECTED] wrote: > I have problems with my 5.1-Release and 5.1-STABLE boxes: > they freeze if I play anything different from audio CDs. > The cards are ESS 1938, options pcm is in the kernel. > If I try to run xmms/mpg123/KDE or any other application related > with artsd/esound/audiofile, the machines freeze, leaving not > a single chance to escape to shell and kill the process. Is anything printed on the console (or the first vty)? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with nvidia graphics card and -current
On Mon, Aug 04, 2003 at 11:53:05PM -0500, Glenn Johnson wrote: > On Tue, Aug 05, 2003 at 02:38:05PM +1000, Alastair G. Hogge wrote: > > > On Tuesday, 05 August 2003 14:34, Matthew N. Dodd wrote: > > > > > On Mon, 4 Aug 2003, Glenn Johnson wrote: > > > > > > > Question for the developers: Is there someway to avoid having > > > > the combination of vesa and nvidia cause a total lockup of the > > > > machine? I have a feeling I may not be the last person to try > > > > the nvidia driver with vesa enabled, either as a module, or > > > > compiled in the kernel. > > > > > > I'm running a system with the VESA stuff compiled in; the nvidia > > > drivers work just fine. > > > > > > IIRC you're running with ACPI; try not doing that. > > > > I'm also running a system with the vesa module loaded. I'm also > > running ACPI. > > Hmm, the only other thing I can offer here is that I had the console > screen set to "-g 100x37 VESA_800x600". How does that fit into > the picture? Perhaps I could have left vesa in but just set the > resolution to something else. Well, I can have the vesa kernel module loaded and use standard modes for the console and all is well. However, If I use any of the VESA video modes, the nvidia driver will not work. I can start the X server once, any subsequent attempt to restart the X server will cause the machine to freeze up if any of the VESA modes for the console are loaded. -- Glenn Johnson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with PS/2 mouse driver in XFree86 4.3.0
--- Mike Bohan <[EMAIL PROTECTED]> wrote:
> Yes, adding hint.acpi.0.disabled="1" to /boot/device.hints fixed the
> mouse problem.
Try this patch on acpi and see if it solves your problem.
--- sys/dev/acpica/acpi_pci_link.c.orig Thu Jan 2 02:48:49 2003
+++ sys/dev/acpica/acpi_pci_link.c Fri Feb 28 15:18:55 2003
@@ -461,7 +461,10 @@
return_ACPI_STATUS (error);
}
+/*
if (!(sta & (ACPI_STA_PRESENT | ACPI_STA_FUNCTIONAL))) {
+*/
+ if (!(sta & ACPI_STA_ENABLE)) {
ACPI_DEBUG_PRINT((ACPI_DB_ERROR,
"PCI interrupt link is not functional - %s\n",
acpi_name(handle)));
> While this is somewhat pleasing, it also leaves me with uncertainty. I
> tried tweaking
> basically every CMOS combination I could think of. Do you suppose this
> is an
> incompatability between the apci driver and my motherboard? The behavior
I bet you might have problem with parallel port as well. My machine suffered
from this behaviour when someone made the change as shown on the patch. I just
reverted that one. If the patch solves your problem, I believe that this is
related to BIOS not chipset. I have a Celeron on i815ep and the acpi message is
shown below. I just notice that you have a similar acpi signature like mime.
acpi0: on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 10 entries at 0xc00fded0
Good luck.
> makes
> it appear as if something else is fighting over the same resources that
> the mouse uses.
> This would explain why it can only access the device once a second.
> When BIOS
> initializes, it does not list any other device with an IRQ of 12 (which
> I believe is the mouse interface).
> Does anyone have any experience with devices such as mice flaking out
> with apci?
> Thanks again!
>
> -Mike Bohan
>
>
> On Sun, 2003-08-10 at 04:02, Shizuka Kudo wrote:
>
> > --- Mike Bohan <[EMAIL PROTECTED]> wrote:
> > > Hello,
> > >
> > > I have an Abit KT266 based motherboard and am having some trouble using
> > > the PS/2 mouse driver under XFree86. I have the protocol set to "auto",
> > > and the device set to /dev/psm0. This configuration has worked with
> > > this same Intellimouse in the past. The symptoms are that that when the
> > > mouse is moved, the cursor is only updated about once a second. After
> > > searching google, I found the following URL in which another person
> > > experienced the same problem (from freebsd-bugs). Apparently it only
> > > shows up on certain chipsets (VIA based). I tried several other PS/2
> > > mice, to no avail (same outcome). My system is running a day old
> > > -current build, but this other fellow reported the problem in 5.0 (does
> > > not affect 4.x). I'm wondering if anyone else has experienced this
> > > problem, and if so, are there any work-arounds? I've attached my
> > > 'dmesg' output, in the hopes that the information will be of value.
> > > Thank you in advance!
> > >
> >
> > Does disabling acpi make your mouse working?
> >
> > > URL:
> > > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-April/000426.html
> > >
> > > -Mike Bohan
> > >
> > > Copyright (c) 1992-2003 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 5.1-CURRENT #3: Fri Aug 8 09:10:54 EDT 2003
> > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CABOOSE
> > > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0424000.
> > > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0424244.
> > > Timecounter "i8254" frequency 1193182 Hz
> > > CPU: AMD Athlon(tm) processor (1333.91-MHz 686-class CPU)
> > > Origin = "AuthenticAMD" Id = 0x644 Stepping = 4
> > >
> > >
> >
>
Features=0x183fbff
> > > AMD Features=0xc044
> > > real memory = 268369920 (255 MB)
> > > avail memory = 256196608 (244 MB)
> > > Pentium Pro MTRR support enabled
> > > npx0: on motherboard
> > > npx0: INT 16 interface
> > > acpi0: on motherboard
> > > pcibios: BIOS version 2.10
> > > Using $PIR table, 8 entries at 0xc00fdef0
> > > acpi0: power button is handled as a fixed feature programming model.
> > > Timecounter "ACPI-fast" frequency 3579545 Hz
> > > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
> > > acpi_cpu0: on acpi0
> > > acpi_tz0: on acpi0
> > > acpi_button0: on acpi0
> > > acpi_button1: on acpi0
> > > pcib0: port
> > > 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0
> > > pci0: on pcib0
> > > pcib0: slot 8 INTA is routed to irq 10
> > > pcib0: slot 9 INTA is routed to irq 5
> > > pcib0: slot 11 INTA is routed to irq 10
> > > agp0: mem 0xe800-0xebff at
> > > device 0.0 on pci0
> > > pcib1: at device 1.0 on pci0
> > > pci1: on pcib1
> > > pcib0: slot 1 INTA is routed to irq 11
> > > pcib1: slot 0 INTA is routed t
Re: problem with IPv6 gif tunnel activation in rc.conf (latestcurrent)
Hajimu UMEMOTO <[EMAIL PROTECTED]> wrote: > matt> ipv6_network_interfaces="xl1 lo0" > > This line should be `ipv6_network_interfaces="xl1 gif0"'. > Heh. I KNEW it was going to be something stupid I forgot about. Yes it works fine now. Thank you very much! Regards, Matt. -- email: [EMAIL PROTECTED] - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Warning with loader Makefile?
I get this: ===> i386/cdboot ===> i386/kgzldr ===> i386/libi386 ===> i386/loader "/usr/share/mk/bsd.prog.mk", line 38: warning: duplicate script for target "loader" ignored cc -nostdlib -static -Ttext 0x0 -o loader.sym /home/obj/home/src/sys/boot/i386/loader/../btx/lib/crt0.o main.o conf.o bcache.o boot.o commands.o console.o devopen.o interp.o interp_backslash.o interp_parse.o ls.o misc.o module.o panic.o load_elf32.o load_elf64.o isapnp.o pnp.o interp_forth.o vers.o Why is there a duplicate script? -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Adaptec AIC7902 Ultra320 Problems
I've got another drive now to mess about with: da0: Fixed Direct Access SCSI-3 device And I get the same problems. Running non-packetized fixes it. Are you sure this is a firmware issue? Lawrence Farr EPC Direct Limited > -Original Message- > From: Justin T. Gibbs [mailto:[EMAIL PROTECTED] > Sent: 22 July 2003 17:46 > To: Lawrence Farr; [EMAIL PROTECTED] > Subject: Re: Adaptec AIC7902 Ultra320 Problems > > > > I have a Supermicro SuperServer 6013P-8, with: > > > > ahd0: port > > 0x4000-0x40ff,0x4400-0x44ff mem 0xfc30-0xfc301fff irq 5 > at device 2.0 on > > pci3 > > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X > 101-133Mhz, 512 SCBs > > ahd1: port > > 0x4800-0x48ff,0x4c00-0x4cff mem 0xfc302000-0xfc303fff irq 5 > at device 2.1 on > > pci3 > > aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X > 101-133Mhz, 512 SCBs > > > > Trying to install 5.1-CURRENT-20030709-JPSNAP or 4.8-STABLE on the > > box gives a timeout error that will hang the disk in a state that > > resetting the machine does not clear, and only power cycling will > > clear. Ive replaced the disks with no change, but installed and > > ran Redhat 7.3 on the box with no timeouts or errors. > > The problem you are encountering looks to be a drive firmware issue > exposed when the drive is running at high queue depths. The linux > driver limites the tag depth to 32 by default. The FreeBSD driver > does not throttle in this way. It seems that we just overwhelm the > drive with commands and it just stops doing anything on the > bus. According > to the timeout trace, the target just stopped sending packets while > still sitting on the bus. > > I have not tested this particular drive, so I do not know if update > firmware is available for it. You might try running in non-packetized > mode by toggling this option via SCSI-Select. You previous test of > running at "160" just reduced the clock rate, but still > allowed the use > of the newer, faster, packetized format. > > -- > Justin > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INET6 in world
At 12:16 PM -0700 2003/08/05, Kevin Oberman wrote: I may have missed part of this tread as I am on travel. Why is simply not enabling ipv6 adequate? Note: I DO run IPv6 routinely when at work, so I normally do have it enabled. I'd like to get an understanding of what the issue might be. The point is clearly strongly heald be some reasonably knowledgeable people. I'm from the school where you don't run anything you don't absolutely need. Not even if the code is not being used, just loaded. I don't mind having the code on disk and accessible if/when I need it (even though that's also a risk), but I absolutely do not want the code loaded unless I'm actually going to be making use of it. -- Brad Knowles, <[EMAIL PROTECTED]> "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Panic at _mtx_lock_flags+0x43 on VMware 3.x
I got a reproducable panic when installing current snapshot on VMware 3.x on Windows XP. Sorry, panic message and trace is PNG image captured on Windows: http://www.imgsrc.co.jp/~kuriyama/tmp/20030808.png If more information is needed, please let me know. -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. <[EMAIL PROTECTED]> // FreeBSD Project ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vinum lock panic at startup -current
I tried it this morning on different systems. So far the two AMD systems panic with vinum start and the intel/p4 works ok. All systems have no vinum volumes currently. Good dump found on device /dev/ad0s1b Architecture: i386 Architecture version: 1 Dump length: 1073676288B (1023 MB) Blocksize: 512 Dumptime: Fri Aug 8 05:28:09 2003 Hostname: [edited] Versionstring: FreeBSD 5.1-CURRENT #0: Thu Aug 7 12:02:25 MDT 2003 [EMAIL PROTECTED] out]:/usr/obj/usr/src/sys/ROUTER5 Panicstring: mutex Giant owned at /usr/src/sys/geom/geom_dev.c:198 Bounds: 3 On Fri, 08 Aug 2003 10:22:06 +0200, "Poul-Henning Kamp" <[EMAIL PROTECTED]> said: > In message <[EMAIL PROTECTED]>, "Aaron Wohl" > writes: > >I just cvsuped -current this afternoon to get about 1 weeks updates. > >After that the kernel panics booting starting vinum. I removed the one > >vinum volume (reformated as UFS2) I had for testing. And it still panics. > > I changed the /etc/rc.conf > >start_vinum="YES" to NO and can start ok now. > > What was the actual panic message ? > > -- > 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntop broken?
On Wed, 6 Aug 2003, Kris Kennaway wrote: > On Wed, Aug 06, 2003 at 03:39:47PM -0700, Charlie Schluting wrote: > > 5BOn Wed, 6 Aug 2003, Kris Kennaway wrote: > > > > > On Wed, Aug 06, 2003 at 08:57:53AM -0700, Charlie Schluting wrote: > > > > > > > > Howdy, > > > > Running 5.0. > > > > > > cvsup to 5.1 and retry. The package currently builds on a clean 5.1 system. > > > > > > Kris > > > > Interesting. So, I tried, and it deleted all my ports. > > No, update your FreeBSD system to 5.1. Besides, as you have found > out, the ports collection isn't branched. Look at the sample > cvsupfiles in /usr/share/examples/cvsup to see how to update your > system. > > Kris ok, got it. I was trying to avoid updating world to 5.1, given that I've had scary experiences with that. Thanks! --Charlie ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SAN disk with freebsd?
Anyone using a storage area network with freebsd (or linux)? Anything to recommend as working well or to stay way from? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient problem with xl0
Hi, > dhclient is still relying on behavior from the kernel that isn't > guaranteed. I know. But I'd consider that as a kernel bug, not dhclient fault. Would it help the set the card into promisc. mode anyway, even if we don't have link ? > I posted a patch to if_xl.c that should correct the link status for cards > with builtin non-MII PHYs. Ok. Thank you very much ! Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[current tinderbox] failure on sparc64/sparc64
TB --- 2003-08-10 11:12:24 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-08-10 11:12:24 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-08-10 11:14:21 - building world TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1: legacy release compatibility shims >>> stage 1: bootstrap tools >>> stage 2: cleaning up the object tree >>> stage 2: rebuilding the object tree >>> stage 2: build tools >>> stage 3: cross tools >>> stage 4: populating >>> /home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. TB --- 2003-08-10 12:10:39 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Aug 10 12:10:39 GMT 2003 >>> Kernel build for GENERIC completed on Sun Aug 10 12:19:33 GMT 2003 TB --- 2003-08-10 12:19:33 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/conf TB --- /usr/bin/make -B LINT TB --- 2003-08-10 12:19:33 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Aug 10 12:19:33 GMT 2003 [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/in_cksum.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/intr_machdep.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/iommu.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -fin
Re: Best Known Methods for dual booting WinXP + -current
On Fri, 8 Aug 2003, Wilko Bulte wrote: > On Thu, Aug 07, 2003 at 06:49:55PM -0700, David O'Brien wrote: > > On Thu, Aug 07, 2003 at 03:40:27PM -0500, Cagle, John (ISS-Houston) wrote: > > > Had to use FFS filesystem since Grub doesn't support UFS. > > ^^^ > > UFS1 > ^^^ > UFS2 ffs ffs (sic) There is only an ffs according to the man pages (;-<) : %%% $ man ufs No manual entry for ufs $ man 7 ffs | col -bx FFS(7) FreeBSD Miscellaneous Information Manual FFS(7) ... DESCRIPTION The Berkeley fast file system provides facilities to store file system ^^^ data onto a disk device. ffs has been optimized over the years for speed and reliability and is the default FreeBSD file system. ^^ ... $ apropos ufs bread(3), bwrite(3) - read and write blocks of a UFS filesystem cgread(3), cgread1(3)- read cylinder groups of UFS disks extattrctl(8)- manage UFS1 extended attributes fsck_ffs(8), fsck_ufs(8) - file system consistency check and interactive repair growfs(8)- grow size of an existing ufs file system libufs(3)- operate on UFS filesystems from userland newfs(8) - construct a new UFS1/UFS2 file system sbread(3), sbwrite(3)- read and write superblocks of a UFS filesystem ufs_disk_close(3), ufs_disk_fillout(3), ufs_disk_fillout_blank(3), ufs_disk_write(3) - open and close userland UFS disks [So we have a library and some utilities for a UFS filesystem (sic) although we only have an ffs file system ;-).] %%% This was confusing enough when there were only ffs and plain ufs, and no libufs. There is also no support for the ffs, ufs1 or ufs2 file system types: %%% $ lsvfs FilesystemRefs Flags - --- msdosfs 0 linprocfs0 synthetic nfs 0 network ext2fs 0 cd9660 1 read-only ufs 7 procfs 1 synthetic $ find /etc/passwd -fstype ffs Warning: Unknown filesystem type ffs $ find /etc/passwd -fstype ufs1 Warning: Unknown filesystem type ufs1 $ find /etc/passwd -fstype ufs2 Warning: Unknown filesystem type ufs2 $ find /etc/passwd -fstype ufs /etc/passwd %%% Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient problem with xl0
Hi, > Except that you've added code to dhclient that makes poor assumptions > about the ifmedia status word. Its optional; for hardware that you can > detect media status it can be used to display the status. For other > hardware, we shouldn't have to "lie" about media status; if the hardware > doesn't support reporting media status then we shouldn't do anything with > the status word. Isn't there a way to see that the card doesn't support reporting media status ? If the card does report this, I could add code to dhclient and all would be fine. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: help! 5.1 doesn't do the rc thing?
On Thursday 07 August 2003 20:05, Charlie Schluting wrote: > On Thu, 7 Aug 2003, Scot W. Hetzel wrote: > > From: "Charlie Schluting" <[EMAIL PROTECTED]> > > Yes, I do have that. I'm stupmed as to why the network interface didn't > start though. I think that's the reason all my stuff in > /usr/local/etc/rc.d didn't start as well, becuase they couldn't bind to > a port. Also, it didn't read rc.firewall :( > Heck, I even had to manually assign 127.0.0.1 to lo0. Strange. > > still stumped.. but I will work on it later tonight. I have another box > that I did a clean install of 5.1 on so I can compare startup scripts. Have you ran mergemaster already? It will take care of your /etc files (or at least it's supposed to). Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: cvs commit: src/sys/i386/i386 pmap.c]
On Wed, 6 Aug 2003, Alan L. Cox wrote: > If your i386 system has panic()ed in pmap_remove_all() recently, I would > encourage you to update your pmap.c. This is definitely good news! Thanks! regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient problem with xl0
On Sat, 9 Aug 2003, Martin Blapp wrote: > You don't have a working link. Maybe it helps if you add a interface > define in /etc/dhclient.conf wit the possible media. dhclient is still relying on behavior from the kernel that isn't guaranteed. I posted a patch to if_xl.c that should correct the link status for cards with builtin non-MII PHYs. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: help! 5.1 doesn't want to start my nic :)
On Fri, 8 Aug 2003, leafy wrote: > On Thu, Aug 07, 2003 at 07:26:28PM -0700, Charlie Schluting wrote: > > Ok, I found that /etc/rc.d/netif was missing. I moved the one from > > /usr/src/etc/rc.d into place, and I'm thinking that will fix it. > > > > I don't remember telling it NOT to move this file in mergemaster... > > Thanks to everyone who responded. > > --Charlie > > I had the problem a few days ago with exactly the same file. I solution was to > cd /usr/src/etc/rc.d && make install Well, I did what the previous poster suggested, and upon reboot, it still didn't come up. I ran /etc/rc.d/netif manually, and it said it couldn't find /etc/network.subr, so I copied that over manually, rebooted, and the interfaces still didn't start. But, if I run /etc/rc.d/netif manually, it starts just fine now! Yes, the file has execute permissions for all. Anyone know what's up with that? Can anyone give me the rundown on how/what FreeBSD does at boot time to start the network interface? Maybe something is supposed to be running that script, but isn't? Another missing script? Thanks, --Charlie ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Troubles while mounting ext2 from 5.1-RELEASE
"Vincent Caron" <[EMAIL PROTECTED]> writes: > after digging the various mailing-lists, release notes, errata and Google, I > thought > I might get some help here. I have just installed a FreeBSD 5.1-RELEASE on my x86 > laptop. Everything works like a charm, including DRI, except mounting ext2 : > > # mount -t ext2fs /dev/ad0s2 /mnt/linux > ext2fs: /dev/ad0s2: No such file or directory Did you compile EXT2FS support into your kernel? -- Best regards Christian Laursen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
