FreeBSD installation and USB follow-up
Hi: Thanks for your reply. I know that FreeBSD developers are busy people and give up precious time for FreeBSD development. I respect that a great deal, and appreciate the developers taking the time to help. I also understand that the time constraints require that users spend some time looking into problems on their own. I produced a complete system configuration that may help to track down what is going on with my Acer Aspire USB keyboard (see below). I may not be the best qualified to render an opinion, but I have noticed that my keyboard uses IRQ 1 and 12, and I/O ports: 0060h and 0064h, while FreeBSD reserves IRQ 12 and I/O port 0060 fro the PS/2 mouse. I'm not sure exactly how devices map to resources. Is there a coupling of IRQ and I/O port? If so, is my system using (IRQ,I/O port) pairs: (1,0060h) and (IRQ 12,0064h)? Since FeeBSD uses (12,0060h) for the PS/2 mouse, there could be a mismatch. Another possible conflict may be on IRQ 11. FreeBSD assigns this to the Adaptec SCSI controller while my system uses this for the PCI to USB Universal Host Controller. As described in the HARDWARE.TXT file in the installation (snapshot) directory, userconfig is supposed to provide an opportunity to clear up any such conflicts but my system is unusable as soon as the kernel is booted (which occurs just before userconfig). However, the boot floppy kernel is GENERIC, so perhaps it is subsceptable to a device conflict before such a conflict can be resolved by the user. One other clue: the floppy drive light remains on while the system is unusable. Could this indicate a system problem instead of a keyboard problem? SYSTEM SUMMARY ** Windows version: 4.10.1998 Computer Name: Acer System BUS Type: ISA BIOS Name: Acer BIOS Date: 04/01/98 BIOS Version: ACR8EP6C 450V3.2 Machine Type: IBM PC/AT Processor Vendor: GenuineIntel Processor Type: Pentium® II Processor Math C0-processor: Not Present Registered Owner: Registered Company: ** IRQ SUMMARY ** IRQ Usage Summary: 00 System timer 01 Standard 101/102-Key or Microsoft Natural Keyboard 02 Programmable interrupt controller 03 Communications Port (COM2) 04 Communications Port (COM1) 05 ESS Solo-1 SoundBlaster Compatible (WDM) 05 ACPI IRQ Holder for PCI IRQ Steering 05 ESS Solo-1 PCI AudioDrive (WDM) 06 Standard Floppy Disk Controller 07 Printer Port (LPT1) 08 System CMOS/real time clock 09 SCI IRQ used by ACPI bus 09 ACPI IRQ Holder for PCI IRQ Steering 09 Acer PCI Modem Enumerator 09 Acer 56K DataFax PCI Modem 09 XPERT 98 (English) 10 3com Fast EtherLink XL 10.100Mb TX Ethernet NIC (3C905B-TX) 10 ACPI IRQ Holder for PCI IRQ Steering 11 ACPI IRQ Holder for PCI IRQ Steering 11 Intel 82371AB/EB PCI to USB Universal Host Controller 12 Standard 101/102-Key or Microsoft Natural Keyboard 13 Numeric data processor 14 Primary IDE controller (dual fifo) 14 Intel 82371AB/EB PCI Bus Master IDE Controller 15 Intel 82371AB/EB PCI Bus Master IDE Controller 15 Secondary IDE Controller (dual fifo) * IO PORT SUMMARY * I/O Port Usage Summary: h-000Fh Direct memory access controller 0020h-0021h Programmable interrupt controller 0040h-0043h System timer 0060h-0060h Standard 101/102-Key or Microsoft Natural Keyboard 0061h-0061h System speaker 0064h-0064h Standard 101/102-Key or Microsoft Natural Keyboard 0070h-0073h System CMOS/real time clock 0081h-008Fh Direct memory access controller 00A0h-00A1h Programmable interrupt controller 00C0h-00DFh Direct memory access controller 00F0h-00FFh Numeric data processor 0170h-0177h Secondary IDE controller (dual fifo) 0170h-0177h Intel 82371AB/EB PCI Bus Master IDE Controller 01F0h-01F7h - Intel 82371AB/EB PCI Bus Master IDE Controller 01F0h-01F7h - Primary IDE controller (dual fifo) 0200h-0203h Gameport Joystick 0220h-022Fh - ESS Solo-1 SoundBlaster Compatible (WDM) 0295h-0296h Motherboard resources 02F8h-02FFh Communications Port (COM2) 0330h-0331h - ESS Solo-1 PCI SoundBlaster Compatible (WDM) 0376h-0376h - Intel 82371AB/EB PCI Bus Master IDE Controller 0376h-0376h - Secondary IDE controller (dual fifo) 0378h-037Fh Printer Port (LPT1) 0388h-038Bh - ESS Solo-1 PCI SoundBlaster Compatible (WDM) 03B0h-03BBh XPERT 98 (English) 03C0h-03DFh - XPERT 98 (English) 03E8h-03EFh Acer 56K DataFax PCI Modem 03F0h-03F5h Standard Floppy Disk Controller 03F6h-03F6h - Intel 82371AB/EB PCI Bus Master IDE Controller 03F6h-03F6h Primary IDE controller (dual fifo) 03F7h-03F7h - Standard Floppy Disk Controller 03F8h-03FFh Communications Port (COM1) 0440h-047Fh - Motherboard resources 04D0h-04D1h - Motherboard resources 0800h-080Fh - Motherboard resources 0CF8h-0CFFh PCI bus 7000h-7FFFh Intel 82443BX Pentium(r) II Processor to AGP controller 7000h-70FFh - XPERT 98 (English) 8000h-807Fh 3Com Fast EtherLink XL 10/100Mb TX Ethernet NIC (3C905B-TX) 80C0h-8
Re: current.freebsd.org (FTP)
On Tue, Feb 29, 2000 at 12:58:26PM -0800, Jordan K. Hubbard wrote: > I'm still here for another hour, dammit. :-) > > I'm also going to be reachable for most of that week since Holland > does have Internet connections now, you know. They got it along with > electric lighting and running water at least several years ago. :) Yes we do, unlike the US from time to time. Remember FreeBSD Con? We lost water for 2 days in a row. And at least _we_ discovered that it is good idea to have a lot of your electricity undergroud so a small wind will not render whole neighboorhoods without power ;-))) -Guido To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Donn Miller <[EMAIL PROTECTED]> wrote: > Thomas Graichen wrote: >> >> one other thing: does anyone have the XFree86 pre 4.0 snapshot running >> with moused and SysMouse ? - it works fine for me without moused and the >> moues directly under X - but with moused and "SysMouse" "/dev/sysmouse" >> nothing happens when moving the mouse - any further XF86Config magic >> required for this ? - does anyone have an hint here ? (btw. - all this >> on a fresh 4.0-CURRENT box) > Did you select the "mouse systems" protocol in the xf86config menu? > Also, does your mouse work under moused at the console? You should > leave moused_type="auto" as the default. > Basically, does your mouse work under syscons? That's the main thing. yes - "Auto" did it - looks like "SysMouse" as config entry in the XF86Config is broken - anyone here from the XFree86 devel people to take a look at this ? t -- [EMAIL PROTECTED] innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Cliff Rowley <[EMAIL PROTECTED]> wrote: > Greetings, I'm just wondering if anyone has encountered the following, and > what solutions you may have come up with / ideas you may have. > This may not be a FreeBSD problem, since I am using the latest XFree86 > pre-4.0 snapshot. > First: > Almost every time I load a page in Netscape (latest port), I get the > message: > "XFree86-BigFont extension: shmat() failed, size = 4096, errno = 24" with those options the error is gone for me - i think the relevant one is the SHMALL (the others are for postgres) - i found this out by simply reading the piece of source of XFree86 which emits this error and there is written that SHMALL should be at least 48M - so 16k pages = 64M should be fine options SHMMAXPGS=4096 options SHMALL=16384 options SHMSEG=16 options SEMMNI=32 options SEMMNS=128 t -- [EMAIL PROTECTED] innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: things I noticed w/ 4.0
Joseph Jacobson wrote: > > Kernel option VESA fails (see dmesg below). Is this a problem with my > graphics card? Are you, by any chance, both compiling in VESA _and_ loading it with loader? > Kernel option PNPBIOS causes the mouse to stop working. A pointer is > visible at boot (w/ moused) until the mouse is moved, then it disappears > forever. Maybe I'm misunderstanding what PNPBIOS does Weird. Are you sure your BIOS is set to PnP OS = No? > 'halt -p' still doesn't turn my computer off :). Haven't tested any other > functionality of apm though. I usually disable apm in the bios since > it makes turning the system power off w/ the button on the case a problem > under FreeBSD. Any ideas? Yep. Try turning apm in BIOS on. :-) > /usr/games/phantasia doesn't like the return key. You have to use > - (w/ TERMs xterm and cons25). /usr/games/teachgammon doesn't > always clear the screen of previous text completely. M... I seem to recall someone were tweaking phantasia lately... -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: extern variables in shared libraries broken (ld.so or mmap bug)
In <[EMAIL PROTECTED]>, Bruce Evans wrote: > On Fri, 25 Feb 2000, Martin Cracauer wrote: > > It is possible that we indroduced the bug by our profiling changes? > > The line in i386.c that generates the code in question is from > > revision 1.5, which is the profiling delta from the original gcc. In > > that case we can't count on a new gas fixing it for us. > > Reverting to the FSF version of i386.c didn't fix the problem. I build libc with an unchanged gcc-2.95.2 (except assert.c, which needs our compiler) and it has the problem as well. What do you think, is this a showstopper for 4.0? Yes, me thinks. Martin -- % Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: linux-acrobat-4.05 only works with linux-netscape!
On 01-Mar-00 F. Heinrichmeyer wrote: > I had until now no success in using the new linux-acrobat-4.05 from bash > or from my windowmanager menu. But it works fine when called from > linux-netscape! Perhaps this happens because the 'acroread4' program is a shell script with bash'ism's.. It fails normally because the shell is /bin/sh but when run from Netscape it finds /compat/linux/bin/sh (which is bash) and works.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
> In any case, one major offender is imlib. Since I've recently gone
> Gnome, I've had to turn off imlib's "MIT-SHM shared memory" option
> or things would go bad after a few minutes or hours of use.
That explains the errors when running xchat, but that doesnt explain
Netscape ;)
The annoying thing about this is that if a program decides to die because
of this error, it seems I've got a 50/50 chance that it's taken out for
good. I have to reboot to reclaim memory >:(
It'd be nice if we had a utility that could clean out and reclaim the
shared memory in 1 swoop. Then we'd be able to shut down XFree86 (and
obviously any other apps using shared memory), and get on with life :)
(anyone listening?)
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: linux-acrobat-4.05 only works with linux-netscape!
It also helps to take all the plugins away! -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD installation and USB follow-up
> that the time constraints require that users spend some time looking into > problems on their own. It's good to see that you are willing to help. :-) The output below is excellent, and should cover most hardware related questions. > One other clue: the floppy drive light remains on while the system is > unusable. Could this indicate a system problem instead of a keyboard > problem? This might indicate that the floppy 'virtualisation' by the BIOS isn't what FreeBSD expects it to be. Hm, I'll have a look at this this evening. Nick > SYSTEM SUMMARY ** > Windows version: 4.10.1998 > Computer Name: Acer > System BUS Type: ISA > BIOS Name: Acer > BIOS Date: 04/01/98 > BIOS Version: ACR8EP6C 450V3.2 > Machine Type: IBM PC/AT > Processor Vendor: GenuineIntel > Processor Type: Pentium® II Processor > Math C0-processor: Not Present > Registered Owner: > Registered Company: > > ** IRQ SUMMARY ** > > IRQ Usage Summary: > 00 System timer > 01 Standard 101/102-Key or Microsoft Natural Keyboard > 02 Programmable interrupt controller > 03 Communications Port (COM2) > 04 Communications Port (COM1) > 05 ESS Solo-1 SoundBlaster Compatible (WDM) > 05 ACPI IRQ Holder for PCI IRQ Steering > 05 ESS Solo-1 PCI AudioDrive (WDM) > 06 Standard Floppy Disk Controller > 07 Printer Port (LPT1) > 08 System CMOS/real time clock > 09 SCI IRQ used by ACPI bus > 09 ACPI IRQ Holder for PCI IRQ Steering > 09 Acer PCI Modem Enumerator > 09 Acer 56K DataFax PCI Modem > 09 XPERT 98 (English) > 10 3com Fast EtherLink XL 10.100Mb TX Ethernet NIC (3C905B-TX) > 10 ACPI IRQ Holder for PCI IRQ Steering > 11 ACPI IRQ Holder for PCI IRQ Steering > 11 Intel 82371AB/EB PCI to USB Universal Host Controller > 12 Standard 101/102-Key or Microsoft Natural Keyboard > 13 Numeric data processor > 14 Primary IDE controller (dual fifo) > 14 Intel 82371AB/EB PCI Bus Master IDE Controller > 15 Intel 82371AB/EB PCI Bus Master IDE Controller > 15 Secondary IDE Controller (dual fifo) > > * IO PORT SUMMARY * > > I/O Port Usage Summary: > h-000Fh Direct memory access controller > 0020h-0021h Programmable interrupt controller > 0040h-0043h System timer > 0060h-0060h Standard 101/102-Key or Microsoft Natural Keyboard > 0061h-0061h System speaker > 0064h-0064h Standard 101/102-Key or Microsoft Natural Keyboard > 0070h-0073h System CMOS/real time clock > 0081h-008Fh Direct memory access controller > 00A0h-00A1h Programmable interrupt controller > 00C0h-00DFh Direct memory access controller > 00F0h-00FFh Numeric data processor > 0170h-0177h Secondary IDE controller (dual fifo) > 0170h-0177h Intel 82371AB/EB PCI Bus Master IDE Controller > 01F0h-01F7h - Intel 82371AB/EB PCI Bus Master IDE Controller > 01F0h-01F7h - Primary IDE controller (dual fifo) > 0200h-0203h Gameport Joystick > 0220h-022Fh - ESS Solo-1 SoundBlaster Compatible (WDM) > 0295h-0296h Motherboard resources > 02F8h-02FFh Communications Port (COM2) > 0330h-0331h - ESS Solo-1 PCI SoundBlaster Compatible (WDM) > 0376h-0376h - Intel 82371AB/EB PCI Bus Master IDE Controller > 0376h-0376h - Secondary IDE controller (dual fifo) > 0378h-037Fh Printer Port (LPT1) > 0388h-038Bh - ESS Solo-1 PCI SoundBlaster Compatible (WDM) > 03B0h-03BBh XPERT 98 (English) > 03C0h-03DFh - XPERT 98 (English) > 03E8h-03EFh Acer 56K DataFax PCI Modem > 03F0h-03F5h Standard Floppy Disk Controller > 03F6h-03F6h - Intel 82371AB/EB PCI Bus Master IDE Controller > 03F6h-03F6h Primary IDE controller (dual fifo) > 03F7h-03F7h - Standard Floppy Disk Controller > 03F8h-03FFh Communications Port (COM1) > 0440h-047Fh - Motherboard resources > 04D0h-04D1h - Motherboard resources > 0800h-080Fh - Motherboard resources > 0CF8h-0CFFh PCI bus > 7000h-7FFFh Intel 82443BX Pentium(r) II Processor to AGP controller > 7000h-70FFh - XPERT 98 (English) > 8000h-807Fh 3Com Fast EtherLink XL 10/100Mb TX Ethernet NIC (3C905B-TX) > 80C0h-80FFh ESS Solo-1 PCI AudioDrive (WDM) > 8400h-840Fh - ESS Solo-1 PCI AudioDrive (WDM) > 8440h-844Fh - ESS Solo-1 PCI AudioDrive (WDM) > 8480h-8483h - ESS Solo-1 PCI AudioDrive (WDM) > 84C0h-84C3h - ESS Solo-1 PCI AudioDrive (WDM) > 8800h-881Fh - Intel 82371AB/EB PCI to USB Universal Host Controller > 8840h-884Fh - Intel 82371AB/EB PCI Bus Master IDE Controller > 8840h-8847h Primary IDE controller (dual fifo) > 8848h-884Fh - Secondary IDE controller (dual fifo) > > * UPPER MEMORY USAGE SUMMARY > > Memory Usage Summary: > > h-0009h - Motherboard resources > 000Ah-000Ah - XPERT 98 (English) > 000Bh-000Bh - XPERT 98 (English) > 000Ch-000C7FFFh - XPERT 98 (English) > 000Eh-000Fh - Motherboard resources > 0010h-00FFh - Motherboard resources > 0100h-07FFh - Motherboard resources > 8010h-80100FFFh - XPERT 98 (English) > 8010h-820Fh -
Re: pthread_{suspend,resume}_np broken?
On Tue, 29 Feb 2000, John Polstra wrote: > In article <[EMAIL PROTECTED]>, > Daniel Eischen <[EMAIL PROTECTED]> wrote: > > On Tue, 29 Feb 2000, John Polstra wrote: > > > > > Shouldn't the test against PS_SUSPENDED be "==" instead of "!="? > > > > Yes, it should be "==" instead of "!=". > > > > Go ahead and fix it if you want :-) > > Thanks. I'll ask Jordan if I may commit the fix. > > What about the other part of my question? I still don't understand > why in my test program pthread_suspend_np() isn't suspending the > thread. I think it's a separate bug from the pthread_resume_np() bug. Sorry, it was very late here and I missed that part. I see the problem. pthread_suspend_np is broke in that it only will work if the thread is running (PS_RUNNING). Your program is always trying to suspend a thread that is sleeping (PS_SLEEP_WAIT) so changing the state with PTHREAD_NEW_STATE fails. The fix isn't as easy as just correctly setting the threads state. Potentially, the suspended thread could be waiting on a mutex or condition variable and be in another queue. The correct fix is probably to save the threads old state and then set the threads state to PS_SUSPENDED. Resuming should restore the saved thread state. I'll see if I can come up with a correct fix for this. Dan Eischen [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
> options SHMMAXPGS=4096
> options SHMALL=16384
> options SHMSEG=16
> options SEMMNI=32
> options SEMMNS=128
Tried those, same error :(
_XF86BigfontQueryFont: could not attach shm segment
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: mod_ssl & current
I am seeing the same thing with a world built yesterday afternoon. I don't know if this is an issue with multiple dlopen'ed libraries or what. Here is what I believe the port is doing. During the build process, the main apache server is built. The ssl layer is created as an add-in module (.so) which I would assume is dlopen'ed. This module is linked as follows: gcc -L/usr/lib -shared -o libssl.so -lssl -lcrypto At runtine, apache tries to dlopen libssl.so. libcrypto should dlopen librsaUSA.so. Something doesn't seem to be happening correctly though. My previous test was before librsaUSA was created. Can Peter or John shed any light on possible linker or dynamic loader issues here? Jim Bloom [EMAIL PROTECTED] Kris Kennaway wrote: > > On Tue, 29 Feb 2000, Manfred Antar wrote: > > > I needed to add -lRSAglue -lrsaUSA to the SSL_LIBS= line in > > /usr/ports/www/apache13-php3/work/apache_1.3.12/src/modules/ssl/Makefile > > and install the recompiled libssl.so in /usr/local/libexec/apache. > > Works fine > > Note this is for the apache13-php3 port but I bet it will work for the >apache13-php4 port > > This may work, but I doubt this is necessary. -lRSAglue is an empty > library which only exists to keep legacy ports happy, and -lrsaUSA will be > automatically dlopen()ed if you have a recent libcrypto.so. > > As with the other guy, please make sure your libcrypto.so is up to date - > I haven't seen evidence from either of you yet that this is the case :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ntpd hanging machine
> On Mon, 28 Feb 2000, Matthew Frost wrote: > > > I'm experiencing some problems with ntpd. It would appear that a few > > (10-15) minutes after I start it, the machine crashes completely... > > > > Feb 28 14:10:02 egrorian ntpd[153]: ntpd 4.0.99b Mon Feb 28 12:12:17 GMT 2000 (1) > > Feb 28 14:10:02 egrorian ntpd[153]: using kernel phase-lock loop 2040 > > Feb 28 14:10:02 egrorian ntpd[153]: using kernel phase-lock loop 2041 > > > > And then locked solid.. > > I've been seeing the exact same behavior ever since the big ntp4 > merge. Until that point I was using the stock ntp4 from udel with no > problems. But I tried the one shipping with 4.0 and it locks up completely > (looks like a hardware lockup). The ntp4 from udel works completely > though. Odd :) Try disabling where it uses rtprio to set itself realtime and see if that "fixes" it. Peter -- Peter Dufault ([EMAIL PROTECTED]) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
On 1 Mar 2000, Thomas Graichen wrote: > > Basically, does your mouse work under syscons? That's the main thing. > > yes - "Auto" did it - looks like "SysMouse" as config entry in the > XF86Config is broken - anyone here from the XFree86 devel people > to take a look at this ? $ grep -5 -in sysmouse /etc/X11/XF86Config 208-# Identifier and driver 209- 210-Identifier "Mouse1" 211-Driver "mouse" 212-Option "Protocol""MouseSystems" 213:Option "Device" "/dev/sysmouse" 214- I'd recommend just backing up your old /etc/X11/XF86Config, and using the tty mode program xf86config to generate your config file. Or, just do as I have shown above. Apparently, they changed the format of XF86Config. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
On 1 Mar 2000, Thomas Graichen wrote: > > "XFree86-BigFont extension: shmat() failed, size = 4096, errno = 24" > > with those options the error is gone for me - i think the relevant > one is the SHMALL (the others are for postgres) - i found this out > by simply reading the piece of source of XFree86 which emits this > error and there is written that SHMALL should be at least 48M - so > 16k pages = 64M should be fine > > options SHMMAXPGS=4096 > options SHMALL=16384 > options SHMSEG=16 > options SEMMNI=32 > options SEMMNS=128 Here's what I've added to my kernel config to get rid of those errors: # Options for SHM options SHMMAXPGS=4097 options SHMSEG=128 It looks like SHMMAXPGS has to be a power of two + 1. (The original config file says options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 So, it looks like SHMMAXPGS has to be a power of two + 1. That's why I chose 4097 instead of 4096 - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
On Wed, 1 Mar 2000, Cliff Rowley wrote: > > options SHMMAXPGS=4096 > > options SHMALL=16384 > > options SHMSEG=16 > > options SEMMNI=32 > > options SEMMNS=128 > > Tried those, same error :( > > _XF86BigfontQueryFont: could not attach shm segment Try increasing SHMSEG to 128. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
> Try increasing SHMSEG to 128.
Appears to be working fine with SHMAXPGS=4097 and SHMSEG=128 - fingers
crossed ;) Thanks for your help everyone...
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: buildworld fails at ncurses
Kris Kennaway <[EMAIL PROTECTED]> writes: > You don;t have the ncurses port installed? No, I do not. It does not build. I will try doing an update (using sysinstall) to one of the latest -current snapshots and do the buildworld again from there. Roland To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cd9660 - device not configured
-current of Feb, 26th. Innocently I wanted to mount -t cd9660 /dev/acd1c /dist to grab some newer XF86 from the CD when cd9660: device not configured was thrown at me. -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
> "Nicolas" == Nicolas Souchu <[EMAIL PROTECTED]> writes: Nicolas> On Sun, Jan 30, 2000 at 02:42:39PM -0500, Brian Dean wrote: >> >> >> For what its worth, I am able to reproduce this problem on my >> system. Nicolas> Would you mind trying this patch before I send it to Jordan? I certainly don't get any "hangs" any more, but I'm still experiencing "pauses" --- short half-a-second mouse unresponsiveness when someone prints. I'm currently seeing the following on boot: ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP Probing for PnP devices on ppbus0: ppbus0: PCL,MLC,PML ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pthread_{suspend,resume}_np broken?
Daniel Eischen wrote:
>
> On Tue, 29 Feb 2000, John Polstra wrote:
>
> > In article <[EMAIL PROTECTED]>,
> > Daniel Eischen <[EMAIL PROTECTED]> wrote:
> > > On Tue, 29 Feb 2000, John Polstra wrote:
> > >
> > > > Shouldn't the test against PS_SUSPENDED be "==" instead of "!="?
> > >
> > > Yes, it should be "==" instead of "!=".
> > >
> > > Go ahead and fix it if you want :-)
> >
> > Thanks. I'll ask Jordan if I may commit the fix.
> >
> > What about the other part of my question? I still don't understand
> > why in my test program pthread_suspend_np() isn't suspending the
> > thread. I think it's a separate bug from the pthread_resume_np() bug.
>
> Sorry, it was very late here and I missed that part.
>
> I see the problem. pthread_suspend_np is broke in that it only will
> work if the thread is running (PS_RUNNING). Your program is always
> trying to suspend a thread that is sleeping (PS_SLEEP_WAIT) so changing
> the state with PTHREAD_NEW_STATE fails.
>
> The fix isn't as easy as just correctly setting the threads state.
> Potentially, the suspended thread could be waiting on a mutex or
> condition variable and be in another queue. The correct fix is
> probably to save the threads old state and then set the threads state
> to PS_SUSPENDED. Resuming should restore the saved thread state.
>
> I'll see if I can come up with a correct fix for this.
Here's a quick fix. It also includes a simple fix for pthread_kill that
src/libc_r/uthread/test/sigwait/sigwait.c will expose.
I haven't run any other regression tests. I'll do that when I get
some more time. Jason, can you also take a look at these changes and
run some tests on them?
Thanks,
Dan Eischen
[EMAIL PROTECTED]
Index: pthread_private.h
===
RCS file: /opt/b/CVS/src/lib/libc_r/uthread/pthread_private.h,v
retrieving revision 1.36
diff -c -r1.36 pthread_private.h
*** pthread_private.h 2000/01/20 21:53:58 1.36
--- pthread_private.h 2000/03/01 12:49:27
***
*** 576,581
--- 576,583
#define PTHREAD_CANCEL_NEEDED 0x0010
int cancelflags;
+ int suspended;
+
thread_continuation_t continuation;
/*
Index: uthread_cancel.c
===
RCS file: /opt/b/CVS/src/lib/libc_r/uthread/uthread_cancel.c,v
retrieving revision 1.3
diff -c -r1.3 uthread_cancel.c
*** uthread_cancel.c2000/01/19 07:04:45 1.3
--- uthread_cancel.c2000/03/01 13:44:57
***
*** 37,42
--- 37,51
pthread->cancelflags |= PTHREAD_CANCELLING;
break;
+ case PS_SUSPENDED:
+ /*
+* This thread isn't in any scheduling
+* queues; just change it's state:
+*/
+ pthread->cancelflags |= PTHREAD_CANCELLING;
+ PTHREAD_SET_STATE(pthread, PS_RUNNING);
+ break;
+
case PS_SPINBLOCK:
case PS_FDR_WAIT:
case PS_FDW_WAIT:
***
*** 52,58
case PS_WAIT_WAIT:
case PS_SIGSUSPEND:
case PS_SIGWAIT:
- case PS_SUSPENDED:
/* Interrupt and resume: */
pthread->interrupted = 1;
pthread->cancelflags |= PTHREAD_CANCELLING;
--- 61,66
Index: uthread_cond.c
===
RCS file: /opt/b/CVS/src/lib/libc_r/uthread/uthread_cond.c,v
retrieving revision 1.22
diff -c -r1.22 uthread_cond.c
*** uthread_cond.c 2000/01/27 23:06:59 1.22
--- uthread_cond.c 2000/03/01 13:03:46
***
*** 282,289
break;
}
! if (interrupted != 0 && _thread_run->continuation != NULL)
! _thread_run->continuation((void *) _thread_run);
_thread_leave_cancellation_point();
}
--- 282,292
break;
}
! if (interrupted != 0) {
! if (_thread_run->continuation != NULL)
! _thread_run->continuation((void *) _thread_run);
! rval = EINTR;
! }
_thread_leave_cancellation_point();
}
***
*** 449,456
break;
}
! if (interrupted != 0 && _thread_run->continuation != NULL)
! _thread_run->continuation((void *) _thread_run);
_thread_leave_cancellation_point();
}
--- 452,462
Re: cd9660 - device not configured
It seems Christoph Kukulies wrote: > > -current of Feb, 26th. > > Innocently I wanted to > > mount -t cd9660 /dev/acd1c /dist > > to grab some newer XF86 from the CD when > > cd9660: device not configured > > was thrown at me. And you have an acd1 device ?? check you /dev for up to date entries... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd9660 - device not configured
On Wed, 1 Mar 2000, Christoph Kukulies wrote: > mount -t cd9660 /dev/acd1c /dist > > to grab some newer XF86 from the CD when > > cd9660: device not configured > > was thrown at me. Check device major number. It should be like this blaze:netcenter$ ls -l /dev/*acd* crw-r- 1 root operator 117, 0 4 ÆÅ× 15:11 /dev/acd0a crw-r- 1 root operator 117, 2 4 ÆÅ× 15:11 /dev/acd0c To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Little patch to make pam_ssh work ...
Attached is a little patch that make /usr/src/lib/libpam/modules/pam_ssh
work as expected (else it bombs directly with unresolved symbols).
--
UNIX *IS* user friendly. It's just selective about who its friends are.
--unknown
Index: Makefile
===
RCS file: /space3/ncvs/src/lib/libpam/modules/pam_ssh/Makefile,v
retrieving revision 1.1
diff -c -r1.1 Makefile
*** Makefile2000/02/24 22:24:37 1.1
--- Makefile2000/03/01 14:48:06
***
*** 8,14
SRCS= log-client.c pam_ssh.c
CFLAGS+= -Wall -I${SSHSRC}
DPADD+= ${LIBCRYPTO} ${LIBCRYPT} ${LIBUTIL} ${LIBZ} ${LIBGCC_PIC}
! LDADD+= -lcrypto -lcrypt -lutil -lz -lgcc_pic
INTERNALLIB= yes
INTERNALSTATICLIB=yes
--- 8,14
SRCS= log-client.c pam_ssh.c
CFLAGS+= -Wall -I${SSHSRC}
DPADD+= ${LIBCRYPTO} ${LIBCRYPT} ${LIBUTIL} ${LIBZ} ${LIBGCC_PIC}
! LDADD+= -L${.OBJDIR}/../../../../secure/lib/libssh -lcrypto -lcrypt
-lutil -lz -lgcc_pic -lssh
INTERNALLIB= yes
INTERNALSTATICLIB=yes
Re: Two queries [ KDE / XFree86 ]
On 1 Mar, Donn Miller wrote: > It looks like SHMMAXPGS has to be a power of two + 1. (The original No. > config file says > > options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" > options SHMMAXPGS=1025 Thats from LINT. > So, it looks like SHMMAXPGS has to be a power of two + 1. That's why I > chose 4097 instead of 4096 LINT increases the default value by one (I think LINT didn't want to make useless modifications). See /sys//include/vmparam.h. Bye, Alexander. -- It's not a bug, it's tradition! http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
plist/glist query & proposal
Hi How does one query glist (grown defect list) from scsi device ? Wouldn't it be nice if weekly/monthly scripts saved/compared glist with previous versions, so admins can be alerted when devices start dying. L. _ Lauri Laupmaa +3725013369 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd9660 - device not configured
On Wed, Mar 01, 2000 at 03:40:38PM +0100, Soren Schmidt wrote: > It seems Christoph Kukulies wrote: > > > > -current of Feb, 26th. > > > > Innocently I wanted to > > > > mount -t cd9660 /dev/acd1c /dist > > > > to grab some newer XF86 from the CD when > > > > cd9660: device not configured > > > > was thrown at me. > > And you have an acd1 device ?? > check you /dev for up to date entries... isdn-kukulies# ls -l acd* crw-r- 1 root operator 117, 0 1 Mär 12:57 acd0a crw-r- 1 root operator 117, 2 1 Mär 12:57 acd0c brw-r- 1 root operator 19, 8 8 Feb 08:30 acd1a brw-r- 1 root operator 19, 10 8 Feb 08:30 acd1c isdn-kukulies# dmesg: atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... ad0: 19574MB [39770/16/63] at ata0-master using UDMA33 acd0: CDROM at ata1-master using PIO3 acd1: CDROM at ata1-slave using PIO4 > > -Søren -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[PATCH] OpenSSH: login.access and more auth_*
Hi.
This patch implements login.access(5) mechanism in OpenSSH,
add more auth_*() LOGIN_CAP functions for login(1) compatibility
and use += to preserve CFLAGS from make.conf
Please review and commit.
--- secure/usr.sbin/sshd/Makefile.old Mon Feb 28 22:27:31 2000
+++ secure/usr.sbin/sshd/Makefile Wed Mar 1 18:11:32 2000
@@ -1,7 +1,8 @@
# $FreeBSD: src/secure/usr.sbin/sshd/Makefile,v 1.3 2000/02/28 19:27:31 markm Exp $
#
-SSHSRC=${.CURDIR}/../../../crypto/openssh
+SSHSRC= ${.CURDIR}/../../../crypto/openssh
+LOGINSRC= ${.CURDIR}/../../../usr.bin/login
PROG= sshd
BINOWN=root
@@ -9,13 +10,14 @@
MAN8= sshd.8
SRCS= sshd.c auth-rhosts.c auth-passwd.c auth-rsa.c auth-rh-rsa.c \
- pty.c log-server.c login.c servconf.c serverloop.c
+ pty.c log-server.c login.c servconf.c serverloop.c \
+ login_access.c
-CFLAGS=-DLIBWRAP
+CFLAGS+= -DLIBWRAP -DLOGIN_ACCESS -I${LOGINSRC}
.include
-.PATH: ${SSHSRC}
+.PATH: ${SSHSRC} ${LOGINSRC}
.if defined(MAKE_KERBEROS4) && \
((${MAKE_KERBEROS4} == "yes") || (${MAKE_KERBEROS4} == "YES"))
--- crypto/openssh/sshd.c.old Wed Mar 1 17:31:16 2000
+++ crypto/openssh/sshd.c Wed Mar 1 17:52:08 2000
@@ -1293,10 +1293,13 @@
char *user;
#ifdef LOGIN_CAP
login_cap_t *lc;
- char *hosts;
- const char *from_host, *from_ip;
- int denied;
#endif /* LOGIN_CAP */
+#if defined(LOGIN_CAP) || defined(LOGIN_ACCESS)
+ const char *from_host, *from_ip;
+
+ from_host = get_canonical_hostname();
+ from_ip = get_remote_ipaddr();
+#endif /* LOGIN_CAP || LOGIN_ACCESS */
/* Get the name of the user that we wish to log in as. */
packet_read_expect(&plen, SSH_CMSG_USER);
@@ -1375,28 +1378,25 @@
lc = login_getpwclass(pw);
if (lc == NULL)
lc = login_getclassbyname(NULL, pw);
- from_host = get_canonical_hostname();
- from_ip = get_remote_ipaddr();
-
- denied = 0;
- if ((hosts = login_getcapstr(lc, "host.deny", NULL, NULL)) != NULL) {
- denied = match_hostname(from_host, hosts, strlen(hosts));
- if (!denied)
- denied = match_hostname(from_ip, hosts, strlen(hosts));
+ if (!auth_hostok(lc, from_host, from_ip)) {
+ log("Denied connection for %.200s from %.200s [%.200s].",
+ pw->pw_name, from_host, from_ip);
+ packet_disconnect("Sorry, you are not allowed to connect.");
}
- if (!denied &&
- (hosts = login_getcapstr(lc, "host.allow", NULL, NULL)) != NULL) {
- denied = !match_hostname(from_host, hosts, strlen(hosts));
- if (denied)
- denied = !match_hostname(from_ip, hosts, strlen(hosts));
+ if (!auth_timeok(lc, time(NULL))) {
+ log("LOGIN %.200s REFUSED (TIME) FROM %.200s",
+ pw->pw_name, from_host);
+ packet_disconnect("Logins not available right now.");
}
login_close(lc);
- if (denied) {
+#endif /* LOGIN_CAP */
+#ifdef LOGIN_ACCESS
+ if (!login_access(pw->pw_name, from_host)) {
log("Denied connection for %.200s from %.200s [%.200s].",
pw->pw_name, from_host, from_ip);
packet_disconnect("Sorry, you are not allowed to connect.");
}
-#endif /* LOGIN_CAP */
+#endif /* LOGIN_ACCESS */
if (pw->pw_uid == 0)
log("ROOT LOGIN as '%.100s' from %.100s",
@@ -2341,6 +2341,15 @@
ctime(&pw->pw_expire));
}
#endif /* __FreeBSD__ */
+#ifdef LOGIN_CAP
+ if (!auth_ttyok(lc, ttyname)) {
+ (void)printf("Permission denied.\n");
+ log(
+ "LOGIN %.200s REFUSED (TTY) FROM %.200s ON TTY %.200s",
+ pw->pw_name, hostname, ttyname);
+ exit(254);
+ }
+#endif /* LOGIN_CAP */
/*
* If the user has logged in before, display the time of last
--
Andrey A. Chernov
<[EMAIL PROTECTED]>
http://nagual.pp.ru/~ache/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: cd9660 - device not configured
On Wed, Mar 01, 2000 at 03:40:38PM +0100, Soren Schmidt wrote: > It seems Christoph Kukulies wrote: > > > > -current of Feb, 26th. > > > > Innocently I wanted to > > > > mount -t cd9660 /dev/acd1c /dist > > > > to grab some newer XF86 from the CD when > > > > cd9660: device not configured > > > > was thrown at me. > > And you have an acd1 device ?? > check you /dev for up to date entries... Ah, it's: isdn # sh MAKEDEV acd2 isdn # ls -l acd* crw-r- 1 root operator 117, 0 1 Mär 16:26 acd0a crw-r- 1 root operator 117, 2 1 Mär 16:26 acd0c crw-r- 1 root operator 117, 8 1 Mär 16:26 acd1a crw-r- 1 root operator 117, 10 1 Mär 16:26 acd1c funny that MAKEDEV acd1 doesn't make the '1' devices. > > -Søren > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
* Cliff Rowley <[EMAIL PROTECTED]> [000301 03:54] wrote: > > In any case, one major offender is imlib. Since I've recently gone > > Gnome, I've had to turn off imlib's "MIT-SHM shared memory" option > > or things would go bad after a few minutes or hours of use. > > That explains the errors when running xchat, but that doesnt explain > Netscape ;) Yes it does. Since all your programs run as _you_ then it's entriely possible that imlib went apesh*t and did something nasty to the wrong shared segment. > The annoying thing about this is that if a program decides to die because > of this error, it seems I've got a 50/50 chance that it's taken out for > good. I have to reboot to reclaim memory >:( no you don't, see below... > It'd be nice if we had a utility that could clean out and reclaim the > shared memory in 1 swoop. Then we'd be able to shut down XFree86 (and > obviously any other apps using shared memory), and get on with life :) > > (anyone listening?) er, yes this is entirely possible. If you want to clear SHM then use 'ipcs' to list and 'ipcrm' to delete. I used to have a shell script to do this, but i don't know where it went. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: things I noticed w/ 4.0
> > > > Kernel option VESA fails (see dmesg below). Is this a problem with my > > graphics card? > > Are you, by any chance, both compiling in VESA _and_ loading it with > loader? > > > Kernel option PNPBIOS causes the mouse to stop working. A pointer is > > visible at boot (w/ moused) until the mouse is moved, then it disappears > > forever. Maybe I'm misunderstanding what PNPBIOS does > > Weird. Are you sure your BIOS is set to PnP OS = No? heh, when I set this option to "no" in my bios... -CURRENT won't even finish probing the hardware... it just hangs in the boot-probe messages. > > > 'halt -p' still doesn't turn my computer off :). Haven't tested any other > > functionality of apm though. I usually disable apm in the bios since > > it makes turning the system power off w/ the button on the case a problem > > under FreeBSD. Any ideas? > > Yep. Try turning apm in BIOS on. :-) > > > /usr/games/phantasia doesn't like the return key. You have to use > > - (w/ TERMs xterm and cons25). /usr/games/teachgammon doesn't > > always clear the screen of previous text completely. > > M... I seem to recall someone were tweaking phantasia lately... > > -- > Daniel C. Sobral (8-DCS) > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > One Unix to rule them all, One Resolver to find them, > One IP to bring them all and in the zone bind them. > > > 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: Shared memory - Was: 2 Queries
On Tue, Feb 29, 2000 at 03:57:19PM -0600, Ade Lovett wrote: > On Tue, Feb 29, 2000 at 01:41:43PM -0500, Christopher Masto wrote: > > > > In any case, one major offender is imlib. Since I've recently gone > > Gnome, I've had to turn off imlib's "MIT-SHM shared memory" option > > or things would go bad after a few minutes or hours of use. > > Can you expand a bit on "go bad"? I have a couple of machines here > running with GNOME for days on end with no shared memory problems. Title bars in sawmill suddenly turning black, GNOME pixmaps disappearing/getting corrupted, that sort of thing. > I'm not seeing any leaks, though: [...] > Shared Memory: > T ID KEYMODE OWNERGROUP SEGSZ CPID LPID > m 655362622055 --rw-r--r-- rootwheel 1048576298298 > m 41615362 792064 --rw-rw-rw- adestaff 4 12549 12549 Funny, I even have the option turned off and I've still got: chris@lion-around:~$ ipcs -bpm Shared Memory: T ID KEYMODE OWNERGROUP SEGSZ CPID LPID m 655365432010 --rwa--pgsqlpgsql120204204 m 655375432001 --rw---pgsqlpgsql 1063936204204 m 655385432007 --rw---pgsqlpgsql 96424204204 m 196611 0 --rw-r--r-- rootwheel 4096837 53838 m 131076 0 --rw-r--r-- rootwheel 4096837 55434 m 3211269 0 --rwarwarwachrischris 1420800 41206 41206 m 1310726 0 --rw-r--r-- rootwheel 4096837 55429 m 1310727 0 --rwarwarwachrischris 65536934837 m 131080 0 --rw-r--r-- rootwheel 4096837926 m 131081 0 --rwarwarwachrischris 65536934837 m 131082 0 --rwarwarwachrischris 65536934837 m 196619 0 --rw-r--r-- rootwheel 4096837934 Still, it's not just me. Several friends have come to me after my recommendation that they try sawmill+GNOME with the complaint that their title bars were getting messed up, and turning of MIT-SHM solved it. One is running -current, another is running 3.4-RELEASE. And I've heard the same thing on the mailing lists. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
On Wed, 1 Mar 2000, Alfred Perlstein wrote: >I used to have a shell script to do this, but i don't know where it >went. > >-- >-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] I do! (line is wrapped) #!/bin/sh ipcs | sed "s/[ ][ ]*/ /g" | cut -f 2 -d" " | sed "s/[^0-9]//g" | xargs -t -n 1 ipcrm -m To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
* Adam <[EMAIL PROTECTED]> [000301 09:24] wrote: > > > On Wed, 1 Mar 2000, Alfred Perlstein wrote: > > >I used to have a shell script to do this, but i don't know where it > >went. > > > >-- > >-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] > > I do! (line is wrapped) > > #!/bin/sh > ipcs | sed "s/[ ][ ]*/ /g" | cut -f 2 -d" " | sed > "s/[^0-9]//g" | xargs -t -n 1 ipcrm -m > heh, did you write that, or find it somewhere? It looks exactly like the one i wrote a couple years back. :) -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ES1370 - no sound completely :(
Hi! I have a Ensoniq AudioPCI 64 card, and can't get a bit of sound from it since i've installed it on my FreeBSD box. dmesg: ... pcm0: port 0xd000-0xd03f irq 12 at device 12.0 on pci0 ... cat /dev/sndstat FreeBSD Audio Driver (newpcm) Feb 22 2000 17:10:37 Installed devices: pcm0: at io 0xd000 irq 12 (1p/1r channels duplex) When I'm trying to play any wav (or any other soundfile) of any size (even 2k) with any program (play, waveplay), it stays silent for approx 10-20 seconds, then exits... When I'm trying to play any .mp3 with, say, mpg123 -v, it simply starts and stays on first few frames, and never comes further, just like that: Playing MPEG stream from test.mp3 ... MPEG 1.0, Layer: III, Freq: 44100, mode: Joint-Stereo, modext: 0, BPF: 417 Channels: 2, copyright: No, original: Yes, CRC: No, emphasis: 0. Bitrate: 128 Kbits/s, Extension value: 0 Audio: 1:1 conversion, rate: 44100, encoding: signed 16 bit, channels: 2 Frame#22 [10428], Time: 00:00.57 [04:32.40], ^C [0:00] Decoding of test.mp3 finished. ^C^C $ and quits only when I press triple ^C... What can be a problem? Still can't get any point of it. (Card is OK, it works fine under m$win...) world compiled 3 days ago, kernel as of yesterday, cvsup'ing daily. Adios, /KONG Hostas Red (KVK10, KVK10-RIPE) || UNiX Systems Administrator, ComSet ISP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
On Wed, 1 Mar 2000, Alfred Perlstein wrote: >* Adam <[EMAIL PROTECTED]> [000301 09:24] wrote: >> >> >> On Wed, 1 Mar 2000, Alfred Perlstein wrote: >> >> >I used to have a shell script to do this, but i don't know where it >> >went. >> > >> >-- >> >-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] >> >> I do! (line is wrapped) >> >> #!/bin/sh >> ipcs | sed "s/[ ][ ]*/ /g" | cut -f 2 -d" " | sed >> "s/[^0-9]//g" | xargs -t -n 1 ipcrm -m >> > >heh, did you write that, or find it somewhere? It looks exactly like >the one i wrote a couple years back. :) >-- >-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] It is yours, I had it on a cdrom backup of my homedir. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
On Wed, Mar 01, 2000 at 11:54:35AM -0500, Adam wrote:
> #!/bin/sh
> ipcs | sed "s/[ ][ ]*/ /g" | cut -f 2 -d" " | sed
> "s/[^0-9]//g" | xargs -t -n 1 ipcrm -m
Always with the sed. ipcrm `ipcs -m | awk '$1 == "m" { print "-m " $2 }'`
anyone?
--
Christopher Masto Senior Network Monkey NetMonger Communications
[EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net
Free yourself, free your machine, free the daemon -- http://www.freebsd.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
On Tue, Feb 29, 2000 at 01:41:43PM -0500, Christopher Masto wrote: > Personally, I have this extreme distaste for sysv shared memory. It > is a very scarce resource that is not freed automatically, and seems > to go completely against the unix model. Reminds me of having to free > memory on the Amiga, and slowly running out of chip RAM. > In any case, one major offender is imlib. Since I've recently gone > Gnome, I've had to turn off imlib's "MIT-SHM shared memory" option or > things would go bad after a few minutes or hours of use. I would say that the programs you've mentioned are badly written then. It takes no more than XSync(disp,False); shmctl( shmid, IPC_RMID, 0); right after a call to XShmAttach() for a shared memory image to achieve the automatic reclamation of the memory. Shared pixmaps are different, but not that many programs should use these anyway. Cheers, -- Anton Berezin <[EMAIL PROTECTED]> The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installation floppies and USB
Phoenix wrote: >If it is the same kind of acer as I have you may be in luck, >hidden away on the back panel hidden behind a sticker and a >metal knockout there are 2 ps/2 style connectors. Pull the >top off of your box and see if you have them (near the parrellel >port) I have been running -current on this box for a month >with no problems other than having to use a normal keyboard for >the install. I have an Acer Aspire model 6140 (a PIII 450 system). The system has plastic molding in the back that covers 2 serial ports (only one of which is supposed to work), and a game port. I pulled off the metal case for the system as a whole but did not see any ps/2 ports or other ports. I have looked for an ISA or PCI card that might have a ps/2 or AT-style port for a keyboard but I have not been able to find one. I have also tried to find a keyboard that would use a COM port but that is also non-existant. Anyway, thanks for your input. __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
On Wed, Mar 01, 2000 at 06:20:28PM +0100, Anton Berezin wrote: > I would say that the programs you've mentioned are badly written then. > > It takes no more than > > XSync(disp,False); > shmctl( shmid, IPC_RMID, 0); It takes no more than a well-designed operating system service to ensure that badly written programs don't fail to release resources when they crash. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ES1370 - no sound completely :(
On Wed, 1 Mar 2000, Hostas Red wrote: > Hi! > > I have a Ensoniq AudioPCI 64 card, and can't get a bit of sound from it > since i've installed it on my FreeBSD box. > > dmesg: > ... > pcm0: port 0xd000-0xd03f irq 12 at device 12.0 on pci0 > ... > > > cat /dev/sndstat > > FreeBSD Audio Driver (newpcm) Feb 22 2000 17:10:37 > Installed devices: > pcm0: at io 0xd000 irq 12 (1p/1r channels duplex) > Did you do ./MAKEDEV snd0 ? This solved a similar problem I had with an es1371. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
boot problem with Mylex DAC960
I've got a server, tyan 1832DL with 2 CPU onborad, Mylex DAC960 and 3*9G IBM SCSI Disk. I build a RAID-0 Disk by Mylex dos utility, I like to install FreeBSD 4.0-current, but I cannot boot FreeBSD by floppy image 4.0-2214-CURRENT. If I remove Mylex DAC960, floopy image can boot FreeBSD. I could boot from IDE-CDROM using FreeBSD 3.4 if Mylex DAC960 removed. (this cdrom is from the book "The Complete FreeBSD"). But I cannot install FreeBSD if I cannot boot from a FreeBSD floopy or cdrom. I want my FreeBSD : Boot Loader problem ? It cannot find disk array created by Mylex DAC960 ? Should I do something special for this Mylex Controller ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
On Wed, Mar 01, 2000 at 07:58:34AM -0800, Alfred Perlstein wrote:
> > It'd be nice if we had a utility that could clean out and reclaim the
> > shared memory in 1 swoop. Then we'd be able to shut down XFree86 (and
> > obviously any other apps using shared memory), and get on with life :)
> >
> > (anyone listening?)
>
> er, yes this is entirely possible.
>
> If you want to clear SHM then use 'ipcs' to list and 'ipcrm' to delete.
>
> I used to have a shell script to do this, but i don't know where it
> went.
Hi, I dont' know if this meet what you described, but I use a single line
to clean un-referenced shared memory.
x.sh:
#!/bin/sh
ipcs | awk '{if ($5 == ENVIRON["USER"]) system("ipcrm -m" $2)}'
Before applying 3 options posted by ade lovett into my kernel,
most heavy gtk programs like xmms, gimp, gnome-controlcenter...etc,
will die with whole X crashing. (I invoke X with gnome-session, what the
gnome document said) Thus I have to run x.sh whenever my X crashed with
share memory bodiz *shurg* /.\
--
CirX - This site doesnt' exist.
9c k9o h9 s1bg s1f, 7v .y xqx a sj m8r ffg1 vg5 a6 asox tmul h38.
ant sj m8r ob ? 1fj mwby a1 tao vg5. soq df v' .a. CirX.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ntpd hanging machine
According to Wes Morgan: > merge. Until that point I was using the stock ntp4 from udel with no > problems. But I tried the one shipping with 4.0 and it locks up completely > (looks like a hardware lockup). The ntp4 from udel works completely > though. Odd :) Yes, that's odd. I've never seen that... Can you try to compile a kernel with DDB and try to see whether it hits the debugger or not ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ES1370 - no sound completely :(
Hi! On Wed, 1 Mar 2000, R Joseph Wright wrote: > > I have a Ensoniq AudioPCI 64 card, and can't get a bit of sound from it > > since i've installed it on my FreeBSD box. > > > > dmesg: > > ... > > pcm0: port 0xd000-0xd03f irq 12 at device 12.0 on pci0 > > ... > > > > > > cat /dev/sndstat > > > > FreeBSD Audio Driver (newpcm) Feb 22 2000 17:10:37 > > Installed devices: > > pcm0: at io 0xd000 irq 12 (1p/1r channels duplex) > > > Did you do ./MAKEDEV snd0 ? This solved a similar problem I had with an > es1371. Of coz, not once :) Also I've tried DEVFS' devices (cat a.au /devs/audio0 or something :). It doesn't helps :( Adios, /KONG Hostas Red (KVK10, KVK10-RIPE) || UNiX Systems Administrator, ComSet ISP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld fails at ncurses
I wrote: > I will try doing an update (using sysinstall) to one of the latest > -current snapshots and do the buildworld again from there. Ok, I did just that and it still fails at /usr/src/contrib/ncurses/ncurses/tinfo/comp_hash.c: cc -o make_hash -O -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -DMAIN_PROGRAM /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_hash.c In file included from /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_hash.c:43: /usr/src/lib/libncurses/../../contrib/ncurses/include/tic.h:107: syntax error before `GCC_PRINTFLIKE' The same happens by doing a make directly in /usr/src/lib/libncurses. The source is freshly cvsupped with TAG=. Are there by any means any header files or what not that might be too old and should be taken from inside /usr/src to their original location? The system is now: arthur# uname -a FreeBSD arthur.cs.uni-magdeburg.de 4.0-CURRENT FreeBSD 4.0-CURRENT #6: Wed Mar 1 17:41:18 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/ARTHUR i386 That's -current as of the 2228-snapshot. The compiler is updated: arthur# cc --version 2.95.2 Does that bring us any further? Roland To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ES1370 - no sound completely :(
Hi! On Wed, 1 Mar 2000, Sean O'Connell wrote: > > Of coz, not once :) Also I've tried DEVFS' devices (cat a.au /devs/audio0 > > or something :). > > > > It doesn't helps :( > > Does it play cd audio? I have seen some cases where the mixer > part worked ok (music cd's), but lots of silence from the dsp > (realaudio, waveplay, etc). Yes, mixer part works fine - it changes volumes of pcm, synth, etc, but... Still cannot get a bit of sound from it (excluding a CD, of coz)... Adios, /KONG Hostas Red (KVK10, KVK10-RIPE) || UNiX Systems Administrator, ComSet ISP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: things I noticed w/ 4.0
> > Weird. Are you sure your BIOS is set to PnP OS = No? > > heh, when I set this option to "no" in my bios... -CURRENT won't even > finish probing the hardware... it just hangs in the boot-probe messages. You know, if you included some more details this might even be a useful bug report. -- \\ 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: boot problem with Mylex DAC960
> > I've got a server, tyan 1832DL with 2 CPU onborad, Mylex DAC960 > and 3*9G IBM SCSI Disk. I build a RAID-0 Disk by Mylex dos utility, > I like to install FreeBSD 4.0-current, but I cannot boot FreeBSD by > floppy image 4.0-2214-CURRENT. You need to use a 4.0 snapshot from 2220 or later to boot with the Mylex controller installed. -- \\ 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: Shared memory - Was: 2 Queries
In article <[EMAIL PROTECTED]>, Christopher Masto <[EMAIL PROTECTED]> wrote: > On Wed, Mar 01, 2000 at 06:20:28PM +0100, Anton Berezin wrote: > > I would say that the programs you've mentioned are badly written then. > > > > It takes no more than > > > > XSync(disp,False); > > shmctl( shmid, IPC_RMID, 0); > > It takes no more than a well-designed operating system service to > ensure that badly written programs don't fail to release resources > when they crash. We didn't design that particular service. That's why it's called System V shared memory. Also, it's persistent for legitimate design reasons, just like files are. Applications need to clean up after themselves. The OS has no way of knowing whether an application wants its shared memory segments to survive after it terminates. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
GRE Support in 4.X ???
Hi all, I Just like to ask if there will be support for GRE in 4.X releases (without tunnels implementations), because its needed by wccp protocol managed by Squid & Cisco routers, to create Cache Engines, there are some patches & files that works in the squid home page, Im using them right now with 3.4, and they work great: http://www.squid-cache.org/WCCP-support/FreeBSD/gre.patch & http://www.squid-cache.org/WCCP-support/FreeBSD/gre.c but I think it would be nice to see them integrated in to the base system. Here it is the Squid description for GRE Support (taken from the webpage): FreeBSD first needs to be configured to recieve and strip the GRE encapsulation from the packets from the router. To do this you will need to patch and recompile your kernel. First, a patch needs to be applied to your kernel for GRE support. Apply this patch to your 3.1 kernel. If you use a version other than 3.1 it may not apply. You will need to manually change the appropriate files. Secondly you will need to download gre.c and copy it to /usr/src/sys/netinet/gre.c. Finally add "OPTION GRE" to your kernel config file and rebuild your kernel. Note, the opt_gre.h file is created when you run config. Once your kernel is installed you will need to configure FreeBSD for transparent proxying. Thanks for your time Sincerely Ales To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
< said: > It takes no more than a well-designed operating system service to > ensure that badly written programs don't fail to release resources > when they crash. Unfortunately, the System V shared-memory API is brain-damaged and does not permit this. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
On Wed, Mar 01, 2000 at 11:28:13AM -0800, John Polstra wrote: > > It takes no more than a well-designed operating system service to > > ensure that badly written programs don't fail to release resources > > when they crash. > > We didn't design that particular service. That's why it's called > System V shared memory. I did mean to imply that it was poorly designed, but not that it was designed by FreeBSD's designers. > Also, it's persistent for legitimate design reasons, just like files > are. Applications need to clean up after themselves. You can have many more than 32 files. Files are (usually) well-organized and have names, so you can wipe out your web browser's cache or lock file relatively easily. Files take up a negligible fraction of the available file space. SysV shared memory is limited, unnamed, unorganized, and uses up a very scarce resource. > The OS has no way of knowing whether an application wants its shared > memory segments to survive after it terminates. That's unfortunate. That's one of the reasons I try to stay away from SysV IPC. I don't like to have to reboot. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Process cleanup (was Shared memory ...)
> "John" == John Polstra <[EMAIL PROTECTED]> writes: John> Applications need to clean up after themselves. The OS has John> no way of knowing whether an application wants its shared John> memory segments to survive after it terminates. Tricky when the program crashes. Remember that a bug-free application can still crash due to buggy shared-libraries. I'm too lazy to look right this second ;-) ... do atexit() functions get run when a process takes (say) a segmentation fault? --lyndon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installation floppies and USB
Phoenix wrote: >If it is the same kind of acer as I have you may be in luck, hidden >away on the back panel hidden behind a sticker and a metal knockout there >are 2 ps/2 style connectors. Pull the top off of your box and see if you >have them (near the parrellel port) I have been running -current on this >box for a month with no problems other than having to use a normal keyboard >for the install. I have an Acer Aspire model 6140 (a PIII 450 system). The system has plastic molding in the back that covers 2 serial ports (only one of which is supposed to work), and a game port. I pulled off the metal case for the system as a whole but did not see any ps/2 ports or other ports. I have looked for an ISA or PCI card that might have a ps/2 or AT-style port for a keyboard but I have not been able to find one. I have also tried to find a keyboard that would use a COM port but that is also non-existant. Anyway, thanks for your input. John __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
On Wed, Mar 01, 2000 at 02:57:38PM -0500, Christopher Masto wrote: > > Also, it's persistent for legitimate design reasons, just like files > > are. Applications need to clean up after themselves. > > You can have many more than 32 files. Files are (usually) > well-organized and have names, so you can wipe out your web browser's > cache or lock file relatively easily. Files take up a negligible > fraction of the available file space. That limitation is FreeBSDs fault and is correctable in the kernel config file so it's really the administrator's fault. For instance the default on a recent Irix machine is 600 segments which a maximum size of 512MB each. Solaris has nearly as many. > SysV shared memory is limited, unnamed, unorganized, and uses up a > very scarce resource. Keys provide a limited sort of naming. It's not hierarchical, but it basicaly gives you 2^32 names which can be accessed exclusivly. The resource is only as scarce as the system admin makes it. I don't like FreeBSD's default limits, but they are just that, defaults. > > The OS has no way of knowing whether an application wants its shared > > memory segments to survive after it terminates. > > That's unfortunate. That's one of the reasons I try to stay away from > SysV IPC. I don't like to have to reboot. It would be nice if SysV IPC had a refrence counting mode (though anyone who what they were doing could implement such a thing with a semaphore to do the refcounting which is probalby why they didn't do it). The fact is though, there are significant cases where the OS *cannot* know if the application is done or not. SysV shm is really designed (as far as I can tell) to be a low level API, somewhere around the level of malloc. It's not a complete solution and that's the trap people keep falling into. You have to implement that goop to go around it. It's not really that hard and most of it is write once, use over and over again. If you use ipcrm you don't have to reboot. I've spent the last couple weeks hacking on some code which uses SysV shared memory and semaphores. It's really not that bad. You just have to get into the proper mindset. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Instrallation floppies and USB
Hi: I looked in BIOS setup to see if there were any settings that I could try changing to make the boot floopies work. The only ones that I found that seemed to apply were (defaults in brackets): Configuration Table[Disabled] PCI IRQ setting[Auto] PCI IRQ sharing[No] Plug and Play OS [Yes] Reset Resource Assignments [No] I thought that the Configuration Table might provide the ability to change settings (IRQ, etc.) but it only summarized system specs. (Among these, it showed USB 'enabled') I didn't change PCI IRQ setting. I thought that PCI IRQ sharing might allow for dynamic assignment of IRQs, but changing this to 'Yes' had no effect. Disabling Plug and Play had no effect I thought that Reset Resource Assignments might enable the OS to set resouces (IRQ, etc) but everytime I looked at this after I had chosen 'Yes,' it had been set back to 'No.' Acer support tells me that all this does is reset the resources back to their original values. In sum, I was not able to change anything with the changes that I made. I also went to the Acer support site to see if there were any BIOS or device updates for my system. I didn't find any. I am registered with Acer support and I would be happy to provide the information needed (Toll free phone number, system serial number, my customer id #, etc.) for Nick Hibma or another developer to contact them if that would be helpful. FYI, I also have a 160Kbps DSL connection so if anyone wants me to test reconstructed boot disks/kernels, I can do that. (I believe that John Baldwin has been looking into this.) To summarize the problem and the clues that we now have: 1. When I try to boot the kern.flp disk, I get the message: /boot.config: -P Keyboard: no Booting continues but the keyboard is unusable unless I immmediately hit the space bar then type '-Dh' at the 'boot:' prompt as described in the TROUBLE.TXT document in the -CURRENT snapshot directory. NOTE: That document says that the '-Dh' workaround is meant for older systems with an 84-key keyboard, but it is working for my 1999 Acer Asprire with a 102-key USB keyboard! 2. The installation boots the kernel but immediately after the kernel config screen appears (with 3 options: no config, full screen, CLI), the system becomes unusable. 3. The floppy drive light remains on, as though the floopy is awaiting instructions or has been interrupted in data transfer. 4. I have provided my complete system specs and resource usage in an earlier post. It appears that there may be some resource conflicts. My system uses IRQ 11 for the Intel 82371AB/EB PCI to USB Universal Host Controller, while FreeBSD uses IRQ 11 for an adaptec SCSI Controller. My keyboard and FreeBSD's use of IRQ12 and IOMem 0060h may also be a problem. (This is not an exhaustive list of possible conflicts) 5. I can boot the NetBSD installation disk and use my keyboard to select options (e.g. configure my NIC) so this may provide some additional info or a possible roadmap to a solution. For example, does it dynamically find resources for more devices than FreeBSD (especially the Adaptec SCSI controller and keyboards/mice)? Does NetBSD provide support for USB keyboards in their installation kernel? Etc. John __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
In message <[EMAIL PROTECTED]>, Christopher Masto writes: >SysV shared memory is limited, unnamed, unorganized, and uses up a >very scarce resource. You know, you should go back in the archives to when sysV IPC was released, and you will be able to find some *really* nasty but technically competent critizisms of it. You are preaching to a very seasoned choir here... -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: plist/glist query & proposal
In message <38BD4CD9.22420.5550BD1@localhost> "Lauri Laupmaa" writes: : How does one query glist (grown defect list) from scsi device ? I use camcontrol defects -P or -G to get them. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
typo in sbin/Makefile
This message was sent from Geocrawler.com by "Victor Salaman" <[EMAIL PROTECTED]> Be sure to reply to that address. While doing a make release I just noticed that /sbin/Makefile has DISTRIBUTION=des and fails. Is this supposed to be like this? (I'm new to making a release, but it seems odd) Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: plist/glist query & proposal
On Wed, Mar 01, 2000 at 17:01:13 +0200, Lauri Laupmaa wrote: > Hi > > How does one query glist (grown defect list) from scsi device ? Like this: # camcontrol defects da0 -f phys -G Got 8 defects: 4818:4:54 1338:0:138 1250:1:46 2661:5:117 1696:5:5 1760:5:58 688:9:133 1130:9:166 > Wouldn't it be nice if weekly/monthly scripts saved/compared glist > with previous versions, so admins can be alerted when devices > start dying. It would be nice, although I'm not sure everyone would want it. Also, one problem you may run into is that none of the defect list formats is mandatory. So there's no one format you can use that is guaranteed to work with all drives. If the drive doesn't support the requested format, it is supposed to return a specific error (which camcontrol looks for) along with the defect list in a format that it does support. Unfortunately, many drives don't do this, or return a different error, or return an error but no data. So camcontrol can't always tell the difference between "here's a defect list in some other format" and "I can't do that". One other probelm -- the read defect data command isn't mandatory in SCSI-2 at least. (haven't checked the SCSI-3 specs) So you can't even guarantee that the drive will support the command. Anyway, it should be easy enough to write a script that will compare glists for the drives on your machines and watch for failures. The defect list output is intended to be reasonably easy to script -- the number of defects goes to stderr, and the actual list of defects goes to stdout. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world problems at vm/vnode_pager.h -> vm/vnode_pager.ph
Mike Tancsa [[EMAIL PROTECTED]] wrote: <..> > vm/vnode_pager.h -> vm/vnode_pager.ph > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. > *** Error code 1 <..> I recently saw this on some alphas. This is happening as part of installworld. My guess is that something about the installed perl or h2ph is just broken. I closed my eyes, crossed my fingers & did 'make -i installworld'.After installing the first time, a second installworld completed without errors. So you should do 'make buildworld && make -i installworld' BTW -- did you see this on FreeBSD/i386 or FreeBSD/alpha?? Drew -- -- Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: [EMAIL PROTECTED] Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world problems at vm/vnode_pager.h -> vm/vnode_pager.ph
At 03:48 PM 3/1/00 -0500, Andrew Gallatin wrote: >I recently saw this on some alphas. This is happening as part of >installworld. > >My guess is that something about the installed perl or h2ph is just >broken. I closed my eyes, crossed my fingers & did 'make -i >installworld'.After installing the first time, a second >installworld completed without errors. > >So you should do 'make buildworld && make -i installworld' Yup, did the same thing basically... Did a buildworld and then installworld and ignored errors. Then the kernel, and then did a make world without issue after the reboot. This was on an Intel platform however. ---Mike Mike Tancsa, tel +1 519 651 3400 Network Administrator,[EMAIL PROTECTED] Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
On Wed, Mar 01, 2000 at 09:30:08PM +0100, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Christopher Masto writes: > > >SysV shared memory is limited, unnamed, unorganized, and uses up a > >very scarce resource. > > You know, you should go back in the archives to when sysV IPC was > released, and you will be able to find some *really* nasty but > technically competent critizisms of it. > > You are preaching to a very seasoned choir here... I apologize for belaboring it. I was just responding to some direct comments. There are apparently some in the congregation who are not members of the choir, or they wouldn't be arguing with me. :-) I don't particularly care, as my point is simply "I don't like SysV IPC". I think my mistake was backing that up with "and here are some examples of the things which caused that opinion". In any case, I'll stop. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: typo in sbin/Makefile
On Wed, 1 Mar 2000, Victor Salaman wrote: > This message was sent from Geocrawler.com by "Victor Salaman" <[EMAIL PROTECTED]> > Be sure to reply to that address. > > While doing a make release I just noticed > that /sbin/Makefile has DISTRIBUTION=des and > fails. Is this supposed to be like this? (I'm new > to making a release, but it seems odd) Mark Murray was just frobbing in this area..perhaps you caught the middle of his changes? Resup and try again. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Process cleanup (was Shared memory ...)
On 2000-Mar-02 07:10:39 +1100, Lyndon Nerenberg <[EMAIL PROTECTED]> wrote: >I'm too lazy to look right this second ;-) ... do atexit() functions get >run when a process takes (say) a segmentation fault? Nope. If there's no userland signal handler, the process will never return to userland after a signal. If you really wanted to, you could add handlers for all the signals and make them call the atexit() functions before dying, but that would get messy (since the process state is probably indeterminate if it got an unexpected signal). As various people have pointed out, SysV IPC is mostly an abomination. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot problem with Mylex DAC960
On Wed, Mar 01, 2000 at 11:26:35AM -0800, Mike Smith wrote: > > > > I've got a server, tyan 1832DL with 2 CPU onborad, Mylex DAC960 > > and 3*9G IBM SCSI Disk. I build a RAID-0 Disk by Mylex dos utility, > > I like to install FreeBSD 4.0-current, but I cannot boot FreeBSD by > > floppy image 4.0-2214-CURRENT. > > You need to use a 4.0 snapshot from 2220 or later to boot with the > Mylex controller installed. IIRC you also to reinstall the boot blocks...right? -Guido To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic: free: multiple frees
Hiya, At the bottom of this message is the dmesg output from my 4.0-CURRENT box with a kernel compiled February 27th. The kernel as of a cvsup this afternoon now dies and prints the following message immediately after initializing the keyboard: atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 panic: free: multiple frees If someone can't figure out where this might be coming from I'll hook up a serial console and try to capture a verbose boot. My kernel config is also included at the very bottom. Thanks, Ben Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Feb 27 21:52:28 EST 2000 [EMAIL PROTECTED]:/bits/freebsd/src/sys/compile/ADARA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Features=0x80f9ff real memory = 67108864 (65536K bytes) avail memory = 62386176 (60924K bytes) Preloaded elf kernel "kernel.works" at 0xc0295000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 chip1: port 0xe800-0xe80f at device 4.3 on pci0 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd000-0xd07f mem 0xe180-0xe180007f irq 12 at device 9.0 on pci0 xl0: Ethernet address: 00:10:4b:6a:b4:ee miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: port 0xb800-0xb8ff mem 0xe100-0xe1000fff irq 10 at device 11.0 on pci0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 fd1: <1200-KB 5.25" drive> on fdc0 drive 1 WARNING: "fd" is usurping "fd"'s cdevsw[] WARNING: "fd" is usurping "fd"'s bmaj atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: lpt0: on ppbus0 lpt0: Interrupt-driven port IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging disabled ad0: 19574MB [39770/16/63] at ata0-master using UDMA33 ad2: 17206MB [34960/16/63] at ata1-master using UDMA33 Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers Mounting root from ufs:/dev/ad0s1a vinum: loaded da0 at ahc0 bus 0 target 5 lun 0 da0: Removable Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) vinum: reading configuration from /dev/ad2s1h vinum: updating configuration from /dev/ad2s1g vinum: updating configuration from /dev/ad0s1h vinum: updating configuration from /dev/ad0s1g # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # 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 ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.242 2000/02/16 04:27:03 yokota Exp $ machine i386 cpu I686_CPU ident ADARA maxusers32 #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options INET#InterNETworking #optionsINET6 #IPv6 options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options MFS #Memory Filesystem #optionsMD_ROOT #MD is a potential root device #optionsNFS #Network Filesystem #optionsNFS_ROOT
Re: panic: free: multiple frees
On Wed, 1 Mar 2000, Benjamin Greenwald wrote: > Hiya, > > At the bottom of this message is the dmesg output from my 4.0-CURRENT box > with a kernel compiled February 27th. The kernel as of a cvsup this > afternoon now dies and prints the following message immediately after > initializing the keyboard: > > > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > panic: free: multiple frees This is caused by rev.1.54 of subr_bus.c. atkbdc_isa.c does funky things with the softc. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: free: multiple frees
In message <[EMAIL PROTECTED]>, Bruce Eva ns writes: >On Wed, 1 Mar 2000, Benjamin Greenwald wrote: > >> Hiya, >> >> At the bottom of this message is the dmesg output from my 4.0-CURRENT box >> with a kernel compiled February 27th. The kernel as of a cvsup this >> afternoon now dies and prints the following message immediately after >> initializing the keyboard: >> >> >> atkbdc0: at port 0x60-0x6f on isa0 >> atkbd0: irq 1 on atkbdc0 >> panic: free: multiple frees > >This is caused by rev.1.54 of subr_bus.c. atkbdc_isa.c does funky things >with the softc. I noticed and reported to peter who fixed it a few hours ago. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mod_ssl & current
We have found a fix that will change the building of librsaUSA to fix the problem. The fix will get committed after the release engineer approve the commit. The port will not need to be changed in the long run. Jim Bloom [EMAIL PROTECTED] Jim Bloom wrote: > > You definitely don't need -lRSAglue. That file is an empty library just for > compatibility. > > The port apache3-modssl worked a couple days ago when I last made a pass through > all of the ports using openssl in -current. I'll take a look at it again (by > tomorrow) and see where things stand. The recent upgrade of modssl might have > caused a problem or broken a patch. > > Jim Bloom > [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
IPv6 diagnostic VMWARE 2 beta
World of 2228 under VMWARE 2.0-468 under NT4. Is this one for VMWARE? lnc0 = bridged adapter (network cable disconnected) lnc1 = host adapter The following kernel diagnostics are presented during boot. lnc0: starting DAD for fe80:0001::0250:56ff:fe98:95ec lnc1: starting DAD for fe80:0002::0250:56ff:fee7:93ca lnc0: DAD detected duplicate IPv6 address fe80:0001::0250:56ff:fe98:95ec : 1 NS, 0 NA lnc0: DAD complete for fe80:0001::0250:56ff:fe98:95ec - duplicate found lnc0: manual intervention required lnc1: DAD complete for fe80:0002::0250:56ff:fee7:93ca - no duplicates found -- Mark Knight To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: free: multiple frees
On Thu, 2 Mar 2000, Bruce Evans wrote: > On Wed, 1 Mar 2000, Benjamin Greenwald wrote: > > > Hiya, > > > > At the bottom of this message is the dmesg output from my 4.0-CURRENT box > > with a kernel compiled February 27th. The kernel as of a cvsup this > > afternoon now dies and prints the following message immediately after > > initializing the keyboard: > > > > > > atkbdc0: at port 0x60-0x6f on isa0 > > atkbd0: irq 1 on atkbdc0 > > panic: free: multiple frees > > This is caused by rev.1.54 of subr_bus.c. atkbdc_isa.c does funky things > with the softc. I think it was a problem with psm.c which Peter has committed a fix for already. It bogusly freed the softc (sio.c does too but I doubt if it would happen in normal usage). -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot problem with Mylex DAC960
> On Wed, Mar 01, 2000 at 11:26:35AM -0800, Mike Smith wrote: > > > > > > I've got a server, tyan 1832DL with 2 CPU onborad, Mylex DAC960 > > > and 3*9G IBM SCSI Disk. I build a RAID-0 Disk by Mylex dos utility, > > > I like to install FreeBSD 4.0-current, but I cannot boot FreeBSD by > > > floppy image 4.0-2214-CURRENT. > > > > You need to use a 4.0 snapshot from 2220 or later to boot with the > > Mylex controller installed. > > IIRC you also to reinstall the boot blocks...right? If you're installing a snapshot, you get the bootblocks for free. 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
Re: panic: free: multiple frees
On Wed, 1 Mar 2000, Doug Rabson wrote: > I think it was a problem with psm.c which Peter has committed a fix for > already. It bogusly freed the softc (sio.c does too but I doubt if it > would happen in normal usage). The free in sioclose() happens in normal usage after a pccard goes away. Managing softc's outside the driver is the main bogon here in IMHO. sioclose() needs to free the softc and remove it from any external tables atomically with other closedowns. It uses spltty() to prevent races. This will be fixed by using an internal table for com_addr() again. device_set_driver() has unnecessary races. It frees the softc before clearing the pointer to it. Interrupt handlers shouldn't call it, but some do. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pthread_{suspend,resume}_np broken?
On Wed, Mar 01, 2000 at 09:30:43AM -0500, Daniel M. Eischen wrote: > I haven't run any other regression tests. I'll do that when I get > some more time. Jason, can you also take a look at these changes and > run some tests on them? I just moved a couple of days ago and all my test boxes are still in boxes. It will be at least a couple of days before I can test this properly. Jason To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 diagnostic VMWARE 2 beta
> World of 2228 under VMWARE 2.0-468 under NT4. > > Is this one for VMWARE? > > lnc0 = bridged adapter (network cable disconnected) > lnc1 = host adapter > > The following kernel diagnostics are presented during boot. > > lnc0: starting DAD for fe80:0001::0250:56ff:fe98:95ec > lnc1: starting DAD for fe80:0002::0250:56ff:fee7:93ca > lnc0: DAD detected duplicate IPv6 address fe80:0001::0250:56ff:fe98:95ec > : 1 NS, 0 NA > lnc0: DAD complete for fe80:0001::0250:56ff:fe98:95ec - duplicate found > lnc0: manual intervention required > lnc1: DAD complete for fe80:0002::0250:56ff:fee7:93ca - no duplicates > found > -- > Mark Knight The above log message is of IPv6 duplicated address detection. It is defined in RFC2462, and briefly it does following things, on each of connected interfaces. -Automatically create own addr. -But before actually enable it, do link local multicast query for the addr to the assocated interface, to check if there is already same addr assigned to another host. -Usually it success if no reply is obtained in some period, and fails if an reply is obtained. (It think same addr is already used by some other host.) So this procedure will fail in following cases. -Its own outstanding multicast packets are copyied back from network. -The interface is in PROMISCUS mode. (e.g. tcpdump is exec,ed on the interface.) I have not ever used VMWARE, but I suppose the above lnc0 is VMWARE's virtual bridging interface and copying back its own outstanding multicast packets? Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: lo0 tcp connections in TIME_WAIT/LAST_ACK/FIN_WAIT?
> After upgrading from 3.4 to RC2, i'm noticing something that I never saw > before: > > Active Internet connections (including servers) > Proto Recv-Q Send-Q Local Address Foreign Address(state) > tcp0 0 127.0.0.1.4954 127.0.0.1.4242 SYN_SENT > tcp0 0 127.0.0.1.4953 127.0.0.1.4242 TIME_WAIT > tcp0 0 127.0.0.1.4952 127.0.0.1.4242 TIME_WAIT > tcp0 0 127.0.0.1.4951 127.0.0.1.4242 TIME_WAIT > tcp0 0 127.0.0.1.4950 127.0.0.1.4242 TIME_WAIT > tcp0 0 127.0.0.1.4949 127.0.0.1.4242 TIME_WAIT > tcp0 0 127.0.0.1.4948 127.0.0.1.4242 LAST_ACK > tcp0 0 127.0.0.1.4947 127.0.0.1.4242 CLOSE_WAIT > tcp0 0 127.0.0.1.4945 127.0.0.1.4242 TIME_WAIT > tcp0 0 127.0.0.1.4944 127.0.0.1.4242 TIME_WAIT > tcp0 0 127.0.0.1.4942 127.0.0.1.4242 TIME_WAIT > tcp0 0 127.0.0.1.4940 127.0.0.1.4242 FIN_WAIT_1 > tcp0 0 127.0.0.1.4938 127.0.0.1.4242 FIN_WAIT_1 > tcp0 0 127.0.0.1.4937 127.0.0.1.4242 TIME_WAIT > tcp0 0 127.0.0.1.4936 127.0.0.1.4242 TIME_WAIT > > > Are tcp connections going through lo0 ever supposed to end up like this? I > thought everything that went through lo0 was supposed to be.. well.. > instant and mostly lossless. Any ideas? > > Kevin Hi, does that happen for any apps? Could you please give me info about what is the apps which use the port 4242? Thanks, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release - usr.bin/ssh error
Hi, I'm running a make release with sources current as of 7pm EST. I'm in the process of trying to figure out the following failure. ===> usr.sbin/ktutil install -c -s -o root -g wheel -m 555 ktutil /usr/sbin install -c -o root -g wheel -m 444 ktutil.8.gz /usr/share/man/man8 cd /pub/FreeBSD/usr.bin/ssh; make MAKE_KERBEROS5=yes cleandir && make MAKE_KERBEROS5=yes obj && make MAKE_KERBEROS5=yes depend all install cd: can't cd to /pub/FreeBSD/usr.bin/ssh *** Error code 2 I'm in the process of tracking this down. If anyone has any pointers, I'd appreciate the help. If this has already been fixed and I haven't seen the mail/cvs commit yet, please let me know that too... :-) Thanks! John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP! IPC security (Re: cvs commit: src/sys/kern sysv_ipc.c(fwd))
4.0 had a security bug which would let any user EXCEPT root delete a SYSV semaphore (the sense of a test was reversed). No other releases were affected - rebuild your kernels if this is an issue. Good catch, Brian! For "revision 1.8" in the below read "revision 1.9" (Jan 30, 1999). -- Forwarded message -- Date: Wed, 1 Mar 2000 21:03:22 -0500 (EST) From: Brian Dean <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: cvs commit: src/sys/kern sysv_ipc.c [SNIP - KK] The bug is very easily tested/verified: just create a semaphore, then, as root, try to delete it. If the bug is there, you will get "Operation not permitted". Then try to delete it using an account other than the one that created it, which is supposed to fail, but works fine. It appears that it might have cropped up at version 1.8 sys/kern/sysv_ipc.c. At version 1.8, the check: if (cred->cr_uid == 0) was replaced with: if (suser(cred, (u_short *)NULL)) I'm pretty sure this is what did it, since suser() returns 0 if you _are_ superuser, and an error otherwise (even back then, I checked). [END SNIP] Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! IPC security (Re: cvs commit: src/sys/kern sysv_ipc.c(fwd))
> -- Forwarded message -- > Date: Wed, 1 Mar 2000 21:03:22 -0500 (EST) > From: Brian Dean <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: cvs commit: src/sys/kern sysv_ipc.c > > [SNIP - KK] > > The bug is very easily tested/verified: just create a semaphore, then, > as root, try to delete it. If the bug is there, you will get > "Operation not permitted". Then try to delete it using an account > other than the one that created it, which is supposed to fail, but > works fine. > > It appears that it might have cropped up at version 1.8 > sys/kern/sysv_ipc.c. At version 1.8, the check: > > if (cred->cr_uid == 0) > > was replaced with: > > if (suser(cred, (u_short *)NULL)) It had rotted further since then (as half threatened in rev.1.9) to passing the process pointer so that it can mess up p->p_acflag. This results in the ASU flag always being set in p->p_acflag for root, although no special privilege is required for root to operate on ipc objects owned by root, and especially, no special privilege is required to determine whether an operation is permitted. The ASU flag should only be set if root privilege is used. Most callers of ipcperm() are committed to doing the operation that they check for using ipcperm() if ipcperm() succeeds, so rearrangement of ipcperm() to check for root privilege last would fix most cases. The corresponding code in ufs_access() uses the (cred->cr_uid == 0) check. ufs_access() is used internally (via VOP_ACCESS()) in much the same way as ipcperm(). This seems to give the opposite bug in many callers -- ASU is not set when root privilege is used. Rearranging ufs_access() to check for root privilege last wouldn't help, because ufs_access() shouldn't set ASU -- it is used for the access() system call which doesn't use any special privilege. Now the code has rotted to having an almost unused variable and one other style bug: int error; ... error = suser(p); if (!error) This should be written much like the check in rev.1.8: if (suser(p) == 0) Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/dev/random limited to irq < 16
I found out much to my surprise that our SMP box is not collecting ANY entropy for /dev/random. All the interesting IRQs are over 16, and nobody uses the console. >From sys/i386/i386/mem.c 1.79: /* * XXX the data is 16-bit due to a historical botch, so we use * magic 16's instead of ICU_LEN and can't support 24 interrupts * under SMP. */ Why don't we just flip this from a 16 bit to a 32 bit parameter in time for 4.0-RELEASE? Should just require a quick fiddle in mem.c and in rndcontrol. Stephen. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
d: /kernel: malformed input file (not rel or archive) ??
If i try to load the example in /usr/src/share/exaples/lkm/misc/module/misc_mod.o i get the following. Pleeaaas help ? borg# modload ./misc_mod.o ld: /kernel: malformed input file (not rel or archive) modload: /usr/bin/ld: return code 1 -- Johan Kruger ( B.Ing Electronic Engineering ) Developement Engineer Nanoteq PTA ( 012 6727000 ) e-mail : [EMAIL PROTECTED] e-mail : [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: d: /kernel: malformed input file (not rel or archive) ??
Johan Kruger wrote: > If i try to load the example in > /usr/src/share/exaples/lkm/misc/module/misc_mod.o i get the following. > Pleeaaas help ? > > borg# modload ./misc_mod.o > ld: /kernel: malformed input file (not rel or archive) > modload: /usr/bin/ld: return code 1 What FreeBSD release you are using? If it is 2.2 than the -current is wrong place to ask, but if it is 4.0 than you must note that the lkm subsustem has been abolished long time ago in favor of the new kld system. See man kld and /usr/share/examples/kld for details. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: d: /kernel: malformed input file (not rel or archive) ??
On Wed, 1 Mar 2000, Johan Kruger wrote: > If i try to load the example in > /usr/src/share/exaples/lkm/misc/module/misc_mod.o i get the following. > Pleeaaas help ? LKMs are deprecated in favour of KLDs. Do you have options LKM in your kernel if you really wnt to play with the old technology? Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
