Re: Bootstrapping issues with groff(1)
On Mon, Dec 11, 2000 at 09:07:53AM -0800, Marcel Moolenaar wrote: Ruslan Ermilov wrote: On Sat, Dec 09, 2000 at 12:29:54PM -0800, Marcel Moolenaar wrote: Ruslan Ermilov wrote: On Fri, Dec 08, 2000 at 06:22:09PM -0800, Marcel Moolenaar wrote: Ruslan Ermilov wrote: The attached patches (p4 and p5) try to solve this bootstrapping problem with groff(1). Sorry, I missed this statement before. What exactly are the bootstrapping problems you're seeing? New groff(1) provides new versions of macro packages and device files. When building, we should use THEM rather than installed (obsolete) ones. Is the old groff(1) incompatible with the new groff(1) in the sense that manpages created with the old groff(1) are visibly different from the manpages created with the new groff(1)? Once again. groff(1) supplies macro packages and device description files. New groff is likely to provide modified files. This, I don't care about. We're never going to use an old groff(1) with the new files or vice versa. From a usage point of view, I don't care about the implementation, just the interface. Let me rephrase the question: Did you modify the manpages to get it to work with the new groff(1) or is the new groff(1) backward compatible with the old groff(1)? The new groff(1) is not always backwards compatible. For example, new groff(1) implements .psbb request internally in troff(1), thus -U flag is no longer required for part of share/doc, and was removed. The new groff(1) also supplies an updated version of doc(7) macro package (the package we use for manpages), and if you build world with MANBUILDCAT, you will definitely need the new version of tmac.doc and friends. OK, I will augment the USRDIRS then, add the groff to bootstrap-tools, and leave the better (if one exists) implementation to someone else. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping issues with groff(1)
On Mon, Dec 11, 2000 at 09:12:17AM -0800, Marcel Moolenaar wrote: Ruslan Ermilov wrote: It appers that running mtree(1) with -U under non-root account works OK, i.e. it creates all missing directories, and exits with status of zero. I believe it also emits warnings, right? What if we create the mtree(1)-compatible BSD.world.dist? The below was generated by ``mtree -cdin -k type,mode'' under 4.2-STABLE. You mean a special mtree file for use by the build? Maybe I'm missing something, but doesn't that also duplicate information, or can you generate this subset on the fly? Forget it, it was a bad idea. I though it won't require ``uname'', but it does. -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
console freeze
Hi there, I did browse the lists but found nothing about my problem. Compiling GENERIC of 5.0 works correctly but once I remove most of uneeded hardware, the console/kbd freeze. I join the MACHINE file and the output. I even tried to change the graphic card to a PCI S3, same. I can get the getty on the serial line, so I tried vidcontrol -i on it. It reports stupid info. Is there something I can try? Nicholas -- [EMAIL PROTECTED] Alcôve - Open Source Software Engineer - http://www.alcove.fr # # BAIKAL # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # #http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the NOTES configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.291 2000/11/15 18:36:24 imp Exp $ machine i386 cpu I386_CPU cpu I486_CPU cpu I586_CPU cpu I686_CPU ident BAIKAL maxusers32 #To statically compile in device wiring instead of /boot/device.hints #hints "BAIKAL.hints" #Default places to look for devices. makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols options DDB options MATH_EMULATE#Support for x87 emulation options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] #optionsSOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem #optionsNFS_ROOT#NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem #optionsDEVFS #Device Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV# install a CDEV entry in /dev # To make an SMP kernel, the next two are needed #optionsSMP # Symmetric MultiProcessor Kernel #optionsAPIC_IO # Symmetric (APIC) I/O device isa device pci #optionsCOMPAT_OLDISA # compatability shims for lnc, le #optionsCOMPAT_OLDPCI # compatability shims for lnc # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering #optionsATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device pass# Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 # At keyboard controller device atkbd # at keyboard device psm # psm mouse device vga # VGA screen # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) device apm # Add suspend/resume support for the i8254. device pmtimer # Audio support #device pcm # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel
PCI-PCI Bridge Problems
I cvsuped current ~2000/12/11 @ ~ 22:00, the previous version was from around 2000/12/07. Before the update my Dual intel nic was happy post update the nic isn't even probed. attached is a pciconf -v -l from before and after as well as a a boot -v from after. If you need more info let me know and I'll go back to the 2000/12/11 kernel. Greg -- Email: [EMAIL PROTECTED] ICQ: 93234105 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) Script started on Tue Dec 12 03:07:05 2000 IN /usr/sbin AT Tue Dec 12-03:07:05 ON mage:skafte [4999] uname -a FreeBSD mage.trollkarl.net 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Thu Dec 7 22:40:54 MST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/MAGE i386 IN /usr/sbin AT Tue Dec 12-03:07:08 ON mage:skafte [5000] sudo pciconf -l -v hostb0@pci0:0:0:class=0x06 card=0x chip=0x12378086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82441FX PCI Memory Controller (PMC)' class= bridge subclass = HOST-PCI isab0@pci0:1:0: class=0x060100 card=0x chip=0x70008086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82371SB PIIX3 PCI-to-ISA Bridge (Triton II)' class= bridge subclass = PCI-ISA atapci0@pci0:1:1: class=0x010180 card=0x chip=0x70108086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82371SB PIIX3 IDE Interface (Triton II)' class= mass storage subclass = ATA none0@pci0:10:0:class=0x03 card=0x chip=0x00b81013 rev=0x00 hdr=0x00 vendor = 'Cirrus Logic' device = 'CL-GD5446 64-bit VisualMedia Accelerator' class= display subclass = VGA pcib1@pci0:13:0:class=0x060400 card=0x00dc chip=0x00241011 rev=0x03 hdr=0x01 vendor = 'Digital Equipment Corporation' device = 'DC21151/2 PCI-PCI Bridge' class= bridge subclass = PCI-PCI fxp0@pci1:4:0: class=0x02 card=0x10f08086 chip=0x12298086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = '82557/8/9 Fast Ethernet LAN Controller' class= network subclass = ethernet fxp1@pci1:5:0: class=0x02 card=0x10f08086 chip=0x12298086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = '82557/8/9 Fast Ethernet LAN Controller' class= network subclass = ethernet # pciconf -v -0 hostb0@pci0:0:0:class=0x06 card=0x chip=0x12378086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82441FX PCI Memory Controller (PMC)' class= bridge subclass = HOST-PCI isab0@pci0:1:0: class=0x060100 card=0x chip=0x70008086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82371SB PIIX3 PCI-to-ISA Bridge (Triton II)' class= bridge subclass = PCI-ISA atapci0@pci0:1:1: class=0x010180 card=0x chip=0x70108086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82371SB PIIX3 IDE Interface (Triton II)' class= mass storage subclass = ATA vga_pci0@pci0:10:0: class=0x03 card=0x chip=0x00b81013 rev=0x00 hdr=0x00 vendor = 'Cirrus Logic' device = 'CL-GD5446 64-bit VisualMedia Accelerator' class= display subclass = VGA pcib1@pci0:13:0:class=0x060400 card=0x00dc chip=0x00241011 rev=0x03 hdr=0x01 vendor = 'Digital Equipment Corporation' device = 'DC21151/2 PCI-PCI Bridge' class= bridge subclass = PCI-PCI Copyright (c) 1992-2000 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.0-CURRENT #5: Tue Dec 12 02:14:20 MST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/MAGE Calibrating clock(s) ... TSC clock: 199430909 Hz, i8254 clock: 1193176 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 199432980 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping = 7 Features=0xf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x0045e000 - 0x07ff7fff, 129605632 bytes (31642 pages) avail memory = 126275584 (123316K bytes) bios32: Found BIOS32 Service Directory header at 0xc00faf20 bios32: Entry = 0xfb320 (c00fb320) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb350 pnpbios: Found PnP BIOS data at
link_elf: symbol undefined when loading module
Hi there, Don't know how to deal with the following error: link_elf: symbol PPBUS_IO undefined when loading the vpo module. PPBUS_IO is defined in ppbus_if.h as a static __inline fonction and does not appear as an undefined symbol in vpo.kld... Any clue? How should I investigate the pb? Nicholas -- [EMAIL PROTECTED] Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [jhb@FreeBSD.org: RE: Panic in -current]
I would like to see full dump of 'vidcontrol -i adapter', 'vidcontrol -i mode' and dmesg after the vesa module is loaded (you get very verbose output from the vesa module init code if you boot the kernel with 'boot -v'). I think this is what you asked for, otherwise please let me know. Bye, Andrea -- 0 and 1. Now what could be so hard about that? fb0: vga0, type:VESA VGA (5), flags:0x700ff initial mode:24, current mode:24, BIOS mode:3 frame buffer window:0xb8000, buffer size:0x8000 window size:0x8000, origin:0x0 display start address (0, 0), scan line width:80 reserved:0x0 mode# flags typesize font window linear buffer -- 0 (0x000) 0x0001 T 40x25 8x8 0xb8000 32k 32k 0x 32k 1 (0x001) 0x0001 T 40x25 8x8 0xb8000 32k 32k 0x 32k 2 (0x002) 0x0001 T 80x25 8x8 0xb8000 32k 32k 0x 32k 3 (0x003) 0x0001 T 80x25 8x8 0xb8000 32k 32k 0x 32k 4 (0x004) 0x0003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x 32k 5 (0x005) 0x0003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x 32k 6 (0x006) 0x0003 G 640x200x1 1 8x8 0xb8000 32k 32k 0x 32k 13 (0x00d) 0x0003 G 320x200x4 4 8x8 0xa 64k 64k 0x 256k 14 (0x00e) 0x0003 G 640x200x4 4 8x8 0xa 64k 64k 0x 256k 16 (0x010) 0x0003 G 640x350x2 2 8x14 0xa 64k 64k 0x 128k 18 (0x012) 0x0003 G 640x350x4 4 8x14 0xa 64k 64k 0x 256k 19 (0x013) 0x0001 T 40x25 8x14 0xb8000 32k 32k 0x 32k 20 (0x014) 0x0001 T 40x25 8x14 0xb8000 32k 32k 0x 32k 21 (0x015) 0x0001 T 80x25 8x14 0xb8000 32k 32k 0x 32k 22 (0x016) 0x0001 T 80x25 8x14 0xb8000 32k 32k 0x 32k 23 (0x017) 0x0001 T 40x25 8x16 0xb8000 32k 32k 0x 32k 24 (0x018) 0x0001 T 80x25 8x16 0xb8000 32k 32k 0x 32k 26 (0x01a) 0x0003 G 640x480x4 4 8x16 0xa 64k 64k 0x 256k 27 (0x01b) 0x0003 G 640x480x4 4 8x16 0xa 64k 64k 0x 256k 28 (0x01c) 0x0003 G 320x200x8 1 8x8 0xa 64k 64k 0x 64k 30 (0x01e) 0x0001 T 80x50 8x8 0xb8000 32k 32k 0x 32k 32 (0x020) 0x0001 T 80x30 8x16 0xb8000 32k 32k 0x 32k 34 (0x022) 0x0001 T 80x60 8x8 0xb8000 32k 32k 0x 32k 37 (0x025) 0x0003 G 320x240x8 4 8x8 0xa 64k 64k 0x 256k 112 (0x070) 0x T 80x43 8x8 0xb8000 32k 32k 0x 32k 113 (0x071) 0x0001 T 80x43 8x8 0xb8000 32k 32k 0x 32k 256 (0x100) 0x000f G 640x400x8 1 8x16 0xa 64k 64k 0xf500 2496k 257 (0x101) 0x000f G 640x480x8 1 8x16 0xa 64k 64k 0xf500 2496k 258 (0x102) 0x000b G 800x600x4 4 8x16 0xa 64k 64k 0x 2496k 259 (0x103) 0x000f G 800x600x8 1 8x16 0xa 64k 64k 0xf500 2496k 260 (0x104) 0x000b G 1024x768x4 48x16 0xa 64k 64k 0x 2496k 261 (0x105) 0x000f G 1024x768x8 18x16 0xa 64k 64k 0xf500 2496k 263 (0x107) 0x000f G 1280x1024x8 1 8x16 0xa 64k 64k 0xf500 2496k 264 (0x108) 0x000f G 640x400x16 18x16 0xa 64k 64k 0xf500 2496k 269 (0x10d) 0x000f G 320x200x15 18x8 0xa 64k 64k 0xf500 2496k 270 (0x10e) 0x000f G 320x200x16 18x8 0xa 64k 64k 0xf500 2496k 272 (0x110) 0x000f G 640x480x15 18x16 0xa 64k 64k 0xf500 2496k 273 (0x111) 0x000f G 640x480x16 18x16 0xa 64k 64k 0xf500 2496k 274 (0x112) 0x000f G 640x480x24 18x16 0xa 64k 64k 0xf500 2496k 275 (0x113) 0x000f G 800x600x15 18x16 0xa 64k 64k 0xf500 2496k 276 (0x114) 0x000f G 800x600x16 18x16 0xa 64k 64k 0xf500 2496k 277 (0x115) 0x000f G 800x600x24 18x16 0xa 64k 64k 0xf500 2496k 278 (0x116) 0x000f G 1024x768x15 1 8x16 0xa 64k 64k 0xf500 2496k 279 (0x117) 0x000f G 1024x768x16 1 8x16 0xa 64k 64k 0xf500 2496k 280 (0x118) 0x000f G 1024x768x24 1 8x16 0xa 64k 64k 0xf500 2496k 288 (0x120) 0x000f G 320x240x8 1 8x8 0xa 64k 64k 0xf500 2496k 289 (0x121) 0x000f G 320x240x16 18x8 0xa 64k 64k 0xf500 2496k 290 (0x122) 0x000f G 400x300x8 1 8x8 0xa 64k 64k 0xf500 2496k 291 (0x123) 0x000f G 400x300x16 18x8 0xa 64k 64k 0xf500 2496k 292 (0x124) 0x000f G 512x384x8 1 8x8 0xa 64k 64k 0xf500 2496k 293 (0x125) 0x000f G 512x384x16 18x8 0xa 64k 64k 0xf500 2496k Dec 11 23:20:41 brian /boot/kernel/kernel: VESA: information block Dec 11 23:20:41 brian /boot/kernel/kernel: 56 45 53 41 00 02 20 01 00 01 00 00 00 00 22 00 Dec 11
buildkernel target breaks on pcivar.h
Hi folks, Anyone else seeing this for the last two days in the buildkernel target? [...] linking kernel.debug textdata bss dec hex filename 1250813 122716 112824 1486353 16ae11 kernel.debug objcopy --strip-debug kernel.debug kernel cd /usr/src/sys/modules ; env MAKEOBJDIRPREFIX=/usr/obj/usr/src/sys/AXL/modules KMODDIR=/boot/kernel make obj ; env MAKEOBJDIRPREFIX=/usr/obj/usr/src/sys/AXL/modules KMODDIR=/boot/kernel make all === 3dfx === accf_data [...] === wi === 3dfx make: don't know how to make @/pci/pcivar.h. Stop *** Error code 2 [...] I'm quite careful to blow away obj before I buildworld and buildkernel, otherwise I wouldn't bother the list with this. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel target breaks on pcivar.h
* Sheldon Hearn [EMAIL PROTECTED] [001212 03:32] wrote: Hi folks, Anyone else seeing this for the last two days in the buildkernel target? I see annoying breakage when compiling with -j, are you using it? -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel target breaks on pcivar.h
On Tue, 12 Dec 2000 03:48:58 PST, Alfred Perlstein wrote: Anyone else seeing this for the last two days in the buildkernel target? I see annoying breakage when compiling with -j, are you using it? No sir. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HPT370 RAID - booting
It seems [Ivan Debn_r] wrote: [Charset iso-8859-2 unsupported, filtering to ASCII...] I'm just looking at the disk partitions, and the first 63 sectors are by default marked as unused. So is it really nescessary to have the ofset in the ar driver for HPT? This has been changed in both -current and -stable, so use DD disks with care (ie skip the first 10 secs) Correct me if I'm wrong, but in RAID1 it is essential to be able to take one of the drives and boot from it almost as if it was singe simple disk. Yes, and ? that works just fine... How does the driver handles situation when there is one of the mirror drives broken or missing ? Not at all, you have to use the BIOS to either switch off the RAID or setup a new fresh disks or whatever you want to do. If a RAID array is broken somehow, the driver wont attach it (a safety mesure so you wont blow up the remaining disks).. Is it possible to query the driver to check, if the drives are OK from the userland ? No. However I have an atacontrol thingie on the bench but its not ready yet, with that you will be able to control the RAIDs and other ATA related stuff... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-PCI Bridge Problems
I cvsuped current ~2000/12/11 @ ~ 22:00, the previous version was from around 2000/12/07. Before the update my Dual intel nic was happy post update the nic isn't even probed. Hrm. That's odd; I have one of those here (with a Compaq label on it) as part of my test set. In fact, I have twelve different ethernet devices in the test machine right now trying to reproduce this. 8( attached is a pciconf -v -l from before and after as well as a a boot -v from after. If you need more info let me know and I'll go back to the 2000/12/11 kernel. About the only thing different I can see between your setup and mine is that your bridge gets bus 6, but comes up as pci bus 1. There may still be assumptions somewhere in the code that the pci bus device number corresponds to the bus number, although I'm not having any luck finding them. 8( I'll keep working on this one; things will go a lot faster if I can get my hands on a system that misbehaves in a corresponding fashion. Thanks for the report; keep your eyes out for commits to the PCI code that mention this problem. If you do try again, please let me know how you go. If you're motivated to get involved with the code, I'd be more than happy to point you at a few things worth checking out. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-PCI Bridge Problems
I cvsuped current ~2000/12/11 @ ~ 22:00, the previous version was from around 2000/12/07. Before the update my Dual intel nic was happy post update the nic isn't even probed. attached is a pciconf -v -l from before and after as well as a a boot -v from after. If you need more info let me know and I'll go back to the 2000/12/11 kernel. Actually, I take some of what I said back. pcib1@pci0:13:0: class=0x060400 card=0x00dc chip=0x00241011 rev=0x03 hdr=0x01 vendor = 'Digital Equipment Corporation' device = 'DC21151/2 PCI-PCI Bridge' class= bridge subclass = PCI-PCI ... pcib1: PCI-PCI bridge at device 13.0 on pci0 pcib1: secondary bus 6 pcib1: subordinate bus 6 pcib1: I/O decode0x6-0x60fff pcib1: memory decode 0x0-0xf pcib1: prefetched decode 0x0-0xf pci1: physical bus=6 pci1: PCI bus on pcib1 There are bugs in the code you're running that I fixed tonight, but even so the decode registers there look *totally* wrong. Please cvsup and try again; I'm just about to commit some patches to the bridge code that should at least get that part right, then we'll see what's still going on. Sorry about this. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB modem?
Is it a case of being in the usbdevs list _and_ supporting those specs? Or just following the specs? I believe that being listed in usbdevs isn't a requirement, but I'm not positive. I also haven't had any look getting the thing to work dynamically loading the various modules involved. It is detected as a generic device: ugen0: Siemens AG Vox Chicago 390 ISDN, rev 1.10/1.00, addr 2 I will try to build a kernel with the umodem device in it, see if that makes a difference -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/usr/local vs. /usr/pkg
Andreas Klemm [EMAIL PROTECTED] types: On Mon, Dec 11, 2000 at 12:37:54AM -0500, David Gilbert wrote: ... but /usr/pkg supplanting /usr/local is one of the things that I like about NetBSD. /usr/pkg sounds a little bit odd ... ( at least for my ears). Why not choose what Solaris uses (/opt) ? I'd prefer /usr/opt. However, the reason not use either one is *because* Solaris uses them. See below. It would be an advantage, when designing filesystem size of your OS, that now you would have two completely separate paths /usr and /opt. But it also means you either have another file system where the OS is going to install things, or you have to make (in your words) too large a root file system. Installing ports in /usr means, having a too large /usr or to mount a new filsystem under /usr (/usr/local). Mounting an fs under a mounted fs I dislike much ... I take it you mean "Mounting an fs under a mounted fs other than root ...". But how do you decide what's "too large"? From what I can tell, best practice for first installs these days is to create two very large file systems. Everything installed from the distribution media (or sources) goes on /, and everything else goes in /home. If there isn't going to be anything saved locally, you ignore /home. I would claim that /opt is as bad as /usr/local, for the same reason. It has a history that predates BSDs usage of it for anything, and FreeBSD using it will cause problems for people who think that historical usage is different from installing software that comes with (or through) the OS distribution. My choice (/usr/opt) is bad for the same reason. I don't think /usr/pkg has any use prior to NetBSD using it for installed ports/packages, so it doesn't have that problem. Whether it goes on / or /usr is actually a minor issue. I want packages installed on /usr. If the standard winds up being /opt, I'll just symlink /opt to /usr/opt, and forget it. Likewise, if the standard is /usr/opt, you can symlink /usr/opt to your file system on /opt, and forget it. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB modem?
Whether a device is recognized by a driver depends on one thing only: the probe routine in the driver. It either has to conform to the specs and this device obviously doesn't, or it has to be supported by the driver and therefore the IDs of the device need to be known. The entries in usbdevs* are simply converted to a list of device names plus defines for the use of drivers, to make things simpler. Nick On Tue, 12 Dec 2000, Mark Huizer wrote: Is it a case of being in the usbdevs list _and_ supporting those specs? Or just following the specs? I believe that being listed in usbdevs isn't a requirement, but I'm not positive. I also haven't had any look getting the thing to work dynamically loading the various modules involved. It is detected as a generic device: ugen0: Siemens AG Vox Chicago 390 ISDN, rev 1.10/1.00, addr 2 I will try to build a kernel with the umodem device in it, see if that makes a difference -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Qube Software, Ltd. Private: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-PCI Bridge Problems
On Tue, 12 Dec 2000 05:02:59 -0800, Mike Smith [EMAIL PROTECTED] said: I'll keep working on this one; things will go a lot faster if I can get my hands on a system that misbehaves in a corresponding fashion. You're welcome to come to Iowa and use mine. I'll even put you up. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA [EMAIL PROTECTED] [EMAIL PROTECTED] EDUCATION, n. That which discloses to the wise and disguises from the foolish their lack of understanding. -- Ambrose Bierce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Confusing error messages from shell image activation
David O'Brien writes: On Mon, Dec 11, 2000 at 02:35:43PM -0500, Richard J Kuhns wrote: /usr/libexec/ld-elf.so.1: Shared object "libstdc++.so.2" not found /prog/applix/axdata/axmain: Operation timed out Blah. :-( Applixware depends on the compat3x distribution it seems. Can you install compat3x and see if it now runs? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX Yes, it now runs. So it looks like we have the following scenario: 1. Applixware v5.0 depends on the compat3x distribution, so it won't run on an out-of-the-box FreeBSD 4.2 system. I hadn't noticed that before because I originally installed it on a machine that went through a phase running 3.x, so the older libraries were still there. 2. Applixware v5.0 can be installed anywhere you like as long as you use the package, but you have to manually edit a shell script. Eg, PREFIX=/opt pkg_add -p $PREFIX applix-5.0.tgz Then edit $PREFIX/bin/applix and make sure APPLIX_HOME is set to $PREFIX/applix. By the way, v5 seems to be much more responsive than v4. Purely subjective, of course, but I've had a couple of comments on it. -- Richard Kuhns [EMAIL PROTECTED] PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Roadx319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Giant pb in very recent current?
On Tue, Dec 12, 2000 at 03:39:31PM +0100, Ollivier Robert wrote:
I just upgraded my laptop to yesterday's CURRENT and after a few minutes
(without noticable activity), I get a panic:
WARNING: / was not properly dismounted
panic: mutex Giant owned at ../../kern/kern_intr.c:238
panic: from debugger
You are using logo_saver, are you? Then it's a known issue, I reported it and
am still trying to pinpoint where the problem is. In the meantime, you can
either use a different screensaver, or use vidcontrol -t off.
Is that an IBM Thinkpad by any chance? That would support the idea that we have
a faulty BIOS...
Debugger("panic")
Stopped at Debugger+0x44: pushl %ebp
db trace
Debugger()
panic() at panic+0x70
sithd_loop(0) at sithd_loop+0xe5
--
Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED]
FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #6: Thu Aug 10 17:36:11 CEST 2000
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Give a man a fish and you feed him for a day;
teach him to use the Net and he won't bother you for weeks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Giant pb in very recent current?
According to Andrea Campi: You are using logo_saver, are you? Then it's a known issue, I reported it and am still trying to pinpoint where the problem is. In the meantime, you can either use a different screensaver, or use vidcontrol -t off. Good catch. I'll remove it (I'm always within X anyway). Thanks. Is that an IBM Thinkpad by any chance? That would support the idea that we have a faulty BIOS... Nope, Sony VAIO Z505SX. -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #6: Thu Aug 10 17:36:11 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Confusing error messages from shell image activation
On Tue, Dec 12, 2000 at 10:21:49AM -0500, Richard J Kuhns wrote: 2. Applixware v5.0 can be installed anywhere you like as long as you use the package, but you have to manually edit a shell script. Eg, It is probably too late to fix this, but the script should use this: if ! PREFIX=$(expr $0 : "\(/.*\)/bin/$(basename $0)\$"); then echo "$0: Cannot determine the PREFIX" 2 exit 1 fi (or maybe only do this if PREFIX isn't in the env) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: linprocfs temporarily off the air
Linprocfs has been disconnected from the build, and will remain so for a few days until I have time to fix and test it against Kirk's struct proc changes. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: console freeze
On 12-Dec-00 Nicolas Souchu wrote: Hi there, I did browse the lists but found nothing about my problem. Compiling GENERIC of 5.0 works correctly but once I remove most of uneeded hardware, the console/kbd freeze. I join the MACHINE file and the output. I even tried to change the graphic card to a PCI S3, same. I can get the getty on the serial line, so I tried vidcontrol -i on it. It reports stupid info. Is there something I can try? You haven't setup device hints. You can either statically compile them into your kernel or copy GENERIC.hints to /boot/device.hints and edit it appropriately. Nicholas -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping issues with groff(1)
Ruslan Ermilov wrote: Let me rephrase the question: Did you modify the manpages to get it to work with the new groff(1) or is the new groff(1) backward compatible with the old groff(1)? The new groff(1) is not always backwards compatible. Ok, thanks. That's all I wanted to hear. OK, I will augment the USRDIRS then, add the groff to bootstrap-tools, and leave the better (if one exists) implementation to someone else. Works for me. thanks, -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
A Christmas present from The DJ Agency KlubDJ
Hi, KlubDJ still have DJ's available across the country for the festive season! We even have a few slots left for the much requested Producers, Remixes and DJ's, LUMINA... Please contact us for more details preferably by email for initial enquiries [EMAIL PROTECTED] Happy Christmas and Mental New Year From all at KlubDJ w: www.klubdj.co.uk e: [EMAIL PROTECTED] t: 07092 171780 f: 07092 171790 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel target breaks on pcivar.h
In message [EMAIL PROTECTED] Sheldon Hearn writes: : Anyone else seeing this for the last two days in the buildkernel target? : : I see annoying breakage when compiling with -j, are you using it? : : No sir. Mike did move this file recently... Maybe we need some hacks for it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel target breaks on pcivar.h
Warner Losh writes: : In message [EMAIL PROTECTED] Sheldon Hearn writes: : : Anyone else seeing this for the last two days in the buildkernel target? : : : : I see annoying breakage when compiling with -j, are you using it? : : : : No sir. : : Mike did move this file recently... Maybe we need some hacks for it. I just tried it here and it seemed to work... I also built a kernel last night too. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kororin
âÁÙ` ´ÏÔTCgݯÁ¿áÁ½B http://216.101.214.74/1/ ³¿æA éæñB ¶áAܽË`B ¿ãñ¿ãñ¿áñæè To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PAM issues with login.
I previously posted this to stable, but received no response. Has anyone seen this? After my latest make world, I find I am now experiencing some PAM error when I log in: Dec 8 10:22:33 bsd login: auth_pam: Module is unknown Dec 8 16:14:17 bsd login: unable to dlopen(/lib/security/pam_deny.so) Dec 8 16:14:17 bsd login: [dlerror: Shared object "libc.so.6" not found] Dec 8 16:14:17 bsd login: adding faulty module: /lib/security/pam_deny.so Dec 8 16:14:17 bsd login: auth_pam: Module is unknown Dec 8 16:14:26 bsd su: gross to root on /dev/ttyp0 Dec 8 16:16:28 bsd login: unable to dlopen(/lib/security/pam_deny.so) Dec 8 16:16:28 bsd login: [dlerror: Shared object "libc.so.6" not found] Dec 8 16:16:28 bsd login: adding faulty module: /lib/security/pam_deny.so Dec 8 16:16:28 bsd login: auth_pam: Module is unknown 102 gross@bsd:/usr/home/gross% Is there a trick I need to know to get rid of these PAM errors? The login is able to proceed, but it is messy. Regards, Glen M. Gross Unix Technical Support Specialist Symark Software 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 http://www.symark.com [EMAIL PROTECTED] Main: 800-234-9072 or 818-865-6100 Main fax: 818-889-1894 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message Prev by Date: RE: Lost connection if another client connect to the VNC server Next by Date: Re: Intel PRO/100 (i82557) Server Adapter not seen by fxp. Prev by thread: RE: Lost connection if another client connect to the VNC server Next by thread: problems configuring cardbus card Index(es): Date Thread Glen M. Gross Unix Technical Support Specialist Symark Software 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 http://www.symark.com [EMAIL PROTECTED] Main: 800-234-9072 or 818-865-6100 Main fax: 818-889-1894 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping issues with groff(1)
On Tue, Dec 12, 2000 at 10:23:44AM +0200, Ruslan Ermilov wrote: OK, I will augment the USRDIRS then, add the groff to bootstrap-tools, and leave the better (if one exists) implementation to someone else. Why does groff need to be a bootstrap-tool? Its not like we need to build manpages that early in the build. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Applix problems (Was: /usr/local abuse)
On Mon, Dec 11, 2000 at 05:45:07PM -0600, Mike Meyer wrote: Others have noted that the script it installs in $(PREFIX)/bin/applix has /usr/local wired into it, though. Yes, I will bring that up tomarrow with the BSDi developer putting together the next revision of it. Maybe I should have mentioned I work for BSDi and thus can possibly make suggestions to over come issues. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM issues with login.
On Tue, Dec 12, 2000 at 11:56:03AM -0800, Glen Gross wrote: I previously posted this to stable, but received no response. Has anyone seen this? After my latest make world, I find I am now experiencing some PAM error when I log in: Dec 8 10:22:33 bsd login: auth_pam: Module is unknown Dec 8 16:14:17 bsd login: unable to dlopen(/lib/security/pam_deny.so) Dec 8 16:14:17 bsd login: [dlerror: Shared object "libc.so.6" not found] ^^^ Wow. How does *that* come in here? Are we @ version 6 already? Dec 8 16:14:17 bsd login: adding faulty module: /lib/security/pam_deny.so Dec 8 16:14:17 bsd login: auth_pam: Module is unknown Dec 8 16:14:26 bsd su: gross to root on /dev/ttyp0 Dec 8 16:16:28 bsd login: unable to dlopen(/lib/security/pam_deny.so) Dec 8 16:16:28 bsd login: [dlerror: Shared object "libc.so.6" not found] Dec 8 16:16:28 bsd login: adding faulty module: /lib/security/pam_deny.so Dec 8 16:16:28 bsd login: auth_pam: Module is unknown 102 gross@bsd:/usr/home/gross% Also, I assume this is -STABLE, right? Is your pam.conf up to date and set up correctly? -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM issues with login.
On Tue, Dec 12, 2000 at 11:56:03AM -0800, Glen Gross wrote: I previously posted this to stable, but received no response. Has anyone seen this? After my latest make world, I find I am now experiencing some PAM error when I log in: Dec 8 10:22:33 bsd login: auth_pam: Module is unknown Dec 8 16:14:17 bsd login: unable to dlopen(/lib/security/pam_deny.so) Dec 8 16:14:17 bsd login: [dlerror: Shared object "libc.so.6" not found] Dec 8 16:14:17 bsd login: adding faulty module: /lib/security/pam_deny.so Are you sure this is not a Linux system? FreeBSD doesn't have /lib/security/pam_deny.so nor libc.so.6. -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping issues with groff(1)
David O'Brien wrote: On Tue, Dec 12, 2000 at 10:23:44AM +0200, Ruslan Ermilov wrote: OK, I will augment the USRDIRS then, add the groff to bootstrap-tools, and leave the better (if one exists) implementation to someone else. Why does groff need to be a bootstrap-tool? Its not like we need to build manpages that early in the build. There's no other place. Only bootstrap tools, cross tools and build tools are build in such a way that they can run on the build machine. You can't build it later than cross-tools. It's not a cross tool itself and definitely not a build tool. It must be a bootstrap tool then. -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bug Fix for SYSV semaphores.
Title: Bug Fix for SYSV semaphores. I noticed that sysv semaphores initialize the otime member of the semid_ds structure to 0, but they never update it afterwards. This field is supposed to be the last operation time. ie the last time a semctl was done. In UNIX Network Programming, Stevens suggests using this variable to detect races between multiple processes creating/accessing a sysv semaphore. Anyway, I looked through the code and came up with the following trivial patch. Could some one review it and perhaps commit it? This patch was made against current, but I noticed the bug is there in 4.1.1 and most likely everything before that. Thanks, Jeff (Pardon the revision numbers, they are from my own repository) *** sysv_sem.c 2000/09/15 11:11:48 1.1.1.1 --- sysv_sem.c 2000/12/12 23:44:28 *** *** 543,548 --- 543,550 return(EINVAL); } + semaptr-sem_otime = time_second; + if (eval == 0) p-p_retval[0] = rval; return(eval);
Re: Bug Fix for SYSV semaphores.
On 2000-Dec-12 14:45:37 -0800, Jeff Roberson [EMAIL PROTECTED] wrote: I noticed that sysv semaphores initialize the otime member of the semid_ds structure to 0, but they never update it afterwards. This field is supposed to be the last operation time. ie the last time a semctl was done. See kern/12014, which fixes this and a variety of other bugs. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: PAM issues with login.
I am running the linux emulator, if that's what you mean. But the system is FreeBSD. Script started on Tue Dec 12 15:58:32 2000 101 [1mgross[m@[1mbsd[m:/usr/home/gross%uname -a FreeBSD bsd.xinetd.com 4.1-RC2 FreeBSD 4.1-RC2 #5: Thu Dec 7 16:27:45 PST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/clonix i386 102 [1mgross[m@[1mbsd[m:/usr/home/gross%file /bin/login /bin/login: can't stat `/bin/login': No such file or directory. 103 [1mgross[m@[1mbsd[m:/usr/home/gross%which li[Kogin login: shell built-in command. 104 [1mgross[m@[1mbsd[m:/usr/home/gross%tail /var/adm/messages Dec 12 11:34:53 bsd login: adding faulty module: /lib/security/pam_deny.so Dec 12 11:34:53 bsd login: auth_pam: Module is unknown Dec 12 11:35:16 bsd login: unable to dlopen(/lib/security/pam_deny.so) Dec 12 11:35:16 bsd login: [dlerror: Shared object "libc.so.6" not found] Dec 12 11:35:16 bsd login: adding faulty module: /lib/security/pam_deny.so Dec 12 11:35:16 bsd login: auth_pam: Module is unknown Dec 12 15:58:28 bsd login: unable to dlopen(/lib/security/pam_deny.so) Dec 12 15:58:28 bsd login: [dlerror: Shared object "libc.so.6" not found] Dec 12 15:58:28 bsd login: adding faulty module: /lib/security/pam_deny.so Dec 12 15:58:28 bsd login: auth_pam: Module is unknown 105 [1mgross[m@[1mbsd[m:/usr/home/gross%exit[K[K[K[Kexit exit Script done on Tue Dec 12 15:59:01 2000 On Tuesday, December 12, 2000 1:02 PM, Chris Faulhaber [SMTP:[EMAIL PROTECTED]] wrote: On Tue, Dec 12, 2000 at 11:56:03AM -0800, Glen Gross wrote: I previously posted this to stable, but received no response. Has anyone seen this? After my latest make world, I find I am now experiencing some PAM error when I log in: Dec 8 10:22:33 bsd login: auth_pam: Module is unknown Dec 8 16:14:17 bsd login: unable to dlopen(/lib/security/pam_deny.so) Dec 8 16:14:17 bsd login: [dlerror: Shared object "libc.so.6" not found] Dec 8 16:14:17 bsd login: adding faulty module: /lib/security/pam_deny.so Are you sure this is not a Linux system? FreeBSD doesn't have /lib/security/pam_deny.so nor libc.so.6. -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org Glen M. Gross Unix Technical Support Specialist Symark Software 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 http://www.symark.com [EMAIL PROTECTED] Main: 800-234-9072 or 818-865-6100 Main fax: 818-889-1894 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
World almost fixed..
World should now be fixed after the kinfo_proc change, except for one needed
patch for ipfilter that can be found at
http://www.FreeBSD.org/~jhb/patches/ipfilter.patch. Since it's contrib'd code,
I dno't want to commit and bring the file of the vendor branch and incur all
the wrath that comes along with that. In the meantime, this patch should get
you through world now.
Index: sock.c
===
RCS file: /host/ares/usr/home/ncvs/src/contrib/ipfilter/ipsend/sock.c,v
retrieving revision 1.3
diff -u -r1.3 sock.c
--- sock.c 2000/02/10 03:17:46 1.3
+++ sock.c 2000/12/12 23:57:52
@@ -283,10 +283,10 @@
return NULL;
fd = (struct filedesc *)malloc(sizeof(*fd));
- if (KMCPY(fd, p-kp_proc.p_fd, sizeof(*fd)) == -1)
+ if (KMCPY(fd, p-ki_fd, sizeof(*fd)) == -1)
{
fprintf(stderr, "read(%#lx,%#lx) failed\n",
- (u_long)p, (u_long)p-kp_proc.p_fd);
+ (u_long)p, (u_long)p-ki_fd);
return NULL;
}
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PAM issues with login.
I got a similar error yesterday with current, linux-communicator and a new kde2. I had to execute linux netscape from a text screen with -display. I would get the libc.so.6 error from kde. It was really strange but updating pam.conf, fixed it for me. ed Glen Gross wrote: I am running the linux emulator, if that's what you mean. But the system is FreeBSD. Script started on Tue Dec 12 15:58:32 2000 101 [1mgross[m@[1mbsd[m:/usr/home/gross%uname -a FreeBSD bsd.xinetd.com 4.1-RC2 FreeBSD 4.1-RC2 #5: Thu Dec 7 16:27:45 PST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/clonix i386 102 [1mgross[m@[1mbsd[m:/usr/home/gross%file /bin/login /bin/login: can't stat `/bin/login': No such file or directory. 103 [1mgross[m@[1mbsd[m:/usr/home/gross%which li[Kogin login: shell built-in command. 104 [1mgross[m@[1mbsd[m:/usr/home/gross%tail /var/adm/messages Dec 12 11:34:53 bsd login: adding faulty module: /lib/security/pam_deny.so Dec 12 11:34:53 bsd login: auth_pam: Module is unknown Dec 12 11:35:16 bsd login: unable to dlopen(/lib/security/pam_deny.so) Dec 12 11:35:16 bsd login: [dlerror: Shared object "libc.so.6" not found] Dec 12 11:35:16 bsd login: adding faulty module: /lib/security/pam_deny.so Dec 12 11:35:16 bsd login: auth_pam: Module is unknown Dec 12 15:58:28 bsd login: unable to dlopen(/lib/security/pam_deny.so) Dec 12 15:58:28 bsd login: [dlerror: Shared object "libc.so.6" not found] Dec 12 15:58:28 bsd login: adding faulty module: /lib/security/pam_deny.so Dec 12 15:58:28 bsd login: auth_pam: Module is unknown 105 [1mgross[m@[1mbsd[m:/usr/home/gross%exit[K[K[K[Kexit exit Script done on Tue Dec 12 15:59:01 2000 On Tuesday, December 12, 2000 1:02 PM, Chris Faulhaber [SMTP:[EMAIL PROTECTED]] wrote: On Tue, Dec 12, 2000 at 11:56:03AM -0800, Glen Gross wrote: I previously posted this to stable, but received no response. Has anyone seen this? After my latest make world, I find I am now experiencing some PAM error when I log in: Dec 8 10:22:33 bsd login: auth_pam: Module is unknown Dec 8 16:14:17 bsd login: unable to dlopen(/lib/security/pam_deny.so) Dec 8 16:14:17 bsd login: [dlerror: Shared object "libc.so.6" not found] Dec 8 16:14:17 bsd login: adding faulty module: /lib/security/pam_deny.so Are you sure this is not a Linux system? FreeBSD doesn't have /lib/security/pam_deny.so nor libc.so.6. -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org Glen M. Gross Unix Technical Support Specialist Symark Software 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 http://www.symark.com [EMAIL PROTECTED] Main: 800-234-9072 or 818-865-6100 Main fax: 818-889-1894 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
newpcm/kobj
in the near future, i intend to commit my kobjified newpcm. this gives us several benefits, including: * easier extensibility- new optional methods can be added to ac97/mixer/channel classes without having to fixup every driver. * forward compatibility for drivers, provided no new mandatory methods are added. however, all drivers not in the tree at this time will need to be updated. i hope to mfc to -stable in approximately one month, along with the kobj system. newbus in -stable will not be kobjified. -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping issues with groff(1)
Marcel Moolenaar wrote: Why does groff need to be a bootstrap-tool? Its not like we need to build manpages that early in the build. There's no other place. Only bootstrap tools, cross tools and build tools are build in such a way that they can run on the build machine. You can't build it later than cross-tools. It's not a cross tool itself and definitely not a build tool. It must be a bootstrap tool then. It is used to build the man pages, isn't it? Why, then, it is not a build tool? -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "The bronze landed last, which canceled that method of impartial choice." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping issues with groff(1)
"Daniel C. Sobral" wrote: There's no other place. Only bootstrap tools, cross tools and build tools are build in such a way that they can run on the build machine. You can't build it later than cross-tools. It's not a cross tool itself and definitely not a build tool. It must be a bootstrap tool then. It is used to build the man pages, isn't it? Why, then, it is not a build tool? Build tools are utilities created only for the purpose of building "the software". Build tools are never installed on the system. Put differently; build tools don't have makefiles of their own. groff(1) definitely isn't a build tool, because it has it's own makefiles and is installed on the system. There's an implementation difference as well. Bootstrap tools are built in seperate object directories to avoid problems with the actual built of the tool (as part of stage 4 of make world). Build tools are always built in the "normal" or actual object directory. Also, bootstrap tools are installed under the object tree. Build tools are not installed; they run from the object directory. -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
