reboot -p
Currently, when reboot is invoked with the '-p' command line flag (powerdown), it performs a shutdown with RB_HALT|RB_POWEROFF. In some situations, it can be useful to try to perform a poweroff, but reboot if it fails (e.g. when you are shutting down the system as a result of a power failure, you want the system to reboot, *not* stay down, if power was restored after the start of the shutdown procedure). It would be nice if reboot was changed to pass only RB_POWEROFF (without RB_HALT) when invoked with '-p'. Of course halt(8) whould be unaffected and still pass RB_HALT|RB_POWEROFF when invoked as halt -p. What do others think of this change: --- reboot.cThu Aug 2 12:01:20 2001 +++ /tmp/reboot.c Wed Dec 26 13:03:45 2001 @@ -93,7 +93,7 @@ break; case 'p': pflag = 1; - howto |= (RB_POWEROFF | RB_HALT); + howto |= RB_POWEROFF; break; case 'q': qflag = 1; -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
delock pccard to pci adapter
I probablz made the mistake not to look into the hardware compatibility list when buying this card to build a wireless access point using an ELSA Airlancer MC-11 PCMCIA with tis DeLock (www.delock.de) Any clues to get it working with a FreeBSD 4.4R? :r ls :r l Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-RELEASE #10: Wed Dec 26 10:38:18 CET 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/BGATEI4B Timecounter "i8254" frequency 1193182 Hz CPU: AMD Am5x86 Write-Through (486-class CPU) Origin = "AuthenticAMD" Id = 0x4e4 Stepping = 4 Features=0x1 real memory = 67108864 (65536K bytes) avail memory = 62201856 (60744K bytes) Preloaded elf kernel "kernel" at 0xc0314000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc031409c. npx0: on motherboard npx0: INT 16 interface pcib0 on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 ncr0: port 0xe800-0xe8ff mem 0xfafef000-0xfafef0ff irq 9 at device 1.0 on pci0 isab0: at device 2.0 on pci0 isa0: on isab0 de0: port 0xe400-0xe47f mem 0xfafee000-0xfafee07f irq 10 at device 4.0 on pci0 de0: SMC 21041 [10Mb/s] pass 2.1 de0: address 00:e0:29:0b:7a:4e pci0: at 5.0 irq 11 chip1: irq 12 at device 6.0 on pci0 orm0: at iomem 0xc-0xc7fff,0xe8000-0xebfff,0xec000-0xe on isa0 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 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <8 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 flags 0x10 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port pcfclock0: on ppbus0 ppi0: on ppbus0 pps0: on ppbus0 plip0: on ppbus0 ed0 at port 0x280-0x29f iomem 0xcc000-0xc irq 5 on isa0 ed0: address 00:00:c0:d2:c2:9e, type SMC8216/SMC8216C (16 bit) de0: enabling 10baseT port IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited to 100 packets/entry by default ad0: 6149MB [13328/15/63] at ata0-master BIOSPIO Waiting 4 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s1a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 516MB (1057758 512 byte sectors: 64H 32S/T 516C) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: delock pccard to pci adapter
On Wed, Dec 26, 2001 at 01:21:42PM +0100, Christoph Kukulies wrote: > I probablz made the mistake not to look into the > hardware compatibility list when buying this card > to build a wireless access point using an ELSA > Airlancer MC-11 PCMCIA with tis DeLock (www.delock.de) Your pcmcia chip is not supported by your kernel. You should first check your kernel config for pcmcia support. And then pccardc dumpcis if pcmcia works but you card is not indentified. > chip1: irq 12 at device 6.0 on pci0 Your bridge is only probed as a generic pci chip. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Swap not used *at**all*
Is this normal: andrei@vogon:~ 2:05:49pm% swapinfo Device 1K-blocks UsedAvail Capacity Type /dev/ad4s1b5253440 525344 0%Interleaved This machine is running with 256MB RAM and a 512MB swap device. Swap usage is zero even when running X and postgress and aolserver with a running instance of OpenACS-4. systat(1) with vmstat option shows no activity on swap either. The system is a recent -CURRENT (21-Dec). -- Andrei P.S. From -questions, please cc: me in reply To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fix for broken "burncd msinfo" PR#27593
>Date: Wed, 26 Dec 2001 00:02:23 +1000 >From: Stephen McKay <[EMAIL PROTECTED]> >A number of people have complained that "burncd msinfo" returns the wrong >value when there are already multiple sessions on a CD. This is true, >and is bug bin/27593. >Since I burn a lot of multisession CDs, and have been working out the mkisofs >-C values by hand with the help of "cdcontrol info", I thought now would be a >good time to fix this bug. >Unfortunately, I've found that burncd won't work with SCSI burners, and >the only ATAPI burner I have is at work, and well, it's Christmas and all >that. So this is completely untested, though I believe it should work. OK; I corresponded with Stephen, and since I have an ATAPI CD burner, I tested it (under -CURRENT). The patch works as advertised, as far as I can tell: I was able to make a multi-session CD following Stephen's suggestions, and using output from "cdcontrol info" as a reference, the output from "burncd msinfo" is broken (in that it always returns "0" for the first LBA of the last track) without Stephen's patch, but with the patch applied, the LBAs reported by "burncd msinfo" agree with those reported by "cdcontrol info". >I hope this can make it into 4.5. Likewise -- though my perceived need for it is less than Stephen's, it would be a Good Thing to have this (apparently easily-fixed bug) fixed. Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: multiple audio devices and /dev/dsp*
> on -CURRENT though /dev/dsp seems to be conjured up by the devfs system > and i have simply been unable to find a way to make it point my prefered > device node ... in my case /dev/dsp1. > > Am i missing something obvious here ... or is it simply not possible on > -CURRENT to do something similair to -STABLE ? sysctl hw.snd.unit= where is the unit to use by default. this can also be set from the loader. -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Swap not used *at**all*
In the last episode (Dec 26), Andrei Popov said: > > Is this normal: > > andrei@vogon:~ > 2:05:49pm% swapinfo > Device 1K-blocks UsedAvail Capacity Type > /dev/ad4s1b5253440 525344 0%Interleaved > > This machine is running with 256MB RAM and a 512MB swap device. Swap usage > is zero even when running X and postgress and aolserver with a running > instance of OpenACS-4. Try this: dd if=/dev/zero of=/dev/null bs=192m count=1 That should force some swapping :) -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Swap not used *at**all*
On Wed, Dec 26, 2001 at 09:19:05AM -0600, Dan Nelson wrote: > In the last episode (Dec 26), Andrei Popov said: > > > > Is this normal: > > > > andrei@vogon:~ > > 2:05:49pm% swapinfo > > Device 1K-blocks UsedAvail Capacity Type > > /dev/ad4s1b5253440 525344 0%Interleaved > > > > This machine is running with 256MB RAM and a 512MB swap device. Swap usage > > is zero even when running X and postgress and aolserver with a running > > instance of OpenACS-4. > > Try this: > > dd if=/dev/zero of=/dev/null bs=192m count=1 > > That should force some swapping :) It sure does :) But the question still remains -- is it not odd that there's no swapping when running X, nor is there one when running fairly expenmsive Postgres selects et al? > > -- > Dan Nelson > [EMAIL PROTECTED] -- Andrei To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Swap not used *at**all*
In the last episode (Dec 26), Andrei Popov said: > On Wed, Dec 26, 2001 at 09:19:05AM -0600, Dan Nelson wrote: > > In the last episode (Dec 26), Andrei Popov said: > > > Is this normal: > > > > > > Device 1K-blocks UsedAvail Capacity Type > > > /dev/ad4s1b5253440 525344 0%Interleaved > > > > > > This machine is running with 256MB RAM and a 512MB swap device. > > > Swap usage is zero even when running X and postgress and > > > aolserver with a running instance of OpenACS-4. > > > > Try this: dd if=/dev/zero of=/dev/null bs=192m count=1. That > > should force some swapping :) > > It sure does :) > > But the question still remains -- is it not odd that there's no > swapping when running X, nor is there one when running fairly > expenmsive Postgres selects et al? Not necessarily. It depends on your configuration. If you tell Postgres to use (say) 192MB of memory, then it will definitely swap, just like the dd did. If you only configure it for 64MB, then it could easily coexist with X, Netscape, and other medium-memory-use applications without swapping. I wouldn't expect AOLServer to consume much memory at all. As comparison, I have a 512MB box that runs mysql (256MB), squid (75MB), and roxen (20MB), and occasionally X+mozilla (64MB). It has 30MB of swap used at the moment, which was probably just used once. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Kernel broken
Sources from: Dec, 26 11:28 CET linking kernel procfs.o: In function `procfs_init': procfs.o(.text+0x1ac): undefined reference to `pfs_create_link' procfs.o(.text+0x1c0): undefined reference to `pfs_create_dir' procfs.o(.text+0x1db): undefined reference to `pfs_create_file' procfs.o(.text+0x1f4): undefined reference to `pfs_create_file' procfs.o(.text+0x213): undefined reference to `pfs_create_file' procfs.o(.text+0x229): undefined reference to `pfs_create_file' procfs.o(.text+0x248): undefined reference to `pfs_create_file' procfs.o(.text+0x261): more undefined references to `pfs_create_file' follow procfs.o: In function `procfs_init': procfs.o(.text+0x330): undefined reference to `pfs_create_link' procfs.o: In function `_procfs_mount': procfs.o(.text+0x36b): undefined reference to `pfs_mount' procfs.o: In function `_procfs_init': procfs.o(.text+0x385): undefined reference to `pfs_init' procfs.o: In function `_procfs_uninit': procfs.o(.text+0x39d): undefined reference to `pfs_uninit' procfs.o(.data+0x68): undefined reference to `pfs_unmount' procfs.o(.data+0x6c): undefined reference to `pfs_root' procfs.o(.data+0x74): undefined reference to `pfs_statfs' *** Error code 1 Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel broken
Jan Stocker wrote: > Sources from: Dec, 26 11:28 CET > > linking kernel > procfs.o: In function `procfs_init': > procfs.o(.text+0x1ac): undefined reference to `pfs_create_link' > procfs.o(.text+0x1c0): undefined reference to `pfs_create_dir' > procfs.o(.text+0x1db): undefined reference to `pfs_create_file' > procfs.o(.text+0x1f4): undefined reference to `pfs_create_file' [...] Please read /usr/src/UPDATING : 20011203: The procfs pseudo-filesystem has now been converted to use the pseudofs framework. If you have 'options PROCFS' in your kernel config, you'll need to add 'options PSEUDOFS' if it's not there already. Maxime -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel broken
Xcuse me...overread it... Jan On Wed, 2001-12-26 at 19:46, Maxime Henrion wrote: > Jan Stocker wrote: > > Sources from: Dec, 26 11:28 CET > > > > linking kernel > > procfs.o: In function `procfs_init': > > procfs.o(.text+0x1ac): undefined reference to `pfs_create_link' > > procfs.o(.text+0x1c0): undefined reference to `pfs_create_dir' > > procfs.o(.text+0x1db): undefined reference to `pfs_create_file' > > procfs.o(.text+0x1f4): undefined reference to `pfs_create_file' > [...] > > Please read /usr/src/UPDATING : > > 20011203: > The procfs pseudo-filesystem has now been converted to use the > pseudofs framework. If you have 'options PROCFS' in your > kernel config, you'll need to add 'options PSEUDOFS' if it's > not there already. > > Maxime > -- > Don't be fooled by cheap finnish imitations ; BSD is the One True Code To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Swap not used *at**all*
* Andrei Popov <[EMAIL PROTECTED]> [011226 12:21] wrote: > On Wed, Dec 26, 2001 at 09:19:05AM -0600, Dan Nelson wrote: > > In the last episode (Dec 26), Andrei Popov said: > > > > > > Is this normal: > > > > > > andrei@vogon:~ > > > 2:05:49pm% swapinfo > > > Device 1K-blocks UsedAvail Capacity Type > > > /dev/ad4s1b5253440 525344 0%Interleaved > > > > > > This machine is running with 256MB RAM and a 512MB swap device. Swap usage > > > is zero even when running X and postgress and aolserver with a running > > > instance of OpenACS-4. > > > > Try this: > > > > dd if=/dev/zero of=/dev/null bs=192m count=1 > > > > That should force some swapping :) > > It sure does :) > > But the question still remains -- is it not odd that there's no swapping > when running X, nor is there one when running fairly expenmsive Postgres > selects et al? No, the system tries pretty hard not to swap. In fact swapping is really a bad thing to have happen on a loaded machine as it can result in a cascade failure. If you look in the archives for Matt Dillon's postings on "cascade failure" it will explain things a lot better. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductable donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vm_zeropage priority problems.
Luigi Rizzo wrote: > > Don't know how interesting this can be, but i am writing > (no plans to commit it, unless people find it interesting) > some code to implement a weight-based instead of priority-based > scheduler. The code is basically the WF2Q+ scheme which is > already part of dummynet, adapted to processes. > It is quite compact, and i think i can make it reasonably > compatible with the old scheme, i.e. a sysctl var can be > used to switch between one and the other with reasonably > little overhead. > > This would help removing the ugly property that priority-based > have, which is that one process can starve the rest of the system. Look for "QLINUX". There's a nice paper on "Weighted Fair Share" scheduling referenced on the page, as well as a couple of LRP references. Note that someone recently did a port of the LRP + Resource Containers code to FreeBSD 4.4 (Terrible Rice Univeristy License, though). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
Doug White wrote: > > Dropping -stable crosspost. > > For those of you with this mouse -- we really need the output of 'usbdevs > -v' with the mouse attached. > > I'm betting that this isn't a standard USB mouse and requires a special, > proprietary driver. :( The very idea of a "winmouse" gives me the heebee-jeebees... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
