Re: upgrading 5.4 - 6.0 without reinstalling. safe ?
While we're nit-picking ... ;-) Marian Hettwer [EMAIL PROTECTED] wrote: short additional step: Claus Guttesen wrote: The easiest would be to 1. cvsup to RELENG_6 (or RELENG_6_0) 1.1 cd /usr/obj; chflags noschg *; rm -rf * 2. cd /usr/src 3. make buildworld 4. make buildkernel 5. make installkernel 6. mergemaster -p 7. reboot into single-usermode and verify your new kernel works 7.1 fsck -p 7.2 mount -u -o rw / 8. mount -a 9. make installworld 10. mergemaster 11. reboot Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. C++: an octopus made by nailing extra legs onto a dog -- Steve Taylor, 1998 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: timecounter and Hz quality in kern RELENG_6
martinko [EMAIL PROTECTED] wrote: Oliver Fromme wrote: Michael Schuh [EMAIL PROTECTED] wrote: After digging in the source i have found that timec.c have an routine for computing the so called Hz quality. During boot, the kernel probes several time counters and assigns quality values. Typically you have three of them (i8254, ACPI, TPC). The time counter with the highest quality value will be used for timing by default, but you can change it via sysctl if you know what you are doing. Type sysctl kern.timecounter and see the result. are those quality values preset (i.e. TSC = 800) or are they computed (during boot) somehow? and if the latter, how pls?? They have hardcoded defaults, but some of them are adjusted under certain circumstances. For example, the TSC's default value of 800 is reduced on an SMP-enabled or APM-enabled system. You should be able to look it up in the source code easily yourself. Look for struct timecounter. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Perl will consistently give you what you want, unless what you want is consistency. -- Larry Wall ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: timecounter and Hz quality in kern RELENG_6
Michael Schuh [EMAIL PROTECTED] wrote:
i be very surprised about the performance of RELENG_6.
Congratulations to the entire Team for this very good work.
Now i have 2 Machines installed with 6.0-RC1, and i have seen that on
both machines the Hz is differntly with GENERIC-Kernel.
sysctl kern.clockrate tells you the HZ value.
In FreeBSD 6 the dafult is 1000, unless you change
it via options HZ=x in your kernel configuration.
The values from systat(1) or vmstat(8) are not reliable,
because the counters are only 32bit and can overflow.
For example, one machine here with HZ=1000 reports only
428 in vmstat -i:
$ sysctl kern.boottime ; date +%s ; vmstat -i | grep clk
kern.boottime: { sec = 1123867316, usec = 744735 } Fri Aug 12 19:21:56 2005
1131378875
clk irq0 3216967596428
Dividing the counter value by the uptime (in seconds)
seems to confirm the bogus rate of 428:
$ runtime='( 1131378875 - 1123867316 )'
$ echo '3216967596 / $runtime' | bc
428
But the 32bit counter has already overflowed once, so
we have to add 2^32. This gives the correct value:
$ echo '( 3216967596 + 2 ^ 32 ) / $runtime' | bc
1000
After digging in the source i have found that timec.c have an routine for
computing the so called Hz quality.
During boot, the kernel probes several time counters and
assigns quality values. Typically you have three of
them (i8254, ACPI, TPC). The time counter with the
highest quality value will be used for timing by default,
but you can change it via sysctl if you know what you are
doing. Type sysctl kern.timecounter and see the result.
Can anyone explain me the mystics behind Hz quality,
and why or how this quality is computed and what are the
efforts?
The reason for that is to have a time counter that is as
precise and reliable as possible. For example, TPC has
issues on SMP and power-managed machines, therefore it is
not as reliable as ACPI, so usually the ACPI timecounter
has higher quality (although it takes more clock cycles
to query it).
Oh, there's also a timecounter called dummy, which does
not count time at all. :-) It exists for debugging
purposes only, AFAIK, and has a negative quality value,
so it is never selected automatically.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
When your hammer is C++, everything begins to look like a thumb.
-- Steve Haflich, in comp.lang.c++
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf for 6.0
Thomas T. Veldhouse [EMAIL PROTECTED] wrote: Hmm ... I find this thread surprising, as this is the first I have heard of FreeBSD working correctly with -O2. So, is this the options suggested for make.conf on x86? CFLAGS= -O2 -pipe -fno-strict-aliasing COPTFLAGS= -O2 -pipe In fact, those are the defaults (at least in FreeBSD 6 on i386; amd64 uses additional options like -frename-registers), so I would suggest to _not_ specify the options in make.conf at all. If you specify a CPUTYPE setting in /etc/make.conf, then appropriate -march=xxx options will be added to CFLAGS and COPTFLAGS automatically, so you don't have to care for that either. As the saying goes: Less is more ... ;-) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. File names are infinite in length, where infinity is set to 255 characters. -- Peter Collinson, The Unix File System ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.0 release date and stability
Brett Glass [EMAIL PROTECTED] wrote:
The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't show a
projected date for the finished product. How close is it?
I can't speak for the RE team, but from watching the BETA
and RC progress and reports in the mailing lists ... my
guess is that 6.0-RELEASE will be out very soon. Maybe in
only a few days.
We are (believe it
or not) still running and building production servers with 4.11,
Same here.
We're running our own tests on RC1, but don't have a lot of spare servers to
try it on. So, it's worth asking: How stable is RC1 turning out to be on
uniprocessor platforms? On SMP platforms? How is network and disk
performance
relative to 4.11? (When we tested 5.x, both network and file system
performance were worse than that of 4.11.)
FWIW, I'm running RELENG_6 on two machines (a notebook and
a server) for several weeks, updating every few days, and
putting some workload and various testing on them. So far
I have not encountered any serious problems that were not
resolved. So, stability seems to be very good; my feeling
is that 6.0 will be a _lot_ better than 5.0. A _lot_.
About performance: It seems to be a little slower than
RELENG_4 on my test machines (which are UP). It's not much
slower, but noticeable. (Yes, I know about INVARIANTS,
WITNESS and malloc.conf, those are not the cause.)
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
PI:
int f[9814],b,c=9814,g,i;long a=1e4,d,e,h;
main(){for(;b=c,c-=14;i=printf(%04d,e+d/a),e=d%a)
while(g=--b*2)d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d%g;}
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: harddrive won't mount/boot, superblock can't be fixed.
Mr. Darren [EMAIL PROTECTED] wrote: I had a bad ide cable which I have now replaced. on bootup the filesystem produced a lot of errors and I lost my first superblock. I since fsck'd and repaired the superblock at sector 32. At no time does fsck create, fix, or transfer the sector 32 superblock to the front of the drive. mount won't accept the drive in the condition it's in(says no superblock, or bad superblock.. different programs, different errors). If anyone knows how I could get my data off and format my /var drive, or possibly repair my damaged superblock at the front of the drive with anyone of the 50-some backups that exist throughout the drive. How about copying the fixed superblock with dd(1)? Something like this: dd if=/dev/ad0s1d of=/tmp/sb skip=32 count=16 dd if=/tmp/sb of=/dev/ad0s1d seek=16 count=16 fsck /dev/ad0s1d Those commands are just off the top of my head -- I haven't tested it, no guarantees, you're doing it at your own risk and you should have a backup. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Being really good at C++ is like being really good at using rocks to sharpen sticks. -- Thant Tessman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new FreeBSD-webpage
Tuomo Latto [EMAIL PROTECTED] wrote: Greg Barniskis wrote: well, usability is not an entirely objective measure, but there are objective aspects to it. Like, not having to scroll to find crucial navigation links and the Search box, or to see what the latest You forget the number 1 rule: Thou shalt not add to the number of clicks required. Scrolling is always preferable to clicking since it requires less effort and has a better response time. I'm afraid I have to disagree. Moving the mouse pointer to the scroll bar, clicking it and dragging it is definitely more effort than simply clicking a link. (And don't tell me everyone has a mouse with a scroll wheel. That assumption would be wrong.) So, here's a specific and constructive suggestion: Add on a clearly visible place on the front page a link pointing to the old site and keep the old site updated as well. How about Not new to FreeBSD? under the New to FreeBSD?? I would rather suggest to remove the old page as soon as possible, before people are starting to create hyper links to it. The longer the old front page is available, the bigger the problem will grow. Here's another: Make all headings links. That's a good idea. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Python is executable pseudocode. Perl is executable line noise. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Advice sought on upgrading from 4.11-R to 5.4...
Doug Barton [EMAIL PROTECTED] wrote: I disagree that ignoring comments in the files is a good idea. There is no way for mergemaster to know for sure if the comment is material or not, that's the admin's job. Furthermore, it is non-trivial to automatically detect that a change is inside a comment. Many files use #, but some files use ; or // for comments (e.g. BIND files), send- mail mc files use dnl to introduce comments, and I'm sure there are others. Ignoring everything that starts with # would be a particularly bad idea, because there are files where that character does _not_ introduce a comment. I agree with Doug that changes in comments are sometimes important enough to be read by the admin, e.g. if a default setting changes or an important new option is introduced. Of course, there are also sometimes changes that just fix typos, and dealing with those might be a waste of time, but that's no a valid reason to ignore _all_ changes inside comments. Here's my recommendation for /etc/mergemaster.rc: DIFF_FLAG='-Bub'# Hide changes in whitespace DIFF_OPTIONS='-I$FreeBSD:.*[$]' # Ignores CVS Id tags IGNORE_MOTD=yes # Ignores changes in motd Of course, as always: YMMV. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. C++ is the only current language making COBOL look good. -- Bertrand Meyer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Jail to jail network performance?
[Sorry, this is a late reply, but might be helpful.] Daniel Gerzo [EMAIL PROTECTED] wrote: Hello Brandon, Thursday, September 15, 2005, 5:17:57 AM, you wrote: [...] nullfs looks interesting. I was thinking about sharing files between jails using NFS, but it looks like nullfs would do the trick with better performance. Although the bugs section of the man page for mount_nullfs is rather scary. Does anyone have any experience with it? Does it actually work? btw unionfs is interesting as well, but the BUGS section is pretty the same :) Another possibility is to use union mounts (i.e. using the -o union mount flag with a regular mount). This works without problems and is very stable, but it is a little less flexible than UNIONFS (or NULLFS) because it merges only the directory entries at the mount point. If the point here is to make /tmp/mysql.sock show up in another jail's file space, can I use a symlink instead? Can a jailed process see the target of the symlink? I read that using such a symlinks has security impacts. Symlinks within a jail cannot point to targets outside of that jail. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. When your hammer is C++, everything begins to look like a thumb. -- Steve Haflich, in comp.lang.c++ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sysinstall automatic filesystem size generation.
Chuck Swiger [EMAIL PROTECTED] wrote: Jon Dama wrote: yes, that's quite generous. why isn't /tmp just an mfs mount though? While I like that suggestion personally, some people get perturbed about files in /tmp going away if the power fails or you reboot. Then those people should use /var/tmp instead of /tmp. Traditional UNIX behaviour is that contents of /var/tmp must survive a reboot, while contents of /tmp are not guaranteed to survive a reboot (and in fact, /tmp might be cleaned completely at regular time intervals via a periodic cron job or similar). That's why vi puts its recovery files under /var/tmp, not /tmp. However, there are still cases where it's not desirable to make /tmp a memory-based file system, e.g. on systems that have little RAM and/or no swap (or NFS swap). Also, some people argue that a UFS disk partition with softupdates (or even async) is fast enough for most purposes to be mounted on /tmp. (For what it's worth, I've seen systems set up in a way to newfs the /tmp partiton on reboot.) Therefore, I think the best solution would be to make it an option in sysinstall: If the user doesn't create a separate partiton for /tmp in the partition editor, ask him whether he would like to make /tmp a memory-based file system. Or implement a special hotkey in the partition editor for creating a memory-based file system -- I guess this would be the easiest way to implement it. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I invented Ctrl-Alt-Delete, but Bill Gates made it famous. -- David Bradley, original IBM PC design team ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
WITNESS warning output from 6.0-BETA3
Hi, I get the following output under FreeBSD 6.0-BETA3 when WITNESS is enabled. It doesn't seem to cause any harm, though. I cvsupped this system to RELENG_6 a few days ago. I have no idea what is causing this output, whether should worry about it, or even whether this is the right list to report or ask about it. :-) The output occurs when booting, right when the interface (bfe0) is configured for the first time. I have a small self-made script in /etc/rc.d which configures bfe0 several times with different IP addresses and performs a ping test in order to find out in which network the notebook is located, then symlinks various files in /etc depending on the result. The below output happens when that script is executed. Best regards Oliver malloc(M_WAITOK) of 64, forcing M_NOWAIT with the following non-sleepable locks held: exclusive sleep mutex if_addr_mtx r = 0 (0xc23af260) locked @ /usr/src/sys/net/if.c:1905 KDB: stack backtrace: kdb_backtrace(1,40,c104d800,2,e4f46b1c) at kdb_backtrace+0x29 witness_warn(5,0,c06ebd16,c06d9c8c,40) at witness_warn+0x18e uma_zalloc_arg(c104d800,0,102) at uma_zalloc_arg+0x41 malloc(36,c071f4e0,102,0,c23af000) at malloc+0xae ether_resolvemulti(c23af000,e4f46b78,e4f46ba8,c2641bc4,0) at ether_resolvemulti+0x87 if_addmulti(c23af000,e4f46ba8,e4f46ba4,e4f46ba8,10) at if_addmulti+0x84 in_addmulti(e4f46bdc,c23af000) at in_addmulti+0x32 in_ifinit(c23af000,c2641b00,c2627550,0,e4f46c38) at in_ifinit+0x515 in_control(c2707b20,8040691a,c2627540,c23af000,c235b180) at in_control+0x882 ifioctl(c2707b20,8040691a,c2627540,c235b180,0) at ifioctl+0x198 soo_ioctl(c2662360,8040691a,c2627540,c225bd00,c235b180) at soo_ioctl+0x2db ioctl(c235b180,e4f46d04,3,1,286) at ioctl+0x370 syscall(3b,3b,3b,8056da0,0) at syscall+0x22f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280d0a97, esp = 0xbfbfe99c, ebp = 0xbfbfe9c8 --- malloc(M_WAITOK) of 64, forcing M_NOWAIT with the following non-sleepable locks held: exclusive sleep mutex if_addr_mtx r = 0 (0xc23af260) locked @ /usr/src/sys/net/if.c:1905 KDB: stack backtrace: kdb_backtrace(1,40,c104d800,2,e4f469b0) at kdb_backtrace+0x29 witness_warn(5,0,c06ebd16,c06d9c8c,40) at witness_warn+0x18e uma_zalloc_arg(c104d800,0,102) at uma_zalloc_arg+0x41 malloc(36,c071f4e0,102,0,c23af000) at malloc+0xae ether_resolvemulti(c23af000,e4f46a0c,e4f46a3c,0,0) at ether_resolvemulti+0x124 if_addmulti(c23af000,e4f46a3c,e4f46a38,e4f46a3c,1c) at if_addmulti+0x84 in6_addmulti(e4f46a8c,c23af000,e4f46a84) at in6_addmulti+0x4c in6_update_ifa(c23af000,e4f46b8c,0) at in6_update_ifa+0x4cf in6_ifattach_linklocal(c23af000,0) at in6_ifattach_linklocal+0xe5 in6_ifattach(c23af000,0,8040691a,8040691a,0) at in6_ifattach+0xb9 in6_if_up(c23af000) at in6_if_up+0x13 ifioctl(c2707b20,8040691a,c2627540,c235b180,0) at ifioctl+0x1f8 soo_ioctl(c2662360,8040691a,c2627540,c225bd00,c235b180) at soo_ioctl+0x2db ioctl(c235b180,e4f46d04,3,1,286) at ioctl+0x370 syscall(3b,3b,3b,8056da0,0) at syscall+0x22f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280d0a97, esp = 0xbfbfe99c, ebp = 0xbfbfe9c8 --- malloc(M_WAITOK) of 64, forcing M_NOWAIT with the following non-sleepable locks held: exclusive sleep mutex if_addr_mtx r = 0 (0xc23af260) locked @ /usr/src/sys/net/if.c:1905 KDB: stack backtrace: kdb_backtrace(1,40,c104d800,2,e4f46998) at kdb_backtrace+0x29 witness_warn(5,0,c06ebd16,c06d9c8c,40) at witness_warn+0x18e uma_zalloc_arg(c104d800,0,102) at uma_zalloc_arg+0x41 malloc(36,c071f4e0,102,0,c23af000) at malloc+0xae ether_resolvemulti(c23af000,e4f469f4,e4f46a24,c2619700,0) at ether_resolvemulti+0x124 if_addmulti(c23af000,e4f46a24,e4f46a20,e4f46a24,1c) at if_addmulti+0x84 in6_addmulti(e4f46ac4,c23af000,e4f46a84,1,e4f46abc,c261a8a0,e4f46a9c,101,0) at in6_addmulti+0x4c in6_update_ifa(c23af000,e4f46b8c,0) at in6_update_ifa+0x60d in6_ifattach_linklocal(c23af000,0) at in6_ifattach_linklocal+0xe5 in6_ifattach(c23af000,0,8040691a,8040691a,0) at in6_ifattach+0xb9 in6_if_up(c23af000) at in6_if_up+0x13 ifioctl(c2707b20,8040691a,c2627540,c235b180,0) at ifioctl+0x1f8 soo_ioctl(c2662360,8040691a,c2627540,c225bd00,c235b180) at soo_ioctl+0x2db ioctl(c235b180,e4f46d04,3,1,286) at ioctl+0x370 syscall(3b,3b,3b,8056da0,0) at syscall+0x22f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280d0a97, esp = 0xbfbfe99c, ebp = 0xbfbfe9c8 --- -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. anyone new to programming should be kept as far from C++ as possible; actually showing the stuff should be considered a criminal offence -- Jacek Generowicz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail
Re: Install from USB flash drive? Sort of...
Brandon Fosdick [EMAIL PROTECTED] wrote: So I had this brilliant idea that I was going to install FreeBSD on my new amd64 system using a 512MB flash drive since I didn't feel like digging out a CD-ROM. I ended up installing from CD anyway, but I thought I'd share my experience in case anyone else knows how to do this. [...] The next morning it occured to me that I probably could have just copied the files from an install CD. Right. Or from an FTP site. [...] Determined to press on I tried the install from existing file system option, w hich I had never noticed before. That didn't work since I had no idea what path to give it, or even if the flash drive had been mounted. It depends on the FreeBSD version. Older versions mounted it on /dist, if I remember correctly, but newer ones mount it directly on /. Thinking that maybe I had built a bad release I decided to try copying from the disc1 iso. The iso is listed at 515MB which is almost small enough. The packages are about 70MB and they're not strictly necessary so I thought it would work. So I mounted the iso and proceeded to copy the files out, since iso's mount read only and I needed to delete stuff. You can copy directly from the ISO to your flash drive, excluding the things that you don't need (i.e. packages). There's no need to make an additional copy on your HD. For example: # cd /cdrom; find . | grep -v /packages | cpio -dump /flash To my surprise it turned into 1.1GB when copied onto a real filesystem. Obviously that's a problem. Depends on how you copy things. Using cp(1) for recursive copies is almost always a bad idea, because you will get duplicates of all hardlinked files. That's why your copy grew to 1.1GB. For recursive copies, use cpio, tar, pax, cpdup or similar tools. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. C++ is over-complicated nonsense. And Bjorn Shoestrap's book a danger to public health. I tried reading it once, I was in recovery for months. -- Cliff Sarginson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: badblocks
Matthias Buelow [EMAIL PROTECTED] wrote: Augusto Cesar Castoldi wrote: is therer any application similar to badblocks of linux on freebsd? badsect(8) How can I check and mark bad blocks of HD's ? But normally modern drives do that by themselves (and transparently remap them). If the filesystem starts complaining about bad blocks (that is, hard read/write errors), that means the on-disk bad sector list is full and it's probably time to buy a new drive. That's not completely true. The transparent remapping feature only works when sectors are being written to. When you read from a file and get a read error, nothing will be rewritten and you you keep getting the same error. To force the drive to remap the bad sectors, you have to write to them. If the bad sectors are inside a file, it might work to overwrite the file. Otherwise you have to extract the sector numbers from syslog and use dd(1) to overwrite them on the raw device, followed by fsck. Of course it is always a good idea to make a complete backup (if possible) before. If you have a good backup, you can also simply overwrite the whole disk with dd (and then use fdisk, disklabel, newfs as usual and restore from your backup). Note that remapping has to be enabled. For SCSI disks, the camcontrol(8) manpage contains an example for that. Also note that some drives don't remap bad sectors, no matter what you do. In any case: If the drive is used to store important or valuable data, then it should be replaced when read errors occur, no matter whether remapping the bad sectors works or not, because it is quite possible that further sectors will be damaged. Just my 2 Euro cents. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.11 to RELENG_6
Björn König [EMAIL PROTECTED] wrote: Randy Bush wrote: any peculiarities/clues for upgrading an antique from 4.11 to RELENG_6 beyond the To upgrade in-place from 5.x-stable to current in UPDATING? I guess not. From the release notes of 6.0-BETA2: Source upgrades to FreeBSD 6.0-CURRENT are only supported from FreeBSD 5.3-RELEASE or later. Users of older systems [...] Unfortunately, that statement is ambiguous: FreeBSD 4.11 (Jan. 2005) is _not_ older than 5.3 (Nov. 2004). However, I guess that's not what the release notes really mean. For the mentioned update from 4.x to 6.x, I would go via a binary upgrade, which has probably fewer pitfalls and is finished a lot faster than a source upgrade. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. It combines all the worst aspects of C and Lisp: a billion different sublanguages in one monolithic executable. It combines the power of C with the readability of PostScript. -- Jamie Zawinski, when asked: What's wrong with perl? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apache2 just listening to https?
Uzi Klein [EMAIL PROTECTED] wrote: Eirik Øverby wrote: On Jul 28, 2005, at 10:01 AM, Roger Grosswiler wrote: VirtualHost *:80 ServerName freebsd.domain.net ServerAlias freebsd.domain.net DocumentRoot /usr/local/www/data /VirtualHost Make sure you are not enabling SSL globally, but for each vhost individually. Actually, SSL can not be configured per name vhost. (or at least can not work) Because SSL handshake is used before http headers, it just can't be done. You can configure SSL perfectly fine per virtual host, provided that they have separate addresses. You can even use SSL for virtual hosts that share an address, if they listen on different ports (in this case you can use redirects for convenience, so users don't have to type the port numbers). It's correct that SSL doesn't work for pure name-based virtual hosts (not using special tricks), but nobody was talking about that. Try the telnet trick mentioned by others, but simply type GET / HTTP/ 1.0 ENTERENTERENTER Actually, ENTER twice is sufficient. :-) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. cat man du : where Unix geeks go when they die ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apache2 just listening to https?
Uzi Klein [EMAIL PROTECTED] wrote: Oliver Fromme wrote: Uzi Klein [EMAIL PROTECTED] wrote: Actually, SSL can not be configured per name vhost. (or at least can not work) Because SSL handshake is used before http headers, it just can't be done. You can configure SSL perfectly fine per virtual host, provided that they have separate addresses. You can even use SSL for virtual hosts that share an address, if they listen on different ports (in this case you can use redirects for convenience, so users don't have to type the port numbers). It's correct that SSL doesn't work for pure name-based virtual hosts (not using special tricks), but nobody was talking about that. note the *name vhost* Only _you_ were talking about named virtual hosts. :-) They are not an issue in this case. and the user's conf. The user's configuration, as far as it has been (partially) shown, contains just two virtual hosts which run on different ports (port 80 for for HTTP and port 443 for HTTPS). So name-based virtual hosts are _not_ an issue here. Name-based virtual hosts would be a problem if you run multiple of them on the same IP address _and_ on the same port with SSL (usually 443). That's not the case here. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. If you aim the gun at your foot and pull the trigger, it's UNIX's job to ensure reliable delivery of the bullet to where you aimed the gun (in this case, Mr. Foot). -- Terry Lambert, FreeBSD-hackers mailing list. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apache2 just listening to https?
Uzi Klein [EMAIL PROTECTED] wrote: The original post has VirtualHost *:80 ServerName freebsd.domain.net ServerAlias freebsd.domain.net DocumentRoot /usr/local/www/data /VirtualHost ...which should be loaded on startup. Also, i activated NameVirtualHost *:80 Which does exactly nothing unless there actually are multiple virtual hosts for the same IP and port. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. It's trivial to make fun of Microsoft products, but it takes a real man to make them work, and a God to make them do anything useful. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cua*x naming? [Was: Re: FreeBSD 6.0-BETA1 Available]
Brandon S. Allbery KF8NH [EMAIL PROTECTED] wrote: On Mon, 2005-07-18 at 18:18 +0200, Emanuel Strobl wrote: Am Sonntag, 17. Juli 2005 21:12 CEST schrieb Robert Watson: (2) /dev/cuaa* has been renamed to /dev/cuad* I saw that cuaa got cuad and ucom0 got cuaU0. Now what is the meaning of cua? tty AFAIK is TeleTYpe... Call(-out) Unit Access, IIRC. Yes. I remember that some systems (Solaris) used the term ACU for automatic call unit, which just means a modem. I've also seen interpretations saying that cua is related to UART (universal asynchronous receiver/transmitter), which is the basic function description of a serial controller. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. ... there are two ways of constructing a software design: One way is to make it so simple that there are _obviously_ no deficiencies and the other way is to make it so complicated that there are no _obvious_ deficiencies.-- C.A.R. Hoare, ACM Turing Award Lecture, 1980 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: reducing shutdown time
Marc Santhoff [EMAIL PROTECTED] wrote:
I was searching for a way to shorten the stopping time in general.
Have a look at ``sysctl kern.shutdown''. If you have only
read-only filesystems, you can probably safely set them to
zero. I haven't tried that myself, though.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH Co KG, Marktplatz 29, 85567 Grafing
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
PI:
int f[9814],b,c=9814,g,i;long a=1e4,d,e,h;
main(){for(;b=c,c-=14;i=printf(%04d,e+d/a),e=d%a)
while(g=--b*2)d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d%g;}
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dangerous situation with shutdown process
Kevin Oberman [EMAIL PROTECTED] wrote: [...] I believe that the Windows solution to this problem is to put a really, really long delay between when the system is finished syncing and when the power is turned off. Definitely not. When I compare Windows XP and FreeBSD on the same hardware (notebook with ATA disk), then Windows' shutdown process is a lot faster than FreeBSD's. In fact, when I shut it down under XP for the first time, the power was off so quickly that I thought someting must have gone wrong. But everything was OK and normal. This might be the best solution for FreeBSD, as well, but it will irritate people. It is already irritating that FreeBSD sits there doing nothing for ~ 5 seconds before turning power off. Windows doesn't do that. (Yes I know, there's a sysctl for that, but I suspect that it's not save to modify it in FreeBSD.) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Emacs ist für mich kein Editor. Für mich ist das genau das gleiche, als wenn ich nach einem Fahrrad (für die Sonntagbrötchen) frage und einen pangalaktischen Raumkreuzer mit 10 km Gesamtlänge bekomme. Ich weiß nicht, was ich damit soll. -- Frank Klemm, de.comp.os.unix.discussion ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dangerous situation with shutdown process
Matthias Buelow [EMAIL PROTECTED] wrote: Sorry folks, have I somehow dropped into a parallel universe, or is there some serious misunderstanding going on? Seems so. To the OP: There is no sync process that is being killed by shutdown Yes, there is a kernel process called syncer. During shutdown, each of the kernel processes (including the syncer) has 60 seconds to terminate. If it doesn't, timed out is printed on the console. This timeout can be changed using a sysctl tunable (kern.shutdown.kproc_shutdown_wait). The kernel writes out all dirty buffers as part of its shutdown procedure. When you shut down a machine, the kernel flushes all dirty buffers to disk. While it is doing that, it displays the number of remaining buffers, with increasing time intervals between them. If there are still buffers left after a certain number of intervals without change, the kernel gives up. If that is really the problem, then the best solution would be to make the number of flushing intervals and/or the increasing interval a sysctl tunable. They're currently hardcoded at 20 and 50ms, respectively; see the boot() function in src/sys/kern/kern_shutdown.c. That means that the timeout will happen after 10 seconds. Doubling the number of intervals (i.e. 40 instead of 20) will make the timeout happen after 40 seconds, which should be sufficient. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. C++ is the only current language making COBOL look good. -- Bertrand Meyer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dangerous situation with shutdown process
Matthias Buelow [EMAIL PROTECTED] wrote: Oliver Fromme [EMAIL PROTECTED] writes: buffers to disk. While it is doing that, it displays the number of remaining buffers, with increasing time intervals between them. If there are still buffers left after a certain number of intervals without change, the kernel gives up. Why is it doing this? Can't it just enumerate the buffers and write them, one by one? I don't think that the boot() function in kern_shutdown.c can do that. It has got nothing to do with the syncing business itself. It can only trigger the syncing (similar to the sync(8) tool), which basically means performing a vfs_sync with flag MNT_NOWAIT for every mounted filesystem. Then it has to wait for the appropriate kernel process to do its job. See the source. I don't think there's an easy way to change that. If you see such a way, I'd suggest you code it up and use send-pr. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Python tricks is a tough one, cuz the language is so clean. E.g., C makes an art of confusing pointers with arrays and strings, which leads to lotsa neat pointer tricks; APL mistakes everything for an array, leading to neat one-liners; and Perl confuses everything period, making each line a joyous adventure wink. -- Tim Peters ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Possible exploit in 5.4-STABLE
Argelo, Jorn [EMAIL PROTECTED] wrote: [...] This site, of course (almost) completely in Russian, had a file to gain root access with a modified su utility. [...] This is a translation from babelfish: Plain replacement of standard su for FreeBSD. It makes it possible to become any user (inc. root) with the introduction of any password. For this necessary to neglect su with the option -!. with the use of this option does not conduct ravine- files. Was tested on FreeBSD 5.4-STABLE. To install such a modified su utility, you need to be root anyway. So this is not an exploit. It could be useful to install hidden backdoors on cracked machines, though, as part of a root kit or similar. You could achieve the same effect by copying /bin/sh to some hidden place and make it setuid- root (which also requires root priviledges in the first place). The advantage of a modified su utility is the fact that su(1) is setuid-root anyway, so it might be more difficult to detect the backdoor. However -- In both cases the modified suid binary should be found and reported by the nightly security cronjob, unless you also modify find(1) and/or other utilities. This is a very good reason to actually _read_ the nightly cron output instead of deleting it immediately or forwar- ding it to /dev/null. ;-) (Also, local IDS tools like tripwire or mtree might be useful for such cases, too.) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. A language that doesn't have everything is actually easier to program in than some that do. -- Dennis M. Ritchie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD MySQL still WAY slower than Linux
Michael Schuh [EMAIL PROTECTED] wrote: now i have another question, if i use the same Os in 2 versions (RELENG_4, RELENG_5) can i hope that the tests are made on the same part of disk? yoda Hope you always can. But rely on it you should not. /yoda ;-) or in other words can an dd on the two OS' es so much different because they use an totally other part of disk? I think no, the strategie from dd under one OS should not be changed if the OS-Version has changed. It's not the dd which decides where to put the file, it's the filesystem code. And yes, there can be differences between RELENG_4 and RELENG_5. In particular, in RELENG_5 you have UFS2, not the old UFS. There have always been changes to the FS code, for example I remember that the allocation of directories has changed some time ago to improve metadata performance for large trees (known as dirpref). As I said: The only way to make sure you hit the same physical place on the disk is to use a raw partition, not a file on some filesystem. Note that even small differences in the placement of the file can have a noticeable effect on the speed. Apart from the speed differences of the disk cylinders, it can also happen that the file is allocated in a non-contiguous way, especially if it is large and the filesystem already contains a lot of files, and/or had a lot of write+delete operations previously (i.e. causing fragmentation). the part with serial IO related to database-performance have i understand, but i quests me have the others understand my meanings? That I don't know. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. anyone new to programming should be kept as far from C++ as possible; actually showing the stuff should be considered a criminal offence -- Jacek Generowicz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD MySQL still WAY slower than Linux
Michael Schuh [EMAIL PROTECTED] wrote: As i sayed i have the installations always made in the same way, so that i mean. I mean i have alwas made the swap on the first gig of the disk, and the installation on the rest of the disk. and i have no multiple os'es on these disk. The problem is that the file (from dd of=foo) can still end up at completely different physical places on the disk. It depends on the filesystem (ext2, ext3, UFS, whatever) and on the allocation strategies of the filesystem code. UFS might start filling cylinder groups from the beginning of the disk, while ext3 might start at the end (does ext3 even _have_ cylinder groups?). This was just an example, but you get the idea. Of course, it also depends on how much data there already is on the filesystem, and how it is distributed over the disk. For accurate measurements and comparisons, you have to make sure to use _exactly_ the same physical location on the disk. From userland you don't have a way to control the physical allocation of files. Therefore, the only reliable way is to leave an unused partition on the disk, do _not_ put a filesystem on it, and use the raw device in the »dd« command. If you do this, you will always hit the same physical location on the disk. But then again -- as others have already mentioned, serial write speed is not the most important factor for database performance (although the WAL journal files of advanced transactional databases like PostgreSQL are written in a sequential way), so the usefulness of this benchmark is very debatable. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I started using PostgreSQL around a month ago, and the feeling is similar to the switch from Linux to FreeBSD in '96 -- 'wow!'. -- Oddbjorn Steffensen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 380 G4
Palle Girgensohn [EMAIL PROTECTED] wrote: Just a quick check - a client is getting a Proliant 380 G4 with a 6i Raid controller. Haven't used this hardware before. Will it work fine with FreeBSD? Which version will work best, 5.4 or 4.11? Any peculiarities or things to think about? Any input appreciated! It's not supported under 4.x: pci2: unknown card (vendor=0x0e11, dev=0x0046) at 1.0 irq 5 At a customer of ours we're currently forced to run Linux on the newer Proliants because of that problem (FreeBSD 5.x is currently not an option for that customer). Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. [...] one observation we can make here is that Python makes an excellent pseudocoding language, with the wonderful attribute that it can actually be executed. -- Bruce Eckel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filesystems not properly unmounted [OT]
Maxi Combina [EMAIL PROTECTED] wrote: Personally, I have used the ext2fs driver for exactly one reason: to migrate data from Linux to FreeBSD on machines which are being converted from the Dark Side. And that I do not seed the need of insult other OS. And I do not see any insult. (If you're referring to the Dark Side pun, then maybe you should check whether /dev/irony is working correctly for you. I really thought it wouldn't be necessary to add a smiley in that place, but unfortunately I seemed to be wrong.) Even worse if the other OS is open source (as linux). Being open source doesn't mean that a piece of software is any good. In fact, I've seen a lot of open source which is just plain crap. (OK, now _this_ is an insult, but I didn't mention any specific software in particular.) Linux has its _really_ good points. Well, I don't see any. But everybody is free to have his own opinion. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. IRIX is about as stable as a one-legged drunk with hypothermia in a four-hundred mile per hour wind, balancing on a banana peel on a greased cookie sheet -- when someone throws him an elephant with bad breath and a worse temper. -- Ralf Hildebrandt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filesystems not properly unmounted [OT]
Maxi Combina [EMAIL PROTECTED] wrote: I do not seed the need of insult other OS. May be you need to look more carefully. I am not talking _only_ about this thread. You replied specifically to my mail, and you didn't mention any other threads. Well, I don't see any. But everybody is free to have his own opinion. Well, I insist: maybe you should look more carefully :) I do look carefully every day, because it's my job. I work with various operating systems every day, including FreeBSD and Linux. Just to mention the first thing that comes to my mind: several linux distros have achieved a difficult goal: ease of installation-use combined with a stable system. Yup, I know the usual freebsd-for-servers and linux-for- desktops arguments. And to be honest, I'm fed up with them. They're lies. I'm running FreeBSD on my desktop at home, a lot of people are happily running Linux on their servers, and I've seen people successfully installing FreeBSD who have never even heard the word unix until that day. Please let me know if you dont agree, and why. I don't agree, but I won't tell you why, because it is probably a waste of time. I've had this a thousand times before. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I invented Ctrl-Alt-Delete, but Bill Gates made it famous. -- David Bradley, original IBM PC design team ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filesystems not properly unmounted [OT]
Yuval Levy [EMAIL PROTECTED] wrote: Oliver Fromme wrote: I do look carefully every day, because it's my job. I work with various operating systems every day, including FreeBSD and Linux. From a professional I would expect a more mature and balanced approach, rather than my favorite OS is the best one and the others have no advantages. That's not what I wrote. FreeBSD is not the best. There is no such thing as the best, in general. Be real: there is a lot of diversity of OS out there and they all have advantages and disadvantages. Right. Everyone has to decide for himself which tool works best for his job. Yup, I know the usual freebsd-for-servers and linux-for- desktops arguments. And to be honest, I'm fed up with them. They're lies. I'm running FreeBSD on my desktop at home, a lot of people are happily running Linux on their servers, and I've seen people successfully installing FreeBSD who have never even heard the word unix until that day. You can run FreeBSD on your desktop at home because you have the skills, the time, the dedication. For most standard applications it doesn't require any more skills (or time, or dedication) than with any other OS. In fact, getting some applications to work correctly under, say, Windows requires more skills (and time, and dedication) sometimes. You are special. Every human being is special Right. I don't disagree with you there. [...] They do not share your view. I do not share your view. This does not make us liars. Uhm, what are you talking about? I've never called you a liar. But those people who claim that FreeBSD is only suitable for servers and Linux is only suitable for desk- tops -- those are liars. There are plenty of counter- examples. I am moving my servers from Linux to FreeBSD, because FreeBSD gives me the manageability, stability and security that are more important to my clients than the bleeding edge features that often make it into Linux first. I am generally inclined toward Open Source software over proprietary one, but will pragmatically mix and match to obtain what works best for me rather than dogmatically pretend that my favorite OS is the best and its filesystem is the brightest and its license is the only acceptable distribution form. I agree 100%. Most of my machines (i.e. the machines which I own or which I'm responsible for to operate) run FreeBSD, but some also run Linux (Debian), Solaris or Windows. I used to have OpenBSD, too, but it stopped working for me (a long story). And currently I'm evaluating to move one of my privat machines from FreeBSD to DragonFly BSD, because some of its features would be very useful. Still, of all of those systems, FreeBSD is (currently) my favourite. It's particularly versatile to work well for all kinds of different purposes, including servers _and_ desktops. Which brings me back to the topic of this thread: is there anybody out there with the skills to cleanly solve this shameful situation in which rebooting FreeBSD results in unclean mounting of ext2 (and potentially other) volumes? A umount command in rc.shutdown should be a feasible work-around. Fixing the driver is probably not a high-priority, because not many users are affected by the problem, I guess. (But then again: It's open source, so you can try to fix it yourself.) Best regards Oliver PS: I think this should rather move to the -chat list. -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. And believe me, as a C++ programmer, I don't hesitate to question the decisions of language designers. After a decent amount of C++ exposure, Python's flaws seem ridiculously small. -- Ville Vainio ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filesystems not properly unmounted
yuval levy [EMAIL PROTECTED] wrote: In my opinion, an O/S that can not handle the most popular file systems is handicapped in a world of increasing diversity. Please excuse me jumping in here, but ext2/ext3 is certainly _not_ one of the most popular file systems for most members of this mailing list. Personally, I have used the ext2fs driver for exactly one reason: to migrate data from Linux to FreeBSD on machines which are being converted from the Dark Side. And that requires mounting the file system just once (read-only), copying the data, then umount it, followed by newfs. There's no need to even think about shutting down while the ext2fs is still mounted. I'd recommend against mounting any ext2/ext3 file systems permanently for sharing data between Linux and FreeBSD. There are better ways to do that. (The best way, of course, is getting rid of Linux in the first place.) Best regards Oliver PS: For what it's worth, the most popular filesystems for me are UFS/UFS2, NFS, ISO9660, UDF, and maybe FAT. No more. I guess for the majority of computer users the most popular filesystems are NTFS, ISO9660, FAT and maybe HFS, and they don't even know what ext2 is. :-) -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. FreeBSD is Yoda, Linux is Luke Skywalker -- Daniel C. Sobral ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IP Firewalling by DNS name
Ivan Voras [EMAIL PROTECTED] wrote: Is it possible to use ipfw to filter packets by domain name? No. That would required the IPFW code to perform reverse DNS lookups, which isn't really feasable. (In theory you could write a small filter program that receives the ssh setup packets via an IPFW divert(4) rule. However, DNS lookups can take a significant amount of time which could probably interfere adversely with the TCP retransmission timeout of the setup (SYN) packets. But I could be wrong.) What I need it for: I'd like to allow ssh logins only from a specific TLD (by reverse lookup...) - maybe there's another way? If there's a limited number of IP addreses or subnets within that TLD that you want to allow access, then use those addresses in IPFW rules. Another way is to use the TCP wrapper, see hosts_access(5). However, be aware that this is working at a higher level than IPFW. If you want to control logins to a single account only (which is under your control), you could use public-key- authentication and put the TLD with your public key in the ~/.ssh/authorized_keys file, like this: from=*.org ssh-dss ... your key and disable password authentication alltogether. Then you can only login with your private key _and_ from that TLD. If it's not your own account and you don't trust the user, then change his ~/.ssh/authorized_keys file like above, and then set the system-immutable flags on the file _and_ on the directory (chflags schg ...). (Note that chmod and chown will not be sufficient, because the use can still rename the ~/.ssh directory and create a new one.) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. If Java had true garbage collection, most programs would delete themselves upon execution. -- Robert Sewell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IP Firewalling by DNS name
Ivan Voras [EMAIL PROTECTED] wrote: Igor Robul wrote: Ivan Voras wrote: What I need it for: I'd like to allow ssh logins only from a specific TLD (by reverse lookup...) - maybe there's another way? /etc/hosts.allow man 5 hosts_access How safe is it? It works in userland, so it only kicks in after the TCP connection has already been established. IPFW works in the kernel on a packet level, so it kicks in much earlier. Whether it's safe enough for you is up to you to decide. As I understand it, sshd actually accepts connections prior to checking hosts.allow? Yes, the connection is accepted first, because there is no information available about it before it is accepted. But if the check fails, the connection will be closed immediately. In hosts.allow, there's an example for sshd but it contains: # Wrapping sshd(8) is not normally a good idea, but if you # need to do it, here's how #sshd : .evil.cracker.example.com : deny Why it's not a good idea? :) There are several reasons. First, it relies on DNS, which is not necessarily a good idea. If someone can spoof your DNS (which is not as difficult as many people think it is), you're toast. Second, SSH provides authentication mechanisms which are much more secure, such as public key authentication. Also, SSH uses host keys for identification, so you don't have to rely on DNS. However, in your case I think it's OK to use TCP wrapper, because you want to use that in _addition_ to the usual SSH authentication (for pre-filtering, so to speak), but not to replace it. Just keep in mind that DNS results might not be reliable. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I made up the term 'object-oriented', and I can tell you I didn't have C++ in mind. -- Alan Kay, OOPSLA '97 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IP Firewalling by DNS name
Lowell Gilbert [EMAIL PROTECTED] wrote: Oliver Fromme [EMAIL PROTECTED] writes: Ivan Voras [EMAIL PROTECTED] wrote: As I understand it, sshd actually accepts connections prior to checking hosts.allow? Yes, the connection is accepted first, because there is no information available about it before it is accepted. But if the check fails, the connection will be closed immediately. Well, that's not necessarily the best way to explain it. When you're working with TCP wrappers, you're running out of inetd(8), so there isn't really any sshd at all until the wrappers have decided to allow the connection. I assume he's not using inetd(8) for ssh (which is not a good ide ain general, and it's not the default anyway). Note that sshd(8) supports hosts_access(3) directly without the help of inetd(8). In hosts.allow, there's an example for sshd but it contains: # Wrapping sshd(8) is not normally a good idea, but if you # need to do it, here's how #sshd : .evil.cracker.example.com : deny Why it's not a good idea? :) There are several reasons. First, it relies on DNS, which is not necessarily a good idea. If someone can spoof your DNS (which is not as difficult as many people think it is), you're toast. Second, SSH provides authentication mechanisms which are much more secure, such as public key authentication. Also, SSH uses host keys for identification, so you don't have to rely on DNS. The reason that it's generally considered a bad idea, though, is just that it's *slow*. No. If you're not running it via inetd(8), then it's actually pretty fast (except for the DNS lookups which can take a while, buth that's not an issue in this particular case). Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I have stopped reading Stephen King novels. Now I just read C code instead. -- Richard A. O'Keefe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Highpoint HPT371 support (kern/59624)
Hi, Why is kern/59624 still open? It's about 1,5 years old. Would someone please commit it? Or, if it cannot be commited, please tell me why. If any information is missing (pcicon -lv output, verbose dmesg or whatever), I'd be happy to provide it. The patch in that PR brings support for the Highpoint HPT371 ATA133 controller to FreeBSD 4-stable (it's supported in FreeBSD 5 for a long time already). The patch is fairly trivial, and I'm running 4.x with that patch for almost two years, using various devices connected to my HPT371 (a DVD- ROM drive, a DVD-R/W recorder, several UDMA harddisks using hot-swap via atacontrol detach/attach). Zero problems so far, except that I have to merge the patch each time I update my world. :-) Thank you very much. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I invented Ctrl-Alt-Delete, but Bill Gates made it famous. -- David Bradley, original IBM PC design team ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel: swap_pager: indefinite wait buffer - on 5.3-RELEASE-p5
Uwe Doering [EMAIL PROTECTED] wrote: Oliver Fromme wrote: If they're really identical (i.e. the same size and same geometry), then you can use dd(1) for duplication, like this: # dd if=/dev/ad0 of=/dev/ad1 bs=64k conv=noerror,sync The noerror,sync part is important so the dd command will not stop when it hits any bad spots on the source drive and instead will fill the blocks with zeroes on the destination drive. Since it's only the swap partition, you shouldn't lose any data. I would like to point out that the conclusion you're drawing in the last sentence is invalid IMHO. I'm afraid I don't agree. indefinite wait buffer messages at apparently random block numbers just indicate that the pager was unable to access the swap area (in its entirety!) when it wanted to. It means that the disk drive was either dead at that point in time or busy trying to deal with a bad sector. This sector could have been anywhere on the disk. It just kept the disk drive busy for long enough that the pager started to complain. The OP specifically said that the swap_pager messages were the only kernel messages that he got. That indicates that only the swap partition is affected, because otherwise there would have been other kernel messages indicating I/O errors from one of the filesystems on that disk. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. C++ is to C as Lung Cancer is to Lung. -- Thomas Funke ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel: swap_pager: indefinite wait buffer - on 5.3-RELEASE-p5
Zoltan Frombach [EMAIL PROTECTED] wrote: Apr 29 02:10:14 www kernel: swap_pager: indefinite wait buffer: device: ad0s1a, blkno: 328636, size: 8192 Apr 29 02:10:24 www kernel: swap_pager: indefinite wait buffer: device: ad0s1e, blkno: 329842, size: 4096 [...] The error message indicates that there was an I/O error accessing the swap area on your disk. Usually that's an indication for a hardware failure, e.g. a dying disk. I happen to have an identical hard drive around here, unused. If I hook it up as a slave (IDE) drive, is there a way I can mirror the dying drive to the spare one (with all partitions, etc, intact)? If they're really identical (i.e. the same size and same geometry), then you can use dd(1) for duplication, like this: # dd if=/dev/ad0 of=/dev/ad1 bs=64k conv=noerror,sync The noerror,sync part is important so the dd command will not stop when it hits any bad spots on the source drive and instead will fill the blocks with zeroes on the destination drive. Since it's only the swap partition, you shouldn't lose any data. However, one disadvantage of dd is that it copies the drive on block level, which means that it will also copy empty blocks which aren't used at all. Neither does it make sense to copy the swap partition. If the filesystems on that drive don't contain much data, it might be mor efficient to copy the data on filesystem level. To do that, copy just the boot sector and disklabel (using dd(1) to copy the first 64k or something should be sufficient), then newfs the filesystems, mount them and copy the contents with an appropriate tool. I recommend cpdup from the port collection, because it's fast and easy to use, but cpio should work as well (and it's in the base of pretty much every UNIX system). Performing newfs + filesystem copy also has the advantage that you're starting with fresh, unfragmented filesystems, and it gives you the opportunity to finetune the parameters if necessary, such as the inode density (newfs -i). Any help/comments would be appreciated. Please CC me, as I am not a subscriber of this list. Thanks!!! In that case you should set the Reply-To header in your mail appropriately. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. In My Egoistical Opinion, most people's C programs should be indented six feet downward and covered with dirt. -- Blair P. Houghton ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Headsup: USB MFCs to 4.x
Julian Elischer [EMAIL PROTECTED] wrote: I have just merged in most of the lowest level changes to 4.x from 6.x. Thank you very much! It's very good to see such important updates in RELENG_4, despite the existance of RELENG_5. If you use USB on 4.x machines and are planning on following RELENG_4 then I suggest you test the latest sources to avoid nasty surprises later. I do follow RELENG_4. Unfortunately I'm currently in the process of moving to a new flat, so I have zero time for testing right now. I will probably merge some of the actual device drivers as well, though I have limited resources for testing them.. Maybe my USB modem will work one day. For the time being I'm using a good old serial (RS232) modem (fortunately my notebook still has an RS232 serial port). I'll test it as soon as I have the time, and report the results. Thanks again for your work, it's really appreciated! Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Python tricks is a tough one, cuz the language is so clean. E.g., C makes an art of confusing pointers with arrays and strings, which leads to lotsa neat pointer tricks; APL mistakes everything for an array, leading to neat one-liners; and Perl confuses everything period, making each line a joyous adventure wink. -- Tim Peters ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck_ufs: cannot increase directory list
Eric Anderson [EMAIL PROTECTED] wrote: I rebooted my server, and fsck'ed the disks, and here's what I get: # fsck -y /vol1 ** /dev/da0s1d ** Last Mounted on /vol1 ** Phase 1 - Check Blocks and Sizes fsck_ufs: cannot increase directory list That error message is printed if a memory allocation fails. (It's the memory that fsck uses for caching the inodes of directories.) # df -i Filesystem 1K-blocksUsed Avail Capacity iused ifree %iused Mounted on /dev/da0s1d1891668564 1643042028 9729305294% 32927755 211542003 13% /vol1 What's wrong? It lets me mount it rw and ro, but I'm afraid data is going to get corrupt. Well, you have a 2 Tbyte filesystem with nearly 250 million inodes. That's really a lot, and fsck will need a lot of memory (and probably run for a long time). First you should check if you hit a (soft or hard) resource limit with the ulimit command. See sh(1) for details on the ulimit usage. If you ran fsck in single user mode, you might have to enable swapping beforehand (swapon -a) if your physical RAM is not sufficient. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I suggested holding a Python Object Oriented Programming Seminar, but the acronym was unpopular. -- Joseph Strout ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: internal modem / pnp0 / FAQ error ?
pan [EMAIL PROTECTED] wrote: From: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html 4.5.2. Why is FreeBSD not finding my internal Plug Play modem? You will need to add the modem's PnP ID to the PnP ID list in the serial driver. [...] That FAQ entry is very outdated. And it does not apply to your case at all. I have a pci winmodem The term PnP from the FAQ entry refers to ISA PnP cards, not to PCI cards. Furthermore, it refers to cards which are controlled by the sio driver (serial I/O), not to win modems. It's a completely different thing. (yes I know - plan on using ltmdm) So your winmodem card uses the Lucent chipset supported by ltmdm? If so, you only need to install ltmdm, and that's all you need to do. If ltmdm doesn't support your winmodem, then it's pretty much a dead horse. I would rather recommend to buy a real modem. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Emacs ist für mich kein Editor. Für mich ist das genau das gleiche, als wenn ich nach einem Fahrrad (für die Sonntagbrötchen) frage und einen pangalaktischen Raumkreuzer mit 10 km Gesamtlänge bekomme. Ich weiß nicht, was ich damit soll. -- Frank Klemm, de.comp.os.unix.discussion ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange disk problems make the system lock up
Scot Hetzel [EMAIL PROTECTED] wrote: In FreeBSD, the disk is broken down into slices and partitions. A slice is equivalent to a DOS partition, but can be broken down into 8 partitions (a-h). The c partition is reserved because it is used to define the entire disk. It's not reserved, it's rather a convention. Also, there is the convention that a is the root filesystem, b is the swap partition, and d is the entire disk. None of those conventions are enforced. The only thing which is hardwired is that the default kernel will always try to boot from the a partition, so if you make a bootable disk, then the root filesystem should be on a. If you have a removable disk or other medium on which you only need a single filesystem (an dit doesn't have to be bootable), nothing prevents you from newfs'ing the c partition and mounting it. I've done that before. -ROOT-# dd if=/dev/zero of=disk bs=1m count=20 20+0 records in 20+0 records out 20971520 bytes transferred in 0.389265 secs (53874653 bytes/sec) -ROOT-# vnconfig -s labels -c /dev/vn0 disk -ROOT-# disklabel -w -B vn0 auto -ROOT-# disklabel vn0 | sed 1,/part/d #size offsetfstype [fsize bsize bps/cpg] c:409600unused0 0 # (Cyl.0 - 19) -ROOT-# newfs /dev/vn0c Warning: Block size restricts cylinders per group to 105. /dev/vn0c: 40960 sectors in 10 cylinders of 1 tracks, 4096 sectors 20.0MB in 1 cyl groups (105 c/g, 210.00MB/g, 2560 i/g) super-block backups (for fsck -b #) at: 32 -ROOT-# mount /dev/vn0c /mnt -ROOT-# df -k /mnt Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/vn0c 201102 18500 0%/mnt Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Python is executable pseudocode. Perl is executable line noise. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA ICRC error
I remember having the same problem on a machine once. Replacing the IDE cable with a known good one helped. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. C is quirky, flawed, and an enormous success. -- Dennis M. Ritchie. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: swapfile being eaten by unknown process
John [EMAIL PROTECTED] wrote: Thanks for your input so far. Here is the output from top: last pid: 59737; load averages: 0.02, 0.03, 0.00up 1+18:32:57 15:16:36 82 processes: 1 running, 79 sleeping, 2 zombie CPU states: 0.4% user, 0.0% nice, 0.4% system, 0.0% interrupt, 99.2% idle Mem: 105M Active, 31M Inact, 61M Wired, 144K Cache, 33M Buf, 33M Free Swap: 455M Total, 86M Used, 369M Free, 18% Inuse PID USERNAME WRITE FAULT TOTAL PERCENT COMMAND 177 root 0 0 0 0 0 0 0.00% adjkerntz 59693 www 0 0 0 0 0 0 0.00% speedy_back 59692 www 0 0 0 0 0 0 0.00% speedy_back 59663 www 0 0 0 0 0 0 0.00% speedy_back 59662 www 0 0 0 0 0 0 0.00% speedy_back 59658 www 0 0 0 0 0 0 0.00% speedy_back [...] lots of other processes but all with 0s. occasionally I will see numbers under VCSW IVCSW READ but they just flash on then its back to 0 again. That looks pretty normal. In fact, it looks perfectly fine. There doesn't seem to be any significant paging activity, but maybe some processes have been swapped to disk (which is normal). Type vmstat -w 5 and watch the output of the po (page out) and sr (scan rate) columns for, say, half a minute. If they're near zero most of the time, there is no paging activity, and you need not worry about RAM. Next, I'd suggest you type ps -waxwum | less. That will dispay a list of processes sorted by memory usage (largest ones at the top). Check the top-10 or so for any processes that might be kill candidates. If in doubt, copypaste the top-10 into a follow-up in this thread. I need to look up what those 2 processes are doing zombified. Zombie processes don't take up any memory (except for the entry in the process table, but that's just a few bytes), so they shouldn't cause any problem. I think I just need more RAM, but I'd expect there to be none free before it starts eating swap. Why with free RAM wouldn't my swap also be liberated? You do not need more RAM. At most, a little more swap space wouldn't hurt, but even that isn't strictly necessary, given that only 18% of your swap are in use. I'd start worrying if that number goes beyond 50%. FreeBSD tries to conserve RAM by swapping processes and pages to disk which haven't been used for a certain time. For example, on a system which runs X11, you'll see the text-mode gettys (those running one the syscons virtual consoles) being moved to swap. That's a good thing, because those processes aren't needed normally, so keeping them in RAM would be a waste of memory. If they're used one day, they're paged back into RAM pretty quickly. Also, when RAM begins to get full, FreeBSD starts paging more aggressively. If the situation clears up and RAM gets free again, those pages stay in swap until they're actually used. For those reasons (and others) it is normal that swap space is being used even though there is free RAM available. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one? -- Tom Cargil, C++ Journal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Save the Demon!
[EMAIL PROTECTED] wrote: Oh I would not suggest removing Beastie altogether Jesper! That one is too well known, but to add a supplementary angel with the feminine would add to the Package. I am not talking St. Michael here, but rather Lillith, or Mary, or one of Lot's daughters, or even Dinah (who was raped), or the Harlot by the side of the road...no, not the harlot, because it would better be the absolute opposite of Beastie...but not too soft, not Bianca, but the shrew. Probably a Mary would make a good bet. AFAIK, one of the main points of that logo competition is to do away with anything that could be interpreted in an religious way. Therefore an image of an Angel would be completely inappropriate. (Why feminine anyway? Beastie has no specific gender, therefore it would be best to not bias the logo one way or the other.) Also take into account that a logo is not a mascot and should not be designed in a way that it could be confused with the mascot (Beastie will still exist), so the logo should not contain a person or creature. Just my 2 cents, YMMV. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Emacs ist für mich kein Editor. Für mich ist das genau das gleiche, als wenn ich nach einem Fahrrad (für die Sonntagbrötchen) frage und einen pangalaktischen Raumkreuzer mit 10 km Gesamtlänge bekomme. Ich weiß nicht, was ich damit soll. -- Frank Klemm, de.comp.os.unix.discussion ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Save the Demon!
[EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: AFAIK, one of the main points of that logo competition is to do away with anything that could be interpreted in an religious way. Therefore an image of an Angel would be completely inappropriate. (Why feminine anyway? Beastie has no specific gender, therefore it would be best to not bias the logo one way or the other.) I'm not seeing a problem here. Beastie is not a religious icon, not is it intended to be one. Right -- but it looks like one. And every now and then there are people who are offended by it because of their religious bias. FreeBSD has no connection (afaik) with any religion. Right. What we do have is a well recognised and accepted logo which has been around for a long time. Changing it because a couple of people have misinterpreted it strikes me as foot shooting. Nobody is proposing to change the existing mascot, so there is no foot shooting. This competition is about creating a new logo, not changing the existing mascot. Putting yet another religous creature (such as an angel) into the newly designed logo would make matters worse -- _That_ would qualify as foot shooting. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. To this day, many C programmers believe that 'strong typing' just means pounding extra hard on the keyboard. -- Peter van der Linden ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Save the Demon!
Dan Ponte [EMAIL PROTECTED] wrote: Oliver Fromme [EMAIL PROTECTED] wrote: AFAIK, one of the main points of that logo competition is to do away with anything that could be interpreted in an religious way. Therefore an image of an Angel would be completely inappropriate. (Why feminine anyway? Beastie has no specific gender, therefore it would be best to not bias the logo one way or the other.) Also take into account that a logo is not a mascot and should not be designed in a way that it could be confused with the mascot (Beastie will still exist), so the logo should not contain a person or creature. Such a goal makes no sense. It does make sense. It was one of the requirements laid down for NetBSD's logo competition, which was completed successfully last year. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. (On the statement print 42 monkeys + 1 snake:) By the way, both perl and Python get this wrong. Perl gives 43 and Python gives 42 monkeys1 snake, when the answer is clearly 41 monkeys and 1 fat snake.-- Jim Fulton ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Logo competition (was: Re: Save the Demon!)
Mike Jakubik [EMAIL PROTECTED] wrote: Oliver Fromme said: [...] I'm not seeing a problem here. Beastie is not a religious icon, not is it intended to be one. Right -- but it looks like one. And every now and then there are people who are offended by it because of their religious bias. Boo Hoo! Use Linux then, or is the Penguin sacrilege to your religion too? Personally I do not care, but there are people who do care, and we shouldn't be too arrogant or intolerant to ignore them. There's no sane reason to scare them off to Linux. Currently, FreeBSD lacks a real logo (it does have a mascot, though, but that's a different thing), and given the fact that FreeBSD is an open source project largely driven by community efforts, it's a natural thing to let the community design and vote for a new logo by having a public competition. I don't see anything wrong with that. NetBSD did the very same thing last year, for very similar reasons. (BTW, the subject of this thread is nonsense. There's no need to save the demon because Beastie is not in danger at all; apart from that it's spelled daemon or dæmon.) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I suggested holding a Python Object Oriented Programming Seminar, but the acronym was unpopular. -- Joseph Strout ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ULE status
Mipam [EMAIL PROTECTED] wrote: On Tuesday, 8. February 2005 14:02, Mipam wrote: Okay clear, but the fact that it's in 5-stable suggests the it's stable to use, else why would it be in 5-stable. Maybe i'm completly wrong in this interpretation? [...] I though what's in -stable should be safe to use, but i wasn't sure this is the right understanding of 5-stable. No. There have always been things in -stable which were not stable itself. Of course, they were not enabled by default, and the documentation contained the appropriate warnings. There are always things which could perfectly be used to shot yourself in the foot. One of the well-known examples would be NULLFS and UNIONFS which were part of 3-stable and 4-stable all the time, but they weren't really stable in general (except under very limited, controlled conditions). (Note that I'm not saying anything about the stability of ULE.) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. If you aim the gun at your foot and pull the trigger, it's UNIX's job to ensure reliable delivery of the bullet to where you aimed the gun (in this case, Mr. Foot). -- Terry Lambert, FreeBSD-hackers mailing list. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ULE status
Mipam [EMAIL PROTECTED] wrote: Thanks for all comments on this topic. A good point was made upon the fact that there were always options available that weren't stable in X-stable. The docs contained appropriate warnings about it you mentioned. I guess you're referring to my comment. Cool, I wish to read the docs on ULE and possible warnings about using ULE, where can i find it? So far, the ULE scheduler has not been part of any stable FreeBSD release, so it's not completely surprising that there isn't much documentation to be found. (I think it's not even mentioned in NOTES.) If you're looking for a generic description of URL and all the technical details, have a look at this paper: http://www.usenix.org/publications/library/proceedings/bsdcon03/tech/roberson.html Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure. -- Eric Allman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adjusting time on a secured FreeBSD machine.
Eli K. Breen [EMAIL PROTECTED] wrote: I'm running in to an issue where I can't set the clock on a machine because the secure level was bumped to 2 before the clock was set. Unfortunately adjustments are now clamped to 1s. Is there any way I can force ntpd to adjust the clock by say, 1s every two seconds or at least something more frequent than 0.128 ms / update? No. (It's 0.5 ms/s, not 0.128 ms/s, BTW.) The ntpd(8) manpage says: | The maximum slew rate possible is limited to 500 parts-per-million | (PPM) as a consequence of the correctness principles on which the | NTP protocol and algorithm design are based. As a result, the local | clock can take a long time to converge to an acceptable offset, about | 2,000 s for each second the clock is outside the acceptable range. | During this interval the local clock will not be consistent with any | other network clock and the system cannot be used for distributed | applications that require correctly synchronized network time. So your choices are to reboot, or to wait until the local clock is synchronized again. You didn't mention how far off your clock is, so I can't tell how long it will take. The maximum slew rate is 1.8 seconds per hour, so if your clock is off by half a minute, it will take about 17 hours to get back in sync. If you can't wait, you'll have to reboot. Best regards Oliver PS: You need to specify the -x option to ntpd, so it does not try to step the clock by more than 1 second. -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. C is quirky, flawed, and an enormous success. -- Dennis M. Ritchie. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adjusting time on a secured FreeBSD machine.
Rob MacGregor [EMAIL PROTECTED] wrote: Eli K. Breen wrote: I'm not sure that this will cut it as it will days a very long time to adjust to the proper time. Is there any way to speed this up? Not within NTPd itself. You could go with manually stepping the time in 1s intervals. Adding to that, the following /bin/sh snippet should do (untested!). You have to kill ntpd before. STEP=100# number of seconds to step forward while [ $STEP -gt 0 ]; do date -f %s $(( `date +%s` + 1 )) sleep 1 STEP=$(( $STEP - 1 )) done It will take about 100 seconds to correct the clock forward by another 100 seconds. If you need to correct backwards, replace + 1 by - 1. For different numbers of seconds to correct, replace the 100 in the first line. When you have approached the correct time sufficiently (i.e. within a few seconds), restart ntpd with the -x option. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Documentation is like sex; when it's good, it's very, very good, and when it's bad, it's better than nothing. -- Dick Brandon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adjusting time on a secured FreeBSD machine.
Sorry for replying to myself ... Oliver Fromme [EMAIL PROTECTED] wrote: Adding to that, the following /bin/sh snippet should do (untested!). You have to kill ntpd before. STEP=100# number of seconds to step forward while [ $STEP -gt 0 ]; do date -f %s $(( `date +%s` + 1 )) sleep 1 STEP=$(( $STEP - 1 )) done It will take about 100 seconds to correct the clock forward by another 100 seconds. If you need to correct backwards, replace + 1 by - 1. For different numbers of seconds to correct, replace the 100 in the first line. When you have approached the correct time sufficiently (i.e. within a few seconds), restart ntpd with the -x option. Stepping backwards with that script won't work, I guess, because the steps will be larger than 1 second. If you have to step backwards, try to replace the date line with these: NOW=`date +%s` sleep 0.9 date -f %s $NOW Again: it's untested. Also beware that it might be a very bad idea to step the time on a live multi-user system. Some programs don't like it at all. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. The scanf() function is a large and complex beast that often does something almost but not quite entirely unlike what you desired. -- Chris Torek ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Use loader to load kernel.gz and mfsroot.gz in ext2 filesystem?
?? ?? [EMAIL PROTECTED] wrote: I put loader,kernel.gz and mfsroot.gz in an ext2(dos) file system on harddisk,and hope to directly use grub or use grub and loader(or other means?) to boot the system. When I use grub to transfer loader,I find it(freebsd loader) can't read files in ext2(dos) file system,and when i use grub 0.93 of redhat 9.0 to directly load mfsroot.gz by initrd /mfsroot.gz,it fails with linux kernel must be loaded before initrd. My goal is to put install.cfg,freebsd kernel and mfsroot on harddisk,then boot from harddisk into freebsd,and install it from original freebsd cd. Why are you trying to use ext2fs (or msdosfs)? Is there a reason why you cannot use UFS? I suggest you use UFS. There's no need to use GRUB at all. I also wonder why you don't boot the installation from CD in the first place. Since you use a CD anyway ... Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Clear perl code is better than unclear awk code; but NOTHING comes close to unclear perl code (taken from comp.lang.awk FAQ) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Very large directory
Peter Jeremy [EMAIL PROTECTED] wrote: On Wed, 2005-Jan-19 21:30:53 -0600, Phillip Salzman wrote: They've been running for a little while now - and recently we've noticed a lot of disk space disappearing. Shortly after that, a simple du into our /var/spool returned a not so nice error: du: fts_read: Cannot allocate memory No matter what command I run on that directory, I just don't seem to have enough available resources to show the files let alone delete them (echo *, ls, find, rm -rf, etc.) I suspect you will need to write something that uses dirent(3) to scan the offending directory and delete (or whatever) the files one by one. Skeleton code (in perl) would look like: [...] I would suggest trying this simple hack: cd /var/spool/directory ; cat . | strings | xargs rm -f It's a dirty hack, but might work, if the file names in that directory aren't too strange (no spaces etc.). Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. If Java had true garbage collection, most programs would delete themselves upon execution. -- Robert Sewell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Very large directory
David Landgren [EMAIL PROTECTED] wrote: Oliver Fromme wrote: I would suggest trying this simple hack: cd /var/spool/directory ; cat . | strings | xargs rm -f It's a dirty hack, but might work, if the file names in that directory aren't too strange (no spaces etc.). why suggest a dirty hack that might not work, when the proposed Perl script would have worked perfectly? In this case, the hack _should_ work, and is about 1/10 of the size of the perl script and leaves a lot less room for typing errors. Aport from that, perl might not even be installed on the machine in question, who knows. But of course: YMMV. It was just a suggestion. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I made up the term 'object-oriented', and I can tell you I didn't have C++ in mind. -- Alan Kay, OOPSLA '97 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ciss(4) adapter not recognized (Compaq/HP Smart Array 6i/64xx)
Hi, We've got a new Compaq/HP server machine, but there are problems installing FreeBSD because the RAID controller is not recognized. It's a CISS 6i (according to the specs) which I expected to be recognized by the ciss(4) driver. But unfortunately, it isn't. This is the output from dmesg: pci2: unknown card (vendor=0x0e11, dev=0x0046) at 1.0 irq 5 According to pciids.sourceforge.net, 0e11 is Compaq, and 0046 is their ID for the Smart Array 64xx. It is not in the list of supported IDS in src/sys/dev/ciss/ciss.c. Would it work to just add that ID to the list, compile a kernel, and then use that kernel to boot the installation? (I don't have time for many experiments, because the box is installed in a computing centre which is not exactly nearby. That's why I'm asking here first, instead of just trying to insert that ID in the source.) I'm wondering if the device ID is really correct. All the other IDs in the ciss.c source are in the 0x40XX range. 0x0046 seems pretty odd. Also, there's a CISS_BOARD flag associated with each of the devices. Should I set it to SA5 or SA5B for the new ID? (My guess would be SA5, but I could be wrong.) Any hints and advice would be greatly appreciated! Best regards Oliver PS: I'm using 4-stable, but I checked the CVS repository and verified that the device ID is neither in 5-stable nor HEAD. Searching for this device in the list archives gave zero hits. -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I have stopped reading Stephen King novels. Now I just read C code instead. -- Richard A. O'Keefe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: backporting tail from HEAD to RELENG_5
Xin LI [EMAIL PROTECTED] wrote: On Thu, Jan 13, 2005 at 01:01:44PM -0600, Doug Poland wrote: Cool, I currently get this functionality from misc/xtail. xtail was on my short list of must-have ports. Would you please share the list with us? I think it would be helpful if we know the needs :-) I'm surprised that nobody else replied. This is a list of small non-X11 ports that I install on most machines (even non-FreeBSD if applicable). This list is certainly not complete, and everyone probably has his/her own favourite tools. - cpdup(great to copy/sync directory trees) - cvsup-without-gui (cannot use FreeBSD without it) - elinks (nice text web browser, better than lynx) - fping(useful to ping multiple hosts/nets at once) - joe (my fav. editor, though I can cope with vi, too) - logsurfer (useful tool to watch your logs) - lsof (can't live without it) - lynx-ssl (sometimes useful) - netcat (well-known) - nmap (well-known) - omi (I use this one to mirror stuff via FTP) - par (I use this often for mail / news) - screen (can't live without it) - strace (better than ktrace and truss, IMO) - super(better than sudo, in my opinion) - trafshow (very nice tool to watch network activity) - zsh (my favourite shell, very powerful) Of course, lots of people will probably have different opinions about some of those tools. But that's one of the big advantages of FreeBSD and its ports collection: You have enough things to chose from, so go and try them to find the one which suits you best. :-) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Python is executable pseudocode. Perl is executable line noise. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dual cpu and top in 5.3
Chris [EMAIL PROTECTED] wrote: Hi, I have a dual athlon mp system running FreeBSD 5.3-RELEASE-p2, I have wondered if both cpu's should show in top. Here is a snapshot of my top output. last pid: 15520; load averages: 0.28, 0.09, 0.03up 7+23:21:08 23:05:33 153 processes: 2 running, 151 sleeping CPU states: 0.2% user, 0.0% nice, 3.3% system, 2.5% interrupt, 94.0% idle Mem: 770M Active, 67M Inact, 115M Wired, 40M Cache, 112M Buf, 9804K Free Swap: 2048M Total, 920K Used, 2047M Free I compiled a SMP kernel of course, but I am not confident I have this setup right because of lack of evidence showing I am in SMP modein top, here is my dmesg boot log which does say 2 cpus detected. On SMP machines, top should show a column titled C which contains the number of the processor on which the process was scheduled last (i.e. either 0 or 1 if you have two processors). [...] FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 [...] SMP: AP CPU #1 Launched! Looks OK. You can also query sysctl hw.ncpu to get the number of processors detected (and supported) by the kernel. Is it all looking dandy and I am ok or have I missed something, and should top show 2 cpu's or just 1? The top command doesn't display the number of processors directly, as far as I know. But it has the C column, as explained above. On an SMP machine of mine with two processors (it's a dual Celeron-466), the output looks like this: last pid: 55565; load averages: 0.01, 0.01, 0.00 up 295+04:59:09 00:40:23 76 processes: 1 running, 75 sleeping CPU states: 0.2% user, 0.0% nice, 0.2% system, 0.0% interrupt, 99.6% idle Mem: 72M Active, 7296K Inact, 35M Wired, 48K Cache, 25M Buf, 39M Free Swap: 320M Total, 29M Used, 291M Free, 8% Inuse PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 77 bind 2 0 12512K 9820K select 0 394:50 0.00% 0.00% named 22723 root 2 0 2200K 264K poll 0 190:52 0.00% 0.00% dovecot 111 root 2 0 3056K 936K select 1 94:35 0.00% 0.00% sendmail 79 root 2 0 1312K 364K select 1 35:56 0.00% 0.00% ntpd .. and so on. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. A language that doesn't have everything is actually easier to program in than some that do. -- Dennis M. Ritchie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
Craig Boston [EMAIL PROTECTED] wrote: On Tuesday 04 January 2005 9:57 pm, Wilkinson, Alex wrote: How can I confirm that ACPI has been setup to do this ? Hmm, well, the easiest thing to check is to run sysctl hw.acpi.power_button_state and see if that sysctl exists and if so, what it's set to (mine is S5, which IIRC is complete power-off). Also, check dmesg and see if you see a line similar to acpi_button0: Power Button on acpi0 If both of those show up, chances are that your ASL has a power button entry and it should do the right thing. Other than that, you could always wait until the system is idle and just try hitting the button to see what happens ;) I'd recommend to quit all applications (particularly X11), then forcibly re-mount all filesystems to read-only (using mount -ufo ro ...), then press the power button. That way no harm will be done to the filesystems if it doesn't work. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
Rob [EMAIL PROTECTED] wrote: [...] However, the main user of this particular PC is not at all a guru; on 4.10 I had rc.conf configured such that at bootup all filesystems would be automatically fixed with: fsck_y_enable=YES. With 4.10, this always worked nicely, whatever sudden power cut have happened. However, with 5.3, a recent powercut crippled the /usr filesystem such that X11 hanged. The user of this PC was convinced that FreeBSD was infected by a virus :(. I would strongly advise you to teach that user to properly shut down the machine instead of just pressing the power button, thus eliminating the real cause of the problem. (If you're suffering from frequent power outages, then a UPS should be installed.) By the way, you can map a key combination (Ctrl-Alt-Del or something else) to the »halt« or »power-down« functions, using kbdcontrol, so it's very easy and intuitive to shut down the machine properly. See the kbdmap(5) manpage for details. Apart from that, I suggest you simply disable background fsck. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. We're sysadmins. To us, data is a protocol-overhead. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the best graphicscard for FreeBSD
alex bustamante [EMAIL PROTECTED] wrote: Is there any graphicscard that is known to work better than others with freebsd/x11? (open sourcecode for the drivers, etc) Here are my two (Euro) cents ... If you don't want to play the latest 3D ego shooter games, get a Matrox MGA G400 (or even G200) from eBay. They are cheap, work very well for 2D stuff (even support OpenGL for those cool 3D screen savers). Also, the analog VGA output of Matrox cards has legendary quality which matches that of the digital DVI output of other cards (you get an excellent, sharp picture). And last but not least, the XFree86/Xorg drivers are rock-stable. I'm using Matrox MGA cards for many years, starting with the Matrox Millenium. Unfortunately, Matrox has gotten stingy of drivers and specs lately, so I'd advise against buying their newer cards (Parhelia). Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. When your hammer is C++, everything begins to look like a thumb. -- Steve Haflich, in comp.lang.c++ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 on Intel 386 ?
Rob [EMAIL PROTECTED] wrote: I thought 386 support had been removed since 5.X. But http://www.freebsd.org/releases/5.3R/installation-i386.html says: 1.2 Hardware Requirements FreeBSD for the i386 requires a 486 or better processor to install and run (although FreeBSD can run on 386 processors with a custom kernel) What does this mean? Should I install on 486 or higher, build a custom kernel and then physically put the very same disk in a 386 PC? I haven't tried this myself, but you should be able to re- place the GENERIC kernel on the install CD with a custom kernel that contains i386 CPU support. That way you don't have to physically move disk drives. Alternatively, install FreeBSD 4.10 (or -stable) which still supports i386 in GENERIC, then update from there, keeping the i386 option in your kernel. Note that you will need a hardware FPU (i387 math co-pro). FreeBSD 4.x supports math emulation, so you don't need a hardware FPU there, but apparently that support has been removed in FreeBSD 5.x. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one? -- Tom Cargil, C++ Journal ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Configuring a DVD burner on 4.10
DONALD GOODWIN [EMAIL PROTECTED] wrote: The drive is seen by the OS. I can mount it using a normal CD-R. But when I try to use it for a burner, it doesn't work (get a bad ioctl message). The _exact_ wording of the error message might be helpful. When I run camcontrol devlist, the drive shows up on bus 2. But, when I run cdrecord, bus 2 is not seen. Camcontrol reports the device (/dev/adc0a) is using pass4. But there is no /dev/pass4 device in /dev. Then create it (as root): cd /dev; sh MAKEDEV pass4 The message i get is inapproriate ioctl. Driving me nuts. Thoughts/pointers/questions are greatly appreciated. I would recommend using the dvd+rw-tools port instead of cdrecord (/usr/ports/sysutils/dvd+rw-tools). Despite the name, it supports all types of DVD-R/-RW/+R/+RW. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Clear perl code is better than unclear awk code; but NOTHING comes close to unclear perl code (taken from comp.lang.awk FAQ) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ALi M5451 Sound Card.
David Rio [EMAIL PROTECTED] wrote: pcm0: Acer Labs M5451 at device 4.0 on pci0 pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 You could try to add this line to your kernel: options PCI_ENABLE_IO_MODES It might help, or maybe not, but it's worth a try. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broadcom BCM5703X causing reboot? 4.8-RC2
L. Jankok [EMAIL PROTECTED] wrote: FreeBSD proxy.mynet.not 4.7-20030218-STABLE FreeBSD 4.7-20030218-STABLE #0: Mon Feb 24 15:17:06 CET 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/MYNET-S MP-PROXY i386 I have now installed 4.8-RELEASE on my machine. Lets see how long it will survive. :-) bge0: Broadcom BCM5703X Gigabit Ethernet, ASIC rev. 0x1002 mem 0xf7ef-0xf7 ef irq 11 at device 2.0 on pci1 Hmm, mine is a bit different: bge0: Broadcom BCM5701 Gigabit Ethernet, ASIC rev. 0x105 mem 0xf7fb-0xf7fb irq 5 at device 5.0 on pci1 works like a charm pumping approximately 232 GB a month Thanks, that's very encouraging ... however ... My machine has a network traffic of 540 Gbyte a *DAY*. That's about 16 Tbyte a month, if my /usr/bin/bc isn't failing. :-) Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Passwords are like underwear. You don't share them, you don't hang them on your monitor or under your keyboard, you don't email them, or put them on a web site, and you must change them very often. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolver Issues (non valid hostname characters)
Ken Menzel [EMAIL PROTECTED] wrote: I am not sure where you think freebsd needs support for underscores in the resolver. freebsd2# hostname -s free_bsd2 freebsd2# hostname free_bsd2.icarz.com freebsd2#vi /etc/hosts (edit host file here adding new name) freebsd2# ping free_bsd2 PING free_bsd2.icarz.com (207.99.22.11): 56 data bytes 64 bytes from 207.99.22.11: icmp_seq=0 ttl=64 time=0.128 ms Neither the machine's hostname nor /etc/hosts have got anything to do with DNS or BIND. In fact, you can set the machine's hostname to anything you like, including not setting it at all, or setting it to something completely different from the machine's DNS name. It might confuse a few programs or scripts, though. In fact, I was working for some time on a Solaris machine before I noticed that its hostname was -s (yes, a dash followed by the letter s). It turned out that a cow-orker had run a configure script of some crappy Linux software a few days before. That configure script used hostname -s to find out the hostname, but that particular version of Solaris did not support that option. Instead, it just set the hostname to whatever was given as the first argument. On another pool of machines, /etc/hosts contains MAC addresses. Those wouldn't be legal names in DNS (because of the colons), but they work perfectly fine in /etc/hosts, so you can easily lookup and ping MAC addresses. That has been very handy in that environment. But in DNS, anything except letters, digits and dashes is not allowed (apart from the separating dots, of course). Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. If you do things right, people won't be sure you've done anything at all. -- God in Futurama season 4 episode 8 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Invalid ps start time values for kernel processes ?
Paul Koch [EMAIL PROTECTED] wrote:
The ps output value for STARTED appears to be incorrect for
kernel started processes. I found this while writing a tiny ps
for our freebsd based network appliance. The start time returned
from /proc/{normal pid}/status (man procfs) appears to be in
UTC while the start time for a kernel process appears to be
localtime (or the other way round). This gave me wild values.
Is this correct behaviour ?
Is your CMOS clock running with local time, rather than UTC?
(i.e. does the file /etc/wall_cmos_clock exist?)
In that case, the kernel will start up with the wrong time
information, because it doesn't know the timezone you're in
(the kernel always uses UTC internally). This information
is corrected by the adjkerntz program in the early stages
of the boot process.
However, the kernel processes start before that correction
happens. If you were living east of Greenwich (i.e. positive
timezone offset), the start time values would even be in the
future.
If FreeBSD is the only operating system on that machine,
I suggest that you run the CMOS clock with UTC, avoiding the
problem alltogether. Of course, you can also just ignore
the wrong start values. They should not cause any harm.
I don't think there is an easy way to fix the problem.
Regards
Oliver
--
Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
All that we see or seem is just a dream within a dream (E. A. Poe)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: 5.0-STABLE ???
Thomas T. Veldhouse [EMAIL PROTECTED] wrote: The only problem I see with this is that anybody following this particular RELEASE has to follow CURRENT, which is almost a contradiction of terms. Not necessarily. There's a RELENG_5_0 branch. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 5.0-STABLE ???
Thomas T. Veldhouse [EMAIL PROTECTED] wrote: A branch or a tag? I don't believe it was branched. A branch. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Ifconfig config of gif tunnels
Matthew Dillon [EMAIL PROTECTED] wrote: I would like mergemaster a whole lot more if: (1) It just overwrote system files that users are not supposed to change anyway, like files in /etc/defaults and the /etc/rc* files. Additionally, I think it might be a good idea to make those files schg by default, and teach mergemaster to noschg/schg them if required. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Some Changes to Mergemaster
Matthew Dillon [EMAIL PROTECTED] wrote: (2) Initial diff does not use the pager and chops it to fit on a single screen. This fixes the problem where you would sometimes be left in the pager and sometimes not be left in the pager, depending on the size of the diff, making it difficult to quickly run through the vast majority of mergemaster files that you would normally just replace, e.g. /etc/defaults/*, /etc/rc* (for most people) and do not need to see the full diff. Will there be an option to always use $PAGER? I prefer that mode of operation (and I guess it would take some time to get my fingers used to anything else). Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: /dev/acd0c bug
Max Khon [EMAIL PROTECTED] wrote: On Tue, Jun 25, 2002 at 11:59:23PM -0700, Mr. Darren wrote: the iso's in question were converted from .cue/.bin.. the vcds I burn turn out ok.. just the mode1 iso's don't... I get that error every time. all my devs are current.. could be related to the ATA problems... why generated .iso image has .ugh extension? bchunk generates such extension when it can't determine track mode properly. if you have created .cue file yourself, you could specify incorrect track mode. can you show your .cue file? And why not used cdrdao, which can read .bin/.cue files directly, without the need to make the .iso detour? I use it successfully on FreeBSD 4.6 with a 24x ATAPI CD-RW drive (Benq, formerly known as Acer). ftp://ftp.freebsd.dk/pub/ATA/ (I don't think the ATA-enabled cdrdao is in the ports yet.) Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: wi0+ata
Vlad Berliba [EMAIL PROTECTED] wrote: 1. I have a Lucent Orinoco PCMCIA radio card witch PCI-PCMCIA adapter. The card works great since FreeBSD 4.4. Is there any way to be recognized faster by the kernel ? I have to wait 10s until it comes up. That's something I'd like to know, too. It seems to happen with all PCMCIA cards, not only NICs. It's a bit annoying to have to wait 10 seconds just to read a picture from my camera's CompactFlash. 2. I'm experiencing a speed drop on moving files on my hard disk. I don't know about the average data rate but I was having peeks of 8.x sometimes even 9 MBytes/s and know the maximum is 7.x Mbytes/s Well, the speed changes on the area of the disk. On the outer cylinders, a disk is much faster than on the inside. So it depends very much where the data gets written. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: how to tell if 'make buildworld' finished?
Christopher Schulte [EMAIL PROTECTED] wrote:
At 10:37 PM 1/6/2002 +0100, you wrote:
I usually run a shell command like this ('#' is the prompt):
# (date; make buildworld; date) | tee /var/tmp/buildworld.log
You can also look at the `script` command. When executed, a new shell will
begin and all output to terminal is stored in a file which can be checked
after the fact.
I know about script, but I don't like it that much.
It tends to destroy my carefully crafted zsh prompt
(which is not simply a #, of course). :-}
Regards
Oliver
--
Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
All that we see or seem is just a dream within a dream (E. A. Poe)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: pathname length over NFS
Chad R. Larson [EMAIL PROTECTED] wrote: Why is there an overlap between the recommended codes in sysexits(3) and /usr/include/errno.h? They serve different purposes, and are used for different things, so there shouldn't be a conflict. The errno values are used as return values from syscalls and library functions. They are _not_ used for program exit codes. Unfortunately, some programs print numerical errno values because they're too stupid (or too lazy) to use perror() or strerror() or some similar way to display a readable error string. Normally, the user should not need to care about errno numbers at all. They are for programmers. The sysexits(3) values were originally intended as a way to communicate between programs: When sendmail calls an external program (e.g. mail_local or procmail), it checks the exit code to find out if everything is alright, or if a transient problem occured, or if something went out of resources, or if a fatal error occured. Depending on that, sendmail deletes the mail, or spools it locally for another delivery attempt at a later time, or bounces it back with an appropriate error message. Other, non mail-related tools use sysexits(3) values, too, to further classify the result beyond the traditional 0/ok and 1/failure, so that scripts and other programs have a better chance to do sensible things when something went wrong. This is a good thing, IMO. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: FreeBSD CD 4.4 CDROM subscriptions - who's doing what?
Warner Losh [EMAIL PROTECTED] wrote: Yes. It appears The Daemon News is going to produce CDROM using the official iso images that the project will release. The posting was at great pains to say they are not associated with WindRiver. I expect that others may do this, or something similar. FreeBSD Services in the UK has already announced they are doing a DVD of all 4 ISOs plus a bunch of extra stuff. Others may do other things too, but I don't think I've seen an announcement from anyone else yet. You can regard this as an official announcement ... Lehmanns in Germany is selling a six CD-ROM set, which is essentially the first four original CDs plus some extra stuff, including Alpha installation bits, extra packages, archives of German BSD mailing lists, German documentation and German sysinstall with translated online help texts (optional, of course -- you can still run the original English sysinstall if you want). Regards Oliver PS: This is the URL: http://www.lob.de/cgi-bin/work/outputexpert?mode=viewonetitnr=210084150 -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: dirpref gives massive performance boost
Tim Bunce [EMAIL PROTECTED] wrote: Can the diprefs code have a useful effect on an individual subtree of a file system if just that tree was deleted and recreated? Well, it depends on how much free space there is on the filesystem, and how fragmented it is. If the filesystem is 90% used, the dirprefs code doesn't have much room to use disk blocks for new directories in an efficient way. But it's probably better than nothing. It's very difficult to say in advance, so I'd suggest you just try it. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: dirpref gives massive performance boost
Robert Gray [EMAIL PROTECTED] wrote: A related question that I was wondering, Does my /kernel have the new dirpref code? If you've build kernel and userland from the same date (which is always recommended), then it is sufficient to look at the newfs(8) manpage. If it has the -g and -h options, then you've got dirprefs in the kernel. They were introduced at the same time as the kernel dirprefs code. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Where did /etc/issue go from telnetd? (fwd)
Alexander Goller [EMAIL PROTECTED] wrote: On Fri, Aug 31, 2001 at 08:03:51PM +0200, Oliver Fromme wrote: But the strange thing is, it still doesn't work. I have no idea why. Ack, but: the telnetd you have installed (probably) is crypto/telnet/telnetd which doesn't behave the same than standard telnetd (i.e. reading im and if). Guess that's why. Nope, I've checked the sources of both the standard telnetd and the crypto telnetd. The former reads the if and the im entries, the latter only the im entry -- but neither works. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
pkg_add doesn't work in jail
Hi, On a 4-stable box, I can't seem to use pkg_add within a jail. # pwd /tmp # ls *.tgz zsh-3.0.8.tar.gz # pkg_add *.tgz can't stat package file '/usr/jail/000/tmp/zsh-3.0.8.tar.gz' I think I've tracked it down to the __getcwd() syscall, which seems to return the absolute path without caring about the jail root. This is bad. In fact, it could be regarded as a security problem, because nothing in userland should be able to actually see the jail root. As a workaround, ``sysctl debug.disablecwd'' seems to work. It disables the syscall, then the getcwd() function in libc traverses the directories back to / itself to build the path. pkg_add works fine now. Can someone confirm my above analysis? Should I submit a PR? Unfortunately, I don't have a real fix. I didn't have a closer look at the __getcwd() code, but it seems pretty non-trivial to fix. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: IPFirewall again
Martin Schweizer [EMAIL PROTECTED] wrote: If I use the following rules and I can connect via ftp (for example ftp.freebsd.org) but after the successful login I can't do ls. As a side note, if you only need a directory listing, you can also type rs . (don't forget the dot). If you use an FTP client that doesn't know the rs command, you can use quote stat . instead. FreeBSD's client knows rs, so you can use that. The advantage of rs over ls is that it works through fire- walls, no matter what, because the directory listing data is transferred through the control connection (it doesn't require a data connction like ls). Unfortunately, some FTP servers don't support it correctly. Most servers whose authors have read and understood RFC959 usually get it right, though, which includes FreeBSD's ftpd and wuftpd. ;-) Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ftpd weirdness; CWD/RETR/... handles {} specially?
Eugene M. Kim [EMAIL PROTECTED] wrote: It depends on the case; in my situation, I'm mirroring quite a large collection of files whose names are just wild, i.e. all sorts of special characters embedded, some of them being shell metacharacters. Note that shell globbing is only performed on LIST. I just tried -- CWD and RETR don't expand them. If mirror has a problem mirroring such files with meta- characters, then mirror has a bug. It works fine using omi (ports/ftp/omi). Regards Oliver PS: Please DO NOT continue to ignore my Reply-To headers. Send to the list, not to myself. Thanks. -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ftpd weirdness; CWD/RETR/... handles {} specially?
Eugene M. Kim [EMAIL PROTECTED] wrote: On Sun, Jul 08, 2001 at 05:33:23PM +0200, Oliver Fromme wrote: Note that shell globbing is only performed on LIST. I just tried -- CWD and RETR don't expand them. [...] ftp cd /roo? --- CWD /roo? 250 CWD command successful. ftp pwd --- PWD 257 /root is current directory. I get this: ftp cd /roo? --- CWD /roo? 550 /roo?: No such file or directory. (There is, of course, a directory /root.) This is the ftpd(8) from 4.3-Release. If the behaviour changed in 4-stable after 4.3-Release, then that's a serious incopatibility indeed. It should be backouted immediately. In particular, globbing upon RETR is _definitely_ not the job of the server. That's what the clients' mget command is for (which sends an NLST, then performs globbing on the client side, and then uses RETR to get the actual files). Globbing upon CWD could be subject to discussion, but at least it should be an option that defaults to off. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: tail
Dan Langille [EMAIL PROTECTED] wrote: On Mon, 30 Apr 2001, Chris Byrnes wrote: We have rm -rf to protect us from doing things to directories (IE: rm /poop). This avoids catastraphic file removals. We need tail -argument to protect us from doing things to directories. This avoids nothing. I agree 100%. Furthermore, we would have to add such an -option to hundreds of tools, literally. That's not feasible. BTW, I often find myself needing to edit a directory (this is sometimes more handy than a bunch of mv commands). This doesn't work with vi, of course (you can read a directory, but you can't write it), so I wrote a small shell script that loads the directory (that is, the filenames) into your $EDITOR and writes them back afterwards (i.e. renames the files). http://www.secnetix.de/~olli/scripts/vils Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: The RELENG_4 (aka -stable) branch is now unfrozen
Bruce A. Mah [EMAIL PROTECTED] wrote: If memory serves me right, Jordan Hubbard wrote: [...] PS. At one point you talked about jotting some of the "roll the release" steps down in case you fall into a hole or get abducted by aliens or something like that In that case I think I could take over the job. ;-) I'm doing the release for the Lehmanns Edition of FreeBSD right now ... Regards Oliver PS: We have 5 (five) CD-ROMs in our set now. :-P -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 Mnchen Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ISA cards with the same ports and adresses problem
Nuno Teixeira [EMAIL PROTECTED] wrote: Reacently I installed two ISA cards: a sound card and a network card. [...] ed2: Realtek Plug Play Ethernet Card at port 0x220-0x23f irq 5 on isa0 sbc0: Creative ViBRA16C at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 Have you set ``PnP-aware OS = no'' in your BIOS setup? Then the BIOS should assign non-conflicting ports and IRQs to the PnP-capable cards (both of those cards are PnP-capable). Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 Mnchen Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: make release broken with too many ports/distfiles...
Tim Zingelman [EMAIL PROTECTED] wrote: So the quick answer is figure out what subset of distfiles I need, put them someplace other than /usr/ports/distfiles set DOCDISTFILES. You could, of course, set up a simple FTP server on localhost, and let ``make release'' fetch the distfiles that it needs itself. That's what I do, kind of. ;-) So I never have to think about what distfiles it needs. (Requires a small hack to the release Makefile so that there's an appropriate setting for the MASTER_SITE in the chroot's make.conf.) Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 Mnchen Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Releases
jonathan michaels [EMAIL PROTECTED] wrote: On Wed, Apr 11, 2001 at 03:45:41PM +0200, Oliver Fromme wrote: Maybe it would reduce confusion somewhat if people would just stop saying ``4.1-stable'' etc. Those simply do not exist. I would also vote for ``uname -r'' saying ``4-STABLE'' and appending the date (similar to the snapshot naming), like ``4-STABLE-20010509''. This is much more useful than ``4.3-STABLE'', IMO. actually, given teh granularity of teh cvs system it might be worthwhile to add hh:mm .. That would be rather difficult. As far as I know, there is no automatic mechanism to store the current date and time somewhere upon a cvs checkout or update. Anyway, just the day should be sufficient in most cases. Think of someone posting a well-known problem to -questions or -stable, and giving his uname output which says, for example, ``4-STABLE-20010509''. Now we can tell him to upgrade because it was fixed on 2001-05-20 or whatever. If he just said ``4.3-STABLE'', it wouldn't help much. Storing the date (without time of day) in that string would require some cron script somewhere (probably on the master CVS server) that updates the newvers.sh file daily. This might sound like a gross hack, but so far I haven't seen a better idea. on second thoughts your sugestion is teh sanest i've seen and personally wonder why it wasn't done like this fron teh begining. Probably because of the gross hack that I described above. :-) But maybe someone else has a better idea how to achieve that. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 Mnchen Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3 Release candidate #2 now ready
Jordan Hubbard [EMAIL PROTECTED] wrote: Due to the recent security fixes which went into the tree, along with the fact that I'll be following a very large moving truck on Monday and will be somewhat busy, I'm releasing the second release candidate image today instead of monday. I've also made two ISO images of 4.3-RC2 available at ftp7.de.freebsd.org: -rw-rw-r-- 1 inof bsd 430229504 Apr 02 15:45 4.3-RC2-combi.iso -rw-rw-r-- 1 inof bsd 49283072 Apr 02 15:54 4.3-RC2-mini.iso The "mini" ISO (47 Mbytes) contains ONLY the "bin" dist, so you can do a minimal install with this one, no more. You'll have to get everything else from the network once you've brought a machine up and running with this ISO. The "combi" ISO (410 Mbytes) contains the complete base system, the ports collection framework (but no distfiles nor packages), XFree86, _and_ this CD also contains a Live Filesystem, so you can use it as a "fixit" CD, too! I haven't tested either of these (due to lack of CD-Rs right now), but I'm pretty confident that the ISOs work fine. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 Mnchen Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FreeBSD 2.2.7 available this weekend
Otter [EMAIL PROTECTED] wrote: Thanks for the tip! I need to bookmark those. Still, you'd be surprised how many people got it from here this weekend. I suppose there's still a demand for it (older machines, maybe?). Probably. I'm forced to run 2.2.x on my old notebook, too, since it can't run any 3.x or 4.x. Regards Oliver PS: Please regard my Reply-To's and don't Cc me. This is annoying. -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 Mnchen Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Revised schedule for 4.3-RELEASE
Brandon D. Valentine wrote: On Fri, 23 Mar 2001, Oliver Fromme wrote: Jordan Hubbard [EMAIL PROTECTED] wrote: Which mirrors will carry the -RC ISO images? I've been trying to I'll _try_ to put 'em up at ftp7.de.freebsd.org, if I can. No promises, though, 'cause I'm extremely busy. IIRC that's aliased to ftp.tu-clausthal.de, right? Right. In that case will you be providing barebones 4.3 ISOs when the release is out? Yes. I've always loved those, since I can pull them down overnight even on a 56k dialup. That's why I create them. :) What would be even better is if there was a barebones CD option that only contained the bindist and was even smaller. There is one: -rw-rw-r-- 1 inof bsd 201242624 Dec 05 17:57 4.2-install.iso -rw-rw-r-- 1 inof bsd 191283200 Dec 05 19:58 4.2-livefs.iso -rw-rw-r-- 1 inof bsd 88379392 Dec 05 18:16 4.2-minimum.iso Well, OK, the "minimum" one contains a bit more than just "bin". It also contains the catpages, compat*, crypto, ports and the kernel sources, but no more. I thought that these are valuable enough to be included. These are the sizes (in Kbytes): 5469catpages 557 compat1x 349 compat20 470 compat21 1211compat22 1058compat3x 10143 crypto 10787 ports 10428 src (kernel sources only) OK, so leaving those off would save about 40 Mbyte of those 88 Mbytes of the minimum ISO. Hm. Sounds like a good deal. I'll think about it. Regards Oliver PS: Please don't ignore my Reply-To's. They're there for a reason. I _do_ read the list, so there's not even need to Cc me. -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 Mnchen Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Applying -STABLE source
E. Jordan Bojar [EMAIL PROTECTED] wrote: Is there a way for me to download the most recent -STABLE source and apply it to or replace the 4.2-RELEASE source without using CTM or CVSup? You could download the src-dist of the latest -stable snap- shot from one of the FTP servers. For example, try to ftp to releng4.freebsd.org and go to /pub/FreeBSD/snapshots/i386/4.2-20010323-STABLE and down- load the complete "src" directory (use wget or a dedicated FTP mirror tool such as "omi"). There's an install script included (don't just blindly run it -- read it first!). Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 Mnchen Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: making a RELEASE
In list.freebsd-stable Plamen Petkov [EMAIL PROTECTED] wrote: 3. hacking /usr/src/release/Makefile, where, instead of 'cvs'-ing srcs, I just 'cp' them in $CHROOTDIR/src Using tar (or star from the ports) is probably better than cp. Well, this is a bit away from the 'standard' release/snap making procedure, but as i said in my prev messages - I do this for me only, to have MY snapshot on a bootable CD, just in case. The price is reasonable - a night of my life :-) And what is the advantage over simply making a backup of your disk? Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) Addresses will change soon!! If in doubt: www.fromme.com "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Irda support
In list.freebsd-stable Daniel O'Connor [EMAIL PROTECTED] wrote: Or give them a real business card.. Still, hotsync'ing via IR is neat :) If I'm not mistaken, the IR feature of the Palm (at least the Palm III) isn't even Irda, but some proprietary stuff. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) Addresses will change soon!! If in doubt: www.fromme.com "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: making a RELEASE
In list.freebsd-stable Nora Etukudo [EMAIL PROTECTED] wrote: On Thu, Aug 03, 2000 at 02:21:24PM +0200, Oliver Fromme wrote: have MY snapshot on a bootable CD, just in case. The price is reasonable - a night of my life :-) And what is the advantage over simply making a backup of your disk? If I have such a CD, I can it auto install on several machines, without further investigation. This is much less time consuming than a cloneing from a backup. Yes, I know that. But Plamen Petkov wrote that he just needed a crash recovery for a single box. In that case, making a full release and putting it on CD-R is a complete waste of time, IMO. You have to make regular backups anyway, except if you don't care about your data at all (and then you can just re-install from your latest release CD-ROM and start over from there). Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) Addresses will change soon!! If in doubt: www.fromme.com "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SSH in 4.1 RELEASE for NonUS users
In list.freebsd-stable Mark Ibell [EMAIL PROTECTED] wrote: The only real option (at least for international users) seems to be to do a 'make world' with USA_RESIDENT=NO. Or install from one of the international servers that build the releases themselves with USA_RESIDENT=NO, including: current.jp.freebsd.org ftp7.de.freebsd.org On ftp7.de there's also a "barebone" ISO image of 4.1-R that has been built the same way. It contains just the base system, sources and XFree86, but no optional packages, so it is much smaller than the ISO on ftp.freebsd.org. There's also a Live Filesystem / "Fixit" CD ISO image. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) Addresses will change soon!! If in doubt: www.fromme.com "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FreeBSD Console
In list.freebsd-stable Sean Kelly [EMAIL PROTECTED] wrote: I am using FreeBSD as a desktop workstation at work. It is very nice and productive, but I have one problem. We have many HP/UX machines, and I am constantly connecting to them. I can't find a terminal type on HP/UX that matches the FreeBSD console exactly. 'ansi' appears to be close, but I still have some horrid drawing errors. Same with remote work on SunOS 5.7. I have simply copied the cons25l1 termcap entry (for latin1 a.k.a. ISO 8859-1) from FreeBSD to Solaris, converted it to terminfo with "captoinfo" and added it to the terminfo database. Works as expected. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) Addresses will change soon!! If in doubt: www.fromme.com "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How to force remote reboot of 3.4-Release?
Michael Robinson [EMAIL PROTECTED] wrote in list.freebsd-stable: Last night, I was running a very large Postgresql query on one of my colocated development servers when all of a sudden the session completely froze. Since then, I can get TCP connections to all the open ports, but they just hang with no services ever coming up. Ping works fine. I have once written a small kernel hack which I called "ICMP REBOOT". When you send a certain ICMP packet from a certain host or network, the machine logs the host and panics. The packet can be sent with a modified ping command. It is very useful, because the reception of ICMP packets is performed by the kernel on the lowest level in the interrupt handler, which means that there's a good chance that it will still work, even if the system is pretty much dead. This hack saved my life a few times. ;) I considered submitting the patch, but I guess it wouldn't be committed because it's a "dirty hack". Someone else who has access to your network could easily reboot your box using IP- spoofing, because it's authenticated by IP addresses only. It's probably a good idea to use it behind a firewall that drops unknown ICMP packets. If someone is interested, I've put the hack online here: http://www.fromme.com/icmpreboot.tar.gz Please read the README file. Use at your own risk. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: enabling bridge-support in rc.conf?
Szilveszter Adam wrote in list.freebsd-stable: Just to get it clear: I did not suggest it to be enabled without user intervention. All I had in mind was to move this particular parameter to rc.conf (or similar) instead of the sysctl. Well, that's debatable. (Personally, as I said earlier in this thread, I don't think that each and every sysctl knob should have an equivalent rc.conf setting. Only the most common ones. I think rc.conf is already bloated and cluttered with stuff, some of which is not needed by 99% of the users and just might cause confusion, and the remaining 1% certainly would know how to throw the switches without rc.conf.) The problem with sysctls is only one: They tend to be badly documented. The bridge(4) manpage documents the sysctl in question _very_ well. Please read it if you don't believe me. I agree that _some_ sysctls are not well-documented (but as I said before: docs don't exist until someone writes them). But the specific sysctl in question (see the subject line) is very well documented. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: AMD 3DNow instructions on FreeBSD
Sean-Paul Rees wrote in list.freebsd-stable: Is there a MMX enabled setiathome for us with non-3DNow! enhanced processors? No, MMX is completely useless for this kind of stuff, because MMX does not support floating point operations. Sorry. However, I modified the FFT algorithm to optimize memory throughput, at the cost of memory footprint (it needs about 2 Mbyte more RAM). The speed increase is not as impressive as with the 3DNow version, but it's still significant. Here are some numbers: Dual Celeron-466, Gigabyte 6BXD mainboard: original code: 18.0 - 18.5 hours per CPU generic optimized code: 10.5 - 11.0 hours per CPU speed increase: ~ 40% Single Celeron-333, Asus P2B mainboard: original code: 14.0 - 14.5 hours generic optimized code: 10.5 - 11.0 hours speed increase: ~ 25% Single Pentium-II-450, Asus P2B-LS mainboard: original code: 9.0 - 9.5 hours generic optimized code: 7.5 - 8.0 hours speed increase: ~ 16% As you can see, the Dual Celeron benefits the most, because it has a very weak RAM bandwidth, but fast (though small) L2 cache. AMD K7-500, MSI MS6167 mainboard: original code: 10.0 - 10.5 hours Athlon optimized code: 4.0 - 4.5 hours speed increase: ~ 60% These numbers speak for themselves. 3DNow rules. :) I'm still waiting for a response from the Seti@home folks. They have all the code, but they seem to ignore it. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: AMD 3DNow instructions on FreeBSD
Randall Hopper wrote in list.freebsd-stable: Hi. Is there a FreeBSD assembler out there which supports the AMD 3DNow instruction set? NASM (in the ports) supports the older ones, but not the newer ones supported by the Athlon/K7. I sent patches to the author to support those, too, but nothing happened. Why I ask: I attempted to build GLX/Mesa3.1 with 3DNow support, and it bombed since our assembler isn't 3DNow-knowledgable (femms, pfmul, etc. undefined). The assembler in -stable has the same shortcoming AFAICT. Facts? Rumors? I'm interested in anything you may know. Well, when I added 3DNow support to the Seti@home client, I assembled the 3DNow instructions "manually", i.e. I created small gas macros for that purpose. It's ugly, but it works. The 3DNow specification (with instruction codes) is available from www.amd.com. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
