Re: What OS are you? fun
Rob wrote: You'd better cite your source and / or reasoning, as ~3*10^8m/s =is= the accepted constant speed of light in vacuum. It's deeper than that. The "second" and the "meter" are both defined in terms of wavelengths of light, which (as a consequence) fixes the speed of light _by definition_, at _exactly_ *299 792 458 m s^-1. [Way OT!] * ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Higher ATA-Mode -> lower speed
martin hudec wrote: amber# dd if=/dev/zero of=/usr/testfile bs=64k count=2000 131072000 bytes transferred in 2.546718 secs (51467023 bytes/sec) These are not very usefull tests of raw disk bandwith because they use the filesystem (and are hence subject to the vagiaries of block allocation, etc) and are not likely to be very repeatable or comparable. Nore are the big enough or long enough to reduce the variance of the result or cover one-off spikes (e.g. what if it is running just when a cron job happens to kick off?) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RAID/Vinum or Shared MFS... Recommendations?
> I thought about what I had read > regarding MFS... that I could make a filesystem in RAM. This being the > case, couldn't it also be shared via samba? Samba interracts with the local filesystem via the normal read()/write()/ open()/close() system calls so doesn't care what the underlying filesystem type is. IOW it should work for UFS, or MFS, or FAT32, or ISO9660, or even ext2 partitions. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: wierd errors
> Jan 11 00:56:11 culverk /kernel: proc: table is full > Jan 11 00:56:14 culverk last message repeated 1022 times This says you have run out of process slots in the kernel - running too many jobs. Either run fewer processes (e.g. use "make -j4" rather than "make -j8") or build a new kernel with a higher maxusers parameter. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: wierd errors
> Can't you just increase the kern.maxproc sysctl?
Nope, it's readonly, because various kernel internal hash tables are sized on
it. See src/sys/kern/kern_{proc,resource,mib}.c
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: wierd errors
> hrmm, I tried that, same error (that was the first thing I tried actually) Hmm, it may be that the particular program you are building has some kind of error (in build scripts, or makefile, or whatever) that is causing an infinite loop somewhere. Examine the last N lines of output before the compile fails. Greg. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: df output incosistency
> While it is technically free, you won't be able to use it in day-to-day > operations. It is reserved for the superuser. I believe it is so that if > something should flood the filesystem, the superuser still has space to > operate on the partition. Partially. It is also a performace hack - the filesystem rapidly gets much slower when there is less than 10% free space, so the system ensures that users can't fill it up so much that it gets too slow. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: /dev/dsp problems with "play" (usr/ports/audio/play), but not with wavplay (usr/ports/audio/wavplay)
> I've got a weird little problem... trying to play wavefiles via > 'play' (usr/ports/audio/play) results in the following (SB Live): > > play: /dev/dsp: Invalid argument Hmm, I'm tracking down a similar problem with waveplay (/usr/ports/audio/ waveplay). The first time this is run after a reboot is OK, but from then on it will not work - it gets the same error (doing a SOUND_PCM_WRITE_CHANNELS ioctl). I am currently doing a CVSup and I hope to have more information from an up-to-date system this evening. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: netstat
>I have been experiencing some strange behavior with netstat. First check: are you sure that your installed userland and running kernel are built from the same set of sources? IE you have built and installed a kernel and rebooted when you last diod a make world? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Illegal Instruction in libm - Problem solved....
> There is an interesting difference in malloc. It defines the symbol > free and if you use that symbol in your program then it tends to > write over some part of your program. By changing the symbol in my > program (an int) to a different name, the problem goes away and it > works properly. I believe this behavior is new because it didn't > have this problem in FreeBSD 4.2-RELEASE. Free() has been part of the malloc() package for as long as the C language has existed (more or less). Redefining standard library names in your code is and always has been a bug. The difference might be that under 4.2 the bug has repeatable consequences due to different code layout in the library or whatever. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Whence Stallion support for -Stable?
[Cc'd to stable and bugs. Please reply to bugs only] The driver for Stallion multiport cards in 4-Stable is quite old. It doesn't support many of the newer cards, in particular the EasyIO-PCI card, nor any card manufactured since about 1998, which have a newer and unsupported UART chip. The driver in -Current is much the same with a few current-isms, afaict. There is a newer driver in the unsupported section of the stallion FTP site: ftp://ftp.stallion.com/drivers/unsupported/FreeBSD/stalbsd-2.0.0.tar.gz This supports all the new hardware but seems to be written for old (3.x-vintage) kernels, because it doesn't go anywhere near compiling under 4-Stable. There is a PR (http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22967) submitted by Jan L. Peterson <[EMAIL PROTECTED]> which gives a new version of the above driver that does compile with 4-Stable, and seems to operate as expected (tho I haven't explored all the corner cases with flow control, modem control etc). But this PR is less than ideal. It contains a link to the new driver (fortunately still valid!) rather than the data itself, it requires bits from the original Stallion tarball, and doesn't update MAKEDEV or man pages. And the driver was written for 4.1.1 and will need updating for a few things that have changed since then (kqueue). It also "is using old-style compatibility shims" (whatever that means). This PR has been untouched since it was submitted 12 months ago. A related PR from the same period (http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19890) has been assigned to davidn but also remains otherwise untouched. I am willing (and I hope able!) to provide a jumbo patch to tie all these pieces together and update this driver in a manner that should be easy for a comitter to commit to -Stable. But I am running -Stable only, and have no experience in porting device drivers to -Current, and cannot test this driver in -Current. Is it worth me putting together such a comprehensive patch, or will the need to run it in -Current first mean my effort would be wasted? Any device writer / committer gurus care to offer some guidance? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: MD5 and DES hashes
> Cheers for any light anyone can shed, As others have said: - check login.conf - force a salt like '$1$$' also: check /etc/auth.conf for a "crypt_default" line. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: No TTYs?
> Yes, it's a hack, So send in the clone()s. :> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: CPUTYPE and ports
> What I'd like to know is if anyone has figured out a way to do a > g++ equivalent to Microsoft's "precompiled headers". Not really needed for gcc. The preprocessor has special-case logic to recognise header files of the form /* optional comments */ #ifndef SYMBOL #define SYMBOL /* Stuff */ #endif (i.e. almost any normal C/C++ header) and not bother to even open the file next time it is referenced. This gives most of the speedup that precompiled headers would give. (The remaining bit is avoiding lexing the include file text, but that's not such a huge burden). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: New cdboot ISO available
> You can always boot off of boot floppies by making kern.flp and mfsroot.flp > images. It's just that the kernel running during install might be stripped > down and thus might not have support for some newer devices. Which hardly seems fatal, as any system with those "newer devices" orta have a BIOS compatible with cdboot (and w2k) in the first place. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: New cdboot ISO available
> Yes, but then who do you target the ISO at? I'm trying to judge how widely > used the older machines are and if we should still use boot.flp on the ISO's > to > accomodate them. It depends on the nature and ubiquity of the "newer devices" that get dropped off kern.flp. If we get to the stage where even a small fraction of new systems aren't supported by kern.flp installs (because they come with RAID cards etc that are not on kern.flp) then it will be time to change. It's much easier for middling-old systems to boot using kern.flp than it is for someone (to pick a hypothetical example) with only a RAID controller not supported by kern.flp to hand-craft a floppy boot image, or do a double install (once to supported IDE drive, once to unsupported-by-kern.flp RAID device). Unless we want to get into the game of having a mix-n-match selection of kern.flp images! (This might be doable if we have 2 kern.flp images - one for "older systems" from 386-P2, one for "newer systems" from P3/Duron on, to pick a somewhat arbitary convention that should at least be fairly easy to explain to newbies.) My gut feel (admittedly a poor guide!) is that, while the majority of FreeBSD _systems_ might be on older (pre-cdboot) hardware, these will likely be upgraded in place (from source, or net packages). The majority of new _installs_ (i.e. use of the boot CD) will be on newer hardware. (Actually, there is probably a fair number of current or potential FreeBSD systems from the 486/P5 era that don't support any form of CD booting, new or old, but they are irrelevent to the current discussion.) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SOME ITEMS THAT YOU MAY BE INTERESTED IN OR BE ABLE TO ADVISE ME ON
> hand carved round table with metal chain link in the middle Every time you think you've seen the worst the net can offer, along comes another AOLer [Hey, the list was [EMAIL PROTECTED]!] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: static routes broken in 4.6-PRE ?
> This line in rc.conf used to work in 4.5-STABLE: > > static_routes="-net 192.168.1.0 10.1.1.1 -netmask 255.255.255.0" I can't imagine how. That is never how the static_routes rc.conf variable has worked. see man rc.conf, what you want is something like static_routes="mynet" route_mynet="-net blah blah blah" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv
> Has anyone tried these patches on 3.5-STABLE? I applied the patch > and it only errored on the name6.c portion. I'm building world with > it but would like to hear from someone who has used this on such an > old system. I've tried it on 3.2-Release. The name6.c stuff is from IPv6 which is not in 3.x, so ignore that file, the other two patch OK. It seems to be working after a day or so in production. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
major problems with recent if_fxp commit
I have a system with buildworld/installworld last done on about 1 June. It's a pretty plain-jayne HP P4 with an on-board fxp0 interface. Did a cvsup, buildworld and buildkernel and installkernel on RELENG_4 from about 1900 UTC on Satuday 10th. Rebooted before doing installworld (just to make sure). Bloody glad I did, because fxp0 is acting very very strange. If I boot multiuser, then pings from the fxp0 to other hosts work, but pings (and all other network access) from other hosts back to the FreeBSD box with fxp0 work only intermittently if at all. If I run tcpdump in promiscuous mode, then pings (and everything else) from all other hosts work as normal. Kill tcpdump, and it all stops again. Run tcpdump in non-promiscuous mode, and it doesn't work either - it sees incoming ICMP ECHO REQ but no (or only very few) outgoing ICMP ECHO REPLY. It's not a module out of date thing (no modules loaded). It's not an IPFW thing (no hits on the deny rules). We've tried from various remote boxes, including Suns, Ciscos and other FreeBSD boxes. If I revert src/dev/fxp to 2002-08-01 (while the rest of the kernel is still the 2002-08-10 version and userland still on the 06-01 version) and recompile and install /kernel, then everything works fine. If I update src/dev/fxp back to RELENG_4 (there have been no commits since approx 08-08) and reinstall the kernel, it fails again. (This is with the rest of kernel source from approx 08-10 and userland from 06-01.) This _really_ looks like something very strange with the latest fxp commit. Dmesg from a verbose boot (with the failing fxp driver) and config file attached. I'm happy to try random bits of debugging on this box if that's a help to anyone. # # $Id: GROLLO,v 1.3 2002/07/23 06:06:29 aaw Exp $ # $Source: /usr/src/sys/i386/conf/RCS/GROLLO,v $ # machine i386 cpu I686_CPU ident GROLLO maxusers0 options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT#NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM#Rate limit bad replies options KBD_INSTALL_CDEV device isa device pci # Floppy drives device fdc0at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # ATA and ATAPI devices device ata0at isa? port IO_WD1 irq 14 device ata1at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0at atkbdc? irq 12 device vga0at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Floating point support - do not disable. device npx0at nexus? port IO_NPX irq 13
wi(4), hostap mode and WEP
I have a DLINK 520 PCI card on a FreeBSD server (running 4.6-stable from around 20 July) and a DLink 650 PCMCIA card in a WinMe laptop. I can get these systems to communicate in Ad-Hoc mode with and without WEP, and in hostap mode on the FreeBSD end without WEP, but I cannot seem to get the combo of hostap and WEP working. Whenever I set an encryption key, the laptop cannot associate, but as soon as I disable WEP on both ends, the laptop finds an association almost immediately. I'm using hex keys at both ends, and even using silly but unambiguous keys like "0x" I can't get this to work with hostap. I've also tried with 64 and 128 bit WEP keys. Nor can I change wi0 from hostap to adhoc mode - "ifconfig wi0 adhoc" returns ENODEV: "ifconfig: SIOCSIFMEDIA: Device not configured". Going from adhoc to hostap mode works fine. This may or may not be related. Has anyone else got this working? Is it expected to work (the man page seems to suggest it should) or is WEP and hostap not supported? (Yes, I know WEP is not very secure, but my main hope is to stop random people leeching my cable link!) wi0: mem 0xfbfe-0xfbfe0fff irq 11 at device 12.0 on pci0 wi0: 802.11 address: 00:05:5d:5b:c4:c8 wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary 1.00.05, Station 1.03.04 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: CDROM/CDRW devices not working.
>9660: /dev/acd0c: Device not configured Did you remake the devices? (cd /dev && sh MAKEDEV acd0) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
tbz/tgz packages balls-up
We run a central build host that builds world/kernel and uses portupgrade to build packages that we then export to all the other hosts (using NFS for installkernel/installworld and portupgrade/ftp for the packages). Sometime in the last month, the Ports makefiles were changes so that the build host now builds all the packages as .tbz files. But none of the package tools on -Stable (cvsup'd and installed as of yesterday) can understand these new packages. If I run "pkg_add -r " I get an error message like this: hellcat## pkg_add -r portupgrade Error: FTP Unable to get ftp://grollo/pub/FreeBSD/ports/i386/packages-4-stable/Latest/portupgrade.tgz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch `ftp://grollo/pub/FreeBSD/ports/i386/packages-4-stable/Latest/portupgrade.tgz' by URL (Note it is looking for a tgz file not a tbz file). So If I specify the URL with the .tbz directly, I get this: hellcat## pkg_add ftp://grollo/pub/FreeBSD/ports/i386/packages-4-stable/Latest/portupgrade.tbz Fetching ftp://grollo/pub/FreeBSD/ports/i386/packages-4-stable/Latest/portupgrade.tbz... gzip: stdin: not in gzip format tar: Child died with signal 13 tar: Error exit delayed from previous errors Broken pipe Similar failures occur with portupgrade. This is a complete cockup. Will someone explain what I have to do to get the fsking package system working again? Who on _earth_ thought they could update the package format without updating any of the tools that deal with packages No comments in UPDATING, no warning, no HEADS-UP, no nothing. Just busted package system. And searching the maillist is futile given the chronic unreliability of the archiver/searcher. I'm pretty pissed off about this To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP: Package compression format changed
> David O'Brien merged the relevant changes yesterday. If you think Looks like I CVSUP'd before the patch made it to the mirror I was using. I've just CVSUPed again and got the changes. Thanks! It's a huuuge pity this didn't happen before the change to the Ports makefiles, tho... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: -STABLE was stable for long time (Re: FreeBSD: Server or Desktop OS?)
> You have chosen to maintain systems which stretch FreeBSD to its limits > and uncover bugs lurking in the code. This is great. But you cannot do > so on the one hand and refuse to face the administrative work on the > other hand. And this is not a FreeBSD problem either - if you are doing stressful or mission-critical things, then you have to put more effort into admin and making sure you get the right OS environment, whether you are running FreeBSD or Solaris or whatever. For example, if you had Solaris boxes in the same job, you wouldn't just willy-nilly add Solaris patches without trying them on a test box To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: More information (was Re: pthread woes)
> I had, same error occured. Even with -O0, which turns off any > optimization whatsoever. Umm, it said 'revert to "-O"', not 'without optimization'. And for a good reason. Compiling with anything but the system compiler and with optimisation set to anything except "-O" is _not supported_. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: weird math in dump(8)
> DUMP: 101.44% done, finished in 0:-1 Id' bet that's caused by activity on the FS between when dump starts (and makes it's estimate of how much to dump) and it finishes. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
hints on KVM switches w/ X
Has anyone got hints on using KVM switches with XFree86? I'm using a wheel mouse and moused, but something gets out of whack when I switch away then back to X. Next time I touch the mouse, all sorts of weird things happen for a fraction of a second, then the mouse starts working OK. This is annoying and dangerous because it often winds up pasting random stuff into xterms. Are there any hints for making this less of a problem? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Large memory issues on 4-STABLE
> However we have a situation where if I set MAXDSIZ to 2048 or above then > things break, so FreeBSD right now has an effectivce limit of 2GB per > process. > > Is this to be considered a bug or a feature? It orta work above 2Gb, and has been known to work to about 3Gb. The fact that tcsh is reporting "unlimited" is probably a bug in tcsh (signed vs unsigned). But you can't put a limit on how much above 2Gb will definitely work, because the kernel's demand for VM space is variable, depending on hardware config, job mix & current activity. (The Kernel uses VM space for various data structures, but the ones that matter most in large RAM machines are the processes VM page tables etc.) So a given MAXDSIZE might work most of the time but fail in interesting ways when things get hot. And failing due to out of VM space is not handled very gracefully at all. If you're lucky you'll get a panic. > Then, with the PAE support, lets say I have 8GB of RAM. Will those same > design limitations restrict me to 3GB of RAM, or 2GB, or will I be able to > have a single process addressing 4GB all by itself? No, the architectural limit is that the kernel and the user program share the one 32-bit address space, and the kernel typically needs up to 1Gb of it, so no user process can be bigger than this 3 Gb (or so) limit. So PAE will not help at all here (and in fact may make it worse as PAE data structures may be large than normal ones.) But with PAE you could have 2 or 3 of these large processes all RAM-resident at once, if you are willing to buy that much RAM. Fixing this is basically not going to happen; 64bit CPUs will be standard way before a project of that magnitude would be finished. Greg, not really a kernel hacker. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.9-PRERELEASE PAE panics Highpoint Raid module (hpt374.ko)
Any module compiled without PAE will probably panic a PAE kernel. (See recent threads about pnc and rl ethernet drivers). Given the fragility of the module build process, a good rule of thumb might be "never use modules in a PAE kernel (or an INVARIENTS kernel, or)". At the very least, you will need to get an updated hpt module from the vendor. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.9 doesn't answer.
First thing to check is rDNS - make sure the box can resolve the IP addresses used to connect to it. That's often why ssh/telnet/ftp/etc hang up - waiting for rDNS results to write log records. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Weird behavior with -stable
Really sounds like there is another machine on the same subnet with the same (new) IP address, and they are having ARP duels. Sometimes you get machine A, sometimes machine B. When you get A, it works, when you get B, there is no HTTP/IMAP/ etc daemons listening and the host key is wrong. Check the output of "arp -a" on another host and compare that to the Ethernet address of the problem box ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HTT and SMP question
> Would you please point out some cases when HTT with machdep.hlt_logical_cpus= > 0 > causes worse performance than machdep.hlt_logical_cpus=1? Typically, running a single, large, CPU-bound process, especially FPU-instensive simulations. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for ntp/PPS setup guide
Thanks all for the enlightening response. There is one bit I still don't get: How do I tell the kernel which port to look for the PPS signal on with PPS_SYNC? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FAILED make buildword (3.1-R => 3.2-S)
> today I fetched the fresh 3.2 stable code using cvsup, starting make > buildworld. It failed. Since I´m out of my depth here, maybe you could > help. You missed the HEADS UP messages posted by John Polstra on -stable on 03 Jul? [you do follow the stable mailinglist, don't you!?] The softupdates files have moved and need new symlinks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: rpc.statd -- memory hog?
> USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > root 156 0.0 0.2 262968 256 ?? Is Mon05PM 0:00.21 rpc.statd rpc.statd mmap()'s a 256Mb chunk of anon memory but never uses most of it. This is 100% normal. [Is this in the FAQ?!?] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How to disable sendmail on autoboot?
> Copy it to /etc/rc.conf and change YES to NO
If by this you mean "copy /etc/defaults/rc.conf to /etc/rc.conf" - this is not
a good idea. The system will not boot ("out of file descriptors" from
infinitely recursing rc.conf scripts.)
just add the relevent line ('sendmail_enable="NO"' in this case) to /etc/
rc.conf and leave the default one alone.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
cvsup, cvs & directory permissions....
I maintain /usr/ncvs via cvsup. By default, the directories in /usr/ncvs are root.wheel, mode 755. This means you need to be root to do a "cvs get" because RCS needs to create lock files in the cvs repository. I often check out various bits of the -CURRENT source so I can compare with what's in /usr/src (which is -STABLE). I wanted to do this as me rather than root, for all the obvious reasons. So I chmod'd all the directories to 775, I was already in group wheel, and all was fine. Until the next cvsup which did a heap of SetAttrs operations and put the directories back to 775. :< Is there some simple way of getting around this? A quick peruse of the CVS man didn 't suggest any way of turning off the RCS locking. The cvsup man page didn't seem to have a flag to say "ignore directory modes". Do I just give up and do it as root? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cvsup, cvs & directory permissions....
"Chris D. Faulhaber" <[EMAIL PROTECTED]> wrote: > >From cvs(1): > -R Turns on read-only repository mode. Well aren't I a complete goose. I originally looked in the cvs man page on our Solaris system, for which -R is "recurse", rather than the FreeBSD system, where (as Chris pointed out) -R is "readonly". Oddly, both claim to be CVS 1.10 `Halibut' (the others were all too flat.) Greg, Red-faced. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How often to run mergemaster?
> I recently started to track 4.X Stable. How often does one need > to run mergemaster, or even better how does one even know that > it needs to be run? Every time you run "make installworld" or "make world". It's no big chore, I usually do it while I'm waiting for the new kernel to compile. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
[Summary] Re: Repeatable panic: zone: entry not free
For the record/mail-list archives: I sumbitted this as a PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=19553) and David Malone pointed out that using KLDs compiled without INVARIANTS in a kernel compiled with INVARIANTS will cause this. See the PR for details. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: International Crypto/ssh broked yet again by deletion of rsa_eay.c,v
I've just done another cvsup and it looks like rsa_eay.c has been added back to the cvs-crypto collection. It looks like it's all fixed; I'm running a buildworld so I should have a definitive answer sometime this afternoon. Thanks all. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: disk partition limits
> Are there any limits for size/quantity of partitions at freebsd > slice? 4 slices per disk, 8 partitions per slice (by convention, partition "c" covers the whole disk so usually only 7 usable partitions). AFAIK FreeBSD cannot use the so-called "extended partitions" (i.e. slices-within-slices). If this is too restrictive for your purposes, use vinum to chop up a large partition into lots of little ones. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
