Re: boot2 problem
Alexey Zelkin wrote: > > > It's pretty consistant with other OS's boot prompt. > Ok, I see that I'll not get answer to my question except "do it otherwise". Actually, you got an answer, though you might have missed it. Boot2 does not have "/kernel" as default, but "/boot/loader". Thus, even if we did identify -v as a "parameter" and passed it to what is being loaded, it would be the loader that receives it. Alas, we just don't have a lot of space for boot2, and we'd rather not spend it on things like that. Rather, we decided to keep boot2 simple, and transfer all niceties to a new stage, the loader. Loader is fully featured, has an extended help, and includes a complete structured programming language. We can't fit all of this into boot2, obviously. And if we decided to add "just this feature" to boot2, where would we draw the line? As the requirements for the boot stage increase, so will boot2. It happened before, and that's why we now have a three stage loader. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
temperature monitor for windowmaker
For all those who mailed this list about the temperature monitor apps saying that the device wasn't configured, I have a preliminary version of an app that should work for you. I just finished writing it about 10 minutes ago, and it only shows temperatures, and only shows them in degrees C right now. In about 20 mins from now (9:00 PM EDT) you will be able to get this app from www.wam.umd.edu/~culverk/ Kenneth Culver To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: QIC ft0 driver support in 4.0-CURRENT gone?
Today Julian Elischer wrote: > hey If someone did adopt it then it wouldn't be a problem.. > if no-on edoes then it can remain 'unsupported' unsupported != tucked away in the attic, out of reach of many/most users. -- Jack O'NeillSystems Administrator / Systems Analyst [EMAIL PROTECTED] Crystal Wind Communications, Inc. Finger [EMAIL PROTECTED] for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel compile problem at ed0
Clean compile. I haven't rebooted yet, but it should be fine. Thank you, ed "Matthew N. Dodd" wrote: > Argh. I know whats wrong but I don't have a good idea on how to cleanly > fix it. > > Comment out: > > sys/dev/ed/if_ed_isa.c ... > > in sys/i386/conf/files.i386 and reconfig/make etc. > > Warner? You mind taking a peek at sys/dev/ed/if_ed_pccard.c and telling > me how to fix it so we can get rid of the sys/i386/isa/if_ed.c hackery? > AFAIK all that is needed is some way to get the softc struct and to tell > the PCCARD system to reserve a softc of ed_softc size. > > On Fri, 15 Oct 1999, Edwin Culp wrote: > > I seem to have a problem compiling a kernel on my laptop with the ed0 > > driver that I use for my D-link 660 pcmcia card. > > > > Running current, cvsup this morning. Make world finished with no problems > > but my attempt at kernel compilation yielded: > > > > > if_ed_isa.o: In function `ed_isa_attach': > > > if_ed_isa.o(.text+0xef): undefined reference to `ed_alloc_port' > > > if_ed_isa.o(.text+0x109): undefined reference to `ed_alloc_memory' > > > if_ed_isa.o(.text+0x11a): undefined reference to `ed_alloc_irq' > > > if_ed_isa.o(.text+0x127): undefined reference to `edintr' > > > if_ed_isa.o(.text+0x152): undefined reference to `ed_attach' > > > if_ed_isa.o(.text+0x15a): undefined reference to `ed_release_resources' > > > *** Error code 1 > > > > > > Stop in /usr/src/sys/compile/LAPTOP. > > > > >From my cvsup of this morning > > > > Edit src/sys/dev/ed/if_ed.c > > Add delta 1.164 99.10.15.03.12.46 mdodd > > Edit src/sys/dev/ed/if_ed_isa.c > > Add delta 1.2 99.10.15.03.12.47 mdodd > > Edit src/sys/dev/ed/if_ed_pci.c > > Add delta 1.22 99.10.15.03.12.47 mdodd > > Edit src/sys/dev/ed/if_edvar.h > > Add delta 1.3 99.10.15.03.12.47 mdodd > > > > Maybe I just need to wait for the rest of the changes. > > > > Thanks, > > > > ed > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > | 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 | This Space For Rent | ISO8802.5 4ever | > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: QIC ft0 driver support in 4.0-CURRENT gone?
On 15 October 1999 at 10:20, Julian Elischer <[EMAIL PROTECTED]> wrote: > the driver could come back if someone who HAD such a device were to adopt > it.. I have one (colorado thing). I _will not_ adopt it :-) but I'd happily send it to a committer that wanted to support it. I haven't used it in years, but AFAIK it still works. If no one volunteers (as I suspect), then RIP ft0... -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: QIC ft0 driver support in 4.0-CURRENT gone?
hey If someone did adopt it then it wouldn't be a problem.. if no-on edoes then it can remain 'unsupported' On Fri, 15 Oct 1999, Garrett Wollman wrote: > < >said: > > > the driver could come back if someone who HAD such a device were to adopt > > it.. > > Probably not. The hardware is just so transcendently evil that it's > unlikely it could be made to work reliably for more than one or two > people at a time. > > At some point we need to stop supporting antique hardware since it > places a significant burden on the advancement of the rest of the > system. > > -GAWollman > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PCI Hardware Modem (Really)
Hi, I've got a Rockwell PCI Modem thats full hardware, and I was wondering if anybody has written a driver for this kind yet. I saw somebody posted something about they were going to write a driver for such a hardware class. Thanks Bill [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weak symbols (Was: World breakage in libc_r?)
On 15-Oct-99 at 15:05, John Birrell ([EMAIL PROTECTED]) wrote: > On Fri, Oct 15, 1999 at 08:09:57PM +0200, Wilko Bulte wrote: > > Sheer curiosity and most likely a somewhat dim question: > > > > what the h* is a weak versus a strong symbol? > > A weak symbol is like an alias for another (strong) symbol. The linker > will link to strong symbols first, then, for any unresolved references, > it will try to resolve against the weak symbols before going on to > the next library. Weak symbols are a good way to hide things in order > to stop polluting the name space. But they can cause problems too. If so, then the definition has changed since they were first invented. (Around 20 years ago, IIRC.) Weak symbols were/are used to refer to external objects that may or may not actually be linked in. The difference between a weak and a strong symbol is/was that a strong symbol would cause the appropriate library to be loaded to ensure that it would be defined (and generate errors if still unresolved at the end of the link) whereas a weak symbol would not cause a library module to be loaded and would not cause an error if left unresolved. I don't recall any consistant name for the behavour you describe, but it was traditionally handled by the linker control file. (Of course, this was on systems which had somewhat smarter linkers than unix's.) -Pat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Weak symbols (Was: World breakage in libc_r?)
On Fri, Oct 15, 1999 at 08:09:57PM +0200, Wilko Bulte wrote: > Sheer curiosity and most likely a somewhat dim question: > > what the h* is a weak versus a strong symbol? A weak symbol is like an alias for another (strong) symbol. The linker will link to strong symbols first, then, for any unresolved references, it will try to resolve against the weak symbols before going on to the next library. Weak symbols are a good way to hide things in order to stop polluting the name space. But they can cause problems too. Our use of weak symbols in libc is incomplete. Although syscalls like read() have _read() as the strong symbol and read() as the weak one, we continue to call read() in other areas of libc. This means that a user can create their own read() function and they won't get a clash when they link against libc, but other functions in libc that really want to call the _read() syscall will call the user's read() function instead. That's broken. We really need to change libc in the way that NetBSD did with their namespace.h stuff. This ensures that the internals of libc call the hidden names, not the weakly exported ones. -- John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't make crashdump after panic
On Fri, 15 Oct 1999, Khetan Gajjar wrote: > > Looks like we have our problem; it's the ATA driver. I don't recall > seeing this error when using the wd driver. Yup. When I force a panic from DDB, I get panic: timeout table full and a message about "Dump already in progress, bailing". I haven't yet looked at them dump, to see whats in it. This doesn't happen with wd driver. Relevent bits of my dmesg: SMP: AP CPU #1 Launched! ad0: ATA-4 disk at ata0 as master ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 DANGER wait_intr active=ATA_IGNORE_INTR ad1: ATA-? disk at ata0 as slave ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue, DMA Creating DISK ad1 Creating DISK wd1 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=04 acd0: CDROM drive at ata1 as master acd0: read 1033KB/s (1033KB/s), 256KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM unknown medium, unlocked Waiting 15 seconds for SCSI devices to settle To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't make crashdump after panic
On Fri, 15 Oct 1999, Alfred Perlstein wrote: > > What is your memory size? what is your swap device size? 256MB. 512MB. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't make crashdump after panic
On Fri, 15 Oct 1999, Alex Le Heux wrote: > On Thu, Oct 14, 1999 at 09:19:33AM -0500, David Scheidt wrote: > > On Thu, 14 Oct 1999, Alex Le Heux wrote: > > > > > After configuring the system for making a crashdump, I get "panic: Timeout > > > table full" halfway through the dump. > > > [snip] > > > > Sounds like your modules are out of date? That bit me. > > > > The panic happened well after the boot. After X had come up. It happened > when I logged in and Windowmaker was busy firing up all the crap that I > have running in the various places on my screen. > > I'd love to make a crashdump and poke it, but I've got no idea why it > doesn't finish de dump. What is your memory size? what is your swap device size? -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't make crashdump after panic
On Thu, Oct 14, 1999 at 09:19:33AM -0500, David Scheidt wrote: > On Thu, 14 Oct 1999, Alex Le Heux wrote: > > > After configuring the system for making a crashdump, I get "panic: Timeout > > table full" halfway through the dump. > [snip] > > Sounds like your modules are out of date? That bit me. > The panic happened well after the boot. After X had come up. It happened when I logged in and Windowmaker was busy firing up all the crap that I have running in the various places on my screen. I'd love to make a crashdump and poke it, but I've got no idea why it doesn't finish de dump. Alex -- ++---+ | SMTP: <[EMAIL PROTECTED]> | E-Gold: 101979 | | ICBM: N52 22.64'6 E4 51.54'1 | PGP: 0x1d512a3f | ++---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: QIC ft0 driver support in 4.0-CURRENT gone?
< said: > the driver could come back if someone who HAD such a device were to adopt > it.. Probably not. The hardware is just so transcendently evil that it's unlikely it could be made to work reliably for more than one or two people at a time. At some point we need to stop supporting antique hardware since it places a significant burden on the advancement of the rest of the system. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot2 problem
hi, On Fri, Oct 15, 1999 at 03:09:44AM -0700, Bill Swingle wrote: > > > > Q: What I do then ? > > > > A: On boot prompt type "kernel -v" > > > > > > > > Q: So ? > > > > A: All works fine (system is booting in verbose mode) > > > > > > '-v' is an argument to the kernel. Specify it as such. 8) > > > > If we have default kernel name then why I can't pass parameters there > > and have to excplicitly type kernel name ? > > You don't have to explicitly specify the kernel name. If the default > kernel has already been loaded you just have to tell it what to do. > > 'boot -v' You're talking about loader(8) boot stage and I about boot2 stage (before loader(8) execution) > It's pretty consistant with other OS's boot prompt. Ok, I see that I'll not get answer to my question except "do it otherwise". Sorry. -- /* Alexey Zelkin && [EMAIL PROTECTED]*/ /* Tavric National University && [EMAIL PROTECTED] */ /* http://www.ccssu.crimea.ua/~phantom && [EMAIL PROTECTED] */ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: jumping from 3.1 to 4.0
[And this is one more reason why the default procedure was "world before kernel" -- I have nothing against changing the procedure, as long as people unbreak the new procedure... ] "Ilmar S. Habibulin" wrote: > > I'm using freebsd 3.1 release at one of my PCs. Today i tried to upgrade > it to current. I read mail-archives and knew, that i had to compile kernel > first. So i made new config and configured and build kernel. While booting > loader prints the next error message and boot fails: > > /kernel text=0x202b9d > elf_loadexec:archsw.readin failed > can't load kernel > > What hould i do to upgrade to current? You need to install a new loader. cd /sys/boot; make depend && make all install. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pcm/ES1370 PCI soundcard problem
So the system builds nice again - thanks. I haven't tried the XFree86 fix yet. However there is a problem with the pcm driver: pcm0: irq 11 at device 15.0 on pci0 pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 Any idea? I used device pcm0 at pci0 in the kernel configuration file. Regards, Marc PS start of verbose dmesg: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #18: Fri Oct 15 18:53:15 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ORANJE Calibrating clock(s) ... TSC clock: 300730129 Hz, i8254 clock: 1193374 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 300684315 Hz CPU: AMD-K6tm w/ multimedia extensions (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping = 0 Features=0x8001bf AMD Features=0x400<> Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 192M bytes Write Allocate 15-16M bytes: Enable Hardware Write Allocate Control: Disable real memory = 201326592 (196608K bytes) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x002e6000 - 0x0bff5fff, 198246400 bytes (48400 pages) avail memory = 192286720 (187780K bytes) bios32: Found BIOS32 Service Directory header at 0xc00faf50 bios32: Entry = 0xfb410 (c00fb410) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb440 pnpbios: Found PnP BIOS data at 0xc00fbfb0 pnpbios: Entry = f:bfd8 Rev = 1.0 Other BIOS signatures found: ACPI: Preloaded elf kernel "kernel" at 0xc02cd000. VESA: information block 56 45 53 41 00 03 00 01 00 01 01 00 00 00 22 00 00 01 40 00 02 03 07 01 00 01 0e 01 00 01 17 01 00 01 00 01 01 01 02 01 03 01 04 01 05 01 06 01 07 01 08 01 09 01 0a 01 0b 01 0c 01 0e 01 0f 01 VESA: 44 mode(s) found VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc027a9c2 (122) VESA: NVidia VESA: NVidia Riva TNT A0 pci_open(1):mode 1 addr port (0x0cf8) is 0x8074 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=55971039) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 58186896 bytes/sec bzero() bandwidth = 58305638 bytes/sec pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=55971039) pcib0: on motherboard found-> vendor=0x1039, dev=0x5597, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found-> vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found-> vendor=0x1039, dev=0x5513, revid=0xd0 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=0 found-> vendor=0x1000, dev=0x0001, revid=0x02 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=15 map[0]: type 1, range 32, base 6300, size 8 map[1]: type 1, range 32, base e2001000, size 8 found-> vendor=0x1274, dev=0x5000, revid=0x00 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 found-> vendor=0x10de, dev=0x0020, revid=0x04 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=10 map[0]: type 1, range 32, base e000, size 24 map[1]: type 1, range 32, base e100, size 24 pci0: on pcib0 i4b_pci_probe: unknown PCI type 1435963449l! isab0: at device 1.0 on pci0 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa0: on isab0 i4b_pci_probe: unknown PCI type 1427312697l! chip1: irq 0 at device 1.1 on pci0 i4b_pci_probe: unknown PCI type 69632l! ncr0: irq 15 at device 13.0 on pci0 ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr0: single-ended, open drain IRQ driver pcm0: irq 11 at device 15.0 on pci0 pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 i4b_pci_probe: unknown PCI type 2101470l! vga-pci0: irq 10 at device 17.0 on pci0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0:
Re: kernel compile problem at ed0
Argh. I know whats wrong but I don't have a good idea on how to cleanly fix it. Comment out: sys/dev/ed/if_ed_isa.c ... in sys/i386/conf/files.i386 and reconfig/make etc. Warner? You mind taking a peek at sys/dev/ed/if_ed_pccard.c and telling me how to fix it so we can get rid of the sys/i386/isa/if_ed.c hackery? AFAIK all that is needed is some way to get the softc struct and to tell the PCCARD system to reserve a softc of ed_softc size. On Fri, 15 Oct 1999, Edwin Culp wrote: > I seem to have a problem compiling a kernel on my laptop with the ed0 > driver that I use for my D-link 660 pcmcia card. > > Running current, cvsup this morning. Make world finished with no problems > but my attempt at kernel compilation yielded: > > > if_ed_isa.o: In function `ed_isa_attach': > > if_ed_isa.o(.text+0xef): undefined reference to `ed_alloc_port' > > if_ed_isa.o(.text+0x109): undefined reference to `ed_alloc_memory' > > if_ed_isa.o(.text+0x11a): undefined reference to `ed_alloc_irq' > > if_ed_isa.o(.text+0x127): undefined reference to `edintr' > > if_ed_isa.o(.text+0x152): undefined reference to `ed_attach' > > if_ed_isa.o(.text+0x15a): undefined reference to `ed_release_resources' > > *** Error code 1 > > > > Stop in /usr/src/sys/compile/LAPTOP. > > >From my cvsup of this morning > > Edit src/sys/dev/ed/if_ed.c > Add delta 1.164 99.10.15.03.12.46 mdodd > Edit src/sys/dev/ed/if_ed_isa.c > Add delta 1.2 99.10.15.03.12.47 mdodd > Edit src/sys/dev/ed/if_ed_pci.c > Add delta 1.22 99.10.15.03.12.47 mdodd > Edit src/sys/dev/ed/if_edvar.h > Add delta 1.3 99.10.15.03.12.47 mdodd > > Maybe I just need to wait for the rest of the changes. > > Thanks, > > ed > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- | 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 | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: World breakage in libc_r?
As Daniel Eischen wrote ... Sheer curiosity and most likely a somewhat dim question: what the h* is a weak versus a strong symbol? Thanks, Wilko > John Birrell wrote: > > Weak symbols don't work too well _between_ libraries. If libc is linked > > before libpthread, any unresolved references when libc is searched will > > use the weak symbols from there, regardless of the fact that a strong > > symbol exists in libpthread. If libc is linked after libpthread, then > > you can have libc internal references to things that should been resolved > > to things in libpthread, but end up using the weak symbols in libc > > because that is all there is left. 8-( > > > > Not a simple problem to solve. The current tools don't help at all. A > > second library pass to resolve weak symbols would have been better. It's > > too late for that now, though, since you can change the semantics on the > > shared loader. > > It'd be interesting to know how Solaris does this. I see they don't > supply a static libpthread, just the dynamic. It seems they do use > a strong symbol in libpthread, and a weak one in libc: > > vfr [80] $ nm /usr/lib/libc.so.1 | grep pthread_mutex_lock > [4394] |596188| 44|FUNC |WEAK |0|12 |_pthread_mutex_lock > [2980] |596188| 44|FUNC |WEAK |0|12 |pthread_mutex_lock > vfr [81] $ nm /usr/lib/libpthread.so.1 | grep pthread_mutex_lock > [333] | 20704| 8|FUNC |GLOB |0|8 |_pthread_mutex_lock > [107] | 20704| 8|FUNC |WEAK |0|8 |pthread_mutex_lock -- | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel compile problem at ed0
I seem to have a problem compiling a kernel on my laptop with the ed0 driver that I use for my D-link 660 pcmcia card. Running current, cvsup this morning. Make world finished with no problems but my attempt at kernel compilation yielded: > if_ed_isa.o: In function `ed_isa_attach': > if_ed_isa.o(.text+0xef): undefined reference to `ed_alloc_port' > if_ed_isa.o(.text+0x109): undefined reference to `ed_alloc_memory' > if_ed_isa.o(.text+0x11a): undefined reference to `ed_alloc_irq' > if_ed_isa.o(.text+0x127): undefined reference to `edintr' > if_ed_isa.o(.text+0x152): undefined reference to `ed_attach' > if_ed_isa.o(.text+0x15a): undefined reference to `ed_release_resources' > *** Error code 1 > > Stop in /usr/src/sys/compile/LAPTOP. >From my cvsup of this morning Edit src/sys/dev/ed/if_ed.c Add delta 1.164 99.10.15.03.12.46 mdodd Edit src/sys/dev/ed/if_ed_isa.c Add delta 1.2 99.10.15.03.12.47 mdodd Edit src/sys/dev/ed/if_ed_pci.c Add delta 1.22 99.10.15.03.12.47 mdodd Edit src/sys/dev/ed/if_edvar.h Add delta 1.3 99.10.15.03.12.47 mdodd Maybe I just need to wait for the rest of the changes. Thanks, ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Timeframe on XFree86 signal fix
> > Hi folks, > > A sequence of silly mistakes and circumstances have conspired against me > to make it impossible for me to run XFree86. I understand that the > XFree86 build is broken in the face of recent signal-related changes. > > I want to know how long I can expect to wait for XFree86 to build on > CURRENT again. I'm not pushing, I just want to know whether I'm in for a > wait of less than a week (in which case I'll do without XFree86) or > whether I can expect to wait longer (in which case I'll bite the bullet > and undo my silly mistakes). > I too was pressed for time and what I did was to dig up the source for a program which uses signals and cut paste the include files to FSConServ.c . I played a little with gcc -E which displays the processing of the include files and took a brief look at signa.h and saw the check for _P1003_1B_VISIBLE... This is all academic since the proper fix was posted to the list. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: pccard kernel config file changes
I've changed the attachment topography for pccard/pcic devices. Now pcic attaches to the isa bus to act as a bridge to the pccard device. For historical reasons, I've left the pccard device name as "card" but this may change to pccard in the future, but there are too many legacy drivers to do that right now. The upshot of all of this is that you need to change your kernel config to controller pcic0 at isa? controller pcic1 at isa? controller card0 in order for thing to work. I've tested this on my laptop, but I only have one pccard slot. I'm interested to hear from others that have more than one slot. I've also tested only on systems that have one pcic, so I'd be interested to hear from those that have more than one pcic in their system. Finally, no pc98 testing has been done. I'm trying to get things to the point where I can attach my slightly rewritten sio code to attach by the end of FreeBSD CON. The next rats nest that I have to sort out is interrupts and bus resources in general given the recent hoisting of resource allocation to the the bus interface. While I'm at it, I'll be trying to untangle the morass of interconnectedness between pcic and pccard. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: QIC ft0 driver support in 4.0-CURRENT gone?
the driver could come back if someone who HAD such a device were to adopt it.. On Fri, 15 Oct 1999, jack wrote: > Today Mike Smith wrote: > > > > > > > Sorry if I ask a FAQ, > > > > Don't be sorry, don't do it. Search the mailing list archives. > > It might help if HARDWARE.TXT (both -current and -stable) didn't > list floppy tapes. It refers to the driver as "stale" rather > than gone. > > -- > Jack O'NeillSystems Administrator / Systems Analyst > [EMAIL PROTECTED] Crystal Wind Communications, Inc. > Finger [EMAIL PROTECTED] for my PGP key. >PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD >enriched, vcard, HTML messages > /dev/null > -- > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot2 problem
> hi, > > On Fri, Oct 15, 1999 at 12:57:26AM -0700, Mike Smith wrote: > > > That's correct. '-v' at the boot: prompt does nothing. > > But '/kernel' is default kernel name, so "-v" will be option to default > kernel name (at least FreeBSD 1.1.5.1/2.* does that :-) ). However, FreeBSD 3.x and 4.x do not. /boot/loader is the default object loaded by boot2. > > > Q: What I do then ? > > > A: On boot prompt type "kernel -v" > > > > > > Q: So ? > > > A: All works fine (system is booting in verbose mode) > > > > '-v' is an argument to the kernel. Specify it as such. 8) > If we have default kernel name then why I can't pass parameters there > and have to excplicitly type kernel name ? You can. Don't interrupt boot2, wait for the loader, and use 'boot -v'. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree build fine but don't install
I managed to fix this problem temporarily for myself, but was hoping the tree would fix itself soon enough. At the top of FSConServ.c add the line #define _P1003_1B_VISIBLE I believe (I deleeted the X source tree), and it'll build fine. Excerpts from FreeBSD-Current: 15-Oct-99 XFree build fine but don't .. by G. Giovannelli@giovannel > I tried to install from the ports XFree 3.3.5 in my 4.0-CURRENT box. > It compile well, but when it's the time of the install I receive this error : > > rm -f FSConnServ.o > cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../.. > -I../../ex > ports/include -DCSRG_BASED -DFUNCPROTO=15 > -DNARROWPROTO -DMALLOC_0_RETURNS_N > ULL -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT -DFS_t -DTRANS_CLIENT > -DBSD44SOCKE > TS FSConnServ.c > In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: > /usr/include/sys/signal.h:212: syntax error before `siginfo_t' > In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: > /usr/include/sys/signal.h:285: field `sigev_value' has incomplete type > *** Error code 1 > Stop in /usr/ports/x11/XFree86/work/xc/lib/FS. > *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: World breakage in libc_r?
> On a related topic, we should fix the Alpha to emit the weak alias > like the i386 does. We should do what ever is reasonably possible to keep these two archs operating the same. IMHO, people will expect their FreeBSD platform knowledge to hold on the Alpha. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't make crashdump after panic
On Fri, 15 Oct 1999, Khetan Gajjar wrote: > I've been getting these really odd panics as well (which I reported > but no-one seemed interested), with that error. I had only the panics caused by loading an out of date KLD. > I'm using the "experimental" ATA code though; are you using IDE > disks with the ATA or old WD driver, or are you using SCSI disks ? I have both IDE and SCSI disks, I am dumping to an ide disk controlled by the ATA driver. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't make crashdump after panic
Around Yesterday, "David Scheidt" wrote : DS> I had a panic tuesday, due to trying to load a broken module. I got the DS> same panic: Timeout table full message. Interestingly, savecore seems to I've been getting these really odd panics as well (which I reported but no-one seemed interested), with that error. In the one case where I provoked it (by loading a kld that was out of sync with the kernel), I also got that error. I'm using the "experimental" ATA code though; are you using IDE disks with the ATA or old WD driver, or are you using SCSI disks ? --- Khetan Gajjar (!kg1779) * [EMAIL PROTECTED] http://khetan.os.org.za/ * Talk/Finger [EMAIL PROTECTED] FreeBSD enthusiast* http://www2.za.freebsd.org/ /dev/random output : I am under the influence of sugar, caffeine, and lack of sleep, and should not be held responsible for my behavior. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: still broken?
Yech, malformed patch. This one applies. :-)
Thanks, Marcel.
Ciao,
Sheldon.
Index: signal.h
===
RCS file: /home/ncvs/src/sys/sys/signal.h,v
retrieving revision 1.21
diff -u -d -r1.21 signal.h
--- signal.h1999/10/12 13:58:15 1.21
+++ signal.h1999/10/15 15:13:39
@@ -131,6 +131,15 @@
void*sigval_ptr;
};
+struct sigevent {
+ int sigev_notify; /* Notification type */
+ int sigev_signo;/* Signal number */
+ union sigval sigev_value; /* Signal value */
+};
+
+#defineSIGEV_NONE 0 /* No async notification */
+#defineSIGEV_SIGNAL1 /* Generate a queued signal */
+
typedef struct __siginfo {
int si_signo; /* signal number */
int si_errno; /* errno association */
@@ -209,7 +218,7 @@
/* Additional FreeBSD values. */
#define SI_UNDEFINED 0
-typedef void __siginfohandler_t __P((int, siginfo_t *, void *));
+typedef void __siginfohandler_t __P((int, struct __siginfo *, void *));
typedef__sighandler_t *sig_t; /* type of pointer to a signal function */
@@ -277,17 +286,6 @@
#defineSIG_BLOCK 1 /* block specified signal set */
#defineSIG_UNBLOCK 2 /* unblock specified signal set */
#defineSIG_SETMASK 3 /* set specified signal set */
-
-#ifndef _POSIX_SOURCE
-struct sigevent {
- int sigev_notify; /* Notification type */
- int sigev_signo;/* Signal number */
- union sigval sigev_value; /* Signal value */
-};
-
-#defineSIGEV_NONE 0 /* No async notification */
-#defineSIGEV_SIGNAL1 /* Generate a queued signal */
-#endif
#endif /* !_ANSI_SOURCE */
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: still broken?
Mark Murray wrote:
>
> Hi
>
> I am getting this breakage when I try to compile XFree86 on a really
> current system:
>
> cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../..
>-I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO
>-DMALLOC_0_RETURNS_NULL -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT -DFS_t
>-DTRANS_CLIENT -DBSD44SOCKETS FSConnServ.c
> In file included from /usr/include/sys/param.h:90,
> from ../../exports/include/X11/Xpoll.h:66,
> from FSConnServ.c:58:
> /usr/include/sys/signal.h:212: syntax error before `siginfo_t'
> In file included from /usr/include/sys/param.h:90,
> from ../../exports/include/X11/Xpoll.h:66,
> from FSConnServ.c:58:
> /usr/include/sys/signal.h:285: field `sigev_value' has incomplete type
> *** Error code 1
Apply the following patch to /usr/include/sys/signal.h. I want to make
sure it doesn't break a kernel or world or adds namespace pollution or
whatever before I commit this. In case of problems, yell!
--- /sys/sys/signal.h Fri Oct 15 16:58:52 1999
+++ /usr/include/sys/signal.h Fri Oct 15 16:55:55 1999
@@ -131,6 +131,15 @@
void*sigval_ptr;
};
+struct sigevent {
+ int sigev_notify; /* Notification type */
+ int sigev_signo;/* Signal number */
+ union sigval sigev_value; /* Signal value */
+};
+
+#defineSIGEV_NONE 0 /* No async notification
*/
+#defineSIGEV_SIGNAL1 /* Generate a queued
signal */
+
typedef struct __siginfo {
int si_signo; /* signal number */
int si_errno; /* errno association */
@@ -209,7 +218,7 @@
/* Additional FreeBSD values. */
#define SI_UNDEFINED 0
-typedef void __siginfohandler_t __P((int, siginfo_t *, void *));
+typedef void __siginfohandler_t __P((int, struct __siginfo *, void *));
typedef__sighandler_t *sig_t; /* type of pointer to a signal
function */
@@ -277,17 +286,6 @@
#defineSIG_BLOCK 1 /* block specified signal set */
#defineSIG_UNBLOCK 2 /* unblock specified signal set
*/
#defineSIG_SETMASK 3 /* set specified signal set */
-
-#ifndef _POSIX_SOURCE
-struct sigevent {
- int sigev_notify; /* Notification type */
- int sigev_signo;/* Signal number */
- union sigval sigev_value; /* Signal value */
-};
-
-#defineSIGEV_NONE 0 /* No async notification
*/
-#defineSIGEV_SIGNAL1 /* Generate a queued
signal */
-#endif
#endif /* !_ANSI_SOURCE */
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: QIC ft0 driver support in 4.0-CURRENT gone?
Today Mike Smith wrote: > > > > Sorry if I ask a FAQ, > > Don't be sorry, don't do it. Search the mailing list archives. It might help if HARDWARE.TXT (both -current and -stable) didn't list floppy tapes. It refers to the driver as "stale" rather than gone. -- Jack O'NeillSystems Administrator / Systems Analyst [EMAIL PROTECTED] Crystal Wind Communications, Inc. Finger [EMAIL PROTECTED] for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: staroffice
On Fri 15 Oct 1999 Jesus Rodriguez wrote: >>Installation process has worked ok, but when i try to run >>/usr/local/Office51/bin/soffice or /usr/local/bin/soffice always get a screen >>that says: >> >>Staroffice is already installed on: >>/usr/local/Office51 >> >>And i can select between Modify, Uninstall and Repair... every time i run >>soffice i get the Setup program. I can run the printer setup program without >>problems. >> >>I don't really know where is the problem :( Hello, Did you execute the 'sed' on the library libosl517li.so and did you check the change? In my case (similar problem) it turned out I had to redo this step. So I took the hex editor and changed the path manually. Regards, Walter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Timeframe on XFree86 signal fix
Sheldon Hearn wrote: > I want to know how long I can expect to wait for XFree86 to build on > CURRENT again. I'm not pushing, I just want to know whether I'm in for a > wait of less than a week (in which case I'll do without XFree86) or > whether I can expect to wait longer (in which case I'll bite the bullet > and undo my silly mistakes). Building X... Please hold on :-) -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Timeframe on XFree86 signal fix
Hi folks, A sequence of silly mistakes and circumstances have conspired against me to make it impossible for me to run XFree86. I understand that the XFree86 build is broken in the face of recent signal-related changes. I want to know how long I can expect to wait for XFree86 to build on CURRENT again. I'm not pushing, I just want to know whether I'm in for a wait of less than a week (in which case I'll do without XFree86) or whether I can expect to wait longer (in which case I'll bite the bullet and undo my silly mistakes). Thanks, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: still broken?
At 15/10/99, Mark Murray wrote: >Hi > >I am getting this breakage when I try to compile XFree86 on a really >current system: > >cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../.. >-I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 >-DNARROWPROTO -DMALLOC_0_RETURNS_NULL -DTCPCONN -DUNIXCONN >-DHAS_STICKY_DIR_BIT -DFS_t -DTRANS_CLIENT -DBSD44SOCKETS FSConnServ.c >In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: >/usr/include/sys/signal.h:212: syntax error before `siginfo_t' >In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: >/usr/include/sys/signal.h:285: field `sigev_value' has incomplete type >*** Error code 1 Hi , I have the same problems right now... and it not a kind think if it happens in this way : # cd /usr/ports/x11/XFree # make compilation is ok # pkg_delete -f XFree-3.3.1 # make install and the make install hangs :-) Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: jumping from 3.1 to 4.0
> What hould i do to upgrade to current? Rebuild and reinstall all your modules. Keep the ols ones "just in case". M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
still broken?
Hi I am getting this breakage when I try to compile XFree86 on a really current system: cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DMALLOC_0_RETURNS_NULL -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT -DFS_t -DTRANS_CLIENT -DBSD44SOCKETS FSConnServ.c In file included from /usr/include/sys/param.h:90, from ../../exports/include/X11/Xpoll.h:66, from FSConnServ.c:58: /usr/include/sys/signal.h:212: syntax error before `siginfo_t' In file included from /usr/include/sys/param.h:90, from ../../exports/include/X11/Xpoll.h:66, from FSConnServ.c:58: /usr/include/sys/signal.h:285: field `sigev_value' has incomplete type *** Error code 1 FYI. M To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
jumping from 3.1 to 4.0
I'm using freebsd 3.1 release at one of my PCs. Today i tried to upgrade it to current. I read mail-archives and knew, that i had to compile kernel first. So i made new config and configured and build kernel. While booting loader prints the next error message and boot fails: /kernel text=0x202b9d elf_loadexec:archsw.readin failed can't load kernel What hould i do to upgrade to current? PS. answer to email please. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot2 problem
On Fri, Oct 15, 1999 at 11:45:56AM +0400, Alexey Zelkin wrote: > hi, > > On Fri, Oct 15, 1999 at 12:57:26AM -0700, Mike Smith wrote: > > > That's correct. '-v' at the boot: prompt does nothing. > > But '/kernel' is default kernel name, so "-v" will be option to default > kernel name (at least FreeBSD 1.1.5.1/2.* does that :-) ). The boot loader was completly rewritten for the 3.x series. > > > Q: What I do then ? > > > A: On boot prompt type "kernel -v" > > > > > > Q: So ? > > > A: All works fine (system is booting in verbose mode) > > > > '-v' is an argument to the kernel. Specify it as such. 8) > > If we have default kernel name then why I can't pass parameters there > and have to excplicitly type kernel name ? You don't have to explicitly specify the kernel name. If the default kernel has already been loaded you just have to tell it what to do. 'boot -v' It's pretty consistant with other OS's boot prompt. -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot2 problem
hi, On Fri, Oct 15, 1999 at 12:57:26AM -0700, Mike Smith wrote: > That's correct. '-v' at the boot: prompt does nothing. But '/kernel' is default kernel name, so "-v" will be option to default kernel name (at least FreeBSD 1.1.5.1/2.* does that :-) ). > > Q: What I do then ? > > A: On boot prompt type "kernel -v" > > > > Q: So ? > > A: All works fine (system is booting in verbose mode) > > '-v' is an argument to the kernel. Specify it as such. 8) If we have default kernel name then why I can't pass parameters there and have to excplicitly type kernel name ? -- /* Alexey Zelkin && [EMAIL PROTECTED]*/ /* Tavric National University && [EMAIL PROTECTED] */ /* http://www.ccssu.crimea.ua/~phantom && [EMAIL PROTECTED] */ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree build fine but don't install
I tried to install from the ports XFree 3.3.5 in my 4.0-CURRENT box. It compile well, but when it's the time of the install I receive this error : rm -f FSConnServ.o cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../.. -I../../ex ports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DMALLOC_0_RETURNS_N ULL -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT -DFS_t -DTRANS_CLIENT -DBSD44SOCKE TS FSConnServ.c In file included from /usr/include/sys/param.h:90, from ../../exports/include/X11/Xpoll.h:66, from FSConnServ.c:58: /usr/include/sys/signal.h:212: syntax error before `siginfo_t' In file included from /usr/include/sys/param.h:90, from ../../exports/include/X11/Xpoll.h:66, from FSConnServ.c:58: /usr/include/sys/signal.h:285: field `sigev_value' has incomplete type *** Error code 1 Stop in /usr/ports/x11/XFree86/work/xc/lib/FS. *** Error code 1 I am sorry if this is a well known problem, but I couldn't read the mailing lists in the past days ... Thanks... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: QIC ft0 driver support in 4.0-CURRENT gone?
> > Sorry if I ask a FAQ, Don't be sorry, don't do it. Search the mailing list archives. > But where is ft0 support gone? Into the bitbucket. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Ditto Max
> Since I dont think my other mail made it through...(since I didnt see it, or > any replys) > > Has anyone gotten an Iomega Ditto Max drive to work on 4.0? I have both > types, Floppy/ditto dash card and Parallel port, and would like to use it to > back up my drive every week or so. It's not supported, and it's a disgusting device. Stuff it in the bin and buy something better. You could have found this information by searching the list archives, BTW. You should do that first as a matter of course to avoid messages like this that may seem to be flames. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot2 problem
> hi, > > Just found problem with boot loader. Attached "FAQ" will describe problem :) This is not a problem. > Q: What I want? > A: Boot in verbose mode > > Q: What I do ? > A: On boot prompt type "-v" > > Q: So ? > A: Nothing (system is booting in normal mode) That's correct. '-v' at the boot: prompt does nothing. > Q: What I do then ? > A: On boot prompt type "kernel -v" > > Q: So ? > A: All works fine (system is booting in verbose mode) '-v' is an argument to the kernel. Specify it as such. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
