Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))
On Fri, 16 Jul 1999, Daniel C. Sobral wrote: > Technical follow-up: > > Contrary to what I previously said, a number of tests reveal that > Solaris, indeed, does not overcommit. All non-read only segments, Neither does HP/UX 10.x. (Haven't got an 11 box handy to check.) The memory allocation process is something like this: 1) reserve is allocated from a swap area. Preference is given to swap devices, even if a swap file system has a higher priority. 2) If there is no space on a swap device, swap is allocated from a swap filesystem, if one is configured. If there is nothing to be allocated in a swap filesystem, the kernel attempts to grow the swap file on a filesystem by swchunk (a tunable, default 2MB, I think). (Swap on filesystems starts at zero or swchunck, and is grown as needed up to the limit spec'd at swapon(1M) time.) 3) If this fails, either because there is no space on the file system, or the swapfile has reached its limit, memory (actual core) is allocated. The system tunable swapmem_on determines whether memory is used for swap reserve or not. Default is to use it. 4) If there isn't swap to reserve, the request fails, even if none of the reserved swap is used. The swapinfo(1M) man page makes this quite clear: +Requests for more paging space will fail when they cannot be satisfied by reserving device, file system, or memory paging, even if some of the reserved paging space is not yet in use. Thus it is possible for requests for more paging space to be denied when some, or even all, of the paging areas show zero usage - space in those areas is completely reserved. The upside of this is that if you do run out of swap, the kernel doesn't kill random processes. The downside is, I have seen 4GB boxes, with plenty of swap, run out with less than a gig of memory actually in use. Oh, and if you swap to a filesystem, you can fill it up, without actually using any of the space. I don't know which behaviors is more bogus. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: softupdates on root partition, no floppy
On Mon, 19 Jul 1999, Matthew D. Fuller wrote: > No, don't leave it alone, make it even SLOWER than usual! > /dev/da0s1a on / (local, synchronous, writes: sync 114 async 3850) > > Question of the day: Why do I have async writes on a sync partition? Because only meta-data writes are done synchronously. Data is still done asynchronously. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: replacing grep(1)
On Tue, 27 Jul 1999, Sheldon Hearn wrote: > In this case, I'm all for the change, since I don't use grep for serious > regex work and the readability gain outweighs any loss of performance. > you probably feel the same way. Out opinions are those of developers, > though. It's always worth remembering that. Does any have numbers about how much slower the new grep is? I have been using the port (version 3) for my interactive grepping, and havedn't noticed a speed difference. I have been using it on zippy machines though, where 30% hit wouldn't be noticed. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Hey kernel hackers, this is worth a read.
On Fri, 30 Jul 1999, Alex Zepeda wrote: > On Fri, 30 Jul 1999, Jordan K. Hubbard wrote: > > > http://features.linuxtoday.com/stories/8191.html > > > > A story on upcoming plans for the Linux 2.4 kernel. Since they're > > going after a lot of the same performance goals we are, it's worth a > > read. > > It seems to me that a lot of the features mentioned are already in > -CURRENT and some in -STABLE. Hmm. I rather liked this paragraph: There are some suprising things missing there. No ISA PnP, just now unifiying read and write buffer caches. There are also things were they appear to be ahead of FreeBSD, like SMP. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Mentioning RFC numbers in /etc/services
On Mon, 2 Aug 1999, Brian Somers wrote: > Yes, but do it the other way 'round - strtol first, if it's not all > numeric, getservbyname(). Can't you have all numeric service names? > David scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Building a new kernel
On Wed, 4 Aug 1999, Warner Losh wrote: > > I have a freebsd-stable system. I can't build a kernel for > freebsd-current on that system unless I upgrade my compiler to egcs. > Will this cause problems for our upgrade proceedure? > > gcc 2.7.2.3 doesn't like i386/include/atomic.h. It complains about > bad assmbler contraints. I upgraded a -STABLE system to -CURRENT using source a month or two ago. The first step is to build the new toolchain, so you shouldn't ever be compiling a new kernel with an old compiler. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Building a new kernel
On Wed, 4 Aug 1999, Warner Losh wrote: > In message > David > Scheidt writes: > : I upgraded a -STABLE system to -CURRENT using source a month or two > : ago. The first step is to build the new toolchain, so you shouldn't > : ever be compiling a new kernel with an old compiler. > > In the past, we've given advise to build a new kernel, then reboot and > do a make upgrade or make world (depending on if you were branch > jumping or not). Also, as part of the aout-to-elf target, a kernel is > built... Read the docs? Who me? It sounds like the 3.X to 4.0-RELEASE documentation should say not to do this. Unless, of course, gcc-2.95 is imported before t hen. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: s...@home bug?
On Fri, 13 Aug 1999, Peter Jeremy wrote: > I've been attempting to run s...@home on -current. Has anyone else > found that both setiathome-1.1.i386-unknown-freebsd4.0 and > setiathome-1.2.i386-unknown-freebsd3.2 fail with the following > message after downloading a work unit: > > Scanning data file > Error reading data: -23 > Bad file header > > The same work unit works with setiathome-1.3.i386-unknown-freebsd2.2.8. You are working through a proxy? Versions prior to 1.3 didn't deal well with some proxies. I don't know the details, but some proxies re-write data in a form that s...@home won't deal with. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Q: panic: pipeinit: cannot allocate pipe -- out of kvm -- code = 3
On Thu, 12 Aug 1999, Addr.com Web Hosting wrote: > It happened more often then I am comfortable with (twice per day on one > occasion). This is a machine running FreeBSD 3.0-STABLE on dual PII 400 > with 1GB of ram and a DPT raid card. The machine is running semi-heavy load > (http/mail/telnet/ftp), as well as nfs server and client. What could I do > to avoid this sort of panic in the future? The first thing I would do is upgrade to a more recent -STABLE. Lots of things have changed since 3.0-STABLE. Even if this particular thing hasn't, there have been a number of nfs improvements, as well as assorted other changes. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD XFS Port & BSD VFS Rewrite
On Sat, 14 Aug 1999, Brian F. Feldman wrote: > On Sat, 14 Aug 1999, James Howard wrote: > > > > > Would it be legal to strip the BSD license of say, inetd and put a GPL on > > it? Many in the Linux community seem to think this is true but I thought > > that'd be just as bad as my BSD licensed GCC distribution :) > > No. You'd have to modify the GPL to include the copyright and BSD clauses. There is also the clause that says "You may not impose any further restrictions on the recipients' exercise of the rights granted herein.", which could be taken to mean you can't use BSD-licensed code, since that requires "This product includes software developed by the University of California, Berkeley and its contributors." be attached to derived works. > > But what would be interesting is: I'm fairly sure that under the terms of the > GPL > the end-user may opt to use a later version at their discretion. Now, if one > were > to buy out the FSF... That is something that always bothered me. I have taken it as the "When we realize that we won't take over the world, we will go to a sensible license" clause. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Sat, 14 Aug 1999, Nick Sayer wrote: > dannyman wrote: > > > > Uhmmm, what if we don't have a floppy drive? > > Do the old SunOS trick: > > 1. Boot single user. > > 2. dd the boot floppy image to your swap partition. To really do the ScumOS trick, you should just assume that the swap partition is sd(0,0,0)b. GRRR! To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: lpd security check for changed-file vs NFS
On Tue, 17 Aug 1999, Garance A Drosihn wrote: > At 6:37 PM -0700 8/17/99, Matthew Dillon wrote: > >If you removed the stat test, I would simply get rid of the -s > >option entirely - require that all files be queued to the print > >spool. > > The administration would kill me. I would prefer to avoid that. > > (note that the check isn't completely removed, it's "only" nullified > for NFS-mounted files. We use AFS for most things here, so the vast Couldn't you turn it off only for NFS mounted files? David scheidt > > Any advice on how to kick AIX so the st_dev+st_ino check will work > right is also welcome. It baffles me why AIX does things the way it > does. It kinda looks like the values it uses are pointers to some The joke about AIX is that it was created by aliens who were given the UNIX documentation, but no example system. I have seen very little that suggests this to be untrue. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: lpd security check for changed-file vs NFS
On Wed, 18 Aug 1999, Matthew Dillon wrote: > :For the general case (eg the code checked into the system), the check > :needs to remain enabled. Anything else is insecure. > : > :Warner Oh, absolutely. However, one of the reasons people use an operating system they have source to is to make it work for them. > > I have to agree... whenever one starts discussing weird, esoteric > workarounds one inevitably introduces security holes. I really think > just disabling the -s option may be the best solution. It is apparent that I was unclear. What I meant was use the fstat test for local files. For NFS mounted files, don't use the test, since it doesn't work, and don't allow the the -s option. (Better would be to accept, and ignore the -s, perhaps producing a warning?) David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On Mon, 23 Aug 1999, Cillian Sharkey wrote: > Keeping records would be handy alright..but cutting out all > the "everything is ok" msgs would reduce reading time..having > an option for full report OR just the important results should satisfy > everyone.. What I do run things through a filter that shows only things that I find interesting. It is only a few dozens of lines of shell. I don't actually do this for FreeBSD daily reports, because there isn't enough there to worry about, but for my application stuff it works a treat. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Please review: rc file changes
On Fri, 27 Aug 1999, Doug wrote: > > Ok, revised diff attached. I made the case indentation change and some > of > sheldon's suggestions are incorporated. I also neglected to mention > previously that I tuned up a few of the comments in the file, as well as > error output. I also was more rigorous about making whitespace consisten on > this pass. Removing double spaces, converting spaces to tabs, etc. This is Why only one space after full stops? I find two much more readable. In general though, I like the case insensitivity and the -r v. -f. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Intel Merced FreeBSD??? Intel? - NOT
On Fri, 27 Aug 1999, Sean Eric Fagan wrote: > In article > > you write: > Look, people, the Merced WILL NOT excuse PA-RISC code directly. It will be > done via emulation/translation, and only a certain particular OS will be > supported (HP-UX 11, I believe they stated -- since HP-UX 11 runs almost all > HP-UX 10.* applications with no problem, I am _guessing_ that this means they > will continue to work). I just asked one of our HP people about this. He says that anything that runs on HP 11.0 PA-RISC will run on IA64. It is his understanding that this includes not only 10.x stuff, but also 9.x and 8.x stuff. We have stuff that runs on 11 that was originally compiled for 8.0. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Intel Merced FreeBSD???
On Sun, 29 Aug 1999, Wes Peters wrote: > > Uh, no, HP has already admitted that when Merced ships it will be slower > than current-generation PA-RISC CPUs. Which means it will also be slower > than Alpha, PowerPC, and UltraSPARC processors you can buy now. > Which is just going to make *everyone* jump ship for an expensive, slow chip, with unproven compilers. Yeah! David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: make aout-to-elf-build Failing
On Wed, 1 Sep 1999, John Birrell wrote: > If there is someone with a scratch disk on which they can install 2.2.8 > (or 2.2.7 or 2.2.6) and do a `make aout-to-elf' and report the results, > we could get this sorted out. I don't have the hardware to do that > anymore. Any list-lurkers want to help out? Assuming I can find my 2.2.6 CDs, I will do this tonight. You don't even need to send me the patch. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: make aout-to-elf-build Failing
On Wed, 1 Sep 1999, John Birrell wrote: > On Tue, Aug 31, 1999 at 08:27:00AM -0700, Doug wrote: > > John Birrell wrote: > a patch to change one word in /usr/src/usr.bin/make/main.c?! Please take > a few moments to have a look for "unknown" in that file. Sigh. > > If there is someone with a scratch disk on which they can install 2.2.8 > (or 2.2.7 or 2.2.6) and do a `make aout-to-elf' and report the results, > we could get this sorted out. I don't have the hardware to do that > anymore. Any list-lurkers want to help out? The obvious one-line fix appears to work. My 2.2.6 to RELENG_3 build hasn't finished yet, but it makes it past the point where it fails due to machine_arch be ing undefined. Do I need to check if 2.2.6 to -CURRENT works? David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: nobody knows the answer?
On Thu, 2 Sep 1999, Evren Yurtesen wrote: > I am using 3.2-Stable and I have a 9GB disk drive used as cache for > squid proxy. I have changed the min free space with tunefs program to 0 > but now I have a problem. Even though I have 250MB free space on the > file system, I get file system full error. You have almost certainly run out of file fragments. Space on FFS filesystems is allocated in the from of blocks, which are divided into fragments. These blocks are not the same as the physical disk blocks, but are a number of sequential disk blocks. The default FFS block size is 8KB. Each FFS block is subdivided into fragments. The default is 8 fragments per block, giving a default frag size of 1KB. A file on an FFS filesystem is made up some number of full blocks, except for the last block in a file, which may be a partial block. One of the reasons that FFS reserves 8% of the disk space for its own use is to efficently handle fragmented blocks. When a file is extended, the filesystem tries to allocate a full block for it. Having this reserve means that it is unlikely that the filesystem will run out of full blocks. What has likely happened on your machine is that you have lots of small files, which take up, say, 5 frags of a block. That leaves you with a bunch of fragmented blocks that cannot contain a whole file. Since FFS can't split a file over multiple fragmented blocks, you are told you are out of space. df(1) reports the amount of free fragments. Since you don't have any free full blocks, you can't extend files. To prevent this from happening again, increase the the min free space back to its default setting. You will not have this problem again, and you will very likely see a substantial improvement in filesystem speed. Most of the tunefs(8) tunables are not something that need to tuned by the user. If you are tuning them, you should have a full understand of what the tunables do, and what the side effects of fiddling with them are. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: PCI modems do not work???
On Mon, 6 Sep 1999, Kevin Day wrote: > > This is pretty much untrue, because not all applications (industrial > > applications) for modems have a PC to talk to, so it's totally > > impossible for conventional modems to go away. I used to make my living > > tending large banks of modems, and not all applications are 56K even, > > because they are only justified if you have a very large modem pool. There are lots of applications where speeds of greater than 1200 bps aren't justified. > non-winmodem model is about 3x the Winmodem style. (You can buy winmodems > very cheap, since everyone is making them now. You can't buy non-winmodem's You can buy winmodems cheap because they are cheap crap. they force the host system to do everything useful. Network quake players will keep the real modem on a PCI card going for a while yet. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Init(8) cannot decrease securelevel
On Tue, 7 Sep 1999, KATO Takenori wrote: > DDB does not provide enough security. Though securelevel cannot be > changed, > > (1) Turn off power. > (2) Boot as single-user mode. Setting the console as insecure should protect against this. > or > > (1) Turn off power. > (2) Remove HDD. > (3) Mount on another FreeBSD box. > (4) Edit a file in the HDD. > (5) Return HDD. > (6) Reboot. > > is available. There isn't a whole lot you can do to protect a system against crackers who have physical access to the system. Heavily armed guards would help, but I don't expect to see them as part of the base distribution anytime soon. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: The usage of MNT_RELOAD
On Wed, 8 Sep 1999, Zhihui Zhang wrote: > > On Wed, 8 Sep 1999, Luoqi Chen wrote: > > > It is created almost exclusively for fsck (and similar programs) to update > > the in core image of the superblock (of / in single user mode) after the > > on disk version has been modified. > > > > Does fsck have to run on a MOUNTED filesystem? If so, your answer makes > sense to me: if fsck modifies the on-disk copy of the superblock, it does > not have to unmount and then remount the filesystem, it only need to > reload the superlock for disk. The root filesystem is mounted when it is fscked, as it is difficult to run fsck, which lives on the root filesystem, without mounting the root filesystem. You shouldn't run fsck on a mounted filesystem, except for this. The results are generally not fun. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: damn ATX power supplies...
On Fri, 10 Sep 1999, Andrew Reilly wrote: > > How is it that BIOS settings can affect this? Do they fiddle > with some battery-backed switch on the motherboard? The ATX power supply has a lead or two that are always powered. This allows the machine do softpower on. It also means that the bios can tell the power supply to go on whenver that the signal is present. Macintoshes have done something like this since the Mac II. most of them had a powr switch that could be configured to always be on when plugged in. I wish someone would make such an ATX power supply! David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: X mailers (was Re: ANNOUNCE: Linux ABI/SDK standards for Ope
On Fri, 10 Sep 1999, Daniel O'Connor wrote: > > Does it do IMAP? I have only seen *1* emailer which does IMAP properly > (xfmail) > all the others either don't support it at all, or treat IMAP like POP (ie just > fetch mail from INBOX). Netscape does, actually. I set up a friend's computer to do this, over an ssh-forwarded local port, even. It all more less "Just worked". On a win98 box, even. shudder. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: X mailers (was Re: ANNOUNCE: Linux ABI/SDK standards for Ope
On Fri, 10 Sep 1999, Daniel O'Connor wrote: > > On 10-Sep-99 Florent Parent wrote: > > I've been trying different MUAs that would allow me to read my mail > > under FreeBSD and NT (dual boot laptop) while sharing the same mail > > folders (shared DOS partition). So far, only VM/Xemacs allowed me to > > do that. Even Netscape FreeBSD/NT use different mechanisms to build > > its "folder summaries" :( > > I'd be interested to hear if anyone has a similar config. (i guess > > I have Cyrus IMAP on my server box and my workstation dual boots freebsd/win95 > so I use xfmail under freebsd and netscape under windows and it works fine :) > This was what I was going to suggest. If you are lucky, you might be able to find an NT imap server that will get along with sharing the folders with a FreeBSD one, so you can keep everything local. I haven't looked, because I don't do windows, except underdress, and never on hardware I own. I don't even have a license of MS-DOS. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Bug in dd seeking beyond 2G
On Wed, 15 Sep 1999, Warner Losh wrote: > In message <199909151928.vaa26...@dorifer.heim3.tu-clausthal.de> Oliver > Fromme writes: > : It only works on two's-complement machines, though, but I'm not > : aware of any FreeBSD port to an architecture that doesn't use > : two's-complement numbers... > > I'm not aware of any one's-complement machine that was manufacture > after about 1980... Not even NetBSD has any one's-complement machines > that it supports :-) Aren't the the Bull GCOS 7 machines ones complement? Or the Unisys 1100/2200 36 bit machines? I do know that some CDC 6600 clones were put together in the '80s, and they would have been ones complement. Software is expensive, building machines out of FPGAs isn't... Negative zero isn't dead yet! To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: cache-friendly scheduling for SMP
On Thu, 16 Sep 1999, Keith Stevenson wrote: > On Thu, Sep 16, 1999 at 12:25:52PM +, greg wrote: > > I'm trying to run 1-2 processes with very large memory footprints on my P2 > > SMP > > machine. I'm finding that the process switches cpu's quite often, which > > obviously isn't good for the caches on the CPU. > > > > Can anybody point me to a paper, mailing list discussion, etc. that > > discusses > > scheduling processes to not thrash the cpu caches? Or if there's anything > > in > > place, how I can take advantage of it, etc. I got stumped on the idea a > > while > > ago, so I'm really curious... > > > All I've heard is a marketing presentation. I haven't seen this is the real > world yet. > > > IBM just released a new version of AIX (4.3.3). One of the big features is > CPU affinity in order to made better use of the CPU caches. They claim to > have done this be having a separate run queue for each CPU. Someone posted some stuff about this to -SMP a bit ago. They had produced a cheduler that prefereed to run a process on the cpu it last ran on. Go check the archives. Would have been 6 or 8 weeks ago, I think David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: ifconfig: changing mac address
On Sat, 15 May 1999, Greg Lehey wrote: : :It seems there's a need, and the possibility. Would somebody like to :suggest a syntax? : ifconfig interface ether ab:cd:ef:fe:dc:ab [options] makes sense to me. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: ifconfig: changing mac address
On Sat, 15 May 1999, Greg Lehey wrote: :On Friday, 14 May 1999 at 21:15:33 -0500, Dan Nelson wrote: :> :> And the next step would be to make the kernel realize that two cards :> ifconfig'd with the same MAC address are meant to be bonded together as :> one route (lots of switches support this). I have some machines that :> I'd love to be able to get 20MB/sec bandwidth between transparently. : :I think you need to reconsider that idea. How are you going to double :the bandwidth of the wire? : I think he means having two interfaces in each box, with the same MAC. So he has two wires, each with 10Mbs. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: ifconfig: changing mac address
On Sat, 15 May 1999, Greg Lehey wrote: : :If you have two different nets, why do you need the same Ethernet :address? : Transparent redundancy. With them both up on the same MAC address, if one fails, you have no loss of connection, though you may drop some packets, of course. Most of the time you get twice the bandwidth. David, who doesn't want to think about writing a driver for this. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: ifconfig: changing mac address
On Sat, 15 May 1999, Greg Lehey wrote: :OK, now maybe I'm missing something here. But an Ethernet address is :used to identify a board. Arp binds it to an IP address. An IP :address is bound to a network. So if you're on a different network, :you get a different IP address. Why do you need the same Ethernet :address? You need a switch to do this. If your clients are on the same ethernet as your server, they can only talk to one MAC address. That means you only get the bandwidth of one interface. If you have a switch that can bond ports together, you can use both cards at the same time, transparently to everybody but the driver and the switch. I know that NetWare supports this, as do some Bay switch, and surely some Cisco stuff. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: What does VOP_WHITEOUT() do?:
On 20 May 1999, R. Matthew Emerson wrote: :"Chuck Youse" writes: :> New daemon book? :> I must have missed that. Do you have the full title? :McKusick, Bostic, Karels, and Quarterman, The Design and Implementation :of the 4.4BSD Operating System, Addison-Wesley, Reading, MA, 1996. :ISBN 0-201-54979-4 Not exactly "new". David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: File system gets too fragmented ???
On Wed, 26 May 1999, Graeme Tait wrote: > It contains about 900,000 files, most of which are small, occupying > around 2-5 fragments. The small files are updated monthly from a tar > > However, I don't understand how the FFS works, so I'm just probing and > guessing as to what's going on here. > > Could someone please shed a little light on this? Is FreeBSD not able to > self-manage a filesystem operated in this way? Is there some way of > preventing the problem, or of periodically cleaning things up (rebuilding > the whole filesystem from backup means being down for over an hour on a > 24x7 server)? The problem you have is that a file on FFS file system can have at most one fragmented block. With the number of small files that you have, it isn't terribly suprising that you are running out of full blocks when there is still space free on the disk. I don't think there is a whole lot you can do about the problem. A 1024B frag size might mask the problem of having space free, but with no aligned blocks, not allocatable. You should also think hard about why you need a million 1536 byte files on the same filesystem. I don't know what you are doing, but you might consider a real database. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: File system gets too fragmented ???
On Thu, 27 May 1999, Don Lewis wrote: > On May 26, 6:59pm, Graeme Tait wrote: > } The filesystem is built with 4096 byte blocks, 512 byte fragments, and > } 2048 bytes/inode, and is mounted 'async noatime'. > > If a file shrinks by one fragment, it'll most likely leave a one > fragment gap in the block that can't be reused by another (new) file, > since the the minimum file size is two fragments. You could easily > get a 12.5% wasteage just from that. This is just shockingly nasty disk usage. I am unable to think of anything much worse, except more of this, with files that change all the time. > > It might help somewhat if a file that grows by a fragment can allocate > the free fragment immediately preceeding it instead of being relocated > to a fresh block. I don't know if FFS does this or not. FFS doesn't do this, and I don't think it could. What I think I would do if I had to deal with something this evil, is go to a 2048 fragment size. Most files will fit in one frag, so the the reallocation problem should be fixed. There will be 1536 blocks wasted for the largest of the small files. Not knowing the distribution of the file sizes, I can't make judgements about what the space wastage will add up to. However, space you can't allocate might as well not be there. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel config script
On Sun, 30 May 1999, Mike Smith wrote: > I'm not sure we want those sort of people. But there's already a What sort of people is FreeBSD after then? There are all sorts of people who need a mailserver, or a webserver, or whatever, who would otherwise get someone to sell them an NT based solution. A friend works for a rather behind the times company who is just getting intra-office email. They had been sold on some gastly solution that runs under NT, and required three boxes to do maybe 80 users mail. Why didn't they use a Unix solution? Too expensive, because they would have had to have paid some high-priced consultant to set things up. If my friend had been able to show off a nifty configuration utility, he might have had better luck selling the FreeBSD solution I recomended. Are you saying that we don't want a presence in any machine room we can get one? That FreeBSD should only be for talented ubergeeks? "The power to serve" doesn't do anyone any good if they can't figure out how to apply it. David Scheidt > Ideally, no interaction at all will be required. Just give me knobs to turn everything off. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel config script
On Sun, 30 May 1999, Bill Huey wrote: > That's fundamentally disturbing especially coming from other fellow > Unix variant folks. > Inter-UNIX rivalries are one of things that has kept unix healthy for so long. Linux tends to pick up most of the 3L1t3 dudez, who don't know anything but how to follow a How-To. I don't have a problem with letting someone else deal with annoying lusers. When they get a clue, and realize that FreeBSD has substantial advantages over Linux, then we can deal with them. It would be nice if there were some migration documentation. (And yes, that *is* an offer. Who do I talk to?) Someone used to have a .sig that summed the difference between Linux and *BSD pretty nicely: "Linux is for people that hate Microsoft. FreeBSD is for people who love Unix." David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: a two-level port system? (fwd)
(CCs snipped) On Tue, 1 Jun 1999, Eivind Eklund wrote: > (3) Hit jkh with a baseball bat until he stops refusing to use soft > updates on the boot floppy during install (due to "making a point") What exactly is the point? We clearly wouldn't be distributing a kernel withoutthe whole sources, so I wouldn't think we would be violating the license. In any event, the -CURRENT /usr/src/sys/ufs/ffs/README.softupdates has a change sugesting that one do something likea "tunefs -n enable /usr " -STABlE still says tunefs -n enable /dev/rsd0s1d. Any reason for this? David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel config script:
On Tue, 1 Jun 1999, Wes Peters wrote:
> If you mean "lack of competition would make UNIX more homogenous and
> more viable to every Tom, Dick, and Jane that comes down the pike,"
> I will agree with that. I just disagree that this is success. UNIX
> was never meant to be a word processor loader, and complete overkill
> for such an application.
I should point out that UNIX's suitably as a document processing
enviornment is one of the reasons that UNIX received support from
BTL management. The fact that it was stable, ran on cheap hardware,
and a cool programing enviornment were bonuses. My bookshelves at
work are kept from floating away by a bunch of elderly UNIX
documentation{1}, which spend a lot of space describing the tools
that let you write papers and books with the system. Of course,
much of what made UNIX suitable for this sort work also made it
adaptable for all the other things that UNIX boxes do to earn their
keep. Things like the pipe, which make it possible to quickly put
together useful programs, because you have to do so little besides
what you really need to do. Raise your hand if you have a two line
pipeline that replaced an expensive commercial application.
I strongly disagree that UNIX is overkill for any application.
Why shouldn't the user be given a stable, flexible platform to do
their work on? Especially if it is one that makes efficient use
of the hardware the user has, so they needn't buy new hardware
every six months? One of the machines I run -CURRENT on is a 4
year-old Pentium. Other than build times being longer than I would
like, I don't have noticable performance issues. The same machine
is essentially unable to run NT, and do work at the same time.
David Scheidt
{1} Anyone need a copy of the UNIX system V Release 2 User and Programmer
Reference Manuals?
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Re: Partitioning a freebsd partition on the fly
On Tue, 1 Jun 1999, Evan Tsoukalas wrote: > My question is, can I shrink my /usr partition down without losing what is on > it? It is a 3.8 gig partition that only has 900 meg or so on it. I would > like to trim about a gigabyte off of it so that I can install Windoze. Is > this going > to be possible, or should I start from scratch installing Winoze first? Resizing FFS filesystems is not possible. In addition, I find that windoze deals with dual-boot machines much better if windows is installed first. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: P5 vs Celeron vs PII
On Thu, 10 Jun 1999, Dennis wrote: > In a nutshell, does anyone have a handle on the relative preformance of > these are? > 333Mhz Celeron vs 333 Mhz PII For a typical job mix, it is pretty close to a wash. The PII seems to have a slight advantage, on the order of 5%. If you are compute bound, and the task fits in cache, the Celery has an advantage, since there is no wait state on cache hits. The PII has a much bigger cache, so even though cache hits are more expensive, they are more likely. I am pretty much unable to tell the difference between a Celeron and a PII at the same clock. The vast majority of my desktop computing isn't compute bound, though. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
softupdates problem?
I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying to load the oss driver, which is not too shocking. What was shocking was the damage done to my filesystem. The automatic fsck failed, with an UNEXPECTED SOFT UPDATES INCONSISTNCY. PARTIALLY ALLOCATED INODE I=39684. Running fsck manually revealed that all inodes from 39684 to 39743 were in this state, which had to be cleared for the filesystem to be cleaned. Only one of these files, the oss/soundon.log file was likely to have been open. The rest were random .h files, and some groff config stuff. I find that quite disturbing. The machine hasn't got enough space to recover the crash dump. The panic, and at least some damage to /usr seems to be possible to recreate at will, so I can clean up things if it is worth looking into further. Here is what is in /var/log/messages for the first panic: Jun 11 21:18:13 tumbolia /kernel: OSS/FreeBSD loading, address = c0a7d0ac Jun 11 21:18:13 tumbolia /kernel: OSS: 240 minutes of evaluation time left Jun 11 21:37:53 tumbolia /kernel: OSS: 240 minutes of evaluation time left Jun 11 21:37:53 tumbolia /kernel: Jun 11 21:37:53 tumbolia /kernel: Fatal double fault: Jun 11 21:37:53 tumbolia /kernel: eip = 0xc0aacbf0 Jun 11 21:37:53 tumbolia /kernel: esp = 0xc4ca2000 Jun 11 21:37:53 tumbolia /kernel: ebp = 0xc4ca2014 Jun 11 21:37:53 tumbolia /kernel: panic: double fault Jun 11 21:37:53 tumbolia /kernel: Jun 11 21:37:53 tumbolia /kernel: syncing disks... 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 giving up Jun 11 21:37:53 tumbolia /kernel: Automatic reboot in 15 seconds - press a key o n the console to abort David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: softupdates problem?
On Sun, 13 Jun 1999, Bernd Walter wrote: > On Sat, Jun 12, 1999 at 12:13:43AM -0500, David Scheidt wrote: > > I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying > > to load the oss driver, which is not too shocking. What was shocking > > was the damage done to my filesystem. The automatic fsck failed, > > with an UNEXPECTED SOFT UPDATES INCONSISTNCY. PARTIALLY ALLOCATED > > INODE I=39684. > > > What kernel-config are you using? > I have had several fs-crashes because of a to high configured maxusers. The only diffs between my config file and GENERIC are: 1. softupdates 2. no support for hardware I haven't got 3. pty is 64 I am not actually complaining about the panic; I think the oss driver is a piece of crap. I just happened to have a soundcard that they support that the FreeBSD drivers don't, and a .wav file I wanted to listen to. What does disturb me is the damage done to a pretty quiet filesystem. I wouldn't have thought that toasting a whole bunch of files that were not in use would be the normal behavior. I have seen lots of panics, but have never seen filesystem damage as bad as this. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
re: david cross's NFS panic fix
On Mon, 14 Jun 1999, Matthew Dillon wrote: > Ack, you may have opened up a can of worms here. I don't even think I don't think it is fair to say he opened a can of worms. He found it, but it was clearly open to begin with. He had the misfortune to stumble across it. Since he has tracked it down, it needs to be quashed, right? (note, CC's trimmed, subject changed, and redirected back into -hackers, which this has wondered out of.) David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: symlink question
On Mon, 14 Jun 1999, Jordan K. Hubbard wrote:
> > symlinks have caused me grief (Pyramid OSx) and never joy. I hope it fails
> > yet again to appear in FreeBSD. Just think of the new security holes for a
> > start.
>
> Name one, please. You can currently point a symlink anyplace you
> like; whether the user has permission to *read* or execute the target
> of the link, however, is where the genuine system administration takes
> over. How the actual value is derived shouldn't make that much
> difference. :)
First try: Suppose foo depends on /usr/local/etc/foo.conf.
/usr/local/etc is a link to /usr/local/${ARCH}/etc. User does
export $ARCH=../../home/user, so /usr/local/etc/foo.conf is now in
their home directory. Depending on how poorly written foo is
written, it may be possible for the user to get foo to do things
it wouldn't normally. There a bunch of these sorts of things
lurking here. Clearly, navigation up the tree can't be allowed,
at least for processes operating with increased privs. There are
probably some other path subversion issues, or potential issues,
lurking in this. This is not to say this isn't a good idea. I
can think of serveral uses that would make my life easier.
David Scheidt
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Re: how do I install driver examples?
On Tue, 15 Jun 1999, Wayne Cuddy wrote: > On my 2.2.7 system I have this directory: > /usr/share/examples/drivers > > This is not on my 3.2S system. I have the 3.1 4 cd set can anyone tell me > what I need to install in order get the drivers extracted from my 3.1 cd? They are on cdrom2. # cd /; (cd /cdrom; tar cvf - usr/share/examples/drivers ) | tar xvf - should work. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: A way to crash system (3.1 & 3.2) with floppy
On Tue, 29 Jun 1999, Travis Cole wrote: > On Mon, Jun 28, 1999 at 09:30:05PM -0400, Jamie Howard wrote: > > On Mon, 28 Jun 1999, Zhihui Zhang wrote: > > > > I just reproduced this on a system running 4.0-CURRENT from about > Sun Jun 27 01:12:42 PDT > > I got a ton of these errors in dmesg and /var/log/messages: > Jun 29 00:17:53 marx /kernel: fd0c: hard error writing fsbn 19 (ST0 > 40 ST1 2 ST2 0 cyl 0 hd 1 sec 2) > > And it let me try several umount commands and even a umount -f. None > of them actualy umounted the floppy drive and it completly reboot my computer > after about 2 or 3 mins. No panic or anything. Once second I'm looking at > X, I can do this from -CURRENT from whenever CTM broke. I have a panic, and a dump which i havne't had time to look at. The panic string is panic: vinvalbuf: dirty bufs David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: A way to crash system (3.1 & 3.2) with floppy
On Tue, 29 Jun 1999, David Scheidt wrote: > I can do this from -CURRENT from whenever CTM broke. I have a panic, and a > dump which i havne't had time to look at. The panic string is > panic: vinvalbuf: dirty bufs > > David > And the dump showsnothing: rally3# gdb -k GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.8 (kgdb) core-file /var/crash/vmcore.8 IdlePTD 2875392 initial pcb at 250320 panicstr: vinvalbuf: dirty bufs panic messages: --- panic: vinvalbuf: dirty bufs syncing disks... 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 giving up dumping to dev (0,131073), offset 256385 dump 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=0) at ../../kern/kern_shutdown.c:288 288 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=0) at ../../kern/kern_shutdown.c:288 #1 0xc0130d40 in boot (howto=0) at ../../kern/kern_shutdown.c:290 Anything else Ishould look for? David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Xfree86 v 3.3.4
On Thu, 1 Jul 1999, Leif Neland wrote: > Does anyone have any inside information on subj? > The website still claims: "We are planning to release 3.3.4 some time in > June 1999" > > I'm longing to get support for my S3 Trio3D. Heh. It now says early july. I have a Voodoo Banshee I want to use. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Xfree86 v 3.3.4
On Thu, 1 Jul 1999, Mark J. Taylor wrote: > > There is a Linux X server for the Voodoo Banshee, over at: > http://developer.soundblaster.com/linux/ > > You might have some luck running it under the Linux emulator. > I've never tried it, as I don't have a Banshee. Thanks! This appears to work pretty well, much better than I would expect a server for a different OS to work. I continue to be very impressed by the Linux emulation! The one problem I have with it is I can't get it to work with sysmouse. For the amount of time I spend using the text console on this box, I can live with killing and started moused manually. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Pictures from USENIX
On Mon, 5 Jul 1999, Greg Lehey wrote: > On Sunday, 4 July 1999 at 15:36:21 -0400, Bill Fumerola wrote: > > It also clears up the misconception that being a member of -core requires > > a beard. > > > > A constant 5 o'clock shadow, maybe, but not a beard. > > And what's wrong with a beard? > > Greg Depends if it 100 F or not. David, clean shaven for the first time in months, Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Easy way to compute memory stats? (procfs?)
On Mon, 19 Mar 2001 [EMAIL PROTECTED] wrote: : Is there an easy way (from script ideally) to get the following :stats: : :free physical mem (avail ram) This is going to be quite small on any busy machine, or machine that has a reasonable uptime. The VM system will cache things unless there's a demand for memory. vm.stats.vm.v_free_count has the value in it, but quite often will be quite a bit lower than the amount of memory that would be available if the system were under memory pressure. If you look at top's output, there is a value labled cache. The pages in this queue are clean, and can be discarded without needing to write them to backing store. The number the system tells you isn't very useful without knowing what the system is doing. :free swap pstat(8) will tell you this :total avail mem Do you mean physical memory, in which case the value of hw.physmem will tellyou. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Easy way to compute memory stats? (procfs?)
On Mon, 19 Mar 2001 [EMAIL PROTECTED] wrote: :> :Is there an easy way (from script ideally) to get the following :> :stats: :> : :> :free physical mem (avail ram) :> :> has a reasonable uptime. The VM system will cache things unless :> there's a demand for memory. vm.stats.vm.v_free_count has the value : : Drat. I was hoping to arrive at a number similar to top's :Free column. Right now the vm stat from sysctl is about 25% of what :top's reporting (256MB physical). At the same time... the free pages :may be a good value for me to toss around given that I'm also :including the load and some statistics of the host's past. The sysctl MIB vm.stats.vm.v_free_count has the same value as top's Free Column. (In pages) It's just not a very useful number. The machine I'm sitting at has 213 pages free, but it's not in any danger of running out of memory. The only times there will be lots of free memory are at system startup, when the memory has never been used, and if a large process exits, freeing its memory. (Quiting Netscape brought my free pages to 13139) : :> :free swap :> :> pstat(8) will tell you this : : Duh, thanks. : :> :total avail mem :> :> Do you mean physical memory, in which case the value of hw.physmem will :> tellyou. : : Phys mem + swap, which I think I can calc pretty easily now :that I have swap. -sc Well, not all memory is swapable, nor is all memory swap backed. Exectuable text sections are backed by the disk file, as it's much faster to just throw them away, reading them from disk if they're needed again, then it is to write them to swap and read them back from there. The same thing is true of files that have been mmaped -- the memory used is backed by the disk file, not swap. The available memory is higher than physical memory + swap. The usable memory is often less than physical memory + swap, as well. This box has 256MB RAM, and 756MB swap. Most of the time, if swap is being touched at all, there's something broken, and the machine is not very useable. However, if I've got something like a huge Netscape process, that's idle, and then start working with something else that uses masses of memory, the idle Netscape can get swapped out, and have 150MB of swapped used, and a box that is its normal zippy self. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: tuning a VERY heavily (30.0) loaded server
On Tue, 20 Mar 2001, Michael C . Wu wrote: : :This box is rather a FreeBSD advocacate itself, as you will see why. Indeed. : :It runs an self-wrote PERL SMTP daemon. (Sendmail and Postfix croaks) How do sendmail and postfix croak? How much mail are you transporting? If you really can't use one of them, why write a replacement in perl? : :* What is possibly the bottleneck that we have for load 30.0? : (since we are not CPU-bound nor memory bound) You're probably blocked on disk IO. David -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: tuning a VERY heavily (30.0) loaded server
On Tue, 20 Mar 2001, Michael C . Wu wrote: : :SWAP is never touched. :) Your vmstat output shows page out activity. I can't tell if it's to swap or to file backed memory, but it's happening. You know this isn't happening when your box blows up? : :last pid: 23395; load averages: 2.08, 2.92, 3.60up 0+01:29:58 02:03:27 :1529 processes:24 running, 1505 sleeping :CPU states: 40.5% user, 0.0% nice, 46.4% system, 1.1% interrupt, 12.0% idle :Mem: 705M Active, 1369M Inact, 332M Wired, 99M Cache, 265M Buf, 7504K Free :Swap: 512M Total, 512M Free You really, really should have at least as much as swap as RAM, probably closer to 2X. A big spike in load can run you out of swap very quickly -- less tan a minute. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fw: Debugging kernel crashes
On Thu, 22 Mar 2001, Gurpratap Virdi wrote: :Hi, : : :I have the following questions related to the above instructions though. :I understand we can use dumpon(8) to tell the kernel to dump the core file :to a swap partition. If our system is only configured with one swap :partition, can we still point the kernel to this partition? I mean would Yes. Your dump partition should be at least as large as your physical memory. :the core file get overwritten when the system reboots and uses the space as :swap again. Now, supposedly the kernel is able to write the core file to the :swap partition and the system reboots without overwriting the core file, how :do we access the core file? savecore(8) will copy the dump to /var/crash at startup. /var/crash needs to be big enough ot hold the dump, and the running kernel. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Locking and Mail spool Files
On Sun, 25 Mar 2001, Marc W wrote: : :Excellent, I will look for that. However, in the meantime, on :older systems (3.x, 4.x, etc ...), is the below assertion correct? : You don't want to put mail spools on NFS filesystems. If you must, use the maildir format, ala qmail. David Scheidt -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: pmap bomb on 4.0-STABLE
On Thu, 5 Apr 2001, Joseph Gleason wrote: :A friend of mine swears by this memory testing utility: : :http://reality.sgi.com/cbrady_denver/memtest86/ : :Apparently it tries a bunch of diffrent test patters that are likely to find :memory problems that a simple test wouldn't find. It is cool because you :just just write the image to a 1.44mb floppy and boot from that to do the :test. : :A major downside is how long it takes. It takes around 8 hours on my laptop The major downside is that software memory testing isn't conclusive. If it detects a problem, you've probably got one. If it doesn't, you may still. The only way to be sure is to use a hardware tester. If you don't have one, and most of us don't, you have to resort to swapping memory. : -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anyone managed to get microns ClientPro's X going
On Sun, 15 Apr 2001, Alfred Perlstein wrote: :* Alwyn Goodloe <[EMAIL PROTECTED]> [010415 19:54] wrote: :> :> We have several systems like our Micron ClientPros running FreeBSD. :> :> These machines have the Intel 82810E chip in it and what seems forever :> there has only been XFree86 drivers for the Linux. : :Almost all the graphical support in XFree86 is in XFree86, there's :probably nothing in there that's Linux dependant. And, in the event that there's some linux binary-only server for this card, it can probably be run on FreeBSD in Linux emulation. I did this for a VodooMumble, when the only xserver was 3dxf's linux binary one. It just worked, except when my linux module got out of sync. David -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: fd driver hacking to recover data
On Thu, 10 May 2001, Luigi Rizzo wrote: :> I have a bunch of old floppy disks with some text files I'd like to :> recover. Many of them have errors and are unreadable past a certain point :> in the disk. Others I can't read from at all. :> :> The ones I can't read, period, are all 1.44MB-size floppies. I've tried :> dd'ing from /dev/fd0c, /dev/fd0.1440, etc., but exits with "Input/Output :> Error" before copying anything. : :i think you can try dd from the raw device (/dev/rfd) using the "iseek" :or "skip" option to jump over the missing sectors. :Alternatively, you can use "conv=noerror,sync" to keep reading :after errors (the bad blocks are NUL-filled) Depending on how the disks are flakey, you may be able to read the bad blocks some of the time. Multiple passes with dd, and combining the results by hand may be worth trying, as might be different floppy drives. David -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: technical comparison
On Tue, 22 May 2001, Shannon Hendrix wrote: : :Point taken, but the "yank power, see who survives" test is illogical :and dangerous thinking. Depends on the enviornment. I've had lots of machines just lose power. People will pull power cords out, the back-up generators won't start before the battery back-up runs out, someone will push the Big Red Switch. Even the best back-up power isn't going to help if it catches fire. I sort of like machines to work when the power comes back. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: brainstorm: "intermediate" disk caching
On Mon, 28 May 2001, E.B. Dreger wrote: : :Of course, with 36 GB drives readily available, maybe I shouldn't worry :until I have a database larger than 72 GB. ;-) If you're really interested in database performance, remember "Spindles is good." Spreading your IO load over as many seperate disks, on as many independent IO channels as practical will improve performance. David -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: "find" and "quota" find different amounts of files
On Tue, 29 May 2001, Mark Stosberg wrote: : :Hello! I'm running FreeBSD 4.3 and have encountered a mystery of some :missing files. Using "find" and "quota" to find the same files, I get :different results. For example: : : :root@nollie vector1> find /usr -user evan -print | wc -l :2435 : :root@nollie vector1> quota evan :Disk quotas for user evan (uid 1075): : Filesystem blocks quota limit grace files quota limit : grace : /usr 561790 101 1012537 0 0 : : :So "find" is reporting 2435 files, but "quota" is reporting 2537. Where :could the difference be hiding? : :I reviewed the man pages for both "find" and "quota" and couldn't find :any clues to this. If it's not actually a bug with one of these :utilities, then I consider it a bug with their documentation since it's :given unexpected results. : These should match. Two things pop into my head as first possibilities. First, you have a race. find(1) and quota(1) are looking at the disk at different times. It's possible that the files got created in the time between find looking at a directory and when quota is run. Whether that's likely will depend on what the machine and the user are doing. If it's consistently like this, then maybe your quota file is corrupt. Are you running quotacheck(8) at startup? I believe the rc.conf flag for that is "check_quotas". If you can afford to take the machine down, run quotacheck and see it fixes the problem. David -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: nfs within jail
Matt wrote: [EMAIL PROTECTED] wrote: Matt, there's nfsshell, an FTP-like client. just google for nfsshell. Won't help in case of NFS4, I guess :-( Stefan Thanks. I'd like to try the nfsshell, but I can't get it to build. It doesn't appear to be a port either. I'm an amateur C coder at best. Could someone take a quick look? It's a very small program. Sources are here: http://www.cs.vu.nl/pub/leendert/nfsshell.tar.gz Release doesn't use autoconfig. Build dies with error: nfs.c:53:27: sys/sysmacros.h: No such file or directory Commenting this line out is sufficent to compile. You then need to change the LIBS line in the make file, removing -lsocket, -lnsl, and -lrpcsoc. That's enough to make it link. I'm unable to actually see if it'll work, though. David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd problem: Cannot detect Hard Disk (SATA)
yoke an wrote: I'm running on SATA mode. Supposingly I will need to configure my Driver on "The Kernel Device Configuration Visual Interface". Not sure the setting for SATA mode and whether 4.8 is supported? SATA is not supported on 4.x. Unless you write support, it's going to stay that way. You either need to use ATA (or SCSI) disks or upgrade to 5.3. Regards. David ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Two keyboards
Julian Elischer wrote: Bram Van Steenlandt wrote: Hi For a pos system I am working on I need support for two keyboards (actually one keyboard(ps/2) and one scanner(usb)). you can already do this.. what makes you call the scanner a keyboard? Proabably, because it acts like one? I don't know about the USB ones, but PS/2 scanners generated keysym data, just like a real keyboard. The idea of the hardware people is "They've already got a keyboard, they take input from it, so let's make the scanner a keyboard!" It makes it easy to use a barcode reader with an application that doesn't know anything about barcodes, barcode scanners or the like. David ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/etc/hosts lines starting with white space are ignored
If a line in /etc/hosts starts with a space or tab, it's not read. I'm not sure that's really a desirable behavior. I'm quite sure it's not the vehavior I expected. It looks like it's the usage of strpbrk() in the gethostent() function of src/lib/libc/net/gethostbyht.c. It wouldn't be hard to fix it to find hostnames on lines starting with " \t". Should I submit a patch? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.4-STABLE corrupting fs on shutdown -p now?
Kris Kennaway wrote: On Mon, May 02, 2005 at 03:38:49AM +0100, Steven Hartland wrote: Why would FS's be being corrupted by "shutdown -p now" where as "reboot" doesnt seem to? Maybe the machine is being powered down before your disks have finished writing their data to disk. My ThinkPad has done this several times. It normally boots, but complains that filesystems aren't clean. I can't reliably reproduce it. As I'm not normally beating on the disk before I power it off, I can't see that it wouldn't have time to write the data. (The buffer counts are always less than 5). It didn't do this on the mid-feb. stable I was running until recently. Kris ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IBM Active Protection System Approach
On Tue, Aug 23, 2005 at 01:06:18AM +0200, Stefan Bethke wrote: > > Early reports from Mac enthusiast sites (and I believe similar > reports from IBM users) indicate that the hysteresis is so small that > gently pounding the table the notebook is sitting on will make the > drive park the heads, and lead to 10 to 20 seconds delay before the > drive can be accessed again. Watching the real time status of IBM APS shows that my T42 will auto ignore "repetiive shock", of hte sort that I can cause by holding the thing in my lap and and typing this message with a little more force than I normally hit the keys. > > Given how tightly coupled mechanically the HD in most notebooks is to > it's shell, it seems a very good idea to pursue. > > If you have access to a new(ish) PowerBook, I recommend checking out > http://www.kernelthread.com/software/ams/. The sensitivity of the > accelerometer is truely astounding. (For those who haven't seen it: > you turn the notebook, and the demo window is turned so it stays > level. It takes *really* small movements to confuse the system.) > The IBM ThinkPads have a similiar applicaiton in the Active protection system properties control panel, under the real-time status tab. It's pretty cool to watch. David ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI project progress report
On Mon, 19 Jun 2000, Brooks Davis wrote: :On Tue, Jun 20, 2000 at 10:49:24AM +1000, Andrew Reilly wrote: : :> Processes do still wind up in "sleep" state, completely paged :> out, don't they? : :Observationaly, no. Unless I actually manage to run my system low on :RAM, none of my swap is used even with ~5MB Eterm processes sitting :unused for days. I suppose if I let memory get tight, they might get :ditched in favor of disk cache, but I haven't seen that happen. Someone :with a better grasp of the VM could give a more preciese answer. I find lots my xterms getting swapped out on my office desktop. It's only (!) got 128MB of RAM, and I routinely have two or three dozen xterms running locally, plus a like number from remote machines, plus an instance of the X server and Netscape. It only takes a couple seconds to swap in one of the xterms when I start to use it again, and I often don't notice, because I have to move my hand from the mouse back to hte keyboard. I'm probably not a typical user, of course. David scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NFS client locks.
On Wed, 21 Jun 2000, Elias Athanasopoulos wrote: :Hi, : :I have a Linux box as an NFS server and a FreeBSD box which acts as an :NFS client. If I explicitly shutdown the NFS services in the Linux box, :actions like 'df', 'ls /mnt' (/mnt is the mount point of the remote :directory), or even 'umount /mnt', in the FreeBSD box, seem to lock forever. :I waited for about 20-25 mins, I got a 'server not responding' message, but :the processes were still locked and I could not even kill them. : :I started again the NFS services in the Linux box and I got a 'server alive' :message in the FreeBSD box, after about 10 mins. : :Is that the correct behaviour? I had a look over /sys/nfs/nfs.h and the Yep. That's the expected behavior. If this is a problem, you can use the intr to make processes blocked on I/O to the missing filesystems interruptible. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How many files can I put in one diretory?
On 26 Jun 2000, Chris Shenton wrote: :I was considering this for a project I developed: web up/download of :lots of large files. I was using MySQL and some of the folks on that :list recommended not storing large files in the DB: even though the :disk consumption is the same, if it's in a DB you can't spread it :across partitions as space requirements grow. That's a failing of your DBMS, and not of a database in general. I add space to existing databases under Sybase fairly often. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PC compatibility cards.
On Wed, 9 Aug 2000, Paul Halliday wrote: :Hi. : :Kinda off topic, but maybe not. : :I just aquired a few pc compatibility cards. From what I can ascertain :they have an onboard p166 processor, 16m ram, 2 meg ati video, 256k :cache, etc. Anyway, after a little reading i figured out what these :little buggers do. Now, has anyone ever tried to mod one of these things :and use it in a "pc"?, they are designed for Macs. : :If anyone has played with one of these, any info would be greatly :appreciated. : The ones I am familiar with were 486 somethings in PowerMac 6100s. I have no idea if you could run FreeBSD on them; they certainly wouldn't work *in* a PC, being PDS cards. ARe the ones you have PCI? David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.1 Release....MIIBUS
On Wed, 23 Aug 2000, Daryl Chance wrote: :Hi, : :I know that in 4.0 Release that miibus was required, though :not marked. I noticed that 4.1 Release miibus is still not :marked as (required), is it no longer required, or is it still :not marked? I ahven't tried compiling it with miibus commented :out, I'm just assuming it's still required : MIIBUS is only required if you have an ethernet adapter that requires it. If you try to include such a device, and not MIIBUS, I'm not at all suprised that the compile fails. It is certainly possible to build a kernel without MIIBUS, though. None of my fxp(4) equipped machines use it, for instance. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: 4.1 lockup at isa0: on reboot
On Sun, 27 Aug 2000, Mike Silbersack wrote: : :On Sun, 27 Aug 2000, Clarence Brown wrote: : :> problem. An obvious difference is that during :> the reboot process the ATI Mach32 VGA board :> resets and does a characteristic "blink" on the :> screen with Red Blue and Green color bands during reset. When the :> earlier heat related problem was evident the reboot froze before this :> point. : :Interesting, I didn't know there were other issues with the board. If I :recall, the problem I was having on warm boot was related to the IDE :drives not working right too. Perhaps the BIOS is configuring the system :in a peculiar way on warm boot that the promise bios / fbsd 4 don't like. I had a 486 that didn't reset the ISA bus on warm boot. There was a pretty good chance that the network card wouln't work until the box was power cycled. It might well be that you have something similiar going on. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Frustration with SCSI system
On Wed, 20 Sep 2000, Marc Tardif wrote: :> > I've been using FreeBSD over the last 6 years (since I switched from :> > NetBSD) to run a small ISP out of my basement. :> > :> > I've had about six disk crashes in as many years and still don't know how :> > to work reliably with them. :> :> "man vinum" :> :> software mirroring == good. :> :What would be the incentives to using vinum instead of simply :concatenating drives in a RAID-1 array (or whatever) using ccd(4)? Concatenating drives is a decidedly different thing than mirroring them is. Mirroring allows you to recover from failed disks without having to restore from tape. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Frustration with SCSI system
On Thu, 21 Sep 2000, Aleksandr A.Babaylov wrote: :I work since 1991 with computer hardware and know exact :that SCSI drives is about ten times less reliability than :IDE. Yes, I understand that SCSI was more ... extremal may be. :I am wery glad that now mostly no need in SCSI drives at all. :Just use good IDE drives, may be second root and regular :dumps to, for example DDS-4 strimer. It is cost effective. This is totatlly contrary to my experience. Heck, I've got a fair number of SCSI disks that predate 1991, happily spinning away. SCSI just works, on everything I've ever used it.I've had a occaisonal problems with things like termination. High quality cables and enclosures solve this. I wouldn't let an IDE disk get within thinking distance of machine whose reliability I cared about. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Frustration with SCSI system
On Wed, 20 Sep 2000, Sergey Babkin wrote: :Plus different manufacturers have different reliability - :if you use Seagate SCSI disks and someone else's IDE then you most :certainly will see a lot more SCSI disk failures. : :-SB, Seagate Hater : I've had almost a thousand Seagates in service for about a year without a single failure. We've replaced 5 or 6 controllers, and a bunch of cables (when the machines first went into service. The techs are murder at bending pins.). I'm quite impressed. : David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Monitoring user activity
On Fri, 22 Sep 2000, Mustafa N. Deeb wrote: :hi , : :I'm look for a way to monitor what happens on my servers :I need to know each command being executed? : :is there away to do that . System accounting should do most of what you want. See accton(8), sa(8), lastcomm(1) to start with. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual console with matrox g400
On Tue, 10 Oct 2000, Greg Lehey wrote: : :Well, you obviously need two keyboards and two mice. I can't think of :a case where that would be useful, but with x2x (in the Ports :collection) you can allow different people access to the same server. I'd think that a monitor, a keyboard, and a mouse are a whole lot cheaper than a monitor, a keyboard, a mouse, and a whole rest of the computer. Modern PCs are more than powerful enough to deal with two ionteractive video users. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: etherchannel / bonding
On Wed, 11 Oct 2000, Dennis wrote: :We will have the feature in our bandwidth manager product for FreeBSD :shortly, including fallover. Its really load balancing; bonding is a bad :term (no doubt coined by the linux camp). : It's telco usage from before there was a linux (and probably before there was a Linus), so it's rather unlikely that they're responsible for it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: etherchannel / bonding
On Wed, 12 Oct 1988, Dennis wrote: :At 09:01 AM 10/12/2000, David Scheidt wrote: :>On Wed, 11 Oct 2000, Dennis wrote: :> :>:We will have the feature in our bandwidth manager product for FreeBSD :>:shortly, including fallover. Its really load balancing; bonding is a bad :>:term (no doubt coined by the linux camp). :>: :> :>It's telco usage from before there was a linux (and probably before :>there was a Linus), so it's rather unlikely that they're responsible for :>it. : : :No, telcos used the term "bonding" for ISDN, which actually IS a physical :bonding technique. Its all the half-wits that think that load balancing is :the same thing that now associate virtual techniques to something very :different. It's used for other cases where a high capacity circuit is built out of multiple physical channels. That's what the original claims about EtherChannel were from cisco, and it's what we use it for. That it continues to work if one the links has a failure is a bonus. It's a substantial bonus, but it would be used even if it didn't. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 16 port 10/100 hubs/switches.
On Tue, 31 Oct 2000, Stephen Hocking wrote: :I just went out & bought a D-Link 10/100 switch. There was another 16 port :10/100 switch on sale by netgear, for twice the price. Now I've established :that they're both switches (as opposed to hubs) and the three machines I :current have connected to it have sucessfully negotiated 100Mbs full-duplex :(speed is great!). Is there any reasons why I should've considered the netgear :unit? I didn't see anything on the box (after a rather cursory perusal) on it :about managability, SNMP et cetera. Probably not. If you don't see performance or reliability problems, no. It's conceivable that one switch can't do 100MB full duplex to every port at the same time. It might, or might not, be the cheaper one. Without test equipment its hard to say. (I've got a 5 port Dlink that I bought about New Year's, which has been great.) David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Time to close the list?
On Fri, 3 Nov 2000, Keith Jones wrote: :On Thu, Nov 02, 2000 at 01:46:14PM -0500, Garance A Drosihn wrote: :> At 3:08 PM + 11/2/00, Terry Lambert wrote: :> >3. Automatically delete all MIME parts with: :> > :> >Content-Type: application/* :> > :> >Which are ever sent via the list software. :> reason we would ever expect an application sent in these :> mailing lists? How easy would this be to implement? : :It's possible (if unlikely) that someone could have zipped up :kernel config and dmesg output and attached them to an email in :a request for assistance. The MIME type could be one of Patches are fairly often sent as tarballs. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: High-availability failover software available.
On Mon, 6 Nov 2000, Andrew Sporner wrote: :Hi, : :Please allow me to introduce myself. I am Andrew Sporner and I have :authored :a H/A Failover system that happens to work with BSD. I would like to Very cool! :The current source is located at http://www.sporner.com/bsdclusters Your webpages seem to be b0rked. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: changing a running process's credentials
On Thu, 16 Nov 2000, void wrote: :Does anyone remember the article in Phrack, issue 53 I think, about :speaking Forth to a Sun's boot-prom in order to write a '0' into the UID :member of one's shell's struct proc? Yes. It works a treat. Similar steps let you do the same thing with DDB or (presumably, haven't tried) remote gdb. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: general Darwin imports (was Re: Darwin cmd import?)
On Jun 5, 2004, at 2:55 PM, Robert Watson wrote: On Sat, 5 Jun 2004, Edwin Groothuis wrote: Now the question of course is: where can I find it? It is somewhere in a CVS repository (that would be nicest), or are it raw sourcefiles only? Edwin, now owning a Mac so not really familiar with things The Open Darwin web site has a web-based CVS browser, but there are some differences between the Apple Darwin and Open Darwin source bits. For our TrustedBSD work affecting Darwin, we generally work from the drops on Apple's www.opensource.apple.com web page, which are available as tarballs. Just about all of that is listed as covered by the APSL. (Except GPL'd stuff, it looks like.) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sudden Reboots
On Oct 1, 2004, at 7:23 PM, Jim Durham wrote: These are very rare except they seem to happen about once a day for a while and then stop... very strange.. and usually caused by hardware problems (e.g. faulty power supply, overheating CPU, bad RAM). Possible, but if so, the hardware fixed itself on the first two boxes I mentioned. All of this can be bad, or not quite bad -- just not healthy -- hardware. Say a power supply that can't supply reliable +5, when the line voltage drops a tad while all the disks are being hammered. It can be a nightmare to figure out. Setup crash dumps, but also make sure that the UPS the box is attached to isn't having problems. If it's not on conditioned power, fix that. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Mall now BSDCentral
On Wed, 11 Jul 2001, Bill Moran wrote: :Wes Peters wrote: :> Just because you don't see it doesn't make it a bad idea. Network admins :> begged for years for a centralized IP address space management server; :> now that they've been given one (that works, and is FREE) people like you :> bitch about it and won't use it. Feh. : :Are you saying you use DHCP for servers? If so, maybe I should shut up :and listen for a while because apparently there's something here I can :learn. I've been using it for client IP pools for years now, but not :for servers. Using DHCP for servers means it's much less work to renumber a network, change router addresses, DNS servers, and so on. Very useful if you've got a zillion machines. Change the settings, and as leases expire, the client servers get the new ones. david -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Whitespace at end of line
On Sun, 15 Jul 2001, Mike Silbersack wrote: : :On Sun, 15 Jul 2001, Jens Schweikhardt wrote: :> I see. Dima suggested in private email that I/we MFC such changes :> relatively fast in order to avoid that; of course this would be done :> only after md5 "approval" of the binaries. : :Whether you MFC it or not, you're going to cause a lot of commit log :pollution. I don't think it's worth the hassle when all we're talking :about is trailing whitespace. : Not only commitlog pollution, but also repository file growth, and wasted bandwidth from those cvsuping the changes. My cvsup of the repository took ~4 times as long when the changes were made to the man pages. You said it would save ~250K in the source tree. What's it do to the size of the whole repository? -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: arcnet support for FreeBSD (request for review)
On Thu, 19 Jul 2001, Julian Elischer wrote: :Max Khon wrote: :> :> hi, there! : :what is arcnet? : It's a token-based LAN protocol. It's used in some embedded applications, as its controllers are cheap, it's pretty low-overhead, and has deterministic behavior (you can calculate the worst case time to send a message to another station). Industrial controlers and data acquistion are the two uses that jump out of my memory. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: not showing in ps
On Wed, 25 Jul 2001, Daniel C. Sobral wrote: :> how i may kill that 31341 port coz ps isnt showing it. : :Install lsof and try "lsof -i :31341". But, frankly, it looks like you :have been hacked. Sockstat will tell you enough, and it's in the base system. : -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Backup file formats: tar, cpio, pax, yadda, yadda, yadda
On Thu, 26 Jul 2001, James Howard wrote: :On Thu, 26 Jul 2001, [iso-8859-1] Lars Kühl wrote: : :> Neither tar nor cpio is suitable for backup purposes. :> Use dump instead. : :A lot of people said this. Why? As near as I can tell, dump isn't that :great either. There is no way to exlude specific directories with dump From the dump(8) manpage: Dump honors the user ``nodump'' flag (UF_NODUMP) on regular files and directories. If a directory is marked ``nodump'', the latter and all files and directories under it will not be backed up. That is, dump propagates the ``nodump'' flag on directories. :and it appears to be quite painful to restore a specific directory (though :I could be wrong about this. Interactive restore isn't that painful, and -x is useful as well. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: crash dump output
On Wed, 1 Aug 2001, Eugene L. Vorokov wrote: :> > Maybe it's offtopic a bit, but can you please give exact instructions of how :> > to compile debug kernel ? My machine crashes sometimes too, I tried to compile :> > debug kernel, but it seemed not so easy and I gave up due to lack of time. Or :> > is there any URL with a good explanation ? :> :> you just call config with '-g' option. and compile the kernel in normal :> way. The freebsd handbook discusses this in more detail. : :Hmm. It seems like I need spare swap device for crashdump ? What can I do :if I have no room on disk for this ? Can normal swap device be used, and :if yes, how to save core on panic ? I think swap device contents will be :lost on the next reboot ... You can use swap for dump, as long as you have a swap device that's slightly larger (64Kb, I think?) than your physical memory. set the rc.conf variable to point to your swap partion dumpon="/dev/da0s1b", or whatever. savecore(8) will save the dump at system startup. It runs from /etc/rc, so it should run soon enough to prevent your dump from having been overwritten by swapping, unless you're seriously pressed for memory. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Finding filesizes in C++ for files greater than 4gb
On Wed, 1 Aug 2001, Joseph Gleason wrote: : :- Original Message - :From: "Alex Zepeda" <[EMAIL PROTECTED]> :> On Wed, Aug 01, 2001 at 09:34:43PM -0400, Joseph Gleason wrote: :> :> > In FreeBSD, how can I determine the size of a file in C++ when the file :is :> > greater than 4gb? :> > :> > Currently, I use stat() and use st_size. That is limited to 4gb (32bit :> > unsigned int) :> :> You're wrong. Read the man page. No soup for you! Next! :> :> - alex : : :Alright, I made a mistake. But I did read the man page. Where does it say :off_t is 64bits? : :My mistake was not digging through the include files enough to see what was :going on. : The types(5) manpage will tell you this. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: if_strip for FreeBSD?
On Tue, 14 Aug 2001, Devin Butterfield wrote: :Hi folks, : :I was thinking about porting netbsd's if_strip driver (the driver for the :metricom ricochet radios--allows you to use these radios as nodes in a WLAN). :Before I do this, I thought I should first check to see if anyone else had :already ported it to FreeBSD...? Are these useful now that metricom has shut down? -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: memory + apache
On Tue, 28 Aug 2001, Dan wrote: : :i am seeing problems where apache is running into swap at times. :When all is said and done...i see alot of available memory from top :and alot still stuck in swap. Restarting apache at that point clears the :swap space right out and memory is used properly again. Is there an actual performance hit here? Stuff that gets paged out is going to stay there until it's used. On a system that's not normally pressed for memory may well mean never. What you've described here isn't a problem. : :These seem to be short bursting peeks which i can;t get to in time to run :vmstat on. When i login i never see any paging or swapping going on maybe Then leave it running. $ while true do date >> logfile vmstat -c 3600 -w 1 | tee -a logfile done will put the date in your logfile every hour, and vmstat's output both to the screen and the logfile everysecond. Next time this happens, look at the logfile, and I'll bet you find you really are running out of memory. Figure out when it starts, and look at the apache logs, and you may be able to figure out what's causing it. It might be unusually heavy load, or memory hogging script, or something like that. It's also possible it's something other than the webserver, like a cronjob that does something ugly, or an interactive user. :2 blocked processes waiting to run seems the average under the b column :in vmstat. Another thing to note is cpu sky rockets when those burts :happen. How can a process go into swap really badly yet seem to not use :all available memory first. Disk I/O does not seem like a factor. What I Do you have any evidence that there's free memory when the box starts swapping? Free memory after the memory shortage has gone away is not evidence that there was memory available when it was swapping. The VM system is smarter than you are. Don't try and tune it before you know what's wrong. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ALT- (Was: how to make 'for' understand two words as a singleargumen)
On Tue, 2 Oct 2001, Greg Shenaut wrote: > Just out of curiosity, what would be an instance where you have > wanted a space in a filename and wouldn't have been satisfied with > 0xa0 instead of 0x20? All the times my file names have actual information in them? If I want to create a file with a space or a * or & or \n in them, let me. they're my feet, I'll shoot them if I want to. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: A way to crash system (3.1 & 3.2) with floppy
On Tue, 29 Jun 1999, Travis Cole wrote: > On Mon, Jun 28, 1999 at 09:30:05PM -0400, Jamie Howard wrote: > > On Mon, 28 Jun 1999, Zhihui Zhang wrote: > > > > I just reproduced this on a system running 4.0-CURRENT from about > Sun Jun 27 01:12:42 PDT > > I got a ton of these errors in dmesg and /var/log/messages: > Jun 29 00:17:53 marx /kernel: fd0c: hard error writing fsbn 19 (ST0 40 ST1 >2 ST2 0 cyl 0 hd 1 sec 2) > > And it let me try several umount commands and even a umount -f. None > of them actualy umounted the floppy drive and it completly reboot my computer > after about 2 or 3 mins. No panic or anything. Once second I'm looking at X, I can do this from -CURRENT from whenever CTM broke. I have a panic, and a dump which i havne't had time to look at. The panic string is panic: vinvalbuf: dirty bufs David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: A way to crash system (3.1 & 3.2) with floppy
On Tue, 29 Jun 1999, David Scheidt wrote: > I can do this from -CURRENT from whenever CTM broke. I have a panic, and a > dump which i havne't had time to look at. The panic string is > panic: vinvalbuf: dirty bufs > > David > And the dump showsnothing: rally3# gdb -k GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.8 (kgdb) core-file /var/crash/vmcore.8 IdlePTD 2875392 initial pcb at 250320 panicstr: vinvalbuf: dirty bufs panic messages: --- panic: vinvalbuf: dirty bufs syncing disks... 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 51 giving up dumping to dev (0,131073), offset 256385 dump 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=0) at ../../kern/kern_shutdown.c:288 288 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=0) at ../../kern/kern_shutdown.c:288 #1 0xc0130d40 in boot (howto=0) at ../../kern/kern_shutdown.c:290 Anything else Ishould look for? David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
