Re: nVidia driver problem w/ FreeBSD 5.2.1-RELEASE + mplayer
On Thu, 27 May 2004, Senandung Mendonan wrote: > On Thu, 27 May 2004, Gautham Ganapathy wrote: > > > I have installed 5.2.1-RELEASE on my system (Athlon XP/nForce 2 > > Ultra/GeForce 3). Unfortunately, I am not able to use nVidia's fbsd > > drivers. I saw a few posts that mentioned it would work under fbsd-5 > > although it was written for 4. Any idea on what might be the problem? > > Did you install the driver via ports ( /usr/ports/x11/nvidia-driver ), or > did you compile yourself? The ports version have some tweaks for you to > try. I've been using the ports version (default install, no tweaking) in > FreeBSD 5.2.1 on my Dell Latitude D800 (GeForce4 4200 Go), with no > problems so far: ran mplayer occasionally with the some mpeg, avi, etc. > > Got one minor gripe though: Can't get the Twinview feature working -- how > to get the display on both the laptop and a projector. (anybody got this > one working?) > Ok. I was building it from source. I'll try it from ports. Thanx. Not sure about Twinview, but I found the following http://lists.freebsd.org/pipermail/freebsd-questions/2003-June/010814.html There seems to be a few options that have to be setup for enabling Twinview and configuring the second monitor. Hope it works Regards Gautham ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Installation problems
In article <[EMAIL PROTECTED]>, Paul Brownsea (pb) writes: pb> ad0: READ command timeout tag=0 serv=0 - resetting pb> ata0: resetting devices .. pb> And then it just hangs. This one is getting popular. There is at least one disk controller chipset out there which FBSD 4.X doesn't understand. If you can turn off DMA disk access in the BIOS, you may be able to install. If you really are just trying it to see, try 5.2.1. It's not officially reccomended for production use yet, but it seems perfectly OK, just remember if something acts weirdly that you shouldn't assume it reflects what 5.X will be like when it is nailed down and solid. In a few months from now when you decide it's just what you need for some real use, 5.X may be the reccomended stable version anyway, so you'll have become familair with the right thing. -- Mail me as [EMAIL PROTECTED]_O_ |< ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mail daemon(s) recomendation request
Mike Maltese wrote: I'm looking for an smtp daemon that is less complex than sendmail, can use procmail and has some virtusertable equivalent features. Allowing relay based on mx is going to be a requirement for some of the boxes as well. Sendmail is working ok for me, but I'm intersted in finding something with a config file I can actually read. I'm going to check into postfix and maybe qmail. I'm also looking for some imap and pop3 daemons (ideally with ssl support) that can use maildir. I'll probably continue to use dovecot for imap and pop3. Anyone have any other suggestions? Qmail is said to be a very robust and secure MTA. Exim is also a popular Sendmail replacement. Personally, I swear by Postfix. Stable, secure and easy to configure, with lots of back-end options. For pop3/imap, I like Courier-IMAP. I'll second the Postfix recommendation. It can do maildir style mailboxes if you want, does procmail, and has good virtual user support. Not sure what you mean by "relay based on mx", but Postfix's configuration allows for all sorts of weird setups if needed. David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Commercial OS breeds commerce, whereas free OS breeds freedom, the only thing more dangerous and confusing than commerce. -- Michael R. Jinks, redhat-list, circa 1997 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mail daemon(s) recomendation request
In article <[EMAIL PROTECTED]>, Joseph Gleason (jg) writes: jg> I'm going to check into postfix and maybe qmail. Haven't played with qmail, but we were handed postfix on some managed linux servers. Years of experience with sendmail made me dread learning another monsterous system. Actually I just went down the config file and did the obvious things and it worked. It even relayed mail under the desired domain name without me having to spend three days living on fermented yak's milk in a hidden lamastary performing weird and unsettling chicken sacrificing ceremonies to the Great Old Ones. The O'Reiley book is comprehensible and the index takes you to the right page. On the whole I feel as if I have slipped into a parallel universe where email is a simple technological matter, not a deep religious mystery. -- Mail me as [EMAIL PROTECTED]_O_ |< ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
failure installing 5.2.1: cbb0: Unsupported card type detected
Hello, I have an old laptop, an HP XE3 OmniBook. Nice machine from an ergonomical point of view, and I was thinking of recycling it by installing FreeBSD. I downloaded the ISO for 5.2.1. It starts to boot just fine, but during the kernel load it dies with the message cbb0: Unsupported card type detected I tried selecting Safe mode, but it freezes earlier with cbb0: [MPSAFE] A few lines above it says cbb0: <02Micro 026933 PCI-CardBus Bridge> irq 9 at device 4.0 on pci2 Is there any way to get around this? I've seen a few messages on the subject in the archives but apparently these all involve running systems, something I don't yet have :( Or should I try 4.10 instead? Thanks for the clues, David -- Commercial OS breeds commerce, whereas free OS breeds freedom, the only thing more dangerous and confusing than commerce. -- Michael R. Jinks, redhat-list, circa 1997 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
help in configuring X for silicon motion lynxEM+ for thinkpad 240x
hi anyone can help me ? i tried many different setting, but still i can't get X to work for my ibm thinkpad 240x. I'm sorry for the long log file.. bash-2.05b# cat /var/log/XFree86.0.log XFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: FreeBSD 5.2.1 i386 [ELF] Build Date: 13 February 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Fri May 28 17:07:20 2004 (==) Using config file: "/etc/X11/XF86Config" (==) ServerLayout "Simple Layout" (**) |-->Screen "Screen 1" (0) (**) | |-->Monitor "My Monitor" (**) | |-->Device "Silicon Motion Lynx family" (**) |-->Input Device "Mouse1" (**) |-->Input Device "Keyboard1" (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc101" (**) XKB: model: "pc101" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (==) Keyboard: CustomKeycode disabled (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/local/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/local/"). (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7194 card , rev 01 class 06,00,00 hdr 00 (II) PCI: 00:07:0: chip 8086,7198 card , rev 01 class 06,80,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7199 card , rev 00 class 01,01,80 hdr 00 (II) PCI: 00:07:2: chip 8086,719a card , rev 00 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 8086,719b card , rev 00 class 06,80,00 hdr 00 (II) PCI: 00:09:0: chip 126f,0712 card 1014,01aa rev a0 class 03,00,00 hdr 00 (II) PCI: 00:0a:0: chip 104c,ac1e card fffc, rev 00 class 06,07,00 hdr 02 (II) PCI: 00:0b:0: chip 1013,6005 card 1014,01a9 rev 01 class 04,01,00 hdr 00 (II) PCI: 00:0c:0: chip 11c1,0449 card 1436,0440 rev 01 class 07,80,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,0), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (--) PCI:*(0:9:0) Silicon Motion, Inc. SM712 LynxEM+ rev 160, Mem @ 0xfd00/24 (II) Addressable bus resource ranges are [0] -1 0 0x - 0x (0x0) MX[B] [1] -1 0 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0 0x000f - 0x000f (0x1) MX[B] [3] -1 0 0x000c - 0x000e (0x3) MX[B] [4] -1 0 0x - 0x0009 (0xa) MX[B] [5] -1 0 0x - 0x (0x1) IX[B] [6] -1 0 0x - 0x00ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0 0xfc011000 - 0xfc011fff (0x1000) MX[B]E [1] -1 0 0xfc00 - 0x (0x400) MX[B]E [2] -1 0 0xfc01 - 0xfc01 (0x1) MX[B]E [3] -1 0 0xfd00 - 0xfdff (0x100) MX[B](B) [4]
ipfw, 2 scripts
Hello, bellow you will find 2 ipfw scripts, first one working, and second is a very good looking, but not working. what am I missing in the second script? first script starts here --- #!/bin/sh ipfw -f flush ipfw add 1 check-state ipfw add 100 allow all from any to any via lo0 ipfw add deny all from 10.0.0.0/8 to any in via tun0 ipfw add deny all from 172.16.0.0/12 to any in via tun0 ipfw add deny all from 192.168.0.0/16 to any in via tun0 ipfw add deny all from any to any frag ipfw add divert natd all from any to 195.5.17.86 in ipfw add allow icmp from me to any ipfw add allow icmp from any to me ipfw add allow gre from 192.168.5.0/24 to me ipfw add allow gre from me to any ipfw add allow tcp from me to any keep-state ipfw add allow udp from me to any keep-state ipfw add allow udp from any to me 53 ipfw add allow tcp from any to any established ipfw add allow tcp from any to me 25 setup ipfw add allow tcp from any to me ssh setup ipfw add allow tcp from any to me http setup via tun0 ipfw add allow tcp from 192.168.7.0/24 to me 3128 setup via ppp\* ipfw add allow tcp from 192.168.7.0/24 to me 2080 setup via ppp\* ipfw add allow tcp from 192.168.7.0/24 to me pop3 setup via ppp\* ipfw add allow tcp from 192.168.5.0/24 to me pptp setup ipfw add allow tcp from 192.168.5.0/24 to me ftp\\-data-ftp setup via em0 ipfw add allow tcp from any to me 53 setup ipfw add skipto 1 all from 192.168.7.40 to any in keep-state ipfw add skipto 1 all from 192.168.7.65 to any in keep-state ipfw add skipto 1 all from 192.168.7.100 to any in keep-state ipfw add deny all from any to any ipfw add 1 divert natd all from 192.168.7.40 to any out keep-state ipfw add divert natd all from 192.168.7.65 to any out keep-state ipfw add divert natd all from 192.168.7.100 to any out keep-state ipfw add allow all from any to any first script ends here after some more thinking I have decided to structurize the firewall behavior, i.e. I wanted to have different sets of rules for 2 my nets, plus one for nat. Here's how I've tryed to do it: second script starts here #!/bin/sh ipfw -f flush ipfw add 1 check-state ipfw add deny all from 10.0.0.0/8 to 195.5.17.86 ipfw add deny all from 172.16.0.0/16 to 195.5.17.86 ipfw add deny all from 192.168.0.0/16 to 195.5.17.86 ipfw add deny all from any to any frag ipfw add allow udp from me to any keep-state ipfw add allow tcp from me to any keep-state ipfw add allow icmp from me to any keep-state ipfw add allow all from me to any ipfw add allow tcp from any to any established ipfw add skipto 1000 all from any to 195.5.17.86 in via tun0 ipfw add skipto 2000 all from 192.168.5.0/24 to me in via em0 ipfw add skipto 3000 all from 192.168.7.0/24 to me in via ppp\* ipfw add skipto 4000 all from 192.168.5.0/24 to not me via em0 ipfw add skipto 5000 all from 10.100.105.0/24 to not me via em0 ipfw add skipto 6000 all from 192.168.7.0/24 to not me out xmit tun0 ipfw add deny log all from any to any ipfw add 1000 divert natd all from any to 195.5.17.86 ipfw add allow tcp from any to me smtp setup ipfw add allow tcp from any to me ssh setup ipfw add allow tcp from any to me domain setup ipfw add deny all from any to any ipfw add 2000 allow tcp from 192.168.5.0/24 to me ftp\\-data-ftp setup ipfw add allow tcp from 192.168.5.0/24 to me pptp setup ipfw add allow udp from 192.168.5.0/24 to me 53 ipfw add allow icmp from 192.168.5.0/24 to me ipfw add allow gre from 192.168.5.0/24 to me ipfw add deny all from any to any ipfw add 3000 allow tcp from 192.168.7.0/24 to me 3128 setup ipfw add allow tcp from 192.168.7.0/24 to me 2080 setup ipfw add allow tcp from 192.168.7.0/24 to me 25 setup ipfw add allow tcp from 192.168.7.0/24 to me 80 setup ipfw add allow tcp from 192.168.7.0/24 to me 110 setup ipfw add allow udp from 192.168.7.0/24 to me 53 ipfw add deny all from any to any ipfw add 4000 allow all from any to 10.100.105.0/24 via em0 ipfw add deny all from any to any ipfw add 5000 deny all from 10.100.105.0/24 to any out via tun0 ipfw add deny all from 10.100.105.0/24 to me via em0 ipfw add allow all from 10.100.105.0/24 to any ipfw add deny all from any to any ipfw add 6000 divert natd all from 192.168.7.40 to any via ppp\* ipfw add divert natd all from 192.168.7.100 to any via ppp\* ipfw add divert natd all from 192.168.7.65 to any via ppp\* ipfw add allow all from any to any second script ends here --- some comments: 192.168.5.0/24 - my base network. 192.168.7.0/24 - my vpn network 10.100.105.0/24 - network of our friends. we can use some of the services there, 192.168.5.77 - is the gateway between 192.168.5.0/24 and 10.100.105.0/24. with second script (which is logically correct for the situation) nothing works. What should I do? If you need some additional info - just ask me. -- With best regards, Gregory Edigarov -- profi.kharkov.ua
Re: openldap dependencies
On Thu, May 27, 2004 at 03:31:07PM +0100, Daniel Bye wrote:
> On Thu, May 27, 2004 at 09:17:09AM -0500, Andy Wettstein wrote:
> > Hello,
> >
> > I'm having a problem with the dependencies for openldap. I build
> > openldap21 with sasl support so I get openldap21-sasl-client. Then I
> > build pam_ldap and it builds fine, but it depends on openldap21-client.
> > So my dependencies are broken and I need to do a pkg_db -F. Is there
> > a way to tell packages that depend on openldap21-client to depend on
> > openldap21-sasl-client instead?
>
> Yes! The portupgrade config file, /usr/local/etc/pkgtools.conf is your
> friend in this case.
>
> The ALT_PKGDEP section is what you want - set something like this (NOT
> TESTED!):
>
> ALT_PKGDEP = {
> 'net/openldap21-client' => 'net/openldap21-sasl-client',
> }
>
> This simply tells portupgrade and friends that for any package that depends
> on openldap21-client, make it now depend instead on openldap21-sasl-client.
>
That's almost what I want to have happen, but this seems only
portupgrade will use that (and I couldn't actually get the ALT_PKGDEP to
work). But I probably need something that changes the @pkgdep, because
I want to be able to install the packages I create on other machines, too.
It doesn't really matter for that package because I won't be able to use
SASL anyway, since I'm going to authenticate Tru64 against this server
and it has to have direct access to the userPassword attribute, which
seems like a mostly braindead way to do it.
Thanks for your response.
Andy
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD and Toshiba Tecra 8000 Sound
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have read several posts on this problem, but mine is slightly different problem in that my machine seems to try and configure more than one pcm device -- cycling through pcm0, pcm1, ... , pcm27. Obviously, I've compiled my kernel with device pcm and I've tried all the usual stuff pci hints, etc to no avail. Any suggestions? Here's my dmesg output: Copyright (c) 1992-2004 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.2-CURRENT #0: Fri May 28 09:32:09 EDT 2004 ~[EMAIL PROTECTED]:/usr/obj/usr/src/sys/WEBER Preloaded elf kernel "/boot/kernel/kernel" at 0xc072e000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc072e26c. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (399.92-MHz 686-class CPU) ~ Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 201261056 (191 MB) avail memory = 191442944 (182 MB) bios32: Bad BIOS32 Service Directory random: Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [GIANT-LOCKED] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xfe08-0xfe0b on acpi0 pcm0: port 0x530-0x537 on acpi0 device_attach: pcm0 attach returned 6 pcm1: port 0x530-0x537 on acpi0 device_attach: pcm1 attach returned 6 pcm2: port 0x530-0x537 on acpi0 device_attach: pcm2 attach returned 6 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 4 INTA is routed to irq 11 pcib0: slot 5 INTD is routed to irq 11 pcib0: slot 9 INTA is routed to irq 11 pcib0: slot 13 INTA is routed to irq 11 pci0: at device 4.0 (no driver attached) isab0: at device 5.0 on pci0 isa0: on isab0 atapci0: port 0xfe60-0xfe6f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 5.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 5.2 (no driver attached) pci0: at device 5.3 (no driver attached) pci0: at device 9.0 (no driver attached) cbb0: at device 11.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib0: slot 11 INTA is routed to irq 11 cbb1: at device 11.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pcib0: slot 11 INTB is routed to irq 11 pci0: at device 13.0 (no driver attached) acpi_lid0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_acad0: on acpi0 pcm3: port 0x530-0x537 on acpi0 device_attach: pcm3 attach returned 6 pcm4: port 0x530-0x537 on acpi0 device_attach: pcm4 attach returned 6 pcm5: port 0x530-0x537 on acpi0 device_attach: pcm5 attach returned 6 pcm6: port 0x530-0x537 on acpi0 device_attach: pcm6 attach returned 6 pcm7: port 0x530-0x537 on acpi0 device_attach: pcm7 attach returned 6 pcm8: port 0x530-0x537 on acpi0 device_attach: pcm8 attach returned 6 pcm9: port 0x530-0x537 on acpi0 device_attach: pcm9 attach returned 6 pcm10: port 0x530-0x537 on acpi0 device_attach: pcm10 attach returned 6 pcm11: port 0x530-0x537 on acpi0 device_attach: pcm11 attach returned 6 pcm12: port 0x530-0x537 on acpi0 device_attach: pcm12 attach returned 6 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model GlidePoint, device ID 0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 pcm13: port 0x530-0x537 on acpi0 device_attach: pcm13 attach returned 6 pcm14: port 0x530-0x537 on acpi0 device_attach: pcm14 attach returned 6 pcm15: port 0x530-0x537 on acpi0 device_attach: pcm15 attach returned 6 pcm16: port 0x530-0x537 on acpi0 device_attach: pcm16 attach returned 6 pcm17: port 0x530-0x537 on acpi0 device_attach: pcm17 attach returned 6 pcm18: port 0x530-0x537 on acpi0 device_attach: pcm18 attach returned 6 pcm19: port 0x530-0x537 on acpi0 device_attach: pcm19 attach returned 6 pcm20: port 0x530-0x537 on acpi0 device_attach: pcm20 attach returned 6 pcm21: port 0x530-0x537 on acpi0 device_attach: pcm21 attach returned 6 pcm22: port 0x530-0x537 on acpi0 device_attach: pcm22 attach returned 6 pcm23: port 0x530-0x537 on acpi0 device_attach: pcm23 attach returned 6 pcm24: port 0x530-0x537 on acpi0 device_attach: pcm24 attach returned 6 pcm25: port 0x530-0x537 on acpi0 device_attach: pcm25 attach returned 6 pcm26: port 0x530-0x537 on acpi0 device_attach: pcm26 attach returned 6 pcm27: port 0x530-0x537 on acpi0 device_attach: pcm27 attach returned 6 pcm0: port 0x530-0x537 on acpi0 device_attach: pcm0 attach returned 6 pcm1: port 0x530-0x537 on acpi0 device_attach: pcm1 attach returned 6 pcm2: port 0x530-0x537 on acpi0 device_attach: pcm2 attach
.p12 file
Hi!! Someone can give me a .p12 file please because I cannot import a certificate in Windows (it's just for try) from Freebsd to Windows because my serveur (freebsd) is KO and I want (for the school) to import a .p12 file to make a VPN. Even if I will not use this fiel is just to show to my teacherthat's is possible. Sorry if I wasn't clear. Thanks - Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! Créez votre Yahoo! Mail Dialoguez en direct avec vos amis grâce à Yahoo! Messenger ! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.3-RELEASE
The FBSD 4.10-RELEASE announcement (http://www.freebsd.org/releases/4.10R/announce.html) mentioned 5.3-RELEASE. Any word on when 5.3 might arrive? -- Brad Tarver, CCNA Network Administrator Forman Perry Watkins Krutz & Tardy 188 East Capitol Street Suite 200 Jackson, MS 39201 United States Ph: 601-960-8600 Fax: 601-960-8613 Important Confidentiality And Limited Liability Notice This email and any attachments may be confidential and protected by law. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the email or any attachment is prohibited. If you have received this email in error, please notify us immediately by replying to the sender and deleting this copy and the reply from your system. Please note that any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of Forman Perry Watkins Krutz & Tardy LLP. (FPWK&T). The recipient should check this email and any attachments for the presence of viruses. FPWK&T accepts no liability for any damage caused by any virus transmitted by this email. Thank you for your cooperation. smime.p7s Description: S/MIME Cryptographic Signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD and Toshiba Tecra 8000 Sound
On Fri, 28 May 2004, John Weber wrote: I have read several posts on this problem, but mine is slightly different problem in that my machine seems to try and configure more than one pcm device -- cycling through pcm0, pcm1, ... , pcm27. Obviously, I've compiled my kernel with device pcm and I've tried all the usual stuff pci hints, etc to no avail. Mine works, but with ACPI disabled. Settings follow: BIOS: Configuration Device Config. = All Devices I/O Ports Sound = Enabled In /boot/device.hints: hint.acpi.0.disabled="1" hint.pcm.0.at="isa" hint.pcm.0.irq="5" hint.pcm.0.drq="1" hint.pcm.0.flags="0x0" In /boot/loader.conf: snd_mss_load="YES" And dmesg shows this: Preloaded elf module "/boot/kernel/snd_mss.ko" at 0xc0a1126c. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc0a11318. ... pcm0: at port 0x538-0x539,0xf8c-0xf94,0xe0e,0x530-0x537 irq 5 drq 1 flags 0xc100 on isa0 -Warren Block * Rapid City, South Dakota USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 5.2.1 on IBM T30
Hi, I have just tried to install a fresh distribution of FreeBSD 5.2.1 on a IBM T30. The system locks up with just after: pccard0: <16-bit PCCard bus> on cbb0 cbb0: [MPSAFE] I have been using this same laptop with FreeBSD 4.9 and 4.10 without any problems. Does anybody have FreeBSD 5.2.1 running on a IBM T30 ? Thanks in advance, Arend ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Starting a second loopback interface and services at startup
Hi! New to FreeBSD and running 5.2.1-RELEASE on an Alpha. I do predominantly SysV/ATT boxes, so I feel a bit out of it... Question #1: I need to create a second loopback interface, which I can do just fine at the command line: # ifconfig lo1 create # ifconfig lo1 inet a.b.c.d netmask x.x.x.x How do I automate this at startup? I stumbled across something in /etc/network.subr that suggests I ought to create /etc/start_if.lo1 which would then be sourced. I assume I can add a ifconfig_lo1 variable to /etc/rc.conf. I tried these, but with no luck. Can anyone point the way? Question #2: I'm trying to start Quagga services on this box (zebra and ospfd). I added scripts to /usr/local/etc/rc.d/ for these two, but no luck. They work fine from the command line, e.g. # /usr/local/etc/rc.d/zebra.sh start # /usr/local/etc/rc.d/ospfd.sh start Both have the .sh extension, which seems to be required. How should I troubleshoot this? I don't find anything in dmesg.today suggesting that there was even an attempt to run the scripts. Also, can one use the rcorder keywords to provide startup ordering for scripts in /usr/local/etc/rc.d ??? TIA, Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3-RELEASE
On Fri, 28 May 2004 09:23:22 -0500 Brad Tarver <[EMAIL PROTECTED]> wrote: > The FBSD 4.10-RELEASE announcement > (http://www.freebsd.org/releases/4.10R/announce.html) mentioned > 5.3-RELEASE. Any word on when 5.3 might arrive? AFAIK, its still "TBD" but I've seen unofficial mentions of this summer sometime. You might want to keep watch on the section "Upcoming Releases" at: http://www.freebsd.org/releng/index.html When there is a schedule for a new release, a link will be posted there. Most FreeBSD users don't wait on a RELEASE, they just install the most recent and then update (see Handbook) to the latest available at the moment. HTH, Randy -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Jumpstart Guide / PXE network installation
Hi everyone! I have followed the 'FreeBSD Jumpstart Guide' to build a system for installing FreeBSD 4.9-RELEASE via PXE. I can now perform PXE client installs, but have so far been unable to resolve the following problems: 1. I have compiled and installed a custom kernel on my PXE server which works fine. I have placed my new kernel in /usr/tftpboot and in the NFS root. The PXE client loads the correct kernel to start the install, but after rebooting the client boots the GENERIC kernel. Where is sysinstall getting this kernel from? 2. I have a 'shutdown' command at the end of my install.cfg script, but on both a Dell Precision 610 and an IBM PC330, this does not work: instead the system reboots and restarts the installation unless I intercept the reboot! What am I missing? 3. I get a prompt 'loading module ida.ko failed'. This is for Compaq Smart RAID, but I did not configure this option in my custom kernel. Presumably, I have not configured the list of kernel modules correctly? Any pointers gratefully received - this has been driving me nuts for too long now! This is my first post to the list. TIA, John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Installation problems
OK, I was going to try turning off DMA, but it won't. There isn't an actual setting in the CMOS setup for it. After consulting the manual it tells me to disable "PCI IDE busmaster", so I did. But DMA is still enabled so it still does the same. Should I just give up or is there anything else to do? On Thursday 27 May 2004 18:59, Scott Kupferschmidt wrote: > Hello, > > The problem is your motherboard has a junk ide controller that FreeBSD > does not support DMA on properly. If you disable DMA in the BIOS, > FreeBSD will boot and install properly. > > Sincerely, > > Scott Kupferschmidt > ISPrime, Inc. > 866.502.4678 ext. 3 > AIM: Scott ISPrime - ICQ: 174337249 > > On Thu, 27 May 2004, Paul Brownsea wrote: > > I thought I'd give FreeBSD a go after enjoying using Linux, so I > > downloaded and burnt the FreeBSD 4.9 ISO images and I can't seem to > > install. I get past the bit with configuring the kernel but get stuck > > just afterwards, the last two messages are as follows: > > > > ad0: READ command timeout tag=0 serv=0 - resetting > > ata0: resetting devices .. > > > > And then it just hangs. > > > > -- > > "Plaese porrf raed." > > -- Prof. Michael O'Longhlin, S.U.N.Y. Purchase > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" -- Real World, The n.: 1. In programming, those institutions at which programming may be used in the same sentence as FORTRAN, COBOL, RPG, IBM, etc. 2. To programmers, the location of non-programmers and activities not related to programming. 3. A universe in which the standard dress is shirt and tie and in which a person's working hours are defined as 9 to 5. 4. The location of the status quo. 5. Anywhere outside a university. "Poor fellow, he's left MIT and gone into the real world." Used pejoratively by those not in residence there. In conversation, talking of someone who has entered the real world is not unlike talking about a deceased person. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
3Ware Escalade problem
Here is what my system is telling me. twe0: unexpected status bit(s) 80 twe0: PCI parity error: Reseat card, move card or buggy device present. Here is what I am running. FreeBSD 4.7 p25 boot disk IDE SCSI tape drive twe0 is an Escalade 7500-4 twe1 is an Escalade 7000-2 I have tried two different 7500-4 cards. I have changed slots. I have tried 3 different motherboards. 2 ASUS P2BS 1 MSI K7 Master-S What I suspect. The Escalade 7500-4 is a 64 bit card. I am using it on a 32 bit bus. The manual doesn't say you can't but I am suspicous. Both 7500-4 cards worked just fine on Linux and Windows on both 32 and 64 bit motherboards IIRC. Is it possible we have a driver issue here? The machine is a backup server so reliability is important. :^) So far I haven't lost any data but.. If you can help great. If you need more info let me know. hal ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
buildworld actually crashed
During buildworld, I wandered off. When I returned, my machine was, alarmingly, in single user mode, demanding that I run fsck manually. I'm running fsck right now, and it's finding all sorts of block size errors, to which I'm simply hitting 'y' and agreeing that things should be salvaged and corrected. Before running fsck, I had a look at the buildworld.out script that was being written to during the buildworld process. I can't tell you exactly what it says, but it definitely came to a stop in the middle of a 'sentence' of output. I.e. it looks like my new machine (yeah, the soon-to-be-fanless EPIA again) must have crashed during buildworld. What could cause buildworld to crash like that? I'm now worried that my PSU board *was* damaged the other day. Is a damaged PSU the most likely cause of this incident? All advice very welcome. -- Bob London, UK echo Mail fefsensmrrjyaheeoceoq\! | tr "jefroq\!" "@obe.uk" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
xmms
In just the last couple weeks xmms has displayed these errors. xmms [] still plays, but from mozilla, xmms exits. Gdk-WARNING **: Missing charsets in FontSet creation Gdk-WARNING **: ISO8859-1 Gdk-WARNING **: ISO8859-1 ** CRITICAL **: Couldn't open playlist font ** CRITICAL **: Couldn't open playlist font I just tried rebuilding multimedia/xmms WITHOUT_GNOME. Same error. What's going on? thanks, gary -- Gary Kline [EMAIL PROTECTED] www.thought.org Public service Unix ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: perl and berkeley
> perl -MCPAN -e 'install BerkeleyDB' > > ... still gives: > > BerkeleyDB.xs:74: #error db.h is from Berkeley DB 1.x - need at least > Berkeley DB 2.6.4 > *** Error code 1 > > I've deleted and re-installed that db3 pkg, but still get the same error. my first try would probably be to remove all CPAN modules installed under the old perl, and reinstall them. Then try installing that DB. However, wiser heads may have a better clue. Sounds like a good plan, but MCPAN doesn't seem to support uninstall of modules. "find" does show where modules are installed to uninstall them manually. I see MCPANPLUS supports uninstall. Dammit, this "simple" project of getting PERL to talk to db3 is like the ball of string. thanks Len ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 3Ware Escalade problem
> Here is what my system is telling me. > > twe0: unexpected status bit(s) 80 > twe0: PCI parity error: Reseat card, move card or buggy > device present. > > Here is what I am running. > > FreeBSD 4.7 p25 > boot disk IDE > SCSI tape drive > twe0 is an Escalade 7500-4 > twe1 is an Escalade 7000-2 > > I have tried two different 7500-4 cards. > I have changed slots. > I have tried 3 different motherboards. > 2 ASUS P2BS > 1 MSI K7 Master-S > > What I suspect. > > The Escalade 7500-4 is a 64 bit card. I am using it on > a 32 bit bus. The manual doesn't say you can't but I am > suspicous. Both 7500-4 cards worked just fine on Linux > and Windows on both 32 and 64 bit motherboards IIRC. 3Ware maintains a list of motherboards where 32bit support works. It will only run 64bit on many board (most of the Intel server boards for example). You may want to check that list for your board(s) (I was too lazy to look it up). Also, I've seen some of the 7500's still shipping w/ old firmware. And, like a lot of PCI problems, it could be the slot. If you can, move it to a different slot. I've also seen this problem on riser cards that share the same pci slot with other cards. Some of the newer risers have little daughter-boards that plug into adjacent slots to rememdy that problem. Good luck, Brent ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld actually crashed
Robert Downes wrote: During buildworld, I wandered off. When I returned, my machine was, alarmingly, in single user mode, demanding that I run fsck manually. I'm running fsck right now, and it's finding all sorts of block size errors, to which I'm simply hitting 'y' and agreeing that things should be salvaged and corrected. Before running fsck, I had a look at the buildworld.out script that was being written to during the buildworld process. I can't tell you exactly what it says, but it definitely came to a stop in the middle of a 'sentence' of output. I.e. it looks like my new machine (yeah, the soon-to-be-fanless EPIA again) must have crashed during buildworld. What could cause buildworld to crash like that? I'm now worried that my PSU board *was* damaged the other day. Is a damaged PSU the most likely cause of this incident? All advice very welcome. Not enough information here to be sure, but it sure sounds like a hardware problem. You might do well to try memtest86 and cpuburn on that machine for a while, to see if you can track down a hardware problem. Monitor the temperature of the machine while doing so, could be that the cooling is inadequate. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld actually crashed
On Friday 28 May 2004 10:00 am, Robert Downes wrote: > During buildworld, I wandered off. When I returned, my machine was, > alarmingly, in single user mode, demanding that I run fsck manually. > > I'm running fsck right now, and it's finding all sorts of block size > errors, to which I'm simply hitting 'y' and agreeing that things > should be salvaged and corrected. > > Before running fsck, I had a look at the buildworld.out script that > was being written to during the buildworld process. I can't tell you > exactly what it says, but it definitely came to a stop in the middle > of a 'sentence' of output. I.e. it looks like my new machine (yeah, > the soon-to-be-fanless EPIA again) must have crashed during > buildworld. > > What could cause buildworld to crash like that? I'm now worried that > my PSU board *was* damaged the other day. Is a damaged PSU the most > likely cause of this incident? Just one of the possibilities. There are connectors that will test ATX psu's. My experience with psu failures is the system dies and you don't have something like HDs. I had what I think is a cpu failure that caused a voltage regulator IC to explode on the mobo. I was looking at the mobo from about 2 feet when it did this. That was about the most exciting thing that happended that day :). I was telling a friend about it and he made the comment that they don't throw shrapnel but disappear into dust. I never saw or felt anything and assume that he was right. Insufficient size will cause intermitant errors depending on the cpu. I usually go at least the next 50 watts up from what is recommended for a cpu. I also have a tendancy to like 350+'s with dual fans. > > All advice very welcome. In the FAQs trouble shooting link is a section on signal 11's. I would look at the options. Very little will cause a buildwold to die but hardware errors. You have to use wavy hands at this point because -stable and -current occasionaly have errors but none of the software errors are likely to cause the system to reset it self during a build. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Starting a second loopback interface and services at startup
Robert Lowe wrote: Hi! New to FreeBSD and running 5.2.1-RELEASE on an Alpha. I do predominantly SysV/ATT boxes, so I feel a bit out of it... Question #1: I need to create a second loopback interface, which I can do just fine at the command line: # ifconfig lo1 create # ifconfig lo1 inet a.b.c.d netmask x.x.x.x How do I automate this at startup? I stumbled across something in /etc/network.subr that suggests I ought to create /etc/start_if.lo1 which would then be sourced. I assume I can add a ifconfig_lo1 variable to /etc/rc.conf. I tried these, but with no luck. Can anyone point the way? I figured out the correct way to do this: 1. Override the default network_interfaces variable in /etc/defaults/rc.conf in /etc/rc.conf. This is a space-separated list of interfaces to start. I included the new loopback interface to create. 2. Create a /etc/start_if. script to create the interface. 3. Add a ifconfig_ variable to rc.conf as well. I had this already, so I did not have to do anything. The reason the last two steps did nothing before was the list of interfaces in the netif script is generated using 'ifconfig -l', which of course does not include interfaces which haven't yet been created, and so the start_if. script is not run. Question #2: I'm trying to start Quagga services on this box (zebra and ospfd). I added scripts to /usr/local/etc/rc.d/ for these two, but no luck. They work fine from the command line, e.g. # /usr/local/etc/rc.d/zebra.sh start # /usr/local/etc/rc.d/ospfd.sh start Both have the .sh extension, which seems to be required. How should I troubleshoot this? I don't find anything in dmesg.today suggesting that there was even an attempt to run the scripts. Also, can one use the rcorder keywords to provide startup ordering for scripts in /usr/local/etc/rc.d ??? The scripts now run properly, but in the wrong order, so I still need an answer here. They seem to execute in alpha-numeric order. I suppose I could start them in one script, but that's not really the answer. Help! I suppose I could use the Snn SysV approach. ;-) -Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
New FreeBSD Installation
Hi, and thanks in advance for any help provided. I am trying to install FreeBSD 4.10 on a new, clean ProLiant DL380 g3. It has four 72.8 GB drives, and currently set up as a RAID5 by it's Smart Array 5i boot controller. I want to start by making this as simple as possible, so only one operating system (BSD). Some specs: ProLiant DL 380 G3 Intel Xeon @ 3.06 Ghz NC7781 Gigabit Server Adapter IDE CD-ROM 1 : DW-224E I have created both the kern.flp and the mfsroot.flp diskettes, and progressed through the initial installation. The first problem I have encountered is being unable to initialize the media from my ISO diskette. I get the following error message: Error mounting /dev/acd0 on dist: Input/output error (5) 100% This is surprising, since on the Hardware Probe results, I have: acd0: CDROM at ata0-master using PIO4 Now I have read that an older issue was that the CD-ROM drives needed to be set as slave to the hard drive controller in order to work properly, but thought this was an older issue, and taken care of. (?) Yet, when I do a Standard Installation, Use the Entire Disk (setting as Bootable), Install a Standard MBR (no boot manager), use Auto Defaults for the Disk partitioning, Attempt a User installation (to keep it basic), and accept the FreeBSD ports collection suggestion, then choose my Installation Media type as CD/DVD (and will be using the 4.10 Disc 1 ISO), the Error mounting... comes up. I do not believe it is the CD-ROM drive itself - there are several disks that I have tested and ran upon it (the ProlLiant's SmarStart, for example). Has anyone encountered this problem? I have read at several areas that it might be an issue with the RAID controller (?) Thanks again for any advice, and have a great holiday weekend! Jon _ FREE pop-up blocking with the new MSN Toolbar get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
xsp
I am trying to compile xsp in my freebsd box (4.9 RELEASE) and I got these error when I do make /usr/local/bin/mcs -debug+ -debug:full -nologo -r System.Web.dll -r:Mono.Posix.dll /d: MODMONO_SERVER /out:mod-mono-server.exe Error CS2008: No files to compile were specified Compilation failed: 1 error(s), 0 warnings *** Error code 1 Stop in /root/xsp-0.13/server *** Error code 1 I am trying to install apache with mod-mono to serve aspx web pages please some idea ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New FreeBSD Installation
> Hi, and thanks in advance for any help provided. > > I am trying to install FreeBSD 4.10 on a new, clean ProLiant DL380 g3. It > has four 72.8 GB drives, and currently set up as a RAID5 by it's Smart > Array > 5i boot controller. How about installing via ftp ? thats what I have used in the past when I didnt have a working CDROM > > I want to start by making this as simple as possible, so only one > operating > system (BSD). > > Some specs: > > ProLiant DL 380 G3 > Intel Xeon @ 3.06 Ghz > NC7781 Gigabit Server Adapter > IDE CD-ROM 1 : DW-224E > > > I have created both the kern.flp and the mfsroot.flp diskettes, and > progressed through the initial installation. > > The first problem I have encountered is being unable to initialize the > media > from my ISO diskette. I get the following error message: > > Error mounting /dev/acd0 on dist: Input/output error (5) 100% > > This is surprising, since on the Hardware Probe results, I have: > > acd0: CDROM at ata0-master using PIO4 > > Now I have read that an older issue was that the CD-ROM drives needed to > be > set as slave to the hard drive controller in order to work properly, but > thought this was an older issue, and taken care of. (?) > > Yet, when I do a Standard Installation, Use the Entire Disk (setting as > Bootable), Install a Standard MBR (no boot manager), use Auto Defaults for > the Disk partitioning, Attempt a User installation (to keep it basic), and > accept the FreeBSD ports collection suggestion, then choose my > Installation > Media type as CD/DVD (and will be using the 4.10 Disc 1 ISO), the Error > mounting... comes up. > > I do not believe it is the CD-ROM drive itself - there are several disks > that I have tested and ran upon it (the ProlLiant's SmarStart, for > example). > > Has anyone encountered this problem? I have read at several areas that it > might be an issue with the RAID controller (?) > > Thanks again for any advice, and have a great holiday weekend! > > Jon > > _ > FREE pop-up blocking with the new MSN Toolbar get it now! > http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
i386 buildworld failure (RELENG_5_2)
I've cleaned out /usr/src and /usr/obj and cvsup'd RELENG_5_2 sources, but I'm still getting the following failure when I run 'make buildworld'. Any suggestions? Cheers, Mat --- ===> usr.sbin/config /usr/obj/usr/src/i386/usr/src/usr.sbin/config created for /usr/src/usr.sbin/config yacc -d /usr/src/usr.sbin/config/config.y cp y.tab.c config.c lex -t /usr/src/usr.sbin/config/lang.l > lang.c rm -f .depend mkdep -f .depend -a-I. -I/usr/src/usr.sbin/config -I/usr/obj/usr/src/i386/legacy/usr/include config.c /usr/src/usr.sbin/config/main.c lang.c /usr/src/usr.sbin/config/mkmakefile.c /usr/src/usr.sbin/config/mkheaders.c /usr/src/usr.sbin/config/mkoptions.c echo config: /usr/lib/libc.a /usr/lib/libl.a /usr/obj/usr/src/i386/legacy/usr/lib/libegacy.a >> .depend cc -O -pipe -I. -I/usr/src/usr.sbin/config -I/usr/obj/usr/src/i386/legacy/usr/include -c config.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/usr.sbin/config/main.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -I/usr/obj/usr/src/i386/legacy/usr/include -c lang.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/usr.sbin/config/mkmakefile.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/usr.sbin/config/mkheaders.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/usr.sbin/config/mkoptions.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -I/usr/obj/usr/src/i386/legacy/usr/include -static -L/usr/obj/usr/src/i386/legacy/usr/lib -o config config.o main.o lang.o mkmakefile.o mkheaders.o mkoptions.o -ll -legacy sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 config /usr/obj/usr/src/i386/legacy/usr/sbin *** Signal 11 Stop in /usr/src/usr.sbin/config. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: perl and berkeley
* Len Conrad <[EMAIL PROTECTED]> [2004-05-28 09:17 -0800]: > >my first try would probably be to remove all CPAN modules installed > >under the old perl, and reinstall them. Then try installing that DB. > >However, wiser heads may have a better clue. > > Sounds like a good plan, but MCPAN doesn't seem to support uninstall > of modules. "find" does show where modules are installed to uninstall > them manually. > > I see MCPANPLUS supports uninstall. Dammit, this "simple" project of > getting PERL to talk to db3 is like the ball of string. Well, good luck with that. I wish I knew more about perl/db3. And remember, most projects are like that. ;] Regards, -- dave [ please don't CC me ] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Searching CVS commits
On Tue, May 18, 2004 at 08:43:33PM +0200, Andreas Kohn wrote: > cvs can't provide you with that kind of information, because it doesn't > remember it (cvs works on file-by-file base). But, it can tell you when > the 1.337 commit to vfs_syscalls.c happened. > > ... > > You can then use the archive of the cvs-src mailing list at > http://lists.freebsd.org/pipermail/cvs-src/2004-February to find the > commit: > > http://lists.freebsd.org/pipermail/cvs-src/2004-February/018554.html > > That should tell you all modified files in this commit. That's EXACTLY what I was looking for! That's a HUGE help. I didn't even know the info in the cvs-src mailing list existed. Thanks a bunch. Kevin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SASL problem
Hi everyone. I'm trying to set up mail system using postfix+cyrus-imapd+cyrus-sasl+mysql+pam_mysql When trying to check mailbox using pop3 or imap I get following error: May 29 01:10:55 relay pop3[849]: badlogin: relay.0f.ru [192.168.127.2] plaintext vasya SASL(-13): authentication failure: checkpass failed I don't get what's happaning. I used this HOWTO (http://www.delouw.ch/linux/postfix.phtml). Besides, I'm getting some errors I can't deal with: May 29 01:05:34 relay imaplocal[810]: badlogin: localhost.0f.ru [127.0.0.1] plaintext cyrus SASL(-13): authentication failure: checkpass failed May 29 01:05:37 relay saslauthd[265]: unable to dlopen(/usr/lib/pam_mysql.so) May 29 01:05:37 relay saslauthd[265]: [dlerror: /usr/lib/pam_mysql.so: unsupported file type] May 29 01:05:37 relay saslauthd[265]: adding faulty module: /usr/lib/pam_mysql.so May 29 01:10:46 relay saslpasswd2: setpass succeeded for vasya May 29 01:10:46 relay saslpasswd2: error deleting entry from sasldb: DB_NOTFOUND: No matching key/data pair found What does it mean and how is it possoble to fix it? Software: FreeBSD 4.9-RELEASE cyrus-imapd-2.2.4.tar.gz cyrus-sasl-2.1.18.tar.gz mysql-4.0.20.tar.gz openssl-0.9.7d.tar.gz pam_mysql-0.5.tar.gz postfix-2.1.1.tar.gz Thanks, Ilia ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Searching CVS commits
On Friday 28 May 2004 01:01 pm, Kevin A. Pieckiel wrote: > On Tue, May 18, 2004 at 08:43:33PM +0200, Andreas Kohn wrote: > > cvs can't provide you with that kind of information, because it > > doesn't remember it (cvs works on file-by-file base). But, it can > > tell you when the 1.337 commit to vfs_syscalls.c happened. > > > > ... > > > > You can then use the archive of the cvs-src mailing list at > > http://lists.freebsd.org/pipermail/cvs-src/2004-February to find > > the commit: > > > > http://lists.freebsd.org/pipermail/cvs-src/2004-February/018554.htm > >l > > > > That should tell you all modified files in this commit. > > That's EXACTLY what I was looking for! That's a HUGE help. I didn't > even know the info in the cvs-src mailing list existed. Thanks a > bunch. > The history is always available using cvsweb.cgi such as http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/vfs_syscalls.c Back up to the top and bookmark it. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fsck_ufs: cannot alloc 3221471004 bytes for inoinfo
On Thursday 27 May 2004 22:30, Christian Hiris wrote: > When I rebooted the machine I got a "giving up on xx buffers" message and > all filesystems marked dirty. After rebooting the system background fsck > run and left one filesystem dirty - "unexpected softupdate inconsistency". > Then the system died within 20 seconds. After that I rebooted into single > user mode started fsck manually: > [...] > > The filesystem held about 1.3 million files, softupdates enabled. > Is there any other way recover this filesystem on the fly? > > Thanks! > ch I 'solved' the problem by switching some of my harddisks to a new controller to eliminate the syncer problem and restored data from backups. The primary cause was a timeout of a harddisk attached to the HPT372 onboard controller on a Epox EP-8KRA2+ mainboard. -- Christian Hiris <[EMAIL PROTECTED]> | OpenPGP KeyID 0x941B6B0B OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu pgpD2CImwiF0X.pgp Description: signature
Re: config is out of sinc
On Thursday 27 May 2004 01:01 am, Kent Stewart wrote: > On Wednesday 26 May 2004 10:19 pm, Earl Larsen wrote: > > What would change for 4.9 current? I am a little confused on the > > difference of RELENG_4_9 and RELENG_4_9_0_RELEASE. Is the first one > > for stable systems, and the later one for current systems? > > You need to read about the branch tags on > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html > > RELENG_4 is stable, which is now going by the name 4.10-STABLE. There is > now a RELENG_4_10_0_RELEASE, which never changes, and RELENG_4_10, > which is only updated with critical fixes and security advisories. Thank you all for the clarafacation. Two last question. I just want to duble check myself. 1) If I want to update 4.9 to 4.10 I would put RELENG_4_10_0_RELEASE in my supfile. And it will update everything to the current version of 4.10. 2) The cvsroot-all is for a cvsup-mirror. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ramdisk-own on 5.2.1
I have a script which was provided to me (from a PR log)
and its for ramdisk-ownership:
=
# PROVIDE: ramdisk-own
# REQUIRE: ramdisk mountcritlocal
# BEFORE: SERVERS
# KEYWORD: FreeBSD
. /etc/rc.subr
name="ramdisk"
stop_cmd=":"
start_cmd="ramdisk_own_start"
ramdisk_own_start()
{
set -x
for unit in $ramdisk_units; do
device="/dev/md$unit"
dir=`mount | grep $device | cut -d' ' -f3`
eval owner=\$ramdisk_${unit}_owner
eval perms=\$ramdisk_${unit}_perms
[ "X$owner" != "X" ] && chown -f "$owner" $device
$dir
[ "X$perms" != "X" ] && chmod -f "$perms" /dev/md$unit
$dir
done
}
load_rc_config $name
run_rc_command "$1"
=
...however, this results is MESSY output to the console and log file(s):
Setting hostname: shadow.
+ device=/dev/md0
+ mount
+ grep /dev/md0
+ cut -d -f3
+ dir=/tmp
+ eval owner=$ramdisk_0_owner
+ owner=root:wheel
+ eval perms=$ramdisk_0_perms
+ perms=1777
+ [ Xroot:wheel != X ]
+ chown -f root:wheel /dev/md0 /tmp
+ [ X1777 != X ]
+ chmod -f 1777 /dev/md0 /tmp
+ device=/dev/md1
+ grep /dev/md1
+ cut -d -f3
+ mount
+ dir=/var/spool/MIMEDefang
+ eval owner=$ramdisk_1_owner
+ owner=defang:defang
+ eval perms=$ramdisk_1_perms
+ perms=0700
+ [ Xdefang:defang != X ]
+ chown -f defang:defang /dev/md1 /var/spool/MIMEDefang
+ [ X0700 != X ]
+ chmod -f 0700 /dev/md1 /var/spool/MIMEDefang
+ _return=0
+ [ 0 -ne 0 ]
+ [ -n ]
+ return 0
...but it does work 100%. Is there any way of 'cleaning' this up so that
one does not see these messages, but that the work is DONE?
--
J.D. Bronson
Aurora Health Care // Information Services // Milwaukee, WI USA
Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ramdisk-own on 5.2.1
On Fri, 2004-05-28 at 19:07, J.D. Bronson wrote:
> I have a script which was provided to me (from a PR log)
> and its for ramdisk-ownership:
>
> =
> # PROVIDE: ramdisk-own
> # REQUIRE: ramdisk mountcritlocal
> # BEFORE: SERVERS
> # KEYWORD: FreeBSD
>
> . /etc/rc.subr
>
> name="ramdisk"
> stop_cmd=":"
> start_cmd="ramdisk_own_start"
>
> ramdisk_own_start()
> {
> set -x
[snip]
>
> ...but it does work 100%. Is there any way of 'cleaning' this up so that
> one does not see these messages, but that the work is DONE?
Remove that "set -x" line.
Joe
--
PGP Key : http://www.marcuscom.com/pgp.asc
signature.asc
Description: This is a digitally signed message part
Re: ramdisk-own on 5.2.1
J.D.,
Take the set -x out.
> = Copied from message sent on Fri May 28 18:07:14 2004
by J.D. Bronson Subject:ramdisk-own on 5.2.1.
>
> I have a script which was provided to me (from a PR log)
> and its for ramdisk-ownership:
>
> =
> # PROVIDE: ramdisk-own
> # REQUIRE: ramdisk mountcritlocal
> # BEFORE: SERVERS
> # KEYWORD: FreeBSD
>
> . /etc/rc.subr
>
> name="ramdisk"
> stop_cmd=":"
> start_cmd="ramdisk_own_start"
>
> ramdisk_own_start()
> {
> set -x
> for unit in $ramdisk_units; do
> device="/dev/md$unit"
> dir=`mount | grep $device | cut -d' ' -f3`
>
> eval owner=\$ramdisk_${unit}_owner
> eval perms=\$ramdisk_${unit}_perms
>
> [ "X$owner" != "X" ] && chown -f "$owner" $device
> $dir
> [ "X$perms" != "X" ] && chmod -f "$perms" /dev/md$unit
> $dir
> done
> }
>
> load_rc_config $name
> run_rc_command "$1"
>
> =
>
> ...however, this results is MESSY output to the console and log file(s):
>
> Setting hostname: shadow.
> + device=/dev/md0
> + mount
> + grep /dev/md0
> + cut -d -f3
> + dir=/tmp
> + eval owner=$ramdisk_0_owner
> + owner=root:wheel
> + eval perms=$ramdisk_0_perms
> + perms=1777
> + [ Xroot:wheel != X ]
> + chown -f root:wheel /dev/md0 /tmp
> + [ X1777 != X ]
> + chmod -f 1777 /dev/md0 /tmp
> + device=/dev/md1
> + grep /dev/md1
> + cut -d -f3
> + mount
> + dir=/var/spool/MIMEDefang
> + eval owner=$ramdisk_1_owner
> + owner=defang:defang
> + eval perms=$ramdisk_1_perms
> + perms=0700
> + [ Xdefang:defang != X ]
> + chown -f defang:defang /dev/md1 /var/spool/MIMEDefang
> + [ X0700 != X ]
> + chmod -f 0700 /dev/md1 /var/spool/MIMEDefang
> + _return=0
> + [ 0 -ne 0 ]
> + [ -n ]
> + return 0
>
>
> ...but it does work 100%. Is there any way of 'cleaning' this up so that
> one does not see these messages, but that the work is DONE?
>
>
>
> --
> J.D. Bronson
> Aurora Health Care // Information Services // Milwaukee, WI USA
> Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
>
--
Michael D HughesLoghome living is the best!
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ramdisk-own on 5.2.1
THANKS GUYS!!! - that was FAST
At 06:14 PM 5/28/2004, Michael D Hughes wrote:
J.D.,
Take the set -x out.
> = Copied from message sent on Fri May 28 18:07:14 2004
by J.D. Bronson Subject:ramdisk-own on 5.2.1.
>
> I have a script which was provided to me (from a PR log)
> and its for ramdisk-ownership:
>
> =
> # PROVIDE: ramdisk-own
> # REQUIRE: ramdisk mountcritlocal
> # BEFORE: SERVERS
> # KEYWORD: FreeBSD
>
> . /etc/rc.subr
>
> name="ramdisk"
> stop_cmd=":"
> start_cmd="ramdisk_own_start"
>
> ramdisk_own_start()
> {
> set -x
> for unit in $ramdisk_units; do
> device="/dev/md$unit"
> dir=`mount | grep $device | cut -d' ' -f3`
>
> eval owner=\$ramdisk_${unit}_owner
> eval perms=\$ramdisk_${unit}_perms
>
> [ "X$owner" != "X" ] && chown -f "$owner" $device
> $dir
> [ "X$perms" != "X" ] && chmod -f "$perms" /dev/md$unit
> $dir
> done
> }
>
> load_rc_config $name
> run_rc_command "$1"
>
>
=
>
> ...however, this results is MESSY output to the console and log file(s):
>
> Setting hostname: shadow.
> + device=/dev/md0
> + mount
> + grep /dev/md0
> + cut -d -f3
> + dir=/tmp
> + eval owner=$ramdisk_0_owner
> + owner=root:wheel
> + eval perms=$ramdisk_0_perms
> + perms=1777
> + [ Xroot:wheel != X ]
> + chown -f root:wheel /dev/md0 /tmp
> + [ X1777 != X ]
> + chmod -f 1777 /dev/md0 /tmp
> + device=/dev/md1
> + grep /dev/md1
> + cut -d -f3
> + mount
> + dir=/var/spool/MIMEDefang
> + eval owner=$ramdisk_1_owner
> + owner=defang:defang
> + eval perms=$ramdisk_1_perms
> + perms=0700
> + [ Xdefang:defang != X ]
> + chown -f defang:defang /dev/md1 /var/spool/MIMEDefang
> + [ X0700 != X ]
> + chmod -f 0700 /dev/md1 /var/spool/MIMEDefang
> + _return=0
> + [ 0 -ne 0 ]
> + [ -n ]
> + return 0
>
>
> ...but it does work 100%. Is there any way of 'cleaning' this up so that
> one does not see these messages, but that the work is DONE?
>
>
>
> --
> J.D. Bronson
> Aurora Health Care // Information Services // Milwaukee, WI USA
> Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
>
>
>
--
Michael D HughesLoghome living is the best!
[EMAIL PROTECTED]
--
J.D. Bronson
Aurora Health Care // Information Services // Milwaukee, WI USA
Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
L2TP port bind failure
Hello, I have an L2TP server running on 4.2 FreeBSD that needs to bind to UDP port 1701.This works usually, but in rare cases, I see another application, say SNMP, has already taken this port, so the L2TP bind fails. The SNMP client doesn't care what UDP port it gets (it doesn't specify a value in the bind call). Is there a way to prevent it from getting the L2TP server's port? Other than starting the L2TP server before SNMP (and all other clients), is there a way to solve this? Thanks, Raja - Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Zyxel Prestige 630
Hello freebsd-questions, Is Zyxel Prestige 630-41 works with FreeBSD? -- Best regards, Alexander mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to get best results from FreeBSD-questions
How to get the best results from FreeBSD questions. === Last update $Date: 2003/03/09 22:09:31 $ This is a regular posting to the FreeBSD questions mailing list. If you got it in answer to a message you sent, it means that the sender thinks that at least one of the following things was wrong with your message: - You left out a subject line, or the subject line was not appropriate. - You formatted it in such a way that it was difficult to read. - You asked more than one unrelated question in one message. - You sent out a message with an incorrect date, time or time zone. - You sent out the same message more than once. - You sent an 'unsubscribe' message to FreeBSD-questions. If you have done any of these things, there is a good chance that you will get more than one copy of this message from different people. Read on, and your next message will be more successful. This document is also available on the web at http://www.lemis.com/questions.html. = Contents: I:Introduction II: How to unsubscribe from FreeBSD-questions III: Should I ask -questions, -newbies or -hackers? IV: How to submit a question to FreeBSD-questions V:How to answer a question to FreeBSD-questions I: Introduction === This is a regular posting aimed to help both those seeking advice from FreeBSD-questions (the "newcomers"), and also those who answer the questions (the "hackers"). Note that the term "hacker" has nothing to do with breaking into other people's computers. The correct term for the latter activity is "cracker", but the popular press hasn't found out yet. The FreeBSD hackers disapprove strongly of cracking security, and have nothing to do with it. In the past, there has been some friction which stems from the different viewpoints of the two groups. The newcomers accused the hackers of being arrogant, stuck-up, and unhelpful, while the hackers accused the newcomers of being stupid, unable to read plain English, and expecting everything to be handed to them on a silver platter. Of course, there's an element of truth in both these claims, but for the most part these viewpoints come from a sense of frustration. In this document, I'd like to do something to relieve this frustration and help everybody get better results from FreeBSD-questions. In the following section, I recommend how to submit a question; after that, we'll look at how to answer one. II: How to unsubscribe from FreeBSD-questions == When you subscribed to FreeBSD-questions, you got a welcome message from [EMAIL PROTECTED] In this message, amongst other things, it told you how to unsubscribe. Here's a typical message: Welcome to the freebsd-questions mailing list! If you ever want to remove yourself from this mailing list, you can send mail to "[EMAIL PROTECTED]" with the following command in the body of your email message: unsubscribe freebsd-questions Greg Lehey <[EMAIL PROTECTED]> Here's the general information for the list you've subscribed to, in case you don't already have it: FREEBSD-QUESTIONS User questions This is the mailing list for questions about FreeBSD. You should not send "how to" questions to the technical lists unless you consider the question to be pretty technical. Normally, unsubscribing is even simpler than the message suggests: you don't need to specify your mail ID unless it is different from the one which you specified when you subscribed. If Majordomo replies and tells you (incorrectly) that you're not on the list, this may mean one of two things: 1. You have changed your mail ID since you subscribed. That's where keeping the original message from majordomo comes in handy. For example, the sample message above shows my mail ID as [EMAIL PROTECTED] Since then, I have changed it to [EMAIL PROTECTED] If I were to try to remove [EMAIL PROTECTED] from the list, it would fail: I would have to specify the name with which I joined. 2. You're subscribed to a mailing list which is subscribed to FreeBSD-questions. If that's the case, you'll have to figure out which one it is and get your name taken off that one. If you're not sure which one it might be, check the headers of the messages you receive from freebsd-questions: maybe there's a clue there. If you've done all this, and you still can't figure out what's going on, send a message to [EMAIL PROTECTED], and he will sort things out for you. Don't send a message to FreeBSD-questions: they can't help you. III: Should I ask -questions, -newbies or -hackers? === Two mailing lists handle general questions about FreeBSD, FreeBSD-questions and FreeBSD-hackers. In addition, the FreeBSD-newbies l
"The Complete FreeBSD": errata and addenda
The trouble with books is that you can't update them the way you can a web page or any other online documentation. The result is that most leading edge computer books are out of date almost before they are printed. Unfortunately, The Complete FreeBSD, published by O'Reilly, is no exception. Inevitably, a number of bugs and changes have surfaced. "The Complete FreeBSD" has been through a total of five editions, including its predecessor "Installing and Running FreeBSD". Two of these have been reprinted with corrections. I maintain a series of errata pages. Start at http://www.lemis.com/errata-4.html to find out how to get the errata information. Have you found a problem with the book, or maybe something confusing? Please let me know: I'm constantly updating it. Greg ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3Ware Escalade problem
Hi, that sounds very familiar to me. I had exactly the same problems using 3ware Escalade Controllers on several "older" Mainboards. Try using a newer Board with an actual Chipset and I bet it will work fine! I think it's a problem with PCI-Version. Greetz, Frank > Here is what my system is telling me. > > twe0: unexpected status bit(s) 80 > twe0: PCI parity error: Reseat card, move card or buggy device present. > > Here is what I am running. > > FreeBSD 4.7 p25 > boot disk IDE > SCSI tape drive > twe0 is an Escalade 7500-4 > twe1 is an Escalade 7000-2 > > I have tried two different 7500-4 cards. > I have changed slots. > I have tried 3 different motherboards. > 2 ASUS P2BS > 1 MSI K7 Master-S > > What I suspect. > > The Escalade 7500-4 is a 64 bit card. I am using it on > a 32 bit bus. The manual doesn't say you can't but I am > suspicous. Both 7500-4 cards worked just fine on Linux > and Windows on both 32 and 64 bit motherboards IIRC. > > Is it possible we have a driver issue here? > > The machine is a backup server so reliability is important. :^) > So far I haven't lost any data but.. > > If you can help great. If you need more info let me know. > > hal > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Zyxel Prestige 630
Without double checking, the 630 is just an ADSL router running a connection to FreeBSD over ethernet. In short, so long as the ADSL parameters are configured on the 630 it should all work just fine. Hope this helps. I'm running a 600 series myself. Jon On Sat, 2004-05-29 at 00:49, Alexander Goryaev wrote: > Hello freebsd-questions, > > Is Zyxel Prestige 630-41 works with FreeBSD? -- ++ | ___ ___ | |/ || / | | / /| |/ /| | / / | | _ / / ___ | | / /__| |/ ___ \ / /__/ __ \/ _ | | /__ | |/ | / / /_/ / ___ \ / /_/ / / / | | / ___ \ | | / /| | / / __ / / \ \ | ___/__ / / / / / / \ \ | | / / | | | |__/ / / // / | \__/ / | |_| | / // / | | /__\/___\ \_/ /__| /__| \_/ \__/|_| /__| /__| | || | www.achean.com | | == | | Jon Mercer [EMAIL PROTECTED] | ++ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fstat support for DTYPE_KQUEUE
Hi. Does anyone have a patch for reporting kqueue descriptor information from fstat? Please cc me in reply. thanks vijay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: config is out of sinc
On Friday 28 May 2004 02:55 pm, Earl Larsen wrote: > On Thursday 27 May 2004 01:01 am, Kent Stewart wrote: > > On Wednesday 26 May 2004 10:19 pm, Earl Larsen wrote: > > > What would change for 4.9 current? I am a little confused on the > > > difference of RELENG_4_9 and RELENG_4_9_0_RELEASE. Is the first > > > one for stable systems, and the later one for current systems? > > > > You need to read about the branch tags on > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags. > >html > > > > RELENG_4 is stable, which is now going by the name 4.10-STABLE. > > There is now a RELENG_4_10_0_RELEASE, which never changes, and > > RELENG_4_10, which is only updated with critical fixes and security > > advisories. > > Thank you all for the clarafacation. > > Two last question. I just want to duble check myself. > > 1) If I want to update 4.9 to 4.10 I would put RELENG_4_10_0_RELEASE > in my supfile. And it will update everything to the current version > of 4.10. It is a matter of semantics. To me, the current version of 4.10 will be RELENG_4_10. The release version never changes and is out of date the first time they post a fix to RELENG_4_10. So, it can never be the current version. > > 2) The cvsroot-all is for a cvsup-mirror. Ok, but you still don't want to do things the way you were setting it up. Don't waste your network bandwidth and the remote computer resources when you have the same data on a local machine. My mirror is on a computer I call crystal and my stable-supfile on crystal looks like # cat stable-supfile # listed at http://www.freebsd.org/handbook/mirrors.html. #*default host=cvsup8.FreeBSD.org *default host=crystal *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix src-all I would make one other point. When you install cvsup-mirror, it wants to run the update on the hour. I find that 20-25 minutes after the hour is much more successful. The mirrored code only changes once an hour and you don't miss anything. I have found that the mirrors are usually loaded on the hour and I got a lot of denied messages until I setup my cvsup mirror update cronjob to run 20-25 minutes later. I still get occasional denies when a new release is tagged but not nearly as many as I had in the past. I don't update my mirror every hour and if I want to force an update in between cronjobs, I run upcvs, which looks like # cat upcvs #! /bin/sh sh /usr/local/etc/cvsup/update.sh Once you get a mirror cvsup, if you have a web server, install cvsweb-2.0.6_1. You can look at the source just like cvsweb.cgi does on freebsd.org. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
installing FreeBSD on dell dimension 6100
Hi, I'm trying to install on my dell dimension 6100 and the installation is hanging on probing devices. I tried disabling acpi and booting in safe mode but both hang at the same spot. What should I try next? Thanks, Bob - Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Error: input: Resource temporarily unavailable
On Thu, 27 May 2004, Gustafson, Tim wrote: > I am getting the following error in "vi" pretty consistently: > > Error: input: Resource temporarily unavailable > > Usually I get this at every attempt I make to run vi. Every now and > then I'll somehow manage to stay in vi however long I want. It seems > that if it's going to bomb, it bombs in the first 30 seconds of running > the program. Otherwise, it doesn't happen at all. > > No other programs do this, as far as I know. > > I have tried installing the nvi-devel port to see if maybe this is fixed > in a new version, but it does the exact same thing. I even rebuilt the > kernel and world after a cvsup to make sure something wasn't broken, but > that didn't work wither. I have tried switching shells from bash to > just sh to see if it's related somehow to bash, but that did not have > any effect either. > > I am currently running FreeBSD 4.9-RELEASE-p8 i386 > > This problem pops up about once a month and then seems to go away by > itself after a few days, but I would really like to know what is causing > it. I have searched the FreeBSD mailing list archives and found a few > references to changing some flag in my shell, and I followed their > instructions, but it did not help. > > Obviously, it is a real pain in the neck since I use vi exclusively and > I despise having to us pico for anything. > > If anyone has any idea how I can fix this, I would really appreciate it. Are you using this when SSH'd into a remote system? I started seeing this after the SSH changed to introduce "untrusted X11 forwarding", but it lasted for about a day and then vanished. FYI, the problem is likely that a system call is returning EAGAIN, and that's getting pushed up through the vi ncurses or another component which doesn't know how to handle that error code, so simply exits. There used to be a similar problem with EINTR as a result if the window change signal and certain bits of vi's state machine. If you can reproduce this easily, could you try running vi under ktrace, then see if you can trigger the problem? The last few dozen lines of kdump would be very helpful, as it would identify the system call that's returning EAGAIN. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Senior Research Scientist, McAfee Research ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problems after CVSUP
Not quite a newbie, but not very good either, apparently. :( I did a cvsup last night, following instructions from the handbook, and hosed up my box. = [EMAIL PROTECTED] /home/ecarmody] $ uname -a FreeBSD oberon.hudsonvalleynetworks.com 5.2.1-RELEASE-p7 FreeBSD 5.2.1-RELEASE-p7 #0: Thu May 27 19:57:55 EDT 2004 root@:/usr/obj/usr/src/sys/GENERIC i386 [EMAIL PROTECTED] /home/ecarmody] $ = I should not be running 5.2.1-RELEASE due to my inexperience, I know, but need to in order to support my IDE controller. I was using the box for www, sendmail, tacacs, ntp, syslog, samba, for my home network, and just trying to learn UNIX a la FreeBSD. My immediate issues are these: At boot, ntpd hangs, holding up the rest of the startup process. If I kill it with a ctrl-c, sendmail then does some funky things, and also hangs. === /var/log/ntp shows: [EMAIL PROTECTED] /var/log] # cat ntp.log 28 May 23:53:37 ntpd[609]: ntpd exiting on signal 15 28 May 23:56:37 ntpd[409]: ntpd exiting on signal 2 [EMAIL PROTECTED] /var/log] # which I think is from me killing it via ctrl-c === So, to workaround temporarily, I commented out ntpd_enable="YES" in rc.conf. Ntpd obviously doesn't hold up my boot anymore but sendmail does. === Starting sendmail. safefile(etc/mail/services.switch, uid=0, gid=0, flags=6480, mode=400): safedirpath(/etc/mail, uid=0, gid=0 flags =6580, level=0, offset=0): [dir /etc/mail] OK No such file or directory Then I get similar lines for /etc/mail/submit.cf, etc/mail/relay-domains, The last line is: Recipient names must be specified I can't seem to find the output I'm seeing in /var/log/messages or /var/log/maillog, so I've hand-typed in the bit above. /var/log/maillog has lots of: May 29 00:00:05 oberon sm-msp-queue[436]: i4S2ug7P087593: to=root, ctladdr=root (0/0), delay=1+01:03:23, xdelay=00:00:00, mailer=relay, pri=4980184, relay=[127.0.0.1], dsn=4.0.0, stat=Deferred: Connection refused by [127.0.0.1] which also started after my cvsup last night. === Not sure what else to provide. Any direction on how to 'shoot and fix this wins a free beer next time you're in NYC. Thanks... Edward Carmody, CCNP Systems Engineer ShoreGroup, Inc. M: 845-649-7791 F: 646-349-3506 [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems after CVSUP
On Friday 28 May 2004 09:41 pm, Edward Carmody wrote: > Not quite a newbie, but not very good either, apparently. :( I did a > cvsup last night, following instructions from the handbook, and hosed > up my box. > > = > [EMAIL PROTECTED] /home/ecarmody] $ uname -a > FreeBSD oberon.hudsonvalleynetworks.com 5.2.1-RELEASE-p7 FreeBSD > 5.2.1-RELEASE-p7 #0: Thu May 27 19:57:55 EDT 2004 > root@:/usr/obj/usr/src/sys/GENERIC i386 > [EMAIL PROTECTED] /home/ecarmody] $ > = > > I should not be running 5.2.1-RELEASE due to my inexperience, I know, > but need to in order to support my IDE controller. I was using the > box for www, sendmail, tacacs, ntp, syslog, samba, for my home > network, and just trying to learn UNIX a la FreeBSD. > > My immediate issues are these: > At boot, ntpd hangs, holding up the rest of the startup process. If > I kill it with a ctrl-c, sendmail then does some funky things, and > also hangs. > > === > /var/log/ntp shows: > [EMAIL PROTECTED] /var/log] # cat ntp.log > 28 May 23:53:37 ntpd[609]: ntpd exiting on signal 15 > 28 May 23:56:37 ntpd[409]: ntpd exiting on signal 2 > [EMAIL PROTECTED] /var/log] # > > which I think is from me killing it via ctrl-c > === > > So, to workaround temporarily, I commented out ntpd_enable="YES" in > rc.conf. Ntpd obviously doesn't hold up my boot anymore but sendmail > does. > > === > Starting sendmail. > safefile(etc/mail/services.switch, uid=0, gid=0, flags=6480, > mode=400): safedirpath(/etc/mail, uid=0, gid=0 flags =6580, level=0, > offset=0): [dir /etc/mail] OK > No such file or directory > > Then I get similar lines for /etc/mail/submit.cf, > etc/mail/relay-domains, The last line is: > Recipient names must be specified > > I can't seem to find the output I'm seeing in /var/log/messages or > /var/log/maillog, so I've hand-typed in the bit above. > > /var/log/maillog has lots of: > May 29 00:00:05 oberon sm-msp-queue[436]: i4S2ug7P087593: to=root, > ctladdr=root (0/0), delay=1+01:03:23, xdelay=00:00:00, mailer=relay, > pri=4980184, relay=[127.0.0.1], dsn=4.0.0, stat=Deferred: Connection > refused by [127.0.0.1] > > which also started after my cvsup last night. > === > > > Not sure what else to provide. Any direction on how to 'shoot and > fix this wins a free beer next time you're in NYC. Thanks... Running cvsup didn't do all of this. What did you cvsup and what else did you do :)? Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Searching CVS commits
On Fri, May 28, 2004 at 02:20:45PM -0700, Kent Stewart wrote: > The history is always available using cvsweb.cgi such as > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/vfs_syscalls.c > > Back up to the top and bookmark it. Also has the alias http://cvsweb.freebsd.org/ Kris pgp0UoKoB8oqw.pgp Description: PGP signature
Re: Problems after CVSUP
On 29-May-2004 Edward Carmody wrote: > Not quite a newbie, but not very good either, apparently. :( I did a cvsup > last night, following instructions from the handbook, and hosed up my box. > > = > [EMAIL PROTECTED] /home/ecarmody] $ uname -a > FreeBSD oberon.hudsonvalleynetworks.com 5.2.1-RELEASE-p7 FreeBSD > 5.2.1-RELEASE-p7 #0: Thu May 27 19:57:55 EDT 2004 > root@:/usr/obj/usr/src/sys/GENERIC i386 > [EMAIL PROTECTED] /home/ecarmody] $ > = > > I should not be running 5.2.1-RELEASE due to my inexperience, I know, but > need to in order to support my IDE controller. I was using the box for www, > sendmail, tacacs, ntp, syslog, samba, for my home network, and just trying > to learn UNIX a la FreeBSD. > > My immediate issues are these: > At boot, ntpd hangs, holding up the rest of the startup process. If I kill > it with a ctrl-c, sendmail then does some funky things, and also hangs. > > === > /var/log/ntp shows: > [EMAIL PROTECTED] /var/log] # cat ntp.log > 28 May 23:53:37 ntpd[609]: ntpd exiting on signal 15 > 28 May 23:56:37 ntpd[409]: ntpd exiting on signal 2 > [EMAIL PROTECTED] /var/log] # > > which I think is from me killing it via ctrl-c > === > > So, to workaround temporarily, I commented out ntpd_enable="YES" in rc.conf. > Ntpd obviously doesn't hold up my boot anymore but sendmail does. > > === > Starting sendmail. > safefile(etc/mail/services.switch, uid=0, gid=0, flags=6480, mode=400): > safedirpath(/etc/mail, uid=0, gid=0 flags =6580, level=0, offset=0): > [dir /etc/mail] OK > No such file or directory > > Then I get similar lines for /etc/mail/submit.cf, etc/mail/relay-domains, > The last line is: > Recipient names must be specified > > I can't seem to find the output I'm seeing in /var/log/messages or > /var/log/maillog, so I've hand-typed in the bit above. > > /var/log/maillog has lots of: > May 29 00:00:05 oberon sm-msp-queue[436]: i4S2ug7P087593: to=root, > ctladdr=root (0/0), delay=1+01:03:23, xdelay=00:00:00, mailer=relay, > pri=4980184, relay=[127.0.0.1], dsn=4.0.0, stat=Deferred: Connection refused > by [127.0.0.1] > > which also started after my cvsup last night. > === > > > Not sure what else to provide. Any direction on how to 'shoot and fix this > wins a free beer next time you're in NYC. Thanks... Did you forget to run mergemaster? When updating via cvsup, you should *always* do the following: 1) cvsup 2) make buildworld 3) make buildkernel 4) make installkernel 5) reboot in single-user mode 6) run mergemaster -p 7) make installworld 8) run mergemaster Then, double-check /etc/rc.conf against /etc/defaults/rc.conf to see if there are any important changes in startup functionality. Then, and only then, should it be safe to reboot. If you've merged in any changes under /etc/mail, you should also cd /etc/mail and make all install before rebooting as well. HTH -- Conrad Sabatier <[EMAIL PROTECTED]> - "In Unix veritas" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
