Re: ATA 4K sector issues
On Wednesday 17 March 2010 03:37:12 am Andriy Gapon wrote: > on 17/03/2010 12:16 Mohacsi Janos said the following: > > Dear FreeBSD hackers, > > What is the situation with ATA 4K dirves in FreeBSD? Are there > > any support for them in fdisk or disklabel? > > More information at: > > http://ata.wiki.kernel.org/index.php/ATA_4_KiB_sector_issues > > Did you mean to say gpart(1)? :) > AFAIK, the tool(s) do not auto-align on 4K boundaries, but they give > user an ability to do that by hand. > Besides, some 4K sector disks lie that they have 512 sectors. An article on the effect is located at http://storageeffect.media.seagate.com/2010/03/storage-effect/y2-011k-looming-for-windows-xp-users/ Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: C coding editor
On Sunday 23 February 2003 10:17 am, Wes Peters wrote: > On Friday 21 February 2003 04:21 am, Clemens Hermann wrote: > > Hi, > > > > what are your favourite editors for coding C? While vi on the first > > terminal, cc on second and runs on the third is fine for very small > > things I doubt it is the way people do it here. > > Terminal? You have heard of this really cool thing called windowing > software? ;^) > > I completely utterly fail to understand why some young developers > attach some sort of romance to writing code on an 80x25 screen, when > all the haxxors my age or older waited (or slaved away) for years, > even decades, to get something better and more flexible. > I love comments like this. We used Microsoft's developer environment to update Unix (HPs and a Cray) for years because that was all we had other than vi. You could click something in Microsoft, right click it and you would see sample code, the headers you needed, and etc. The programs were under strict code control that was acceptable to the USA NRC. I see the same thing more or less using the 'Crusader', 'Code Warrior', or kdevelop environment. In a co-conversion effort using DEC Fortran and f77 on FreeBSD, msdbg would roll over and die but kdbg would show you the signal error. Unfortunately, it wouldn't show you why the line was dying. Writing a one line message of parameters produced a 70 MB file with no clue why it was dying. Msdbg would actually debug the line and show you which pointer went out of range but it would die if you just let it run and not tell you where. Combining the effort produced a solution neither was capable of by themselves in a reasonable amount of time. It all goes under my heading of "what part of making your life easier don't you understand". Have a good day, Kent > I've seen vim, emacs/xemacs, and kdevelop all mentioned in this > thread. I'd just like to point out that the first three have great > advantages under X and the last runs exclusively on X (at least on > UNIX it does). X is for programmers, too. Try it, you'll like it. > You might even find a use for that mouse. -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SiS 900 Ethernet card
Jack L. Stone wrote:
At 02:04 AM 11.26.2002 +0100, Wolfgang Zenker wrote:
Hello,
The problem is that my bios have very few features and I can't disable
the Network Card.
I'm not sure what is the mainboard, it is sis but I don't know which
model. Maybe this dmesg output from OpenBSD may help someone:
cpu0: Intel Pentium 4 ("GenuineIntel" 686-class) 2.20 GHz
[..]
sis0 at pci0 dev 3 function 0 "SIS 900 10/100BaseTX" rev 0x90: irq 10
that's apparently a nic integrated in the SiS 635 chipset.
Wolfgang
At the very least, it should have a jumper on the MB to disable such a
feature you should go to the MB website if you don't have a manual with
the MB layout and jumpers. They should have the info there -- certainly
Tech support would be available I can't imagine an onboard NIC that
would not have an option to disable just as with audio or video
There should be an option in the bios called "Features Setup". In it
you have a choice of "Onboard LAN" enabled or disabled.
There are virtually no jumpers on SIS based motherboards.
Kent
--
Kent Stewart
Richland, WA
http://users.owt.com/kstewart/index.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: SiS 900 Ethernet card
Alexander wrote: The next thing that comes is the Ethernet Card. It is on board and from the dmesg output You see what happens. The card is working properly on Windows XP, RedHat Linux (OpenBSD have the same problems except for the kernel failure). I've tried removing the driver from the kernel so that at least I can boot and install FreeBSD and then probably go on PCMCIA but the kernel failed again saying that the device is unknown (huh !). Please, if someone knows a fix or thinks that can help, write me. I'm ready to test patches and provide more information. A temporary solution as far as the kernel is concerned is to disable the on-board SiS-900 in the bios. Get your boot problem stable. Then, you can fix the kernel and try things. I had problems with the SiS-900 on my SiS-735 based motherboard. I had a number of Intel 100's or 3Coms and adding one of them worked just fine. You need to be able to cvsup and in my case I am dependant on the NIC that is connected to my ADSL modem. FWIW, an FTP between 2 machines with SiS-900's gives me my fastest transfer rates. The 3Com is the slowest. The 3Com's are older because I liked the idea of the onboard memory being 2x larger in the Intels. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: It's dead Jim
Scott Ullrich wrote: > Yes, but what about Apple? Surely OSX sales are increasing BSD > installation counts? Netcraft hasn't detected sites I use since they upgraded to 4.5. They all show up as "unknown". > > -SU > > -Original Message- > From: Alfred Pythonstein [mailto:[EMAIL PROTECTED]] > Sent: Sunday, August 18, 2002 10:24 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: It's dead Jim > > > Mad propz to Hiten 'imbecile' Pandya, btw... > > It is official -- Netcraft is now confirming: *BSD is dying > > One more crippling bombshell crushed the already beleaguered *BSD community > when IDC confirmed that *BSD market share has dropped yet again, now > down to > less than a fraction of 1 percent of all servers. Coming on the heels of a > recent Netcraft survey which plainly states that *BSD has lost more market > share, this news serves to reinforce what we've known all along. *BSD is > collapsing in complete disarray, as fittingly exemplified by failing dead > last [samag.com] in the recent Sys Admin comprehensive networking test. > > You don't need to be a Kreskin [amdest.com] to predict *BSD's future. The > hand writing is on the wall: *BSD faces a bleak future. In fact there won't > be any future at all for *BSD because *BSD is dying. Things are looking > very > bad for *BSD. As many of us are already aware, *BSD continues to lose > market > share. Red ink flows like a river of blood. > > FreeBSD is the most endangered of them all, having lost 93% of its core > developers. The sudden and unpleasant departures of long time FreeBSD > developers Jordan Hubbard and Mike Smith only serve to underscore the point > more clearly. There can no longer be any doubt: FreeBSD is dying. > > Let's keep to the facts and look at the numbers. > > OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many > users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD > posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about > 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the > volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A > recent article put FreeBSD at about 80 percent of the *BSD market. > Therefore > there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with > the number of FreeBSD Usenet posts. > > Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went > out of business and was taken over by BSDI who sell another troubled OS. > Now > BSDI is also dead, its corpse turned over to yet another charnel house. > > All major surveys show that *BSD has steadily declined in market share. > *BSD > is very sick and its long term survival prospects are very dim. If *BSD is > to survive at all it will be among OS dilettante dabblers. *BSD > continues to > decay. Nothing short of a miracle could save it at this point in time. For > all practical purposes, *BSD is dead. > > Fact: *BSD is dying > > > > _________ > Chat with friends online, try MSN Messenger: http://messenger.msn.com > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: offtopic: low level format of IDE drive.
Robert Klein wrote: > On Montag, 8. Juli 2002 23:46, Kent Stewart wrote: > >>Julian Elischer wrote: >> >>>The machiine has 1 CD drive and no floppy.. >>> > ^^ > > >>All of the manufacturers have a program that will do that. Many of >>them even produce a bootable floppy. Check their support web page. >> > > which leaves the "no floppy" problem.. Perhaps you could use the > bootable floppy from the manufacturer as the "el torito boot > image" for a CD-R you create on another machine.. So mount it temporarily on another machine. You don't even need them in the assigned bios tables. When I first started using FreeBSD, I tried the dangerous option and the system would not get past checking the initial hardware. I had to change the HD assignment to none and ll format the disk. Kent > > Robert > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > > . > > -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: offtopic: low level format of IDE drive.
Julian Elischer wrote: > One of my FreeBSD development boxes had a hernia last week when it lost > power while writing to disk. The drive wrote out garbage to a track. > > I want to reformat the drive, (low level) but the bios doesn't have any > support to do this (In the past That is how I did this). > The machiine has 1 CD drive and no floppy.. > > anyone with any ideas as to how one can reformat a hard drive feel free to > lend me a clue.. > All of the manufacturers have a program that will do that. Many of them even produce a bootable floppy. Check their support web page. Kent > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > > . > > -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE
Dmitry A. Bondareff wrote: > Hi! > I have another machine in Internet with 4.1-RELEASE. > An I want upgrade to 4.5-RELEASE. > Will upgrade work ? I have a friend trying that on 2 or 3 machines right now. His make buildkernel is dying because of the ipfilter move from modules/ to contrib/ change. Kent > > - Original Message - > From: "Ruslan Ermilov" <[EMAIL PROTECTED]> > To: "Dmitry A. Bondareff" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Thursday, February 07, 2002 1:38 PM > Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > > > >>On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: >> >>>Hi! >>> >>>I have FreeBSD 4.0: >>># uname -a >>>FreeBSD xxx 4.0-RELEASE FreeBSD 4.0-RELEASE #5: Wed Apr 11 16:06:03 GMT >>> > 2001 > >>> root@xxx:/usr/src/sys/compile/xxx i386 >>> >>>Yesterday I've tried to update it teel 4.5-RELEASE. >>> >>> >>We don't (yet) support upgrades from 4.0. I plan on making it work >>in time for 4.6-RELEASE. >> >> >>Cheers, >>-- >>Ruslan Ermilov Sysadmin and DBA, >>[EMAIL PROTECTED] Sunbay Software AG, >>[EMAIL PROTECTED] FreeBSD committer, >>+380.652.512.251 Simferopol, Ukraine >> >>http://www.FreeBSD.org The Power To Serve >>http://www.oracle.com Enabling The Information Age >> >>To Unsubscribe: send mail to [EMAIL PROTECTED] >>with "unsubscribe freebsd-hackers" in the body of the message >> >> > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > > . > > -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://users.owt.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
Munish Chopra wrote: > On Fri, Dec 28, 2001 at 06:10:09PM +1030, Greg Lehey wrote: > >>I've been using AMD processors almost exclusively in my main work >>machines for over 4 years, and I've been very happy with them. I'm >>currently running a K6/233, a K6/333, an Athlon 750, a Duron 850 and >>an Athlon XP 1700. Last August, though, I bought a machine which gave >>me a lot of trouble, the Duron 850 mentioned above. I found that it >>would freeze for no apparent reason. I established that it wasn't the >>memory by taking the memory of another machine and running it like >>that; it made no difference. I ended up also changing the motherboard >>and the processor, but the hangs continued. I could expect a hang >>within 8 hours when doing 'make release' >> >> > > I'm running an AMD Thunderbird 1200 on an ECS-K7S5A (SiS 735 chipset), > with 256 MB DDR SDRAM installed. I experience random reboots with that > system, though I have had a few people on -questions tell me to make > sure my cards are properly seated as the ECS boards seem to be very > picky about that (I still don't believe that is the reason). I'm going > to check out the RAM later today, but I'm not really sure what is wrong > with that machine. > > My first two AMD machines, a K6-2 350 on as ASUS-P5A and a Duron 800 on > an ASUS-A7V will just freeze after booting and showing the login prompt > (this happens around once every ten boots or so). No problmes under > Windows. A friend of mine running the same motherboard with WinXP also > experiences random reboots though, so I'm hoping a BIOS update might > work some magic, though the fixes list doesn't hint at this. Most other > people I've talked to consider their ECS boards rock-solid. > > >>Just for the fun of it, I tried running Linux on it. I've been >> > > Didn't do that, wouldn't know if the problems also exist under Linux. > > Anyway, that was my experience. The ATA100 controller on the board is > only recognized as an ATA33 controller, but I'll be sending Soeren > whatever he needs shortly in hope of fixing that. He already has code to recognize the SiS-735 chipset and many more SiS versions in -current. They just haven't been MFC'ed. Look for 55131039 in ata-pci.c and ata-dma.c. Kent > > If anyone has even a hint as to what else could be causing these > reboots, I'd very much appreciate it (-questions didn't really come up > with much). > > And before I forget, the machine is running 4.4-STABLE. > > -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://users.owt.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: aps2file doesn't work on FreeBSD
Anthony Schneider wrote: > Linux: > > anthony:/home/anthony:9% uname -a > Linux lappy.slc.edu 2.2.17-21mdk #1 Thu Oct 5 13:16:08 CEST 2000 i686 unknown > anthony:/home/anthony:10% su > Password: > [root@lappy anthony]# echo $USER > root > [root@lappy anthony]# exit > anthony:/home/anthony:11% su -l > Password: > [root@lappy /root]# echo $USER > root > [root@lappy /root]# It may work on Linux that way but you are supposed to do a "su -" on FreeBSD. For example, opal:kent> su Password: opal# env USER=kent opal:kent> su - Password: USER=root The system knows the difference. Kent > > > FreeBSD: > > anthony:/home/anthony:20% uname -a > FreeBSD flack.slc.edu 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT >2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386 > anthony:/home/anthony:21% su > Password: > flack# echo $USER > anthony > flack# exit > anthony:/home/anthony:22% su -l > Password: > flack# echo $USER > root > flack# logout > anthony:/home/anthony:23% > > From 'info su' on my linux box: > >By default, `su' does not change the current directory. It sets the > environment variables `HOME' and `SHELL' from the password entry for > USER, and if USER is not the super-user, sets `USER' and `LOGNAME' to > USER. By default, the shell is not a login shell. > > su version (on my linux box): > > [root@lappy anthony]# su --version > su (GNU sh-utils) 2.0 > Written by David MacKenzie. > > Copyright (C) 1999 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > [root@lappy anthony]# > > Perhaps it's time to contact gnu? > > -Anthony. > > [ and apologies for the line wrapping ] > > On Mon, Dec 17, 2001 at 03:09:19AM -0500, Brandon D. Valentine wrote: > >>On Sun, 16 Dec 2001, Anthony Schneider wrote: >> >> >>>Well, the reason I brought up $USER inheritance is that on linux, $USER >>>is root after an su to root, whereas on FreeBSD, the $USER is the same >>>as before the su. >>> >>[Line wrap at 72, please] >> >>Excerpt from su(1): >>--- >>By default, the environment is unmodified with the exception of USER, >>HOME, and SHELL. HOME and SHELL are set to the target login's default >>values. USER is set to the target login, unless the target login has a >>user ID of 0, in which case it is unmodified. The invoked shell is the >>target login's. This is the traditional behavior of su. >> >>-l Simulate a full login. >>--- >> >>You are observing none other than the expected behavior. I have never >>seen Linux (GNU) su do things any differently in this regard. If they >>do, it's broken. >> >>Brandon D. Valentine >>-- >>"Iam mens praetrepidans avet vagari." >>- G. Valerius Catullus, Carmina, XLVI >> >> >>To Unsubscribe: send mail to [EMAIL PROTECTED] >>with "unsubscribe freebsd-hackers" in the body of the message >> > -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://users.owt.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ep0 driver oddity
Leo Bicknell wrote: > > I broke out a really old card to make a cheap solution work, and > now I'm confused. It's an old 3c509 ISA card, which has been set > to 0x300, irq 5. Those don't conflict, so no issue there. > > Building a kernel with "device ep0" found it, but didn't like it > because it wasn't at the default IRQ 10. So, I rebuilt a kernel > with > > device ep0 at isa? port 0x300 irq 5 > > Here's where my confusion came in, I get this in dmesg: > > ep0 at port 0x300 irq 5 on isa0 > ep0: Ethernet address 00:20:af:6a:d8:d6 > ep1: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 10 on isa0 > ep1: No irq?! > ep1: ep_alloc() failed! (6) > device_probe_and_attach: ep1 attach returned 6 > > ep0 seems to work ok, and there is no ep1. I'm not sure why it's > auto-looking for an additional card. If I leave the 0 off: It has been a while since I setup my 3C509 but what I remember is having to turn off PNP on the card. Kent > > device ep at isa? port 0x300 irq 5 > > config barfs, even though the default is "device ep". > > I get the feeling that if I set this via config I'd be ok, but I don't > have easy access to the console of this particular machine. > > I'm sure I'm missing something really simple, but how can I set > ep0 in the kernel config and not get an ep1 along with it? > Alternatives (eg, loader.conf or something) would be fine, I know > nothing about that. > > -- >Leo Bicknell - [EMAIL PROTECTED] - CCIE 3440 > PGP keys at http://www.ufp.org/~bicknell/ > Read TMBG List - [EMAIL PROTECTED], www.tmbg.org > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://users.owt.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: power supplies
Jim Bryant wrote: > > Kent Stewart wrote: > > > There are problems with PSes when you use NICs with wake up > > capability. The NIC may exceed the capability of one of your low > > amperage voltages. > > > > Kent > > How much current can wake-on-LAN take? I wouldn't think it would be enough to >overload a power supply unless it overloaded the -12V > line which is usually only rated in the mils. What is the average 12V rating? 5-8 >amps? and even more for 5V? I forget what the > average -5V line is rated. I don't remember which one it is. The -12v sounds likely. It was the one in the milliamp range. The NICs came with a warning that the typical AT power supplies were insufficient. I haven't bought one in a box for quite a while and that was where I saw the warning. Kent > > jim > -- > ET has one helluva sense of humor! > He's always anal-probing right-wing schizos! > - > POWER TO THE PEOPLE! > - > "Religious fundamentalism is the biggest threat to > international security that exists today." > United Nations Secretary General B.B.Ghali > > _ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] Carl Sagan quote on Seti@home http://setiathome.ssl.berkeley.edu/pale_blue_dot.html It is hard to believe you are soaring with Eagles (las águilas) when you accept SPAM like a mouse (el ratón). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: power supplies
Dan wrote: > > I had the stangest situation today where a new nic card was put into a > machine and then the machine did not start up. Placed the old nic card > back in the box and it still did not start up. Switched power supplies > with an exactly equal box and both machine booted up fine. This has > happened twice since we started replacing nic cards today with ones with > more buffer space available on them out of about 8 machines now. > > Does this make any sense to anyone? There are problems with PSes when you use NICs with wake up capability. The NIC may exceed the capability of one of your low amperage voltages. Kent > > -- > Dan > > +--+ > | BRAVENET WEB SERVICES | > | [EMAIL PROTECTED] | > | screen;cd /usr/src;make buildworld;cd ~ | > | cp MYKERNEL /sys/i386/conf;cd /usr/src | > |make buildkernel KERNCONF=MYKERNEL| > |make installkernel KERNCONF=MYKERNEL;make installworld| > +__+ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does boot1 still have a > 1023 cyl limit?
John Baldwin wrote: > > On 15-Sep-01 David O'Brien wrote: > > On Fri, Sep 14, 2001 at 03:05:01PM -0700, John Baldwin wrote: > >> 'disklabel -B ad0' as root, where 'ad0' is the disk that boots FreeBSD > > > > Isn't `disklable -B ad0sX' more proper? (especially if the disk has > > multiple FreeBSD slices) > > On x86, yes. I think disklabel -B ad0 will still work though. (It finds the > first FreeBSD slice and does it I think). I tried some more things today since I had a running system. The "disklabel -B ad0s3" works on my system. I can't use the ntldr until I replace the boot record used to boot FreeBSD. Once I copied boot1 to bootsect.bsd, which is what I have in boot.ini, W2K would boot FreeBSD. Having to replace what ntldr was using didn't occur to me until I made the W2K partition the active one and it wouldn't boot FreeBSD. Once I had a matched set, everything was ok. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does boot1 still have a > 1023 cyl limit?
David O'Brien wrote: > > On Fri, Sep 14, 2001 at 03:05:01PM -0700, John Baldwin wrote: > > 'disklabel -B ad0' as root, where 'ad0' is the disk that boots FreeBSD > > Isn't `disklable -B ad0sX' more proper? (especially if the disk has > multiple FreeBSD slices) I tried ad0s3 and the system was just reinstalled using a binary install. It wouldn't boot past the "-" symbol. Kent > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does boot1 still have a > 1023 cyl limit?
John Baldwin wrote: > > On 14-Sep-01 Kent Stewart wrote: > > > > > > John Baldwin wrote: > >> > >> On 14-Sep-01 Kent Stewart wrote: > >> > > >> > > >> > [EMAIL PROTECTED] wrote: > >> >> > >> >> Kent Stewart wrote: > >> >> > >> >> > Mike Smith wrote: > >> >> > > > >> >> > > > So.. if I read you right, booting correctly for > 1024 cylinders > >> >> > > > works > >> >> > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in > >> >> > > > the > >> >> > > > fbsd > >> >> > > > slice? Does this mean that boot1 and boot2 should work just fine > >> >> > > > if > >> >> > > > they > >> >> > > > are loaded by another kind of MBR loader (say, Grub), and they find > >> >> > > > out > >> >> > > > that they are placed beyond the 1023th cylinder? > >> >> > > > >> >> > > This should work, yes. > >> >> > > >> >> > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I > >> >> > had to go back to the boot1 from 4.3 before I could boot. > >> >> > >> >> That could be serious. Can you post a brief description of your > >> >> hardware, together with the BTX register dump if possible? boot1 was > >> >> changed to address some problems with certain hardware, so it is > >> >> important to know if other incompatibilities have been introduced. > >> > > >> > The hardware is Abit VP6 mb w/dual 866 coppermines & 256 MB of PC-133 > >> > memory. Disk0 is a Maxtor 30 GB, disk1&2 are on the HPT-370 controller > >> > and are also Maxtor 30 GB drives. The 2 HD's on the HPT-370 are > >> > identical models. All are rated at ATA-100. The loader has been Win XP > >> > Pro since beta2 and runs FreeBSD about half of the time. > >> > > >> > BTX - Register dump > >> > > >> > int=0006 err= efl=00030216 eip=0de7 > >> > eax=1d3a ebx=30ff ecx=001f edx=00ce > >> > esi=0001 edi=0009 ebp=03fe esp=03b1 > >> > cs=2364 ds= es=0204 fs= gs= ss=9dc5 > >> > cs:eip=0f 00 00 00 70 00 00 00-00 00 00 68 1e 00 00 00 > >> > ss:esp=b9 0d 00 00 00 fe 03 c2-03 02 01 80 00 1f 00 01 > >> > BTX halted > >> > >> 0Fsldt [bx+si] > >> 0003 007000add [bx+si+0x0],dh > >> 0006 add [bx+si],al > >> 0008 add [bx+si],al > >> 000A 00681Eadd [bx+si+0x1e],ch > >> 000D add [bx+si],al > >> > >> That doesn't look to be very sane. > >> > >> Are you sure you haven't mixed an old version of boot2 with a new boot1 or > >> vice > >> versa? > > > > Yes, > > > > coral# mount_msdos /dev/ad0s1 /mnt > > coral# cmp /mnt/boot1 /boot/boot1 > > coral# > > > > They test identical. Boot1 was copied to bootsect.bsd, which is > > referenced in boot.ini. > > Umm, ok. Did you do 'disklabel -B' to update the boot blocks on the disk (the > boot blocks do _not_ live in the /boot files, they are part of the disklabel) > when you updated the boot1 in bootsect.bsd? That I didn't do. What do I need to do? I'm reading the man page and this is foreign country. This system was created at 4.2 and they were created for me at that point. I don't want to have to reset the ntldr butI could find the floppies to do a console recovery if I have to. Kent > > -- > > John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does boot1 still have a > 1023 cyl limit?
John Baldwin wrote: > > On 14-Sep-01 Kent Stewart wrote: > > > > > > [EMAIL PROTECTED] wrote: > >> > >> Kent Stewart wrote: > >> > >> > Mike Smith wrote: > >> > > > >> > > > So.. if I read you right, booting correctly for > 1024 cylinders works > >> > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the > >> > > > fbsd > >> > > > slice? Does this mean that boot1 and boot2 should work just fine if > >> > > > they > >> > > > are loaded by another kind of MBR loader (say, Grub), and they find > >> > > > out > >> > > > that they are placed beyond the 1023th cylinder? > >> > > > >> > > This should work, yes. > >> > > >> > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I > >> > had to go back to the boot1 from 4.3 before I could boot. > >> > >> That could be serious. Can you post a brief description of your > >> hardware, together with the BTX register dump if possible? boot1 was > >> changed to address some problems with certain hardware, so it is > >> important to know if other incompatibilities have been introduced. > > > > The hardware is Abit VP6 mb w/dual 866 coppermines & 256 MB of PC-133 > > memory. Disk0 is a Maxtor 30 GB, disk1&2 are on the HPT-370 controller > > and are also Maxtor 30 GB drives. The 2 HD's on the HPT-370 are > > identical models. All are rated at ATA-100. The loader has been Win XP > > Pro since beta2 and runs FreeBSD about half of the time. > > > > BTX - Register dump > > > > int=0006 err= efl=00030216 eip=0de7 > > eax=1d3a ebx=30ff ecx=001f edx=00ce > > esi=0001 edi=0009 ebp=03fe esp=03b1 > > cs=2364 ds= es=0204 fs= gs= ss=9dc5 > > cs:eip=0f 00 00 00 70 00 00 00-00 00 00 68 1e 00 00 00 > > ss:esp=b9 0d 00 00 00 fe 03 c2-03 02 01 80 00 1f 00 01 > > BTX halted > > 0Fsldt [bx+si] > 0003 007000add [bx+si+0x0],dh > 0006 add [bx+si],al > 0008 add [bx+si],al > 000A 00681Eadd [bx+si+0x1e],ch > 000D add [bx+si],al > > That doesn't look to be very sane. > > Are you sure you haven't mixed an old version of boot2 with a new boot1 or vice > versa? Yes, coral# mount_msdos /dev/ad0s1 /mnt coral# cmp /mnt/boot1 /boot/boot1 coral# They test identical. Boot1 was copied to bootsect.bsd, which is referenced in boot.ini. Kent > > -- > > John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does boot1 still have a > 1023 cyl limit?
[EMAIL PROTECTED] wrote: > > Kent Stewart wrote: > > > Mike Smith wrote: > > > > > > > So.. if I read you right, booting correctly for > 1024 cylinders works > > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd > > > > slice? Does this mean that boot1 and boot2 should work just fine if they > > > > are loaded by another kind of MBR loader (say, Grub), and they find out > > > > that they are placed beyond the 1023th cylinder? > > > > > > This should work, yes. > > > > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I > > had to go back to the boot1 from 4.3 before I could boot. > > That could be serious. Can you post a brief description of your > hardware, together with the BTX register dump if possible? boot1 was > changed to address some problems with certain hardware, so it is > important to know if other incompatibilities have been introduced. The hardware is Abit VP6 mb w/dual 866 coppermines & 256 MB of PC-133 memory. Disk0 is a Maxtor 30 GB, disk1&2 are on the HPT-370 controller and are also Maxtor 30 GB drives. The 2 HD's on the HPT-370 are identical models. All are rated at ATA-100. The loader has been Win XP Pro since beta2 and runs FreeBSD about half of the time. BTX - Register dump int=0006 err= efl=00030216 eip=0de7 eax=1d3a ebx=30ff ecx=001f edx=00ce esi=0001 edi=0009 ebp=03fe esp=03b1 cs=2364 ds= es=0204 fs=0000 gs=0000 ss=9dc5 cs:eip=0f 00 00 00 70 00 00 00-00 00 00 68 1e 00 00 00 ss:esp=b9 0d 00 00 00 fe 03 c2-03 02 01 80 00 1f 00 01 BTX halted Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does boot1 still have a > 1023 cyl limit?
Mike Smith wrote: > > > So.. if I read you right, booting correctly for > 1024 cylinders works > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd > > slice? Does this mean that boot1 and boot2 should work just fine if they > > are loaded by another kind of MBR loader (say, Grub), and they find out > > that they are placed beyond the 1023th cylinder? > > This should work, yes. I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I had to go back to the boot1 from 4.3 before I could boot. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Finding filesizes in C++ for files greater than 4gb
Jim Bryant wrote: > > Joseph Gleason wrote: > > > > - Original Message - > > From: "Alex Zepeda" <[EMAIL PROTECTED]> > > To: "Joseph Gleason" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Wednesday, August 01, 2001 21:45 > > Subject: Re: Finding filesizes in C++ for files greater than 4gb > > > > > On Wed, Aug 01, 2001 at 09:34:43PM -0400, Joseph Gleason wrote: > > > > > > > In FreeBSD, how can I determine the size of a file in C++ when the file > > is > > > > greater than 4gb? > > > > > > > > Currently, I use stat() and use st_size. That is limited to 4gb (32bit > > > > unsigned int) > > > > > > You're wrong. Read the man page. No soup for you! Next! > > > > > > - alex > > > > Alright, I made a mistake. But I did read the man page. Where does it say > > off_t is 64bits? > > > > My mistake was not digging through the include files enough to see what was > > going on. > > I think you got him on that, but [cut and paste of two consecutive lines from the >manpage]... > > off_t st_size; /* file size, in bytes */ > int64_t st_blocks;/* blocks allocated for file */ > > If the manpage specifies int64_t for the blocks, even though off_t isn't specified >in the manpage, what does it lead you to assume? > > Although 64-bit file sizes have been part of FreeBSD since 2.0-RELEASE back in 1994 >[as I recall], maybe the manpages should reflect > this fact by means other than the deductive reasoning outlined above. Joseph has >made a good point. Just so someone can see it. coral# grep BSD_OFF *.h ansi.h:#define _BSD_OFF_T_ __int64_t /* file offset */ coral# pwd /usr/include/machine Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (a bit offtopic) KDE2.1.1 install
> I'm running a p233 with 128mgs of ram, and KDE 2.1.1 install has been > compiling ALL MORNING > > Is this unusual? First, this is a question for -questions. You shouldn't send HTML. No, it could take 12 hours or more on the p233. Kent -- Kent Stewart Richland, WA Cool site http://www.bmwfilms.com mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvsup problems
"Koster, K.J." wrote: > > Dear All, > > Over the past few days I've been getting this error when I "make update": > > ... > Checkout ports/www/hypermail/files/patch-docs::Makefile.in > Delete ports/www/jakarta-tomcat/files > Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": > Directory not empty > *** Error code 1 > Stop in /usr/src. > *** Error code 1 > Stop in /usr/src. > makalu# > > The error message is correct in the sense that that directory is not empty. > It's got two patch fiels and a shell script in it. Permissions look fine > (read-write for root). > > Manually deleting /usr/ports/www/jakarta-tomcat will allow me to run cvsup, > but next time it will have recreated the files it tries to delete, > triggering the error again next time I run cvsup. > > I've set SUP* in /etc/make.conf and the supfiles are stock 4.3-stable. I run > cvsup with a "make update" from /usr/src. This problem occurs on both my > build servers, which have nothing in common except the fact that they are > PC's running FreeBSD-stable. > > What am I doing wrong? You need to remove the lines containing jakarta-tomcat in the checkouts.cvs* file /usr/sup/ports-all/ Some people have been able to just rm the port and others have had to also edit the checkouts file. You can read about it in http://www.freebsd.org/cgi/query-pr.cgi?pr=27495 Kent > > Kees Jan > > > You are only young once, > but you can stay immature all your life. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: if_fxp - the real point
Alfred Perlstein wrote: > > * Dennis <[EMAIL PROTECTED]> [010314 13:36] wrote: > > At 01:47 PM 03/14/2001, you wrote: > > >On Wed, Mar 14, 2001 at 09:09:15AM -0800, Alfred Perlstein wrote: > > > > how many times does windows crash because of poorly written drivers > > > > rather than flaws in the core OS? (*) > > > > > >ALL the time. Microsoft has given the UC-Davis security and formal > > >verification lab a multi-year grant to look at this problem. > > >(the approach being researched is "model checking") > > > > Why would they need to do that? Every time you load a program it updates > > the libraries, breaking older programs. Its a philosophical problem. You > > dont need a grant to figure it out. > > I think the money is for the solution. :) With 2000 and above, your system will check for non-digitally signed dll's and etc. The rule is pretty well enforced but will let you install around it. If you do, you may have shot yourself in the foot. You can recover but you have to run sfc from a command prompt window. That doesn't help you with the product built around the old dll's and with the stupid install. You also really need to have the source entry for the registry pointing to your HD. Otherwise, you are constantly switch the install CD and the sp-1 CDs. The checking takes hours on large systems but is massively longer if you have to spent the time switching CD's. I think Whistler is heading towards including dll's and etc. in the install program's space. You can't read too much about it right now. That gets around the problem with multiple copies because you can have your own, which people assume you have tested your product against and not affect a different product. That is very similar to the problem we are seeing right now with getopt.h. Libgnugetopt installed a terrible version of getopt.h into /usr/local/include. It wasn't a terrible product to libgnugetopt but to anything else that pointed their header includes to that directory. Then products such as KDE-2.1 come along and try to use it. The KDE-2.1 build bombed because the else clause in the old gnu getopt.h has no arguments defined for non-gnu libraries and tight checking kills the compile. Kent > > -- > -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: soft updates performance
void wrote: > > On Mon, Feb 12, 2001 at 10:36:40PM -0800, Jordan Hubbard wrote: > > > > With how many running processors? If you're running -j4 on a > > uniprocessor system, you're only introducing competition for already > > scarce CPU resources, though -j2 can be a speedup since this allows > > one target build to run while another is in an I/O wait. I've only > > seen a speedup with -j4 when using at least 2 CPUs. > > Interesting. When I asked about optimal values on this list maybe a > year ago, I was told that -j(4 * NCPU) was a good choice. I guess that > doesn't work for NCPU == 1. I did some testing last night and found that there was a difference of 50% between -j4 and not running softupdates and running softupdates and no -j4. The buildworld elapsed clock times were 58 minutes for the first case and 38 minutes for the last case. Even -j2 added 11 minutes to the elapsed build time. I thought I had been hit by one of the file system cron jobs on -j2 and ran it again. The difference was around 10 seconds between the two runs. The user time isn't that much different but the -jn contention really slows the buildworld down. The times are in a table at http://dsl1-160.dynacom.net/freebsd/urban_legends.html kent > > -- > Ben > > "I told Paddy no, I told Steve no, I told Paul no, and Ben fell asleep." >--Kate C. (no, different Ben, I would have stayed up) -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: soft updates performance
Sorry about the other one. I intended to start over. I did but not the way I wanted :(. Matthew Emmerton wrote: > > On Mon, 12 Feb 2001, Jordan Hubbard wrote: > > > > One other point that I would like to understand is why -j4 takes > > > longer on all of my systems. That goes against what everyone claims > > > should happen. > > > > With how many running processors? If you're running -j4 on a > > uniprocessor system, you're only introducing competition for already > > scarce CPU resources, though -j2 can be a speedup since this allows > > one target build to run while another is in an I/O wait. I've only > > seen a speedup with -j4 when using at least 2 CPUs. > > FWIW, I've got an ancient dual-CPU machine (Pentium 133s) with an onboard > Adaptec 7870 hooked to a pair of SCSI-2 drives. > > With any intensive build activity (make buildworld, or a kernel > recompile), -j8 gives me the best results. (I came to this conclusion > after profiling a kernel build using -j2/4/6/8/10/12.) > > The only explanation I can give in my case is that the onboard 7870 is a > PCI device and is the main bottleneck in the system (my motherboard is a > very interesting EISA/PCI combo, mfgd in 1991). > > Although Jordan's quite right in saying that using anything larger than > -j2 on a uniprocessor machine will usually be futile, in the world of SMP > things are much stranger, so it's good to experiment. (-j8 is > about a 50% speedup over -j2). YMMV. You have me interested now. I should have a dual P-III 866 running in a few days and I will find out. It is intended to end up running 2 or more Ultra-160 scsi HD's. That will come after I get some timing done with ATA-100 IDE HD's on separate controllers. I haven't tried running -j2 and as soon as my base case with no "-jn" specified and softupdate finishes, I will try "-j2". Kent > > -- > Matt Emmerton -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: soft updates performance
Matthew Emmerton wrote: > > On Mon, 12 Feb 2001, Jordan Hubbard wrote: > > > > One other point that I would like to understand is why -j4 takes > > > longer on all of my systems. That goes against what everyone claims > > > should happen. > > > > With how many running processors? If you're running -j4 on a > > uniprocessor system, you're only introducing competition for already > > scarce CPU resources, though -j2 can be a speedup since this allows > > one target build to run while another is in an I/O wait. I've only > > seen a speedup with -j4 when using at least 2 CPUs. > > FWIW, I've got an ancient dual-CPU machine (Pentium 133s) with an onboard > Adaptec 7870 hooked to a pair of SCSI-2 drives. > > With any intensive build activity (make buildworld, or a kernel > recompile), -j8 gives me the best results. (I came to this conclusion > after profiling a kernel build using -j2/4/6/8/10/12.) > > The only explanation I can give in my case is that the onboard 7870 is a > PCI device and is the main bottleneck in the system (my motherboard is a > very interesting EISA/PCI combo, mfgd in 1991). > > Although Jordan's quite right in saying that using anything larger than > -j2 on a uniprocessor machine will usually be futile, in the world of SMP > things are much stranger, so it's good to experiment. (-j8 is > about a 50% speedup over -j2). YMMV. > > -- > Matt Emmerton -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: soft updates performance
Jordan Hubbard wrote: > > > It was a uniprocessor system. The folklore has it doing more but all I > > You've been listening to the wrong folklore then, that's all. :) True but that is what section 19.4.6.5 in the Handbook implies. It also reads for -current but it has said that since 3.x was the latest stable. I would add -j4 and my buildworld would slow down a few percent. Kent > > - Jordan > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: soft updates performance
Jordan Hubbard wrote: > > > One other point that I would like to understand is why -j4 takes > > longer on all of my systems. That goes against what everyone claims > > should happen. > > With how many running processors? If you're running -j4 on a > uniprocessor system, you're only introducing competition for already > scarce CPU resources, though -j2 can be a speedup since this allows > one target build to run while another is in an I/O wait. I've only > seen a speedup with -j4 when using at least 2 CPUs. It was a uniprocessor system. The folklore has it doing more but all I ever saw it produce was more competition, which resulted in a longer running buildworld. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: soft updates performance
Matt Dillon wrote: > > :Thunderbird 900, with 256 MB of PC-133 memory, and using 3 - ATA-66 > :HD's on different controllers. The elapsed time dropped from 58:16 to > :45:54 by using softupdates. > : > :Kent > > That sounds about right for -pipe. The original email was > 1 hour vs 40 minutes, a 20 minute difference which seemed a bit > high (what I would expect without -pipe). 46 minutes verses 58 minutes > is only a 12 minute 20 second difference, which is more inline with what > I would expect. > > Most of the savings is occuring during the dependancy and > cleaning step(s). The system creates and deletes a huge > number of files in a huge number of directories and softupdates > really helps there. > > Softupdates is not helping much during the actual compilation, > which is a cpu-bound step if you use -pipe (the creation of the > object files costs nothing because there is no other disk activity > going on). On of the differences between the Thunderbird and the P-III is the FSB. AMD claims it gets 200 out of a 100MHz bus. The P-III are mostly using a 133 MHz FSB. I have a dual mb arriving shortly with a pair of 866's. The next test. I have a cluster project that would be very similar to a buildworld. It will end up using 2 - P-II 400's, the AMD, and the P-III's. Some people I work with run batch jobs that run overnight but I think they could wait for them to run with a small version of Purdue's ACME. A few hours of their time would pay for a small cluster. They don't have any problem with work. It is turning jobs around that seems to be the bottle neck. > > The buildworld hits various choke points -- even with -j 128, if > there are only 30 files in a library you will generally only see > 30 compiles going at once. The final library link stage chokes > it down to one process and this will become a pure bandwidth issue > for your disk subsystem for a second or so (for the larger libraries). I have gotten used to watching my buildworld's with top on occasions. I have setiathome running with a "nice" value for nice. On the AMD system, when the buildworld is hitting an I/O bottleneck, seti will be using 40% or more of the system. When it is compute bound, seti doesn't get any time. I think the accrual of time by seti is a sort of integrated past history of the system availability due to an I/O type of bottle neck during the buildworld. It follows the % value reported by time fairly well. Softupdates is the first time the time % value on the AMD went above 60%. I think this indicates I have an overall I/O bottle neck. The current version of seti writes a small blip of data to the HD about every 30-60 seconds and so there isn't much HD interaction going on there. I'm thinking about adding 2 - Ultra-160 scsi's to the system at some point. For the kind of stuff I do, iozone seems to cover the HD activity the best. The tagged queing of the scsi deals with small record random I/O much better than the IDE drives do. From what I have read, FreeBSD supports tagged queing on the new IBM IDE drives but I don't have any of them to use to test. One other point that I would like to understand is why -j4 takes longer on all of my systems. That goes against what everyone claims should happen. Kent > > -Matt -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: soft updates performance
Matt Dillon wrote: > > :> In fact, it's exactly the opposite. 'make world' is CPU-bound, so the > :> speed of the I/O system is irrelevant. If it were I/O bound, soft > :> updates *would* make a difference, because a number of unnecessary > :> writes would be eliminated. > : > :Read what he writes. Soft updates *did* make a difference - they > :shaved ~30% off his worldstone. It's parallelization that doesn't make > :a difference in his case, because his CPU and FSB are fast enough that > :the I/O system is left completely in the dust. This is a 900 MHz box, > :probably with a 100 MHz or 133 MHz FSB, not the old 486DX33 you have > :lying in a corner. > : > :DES > :-- > :Dag-Erling Smorgrav - [EMAIL PROTECTED] > > A suspect a good chunk of that is not using -pipe. I would be > interested in buildworld numbers with -pipe vs with -pipe + softupdates. > Without -pipe softupdates will make a huge difference due to temporary > file creation & deletion. > > When Kirk first tested softupdates against buildworld, he explicitly > tested it with and without -pipe and found that much of the performance > benefit (for buildworld) occured when not using -pipe. The times I reported earlier are all with -pipe and are on an AMD Thunderbird 900, with 256 MB of PC-133 memory, and using 3 - ATA-66 HD's on different controllers. The elapsed time dropped from 58:16 to 45:54 by using softupdates. Kent > > -Matt > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: soft updates performance
Greg Black wrote: > > Alfred Perlstein wrote: > > > * Greg Black <[EMAIL PROTECTED]> [010210 23:33] wrote: > > > Matt Dillon wrote: > > > > > > > Unless you are doing a read-only mount, there are still going to be > > > > cases where having softupdates turned on can be advantageous. For > > > > example, installworld will go a lot faster. I also consider softupdates > > > > a whole lot safer, even if all you are doing is editing an occassional > > > > file. > > > > > > OK, I'm sold on the general idea of using soft updates; but what > > > sort of performance improvements should I expect to see? > > > > > > I do a kernel compile on a freshly-rebooted box with an without > > > softupdates; without, it took 20m45s and with soft updates it > > > still took 20m10s --- this is less than 3% faster, which is > > > close to statistically insignificant. Is this expected, or is > > > there some other factor I should look at? > > > > Does 'mount' actually show softupdates as active? If not you > > need to run 'tunefs' on the partition to set them active. > > Yes, I ran tunefs as per the manual and I checked with mount. Times for cvsup and system builds changed quite a bit if you let the I/O be handled by the controllers. buildworld obj on 2nd controller 1516.863u 442.821s 57:17.18 57.0% 1246+1450k 49613+196329io 1866pf+0w build with log on 3rd controller 1522.877u 455.119s 56:52.29 57.9% 1238+1446k 45803+196359io 1721pf+0w make world with files on 3 controllers and -j4 1547.296u 553.318s 58:16.61 60.0% 1196+1415k 45943+314666io 1655pf+0w make world with files on 3 controllers and -j4 with softupdates 1539.114u 521.486s 45:54.82 74.7% 1209+1431k 48857+129907io 1858pf+0w Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Possible bug in /usr/bin/makewhatis.
Matt Dillon wrote:
>
> I was doing some installworlds and got a bunch of 'gzcat: Broken pipe'
> errors at the very end when it was doing 'makewhatis' on various manual
> directories.
It also only happens if you are running ssh to logon to the computer
doing the makewhatis. You can telnet to the system and you don't see
the problem.
Kent
>
> I believe the problem is related to the makewhatis perl script closing
> the input descriptor before draining all the input, but not being a
> perl progammer I can't tell for sure. The place where the perl program
> appeared to be closing the input prematurely is here:
>
> # ``man'' style pages
> # &&: it takes you only half the user time, regexp is slow!!!
> if (/^\.SH/ && /^\.SH[ \t]+["]?($section_name)["]?/) {
> #while() { last unless /^\./ } # Skip
> #chop; $list = $_;
> while() {
> last if /^\.SH[ \t]/; <<<<<<<<<<<<<<<<<<<<< here
> chop;
> s/^\.IX\s.*//;# delete perlpod garbage
> s/^\.[A-Z]+[ ]+[0-9]+$//; # delete commands
> s/^\.[A-Za-z]+[ \t]*//; # delete commands
> s/^\.\\".*$//;#" delete comments
> s/^[ \t]+//;
> if ($_) {
> $list .= $_;
> $list .= ' ';
> }
> }
> &out($list); close F; return 1; <<<<<<<<<<<< closing here
> ...
>
> Could someone take a look at that? There might be other places as well.
> Thanks!
>
> -Matt
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
--
Kent Stewart
Richland, WA
mailto:[EMAIL PROTECTED]
http://kstewart.urx.com/kstewart/index.html
FreeBSD News http://daily.daemonnews.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Sitting on hands (no longer Re: FreeBSD vs Linux, Solaris, and NT)
SteveB wrote: > > > -Original Message- > > From: Drew Eckhardt [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, December 21, 2000 12:15 PM > > To: SteveB > > Cc: [EMAIL PROTECTED] > > Subject: Re: Sitting on hands (no longer Re: FreeBSD vs > > Linux, Solaris, > > and NT) > > > > > > In message > > <[EMAIL PROTECTED]>, admin@bsdfan > > .cncdsl.com writes: > > > > >QA is unglamorous work, but needs to be done. > > > > Does this mean you're volunteering? > > > > > I don't have a lot of time, but I would volunteer if there was a QA > project. I think it would be a good learning experience. One of the things I have been doing it cycling through 4 systems upgrading the userland and kernel. I have a script setup such that I capture everything from the cvsup log to build and installs. During the transition between 4.1.1-stable and 4.2-stable, one of this systems was updated everyday. It isn't a QA cycle that I experienced in the commercial world associated with the US Nuclear Regulatory Commission but it did insure that my setups work. If someone popps up on -stable and says that the "Buildworld is failing" for 4-stable, it is really easy to fire off that script and find out if it is. I have one running at this time. Kent > > Steve B. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Floppy disk is full
"Aoyama, Kieko" wrote: > > Hello, I am Kieko Aoyama. > > I am working at Compaq Computer K.K. in Japan. > Please tell me the way of > "getting boot.flp,fixit.flp,,kern.flp from FTP directory" > > But, > I know the location of FTP directory,and I am going to getting these files > to floppy disk(1.6MB). > And I get the ERROR "You cannot write the file to disk". > > The OS that I'm using is Windows2000. > And I am getting these files to drive A:. > Please show me the way. You have to use fdimage from the /tools directory since they are images of the floppy. Kent > > --- > Kieko AOYAMA@Compaq Computer K.K. > Tel:03-5349-4491(4491) > Fax:03-5349-7458 > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: make buildworld fails
Dave Hayes wrote: > > Kent Stewart <[EMAIL PROTECTED]> writes: > > I did a cvsup build of 3 systems using 4-stable when it showed up as > > 4.2-release. How did you install 4.2 and did you cvsup src-all. > > This is a 3.3-RELEASE system upgrading to 4.2, I did cvsup src-all, > > > You are dying building the gnu /binutils. Function mkstemps is a > > function in the Standard C Library libc and is located at > > /usr/src/contrib/binutils/libiberty/. It is almost like you are > > missing a > > ldconfig -R /usr/obj/usr/src/lib/libc > > or libc doesn't exist because of the install. > > This could very well be. I am following the instructions in UPGRADING > under "To update from 3.x to 4.x stable". The general comment is that you have to be at 3.5 to do that. However, Engelshall had a process that worked for almost every concievable difficulty at 3.5 > 4.x. There were somethings fixed in the week or so after 4.2 was released and you might consider 4-stable. Some things in Engleshall's procedure are out of date such as mv'ing /MYKERNEL to /kernel but it touches on some of your problems. See http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=51796+57580+/usr/local/www/db/text/2000/freebsd-stable/20001015.freebsd-stable If you have to fight upgrading and making two worlds (3.5 and 4.2-R), a binary upgrade followed by making your world and kernel will be much faster. The 4.x buildworld just about requires 2x as long as a buildworld in 3.x. I use the buildworld sequence from /usr/src/UPDATING almost religiously because I cvsup everytime I do a build. I also like the idea of building everything before I start the installs. In my situation, I found that putting the process into a script would have everything built when I would go back to check on the status. Doing the individual steps typically left me at just the end of the buildworld. Kent > -- > Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] > >>> The opinions expressed above are entirely my own <<< > > There is no greater calamity for a nation or individual >than not finding contentment in one's sufficiency. -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: make buildworld fails
Dave Hayes wrote: > > Kent Stewart <[EMAIL PROTECTED]> writes: > > Dave Hayes wrote: > >> > >> Cvsup'd sources (tag=RELEASE_4_2_0) from scratch fail: > > I don't see a tag=RELEASE_4_2_0. There is a tag=RELENG_4_2_0_RELEASE. > > Could this be your problem. > > No, I misreported the tag. If I had tried that, there'd probably be no > sources. ;) Just making sure :) I did a cvsup build of 3 systems using 4-stable when it showed up as 4.2-release. How did you install 4.2 and did you cvsup src-all. You are dying building the gnu /binutils. Function mkstemps is a function in the Standard C Library libc and is located at /usr/src/contrib/binutils/libiberty/. It is almost like you are missing a ldconfig -R /usr/obj/usr/src/lib/libc or libc doesn't exist because of the install. Kent > -- > Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] > >>> The opinions expressed above are entirely my own <<< > > "We should never live in a world where dreams are rarer than money." > -Mathhew Brodrick > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: make buildworld fails
Dave Hayes wrote: > > Cvsup'd sources (tag=RELEASE_4_2_0) from scratch fail: I don't see a tag=RELEASE_4_2_0. There is a tag=RELENG_4_2_0_RELEASE. Could this be your problem. Kent > > ===> objdump > ... > ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': > choose-temp.o(.text+0x264): undefined reference to `mkstemps' > > Is this a simple fix I hope? > -- > Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] > >>> The opinions expressed above are entirely my own <<< > > No snowflake falls in an inappropriate place. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel compile problem?
Lists Account wrote: > > Hi all, > > Just wondered if anyone could help me out here, Im trying to cvsup from > 4.0-RELEASE to 4.1-STABLE and on a make depend on my kernel I get the > following: It doesn't work this way. When you cvsup, you need to follow the recipe in /usr/src/UPDATING. There is a section on upgrading from 4.x to 4.1-stable. The safe route is to follow the buildworld, build[install]kernel, installworld sequence. Kent > > ===> agp > make: don't know how to make agp_if.c. Stop > *** Error code 2 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Anyone else getting this error on a build? > > I last cvsupped at 8:50am GMT+2 > > Thanks > > Andrew > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: problem on 4.1-RC (4.0-stable)
Ulf Zimmermann wrote: > > On Tue, Jul 18, 2000 at 09:09:47PM -0700, Kent Stewart wrote: > > > > > > Ulf Zimmermann wrote: > > > > > > Hello, > > > > > > I updated via cvsup (cvsup from tuesday afternoon PDT), I went into > > > single user mode, did make world, make buildkernel KERNEL=FOURTYTWO > > > and make installkernel KERNEL=FOURTYTWO. Everything but one thing > > > I can find seems to work fine, but ps doesn't. > > > > Did you boot /FOURTYTWO or do the rename sequence to make it kernel? > > It sounds like your kernel and world might be a little out of > > sequence. > > I did the move. I rebuild the kernel again, same file size got created. > Yes, I agree it sounds like stuff is out of sync, but I did the complete > world after I cvsup and made the kernel. I thought it was something simple. I'm running 4.1-RC on 3 computers and ps works on all of them. Having something out of sequence could produce symptoms like that. FWIW, 4.1-RC is broken right now when you try to build the netinet section. So you can't cvsup to make sure didn't grab files in the middle of an upgrade. Kent > > > > > Kent > > > > > > > > Trying to use ps: > > > > > > fourtytwo ulf home/ulf > ps > > > ps: bad namelist > > > > > > Rebuilding kerbel, libkvm or ps produce the same bins. "bad namelist" > > > is in error inside of libkvm (kvm_i386.c) after using kvm_nlist. > > > > > > Anyone got an suggestion what to check or what maybe broken ? > > > > > > -- > > > Regards, Ulf. > > > > > > ----- > > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > -- > > Kent Stewart > > Richland, WA > > > > mailto:[EMAIL PROTECTED] > > http://kstewart.urx.com/kstewart/index.html > > FreeBSD News http://daily.daemonnews.org/ > > > > Bomber dropping fire retardant in front of Hanford Wild fire. > > http://kstewart.urx.com/kstewart/bomber.jpg > > -- > Regards, Ulf. > > - > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: problem on 4.1-RC (4.0-stable)
Ulf Zimmermann wrote: > > Hello, > > I updated via cvsup (cvsup from tuesday afternoon PDT), I went into > single user mode, did make world, make buildkernel KERNEL=FOURTYTWO > and make installkernel KERNEL=FOURTYTWO. Everything but one thing > I can find seems to work fine, but ps doesn't. Did you boot /FOURTYTWO or do the rename sequence to make it kernel? It sounds like your kernel and world might be a little out of sequence. Kent > > Trying to use ps: > > fourtytwo ulf home/ulf > ps > ps: bad namelist > > Rebuilding kerbel, libkvm or ps produce the same bins. "bad namelist" > is in error inside of libkvm (kvm_i386.c) after using kvm_nlist. > > Anyone got an suggestion what to check or what maybe broken ? > > -- > Regards, Ulf. > > - > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Worst case swapping.
Matthew Dillon wrote: > > :Believe me, I look at these things. Yes there is a lot going on and a > :lot using memory. I normally have about 20% to 25% of my Gig of swap > :used... meaning that I have allocated roughly double my RAM in > :applications. > : > :And when this worst-case happens, memory is full... but the only > :active application is Netscape. > : > :On my home machine, the same thing tends to happen. It only has 128M > :and vastly fewer things going on. I see cases were I'm surfing for > :20-30 minutes and I will hit this 10 to 30 second (longer, becase the > :swap at home is slower) gap in netscape response. > : > :The only other applications running would be something like a small > :UUCP transfer or a small amount of NFS traffic when the wife's > :(diskless) machine changes screensavers. > : > :Dave. > > Hmm. How large a memory-cache do you have configured for netscape? > Disk cache? What is the RSS and VSZ of the netscape binary while > the paging is going on? Please post a ps axl of the state of the system > while the paging is going on. Netscape reallys goes to pot in a hurry if you allow it to use more than 1-2MB of memory cache. A friend was seeing a terrible response and tracked it back to Netscape's memory cache. He had a lot of memory and started out with something on the order of 16MB. By the time he was satisfied he was allowing less than ~2MB of memory cache, which is all I had ever allowed it to use. I seem to remember an affect on how much disk cache but that part of the memory has evaporated. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Comments on Athlon [motherboards] sought..
Mike Smith wrote: > > > > > Ah, the K7V already has as many PCI slots as you can drive off the existing > > > > bridge, and who wants ISA slots these days? Oh, there is the WaveLan ISA > > > > card I need... > > > > > > Right, that is exactly what I mean. I rather see a ISA/PCI combo slot that I > > > might use than this AMR thing I will 100% sure never use. > > > > The writeup on the ASUS home page indicated this slot will function as > > a PCI slot. When I was reading it, it looked sort of like the old > > VL-bus, which you could use as an ISA slot. > > You're confusing this with an old, unrelated connector which was aligned > with a PCI slot. This is a completely different animal. Very definately. This time I followed the links until I came to HTTP://www.asus.com/products/motherboard/Pentiumpro/Cuwe-fx/amrslot.html This one had an image of one. There wasn't anyway to confuse the two :). Kent > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Comments on Athlon [motherboards] sought..
Wilko Bulte wrote: > > On Fri, Jun 09, 2000 at 05:06:33PM -0600, Wes Peters wrote: > > Wilko Bulte wrote: > > > > And a horrible way to loose valuable PCB real estate that could have housed a > > > PCI/ISA slot. A modem line interface on an L-shaped 'blech' with a cable > > > to the mom board would be better IMHO. Would allow the owner to throw > > > it away and put PCI/ISA expansion on the machine ;) > > > > Ah, the K7V already has as many PCI slots as you can drive off the existing > > bridge, and who wants ISA slots these days? Oh, there is the WaveLan ISA > > card I need... > > Right, that is exactly what I mean. I rather see a ISA/PCI combo slot that I > might use than this AMR thing I will 100% sure never use. The writeup on the ASUS home page indicated this slot will function as a PCI slot. When I was reading it, it looked sort of like the old VL-bus, which you could use as an ISA slot. Kent > > -- > Wilko Bulte FreeBSD, the power to serve http://www.freebsd.org > http://www.nlfug.nl > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
UDMA-33 Error Messages
I had a power outage this morning and my 4.0-Stable system suddenly started generating the following messages Jun 1 09:38:55 opal /kernel: acd0: DVD-ROM at ata1-master using PIO4 Jun 1 09:38:55 opal /kernel: Mounting root from ufs:/dev/ad0s3a Jun 1 09:38:55 opal /kernel: ad0: UDMA ICRC READ ERROR blk# 0 retrying Jun 1 09:38:55 opal last message repeated 2 times Jun 1 09:38:55 opal /kernel: ad0: UDMA ICRC READ ERROR blk# 0ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA Jun 1 09:38:55 opal /kernel: falling back to PIO mode Jun 1 09:38:55 opal /kernel: WARNING: / was not properly dismounted This machine had never done this before and I noticed that the reboot hadn't taken care of the dismount message. I had to manually fsck the system. A single user boot produced much nastier messages and were persistant. I rebooted three times before I did the manual fsck. The boot to single user was the third boot. The reboot after the fsck sequence produced the following boot stream cut and pasted from dmesg. Jun 1 10:20:23 opal /kernel: ad0: 19541MB [39703/16/63] at ata0-master using UDMA33 Jun 1 10:20:23 opal /kernel: ad1: 6679MB [14475/15/63] at ata0-slave using UDMA33 Jun 1 10:20:23 opal /kernel: ad3: 12970MB [26353/16/63] at ata1-slave using UDMA33 Jun 1 10:20:23 opal /kernel: acd0: DVD-ROM at ata1-master using PIO4 Jun 1 10:20:23 opal /kernel: Mounting root from ufs:/dev/ad0s3a I also noticed the "/kernel: WARNING: / was not properly dismounted" in messages from people having ATA read error troubles on UDMA drives. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NFS server problems on 3.4-S, any interest?
Doug Barton wrote: > > On Mon, 22 May 2000, Matthew Dillon wrote: > > > :>From the workstation: > > :Name Mtu Network Ipkts IerrsOpktsOerrs Coll Drop > > :fxp0 150032102492 0 31653667 0 30900 0 > > : > > :>From the fileserver: > > :Name Mtu Network Ipkts IerrsOpktsOerrs Coll Drop > > :xl0 1500 3250417328967 32900227 00 0 > > : > > : I did find it a little unusual that I was getting collisions on a > > :crossover cable, but when I looked at the mail archives related to that > > :problem I read that the intel cards are very aggressive packet pushers, > > :and that this isn't all that unusual. The ratio of good packets to > > :collisions seemed healthy enough to not warrant too much concern. > > > > 28967 input errors on xl0? Problem! > > heh... ok, I can take a hint. > > > But the real problem is that you are attempting to do 10BaseT > > full-duplex. Full-duplex operation with 10BaseT is problematic > > at best. Full duplex has good interoperability at 100BaseTX speeds, > > but not at 10BaseT speeds. > > Ok, I learned something new. :) I've had "get another fxp0 and a > real switch" for the home network on my list for a while now, I guess it's > time to move that up a little. > > > Crossover cables work fine, usually, but I personally *never* use them. > > I always throw a switch in between the machines and let it negotiate > > the duplex mode with each machine independantly, plus it gives me nice > > shiny LEDs that tell me what the switch thinks the port is doing as > > a sanity check. > > Yeah, I miss the blinky lights. I went to the x-over cable because > the hub I bought originally was giving me non-stop collisions under > load. It worked really well for about 5 months, then the last couple > months it's given me problems. I'm still learning the whole networking > thing, so I appreciate the insight. I had an fxp0 that the mounting bracket was a little long and the pressure of screwing it down messed things up. I would get 10MB/s out but only 10KB/s into that system. It was dropping 300-700 bytes in some packets. I found out last night that I could remove the screw and it worked just fine. An old 3C905-TX didn't have the problem either but I only got 8-9MB/s. A spare fxp0 also didn't have the problem and it was 11MB/s both directions. Kent > > Doug > -- > "Live free or die" > - State motto of my ancestral homeland, New Hampshire > > Do YOU Yahoo!? > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
Kris Kennaway wrote: > > On Mon, 24 Apr 2000, Kent Stewart wrote: > > > This is what I see on a buildworld with 4.0-Stable > > > > Modified /etc/make.conf and commented out CFLAGS= -Os -pipe > > 3707.4u 799.6s 1:35:52.46 78.3% 1374+1477k 56974+173232io 2337pf+0w > > 3693.9u 800.5s 1:29:45.73 83.4% 1375+1477k 55201+173224io 2160pf+0w > > Modified /etc/make.conf and added CFLAGS= -pipe > > 3559.2u 807.2s 1:28:00.05 82.6% 1608+1286k 56499+174033io 2516pf+0w > > This is an old message, but what you're seeing here is that if CFLAGS is > not overridden, it is set by sys.mk to "-O -pipe" > > Setting CFLAGS explicitly to "-pipe" is faster because it does no > optimization, "-Os -pipe" would be slower because it does more. Leaving > out -pipe would be slower still, because the compiler does data passing > using temporary files in /tmp instead of via a pipe. Part of this you had to go back about 15-20 messages. There were some comments about options that would speed the system up. I then ran both styles of buildworlds on kernels built with the -Os to see if my buildworld times changed. It wasn't significant. A long about this same time I ran some tests with using this for IBM DCAS drive current setup. da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Previously, the tagged queueing was turned off. I have run a number of tests with 4.0-Stable and enabling tagged queueing on this drive didn't slow the disk down. It really didn't speed it up to speak of either. Kent > > Kris > > > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe <[EMAIL PROTECTED]> > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [OT] Finding people with GSM phones (was Re: GPS heads up )
Wes Peters wrote: > > Alex Stamos wrote: > > > > > > > > > What's the actual background behind this? > > > > > > Being able to track 911 calls in the case of emergency. > > > > While some people may find this a convenient excuse for more Big Brother tactics, > > I once spoke to a paramedic friend about 911 cell phone tracking after it was first > > announced. She said that she couldn't overestimate the problems caused by people > > giving bad directions or locations over cell phones. Apparently, its not uncommon > > for a person, still dazed from an accident, to report their location as "Somewhere > > on Interstate 80". -For those non-Americans, I-80 is a 3,000 mile freeway that > > starts in San Francisco and ends in Boston.- > > Well, New York. It also includes some of the emptiest parts of the continental > USA, mostly in Nevada and Utah. > > The problem is a lot worse in the empty places, where you have thousands of miles > of unpaved roads that still manage to get some mobile phone coverage. The analog > cell tower in Callao, Utah, for instance, covers a fixed population of about 100 > people, and an area larger than the state of Rhode Island. > > >On another topic, I recently read an article on Ace's Hardware comparing the > > performance of standard benchmarks, on a Alpha 21264 under Linux, compiled with the > > GCC and Compaq's proprietary compiler. Compaq's C compiler kicked GCC's ass in > > almost every metric. My questions: Is such a compiler available for *BSD? Why is > > GCC so bad at Alpha optimization when it does so well on x86? Is somebody asleep > > at the wheel here? > > Who said it's any good at X86 optimization? I find setiathome, which was compiled with an Intel compiler on the Windows side, out calculates setiathome on the same computer 20-25% on the average when I boot FreeBSD 4.0 and run it there. Kent > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > [EMAIL PROTECTED] http://softweyr.com/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [OT] Finding people with GSM phones (was Re: GPS heads up )
Mike Smith wrote: > > > There were some famous cases where some criminals were located by tracking > > down their cell phone. The police needed some decision from court to do > > that, but after that, it was a short way to go. The GSM nets have some of > > this ability built in, to track phones. The operators only don't want the > > "normal" citizen or user to know about that. > > This capability of GSM was well known when it was introduced in .au, but > when my phone was stolen, the telco bastards wouldn't admit to being able > to tell me anything about where it was (even though I could still call > it...). > > What's being proposed here sounds just slightly scary. Depends on your big brother complex. When I first went to work at Hanford, I was told that 1 in 10 calls were recorded. You didn't worry about it. You didn't say anything stupid either :). Some of the western parts of the US have a lot of milleage between towns. Australia is much worse in a lot of areas. How many people know if they are closer to one emergency service or another. One could be 100 miles (160km) away and the next one could be 10. It could be even worse and would depend on a helicopter being dispatched with paramedics. You are in the middle of no where but you can still have an active cell phone. It doesn't do the emergency services people any good unless they have an idea where you are. Kent > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Include headers error in kdebase-1.1.2
I have been trying to build kbebase-1.1.2 and the make dies trying to compile kscreensaver/morph3d.cpp. It seems to find X11/Intrinsic but it cant't find GL/xmeasa.h. The directories X11 and GL are at the same level in the X11R6 tree. I've found that if I add "-I/usr/X11R6/include" to the "all_includes" make variable in the kscreensaver Makefile, it will build. This leads me to believe that my "/usr/X11R6/include" path hasn't been setup in my system. It could also be a bad generate by automake. How do I determine what is causing the problem? I have two systems running FreeBSD 4.0-Stable and it occurs on both of them. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GPS heads up
Nate Williams wrote: > > > > >: With 12-channel chipsets becoming common, new devices are getting quite > > > >: good at this. > > > > > > > >Yes. Most of the data I have is for 6 channel models. > > > > > > 12-chanel chipsets are overkill if you don't live more or les exactly > > > on the equator or one of the poles. Here where I live (56 north) about > > > 30% of the sky is never covered by a satelite because of the inclination > > > of the satelites being non-zero. > > > > Get used to them, both Garmin and Trimble are using 12-channel engines > > now. Even the cheapo Rockwell chipset is 6 channels, going to 12 by > > the time the start putting them into mobile phones next year. There's > > a mandate in the USA that all mobile phones have GPS in them by 2003, > > Actually, the phones don't have to have GPS, but they must be able to > get a fix on them good to 100m. I talked to one of the engineers at > Qualcomm last year who is working on this, and GPS isn't going to be > used because it doesn't work in buildings. And, most of the world's > cell-phones are used in buildings. They are doing triangulation and > putting GPS units in the cell towers instead, which is far cheaper. > > Plus, they can get a fix on the phone in 300ms (good to about 25m), > which is far faster than a GPS unit can do it. Basically, the phone is > 'locked on' as soon as you turn it on and it finds a cell tower. And, > apparently they've figured out a way to get a coarse fix on it even > where there is only one tower, although when I pressured him, he just > smiled and claimed it was a trade secret. > > Or so I've been told, but I trust the source since he's one of the > smartest guys I ever met. :) The direction and distance doesn't seem to be too much of a challenge. Most of you are HAM's and some of you may even remember the old Bunny hunts. This game at Hamfests disappeared when the directional finders were developed that detected the phase difference between 4 antennas. With the phase differences the unit would calculate a relative heading and light up that LED. All you had to do then was just drive to the hidden transmitter using the bearing present by the lighted LED. The cell towers have ~10 antennas, which should provide more accuracy than 4 did. The cell phone probably responds similarly to an IFF on an airplane and any delay would pin point the cell phone within a reasonable distance down that heading they could calculate. You are going to have to calibrate the delay but that would be a function of the logic chips. It could also be close to a constant. Multipath would cause problems in the larger cities. Anyone that has tried to use a 2m handheld in Dallas is familiar with that problem :). But you have more cell towers and the cities and you could triangulate that way. -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GPS heads up
Nate Williams wrote: > > > >I disagree. I routineles pick up 10-11 satellites, and I'm about > > >half-way between the pole and the equator. Heck, I just looked, and > > >I've got 8 locked on right now. > > > > Right, 8 is the norm. When you have 10 or 11 a couple or four of them > > are so low on the horizon that they hardly matter. > > Actually, the horizon ones are the best ones for calculating altitude, > so they are very much being used. And, from looking at the satellite > map, only a couple of them are on the horizon. (I *really* like the > Garmin 12 unit. :) Does anyone have a unit that picks up the Russian GLONASS satellites and well as the USA GPS? It is supposed to improve the accuracy. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GPS heads up
Mike Nowlin wrote: > > > This is what "Differential GPS" provides: a standard time source that > > can be used to remove the SA meanderings from the GPS fix. > > If I'm understanding this correctly (with very little actual research into > it) is that a DGPS station essentially transmits the difference between > what it "hears" as it's location and what it's actual measured location > is to the clients, which apply this change to their local "heard" > position. (Assuming that both sides are within the appropriate range of > each other that allows them to hear the same satellites.) > > Do I have it about right? > > (I just hooked up my Garmin GPS-20 and my Delorme Tripmate again to my > "figure out what the differences are between these two GPS units are and > plot them on the screen" program -- it'll be interesting to compare the > results from now and 6 months ago...) > > Out of curiosity, how many people in this discussion are hams? > > --mike N8NVW > > (Funny how the GPS changes are two weeks after the FCC Part 97 licensing > changes took place... I wonder if there's any (even remote) > connection...) I think there is one or more GPS systems up there. When you have the only one, you can introduce side effects like that and they matter. When someone else has one, it doesn't matter that much any more. IIRC Russia was starting to put one up more than a year ago. If we don't think it matters anymore, than one of them is operational. Kent - ka7gkw > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GPS heads up
Poul-Henning Kamp wrote: > > In message <[EMAIL PROTECTED]>, Matthew Dillon writes: > >Ok, this has nothing to do with FreeBSD, but I just had to post > >something since nobody else has. > > > >By presidential order, on May 1 the error introduced into the GPS > >system, called 'SA', was turned off. > > > >This means that your GPS receivers are now around 5-10 times more accurate > >then they were before May 1st. > > This has nothing to do with FreeBSD unless you count NTP servers, > but actual data can be found on: > > http://212.242.40.185/cgi-bin/ppsoffset.cgi > It may not have anything to do with the OS FreeBSD but it has a lot to do with what we can do easily and for a really modest price. The techno-farms need to know where they are at in a field when they record data. The old offset error made it such that the operator knew where they were but the computer couldn't tell which field they were in. A simple differential was expensive. Now, you don't have the wild swings and two computers recording data using the GPS derived time may be close enough to record which plant they are taking data for. Kent > This is "gps.freebsd.dk" one of, if not the, most precise NTP stratum 1 > servers in the world: +/- 20nsec. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > [EMAIL PROTECTED] | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
Dan Nelson wrote: > > In the last episode (Apr 26), Kent Stewart said: > > I just noticed that mine isn't showing "Tagged Queueing Enabled" is > > that something I can set? The adapter is an Adaptec 2940uw. > > > > da0 at ahc0 bus 0 target 4 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > > da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) > > The CAM code has a quirk entry for IBM DCAS drives that turns it off; > check out /sys/cam/cam_xpt.c, line 320. I suggest benchmarking with > and without the quirk entry, and if it's faster with tagged queueing, > update PR kern/10398. What would you suggest. Do you remove the entry or just change the tags field? It has mintags=0 and maxtags=0. The other entries have mintags=24 and maxtags=32. I 've have about 6 hours of buildworlds on it right now. Plus some other benchmarking. Kent > > -- > Dan Nelson > [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
Matthew Dillon wrote: > > The standard PCI bus can do 130 MBytes/sec. Even with overhead issues > (setup for a DMA burst) it can still do 100 MBytes/sec. But that depends on what is also going on at the same time. There are three other cards in my PCI bus. You can eliminate one because I wasn't using the sound card :). > > A standard SCSI controller can do 40, 80, and now even 160 MBytes/sec > over the wire - standard copper cabling w/ LVD connectors (example > below). This is where the cache size on the HD becomes important. It also acts like a hardware double buffering. > > A modern hard disk can do 10-30 MBytes/sec to/from the platter, assuming > no seeks. But the moment it needs to seek the performance drops > drastically ... generally down to 1-5 MBytes/sec. I haven't seen any 30MB/s. The 10K LVD IBM's were just about the fastest at 20MB/s continuous. The drop for UDMA drives is to even lower rates. > > So in the case of a file copy over a SCSI bus, the physical disk is > almost always going to be the limiting factor. I just noticed that mine isn't showing "Tagged Queueing Enabled" is that something I can set? The adapter is an Adaptec 2940uw. da0 at ahc0 bus 0 target 4 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
Narvi wrote: > > On Sat, 22 Apr 2000, Matthew Dillon wrote: > > [snip] > > > disk itself is probably the bottleneck. Disk writes tend to be > > somewhat slower then disk reads and the seeking alone (between source > > file and destination file), even when using a large block size, > > will reduce performance drastically verses simply reading or writing > > a single file linearly. Double buffering may help a disk-to-disk > > file copy, but I doubt it will help a disk-to-same-disk file copy. > > > > Wouldn't coping the file to another disk and then back to the original one > than just a simple copy in some cases be faster then? > > After all, you are saving a lot of head seeks. The problem is that if they are on the same data channel then you have conflicts for access to the data bus. Some products like SCSI are better suited for that environment but data still only flows one direction at a time. On the old ISA bus, you could just about watch data flow with an analyzer plugged on to a new interface card. We had one interface card that the data ready went true before the data was stored into the on_card memory. The cpu was fast enough that I could watch the bits in the memory change. I couldn't get good data until memory had stablized. Cray's were really good at handling data in 1988 because they had 100MB/s + 1000MB/s data channels. I'm not sure how wide the data channels were. It seems like the 100MB/s was 16 bytes wide and the 1000 MB/s was 32 bytes wide. Their high speed disks were striped to provide 20MB/s continuous transfers. Getting data off of the disk was far more important to throughput than writing the data. The queued read/write ability of the scsi drives made life better but the disk was still the bottle neck to high speed data. The PCI bus probably shares that honor on the modern PC. It is only 4 bytes wide and relatively slow. The new 64bit PCI bus will help but that is a long way from the 256 bit or 512 bit wide Cray data channels that Cray was using in 1988. A while back I was given some parameters that could change the time required for a 4.0-Stable buildworld. The only option that improved my buildworld time was "CFLAGS= -pipe". It saved about 140u seconds. The option "-Os" made a buildworld take 1/3 longer. I also did an installworld (and kernel) of a -Os system and that really didn't change the times. The jump for version 4.0 on a Celeron 433a was 3560u + 800s to 4950u + 800s. There are still some options to try but "softupdates" didn't help. The buildworld using an UW scsi for /usr/obj was actually a little bit longer than using a UDMA66 ATA HD. The scsi was flat out at 8MB/s where as the UDMA HD was capable of 12-14MB/s. The Maxtor UDMA drive had a 2MB cache and the IBM uw was much smaller. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
George Cox wrote: > > On 24/04 00:08, Christian Weisgerber wrote: > > > Hasn't O'Brien recently said that in fact "-pipe" is already the default > > for our cc, so explicitly specifying the option doesn't do anything? > > Try compiling a 'hello world' program with and without the '-pipe' option > but with '-v' switched on in both cases and compare the difference in the > messages. This is what I see on a buildworld with 4.0-Stable Modified /etc/make.conf and commented out CFLAGS= -Os -pipe 3707.4u 799.6s 1:35:52.46 78.3% 1374+1477k 56974+173232io 2337pf+0w 3693.9u 800.5s 1:29:45.73 83.4% 1375+1477k 55201+173224io 2160pf+0w Modified /etc/make.conf and added CFLAGS= -pipe 3559.2u 807.2s 1:28:00.05 82.6% 1608+1286k 56499+174033io 2516pf+0w Kent > > best; > > gjvc > > -- > George Cox <[EMAIL PROTECTED]> > Tel +44 1235 544 127 > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
Matthew Dillon wrote: > > :The bugs were fixed in 4.0? What I saw was far too much cpu going to > :setiathome on 3.4. Seti hardly ran on 4.0. I don't have quantities > :because I have only noticed the really large increase in cpu time > :required to build 4.0. The wall clock time on a buildworld hardly > :changed (55-60 minutes) whether I ran seti or not on 3.4. I can watch > :the wall clock time on some of my future builds and see how they are > > I don't know what your setup is, Kent, but when I do a buildworld > my system is 95% cpu bound, with virtual no idle time at all. It's > all going to the buildworld. On both 3.x and 4.x. It is on 4.x but it wasn't on 3.4. At least, seti was taking time that it shouldn't have been getting. > > Try mounting /usr/obj with softupdates turned on, and if your /tmp > is not a softupdates partition then make sure you are building with > -pipe in /etc/make.conf: > > (For 3.x) > > CFLAGS= -O2 -pipe > > (For 4.x) > > CFLAGS= -Os -pipe I am trying this right now. I thought that optimizing this way was dangerous for the kernel. The problem for the new people is what works and when. You have to understand that Murphy sits on my shoulder. If there are 2+ bugs in a product, I will eventually end up seeing one of them :). I have been going to turn on softupdates but haven't got there yet. I want to link /usr/obj to the scsi drive first. Then, I think I will try softupdates. Try the worst combo's first and then add features but write the times down when you try the different arrangements. If 50% of my Cray throughput was write behind caching, then softupdates could be an equal share on FreeBSD. A benchmark that ran in four hours versus eight hours is a big change. I don't have a good batch system but the speed of my FreeBSD systems have a lot going for them clock wise. The Cray had 16MW (128MB) of memory and that is pretty much a starter system now days. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
Matthew Dillon wrote: > > :You are right but that is because I haven't started keeping record on > :4.0-Stable and we were comparing apples and oranges. A buildworld of > :3.4-Stable required around 2000u seconds using gcc-2.8.2 on my system. > :Setiathome, which is running at a nice of 19, still consumed 90% of > :the cpu. A buildworld on 4.0-Stable required 3500u seconds using > :gcc-2.95.2 and setiathome didn't accrue any appreciable cpu time > :during the build. There were definitely some changes there :). > : > :Kent > : > :-- > :Kent Stewart > :Richland, WA > > Both 3.4 and 4.0 buildworlds are cpu-bound. If you are trying to test > buildworlds, then don't run setiathome (or anything else) while doing > the test... it will skew the results of your tests due to differences > between the 3.4 and 4.x schedulers (specifically, various scheduler > bugs were fixed in 4.x that effect niced cpu-bound background programs > such as setiathome, giving them way, way too much cpu). The bugs were fixed in 4.0? What I saw was far too much cpu going to setiathome on 3.4. Seti hardly ran on 4.0. I don't have quantities because I have only noticed the really large increase in cpu time required to build 4.0. The wall clock time on a buildworld hardly changed (55-60 minutes) whether I ran seti or not on 3.4. I can watch the wall clock time on some of my future builds and see how they are skewed by stopping seti before I being the buildworld. I just haven't got 4.0 to the capability I had with with 3.4 before I tried to upgrade to 4.0 and it died in the middle of creating the installkernel. The rest of the system was pretty much broken at that point and I used the opportunity to restructure everything. It has been a good check on some of the ports because I found a few that assumed you have things like Bison, automake, and autoconf installed and I didn't. > > It is simply impossible to fairly measure I/O performance in the > presence of unrelated background-running programs, especially under 3.x. > And even though 4.x does a better job of it, it will still skew the > results. I was looking at this as more of a real world setup simulation. Seti is almost pure cpu and the buildworld used everything else. I ran the build world from an x-term and from the command line. That didn't seem to matter much. The system also provided my dialup and nat'ing for my internal network. Seti was run from a script that was started from an login before I did my startx. It would chug along from one network problem at Berkeley until the next one with out any intervention on my part. The system was on a UPS and didn't go down on the occasional 1 or 2 second long power outages. Between the two codes, they mimic most of the types of calculations I've been associated with for many years. I have people that are using Windows 9x machines and I think they would be better off with something like FreeBSD. The programs were developed in unix environment. A lot of users are using Linux. Some are using PVM to combine systems into a single parallel virtual calculation. Lehey Fortran-90(77) running on Win9x with their protected mode interface setup has to be a terrible choice. The problem is proving it and providing an alternative :). A couple would run better on a scsi because of the queued read/write I/O that you identified. You can say anything is a POS but people won't listen unless you can show them a better way. I'm retired and no longer have a contract manager to answer to and can experiment. Cheers, Kent > > -Matt -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
Matthew Dillon wrote: > > :I tested build worlds where I created my /usr/obj on one controller > :and left the /usr/src on a different controller. The buildworlds are > :pretty much I/O bound. They ran faster but not that much faster when > > Buildworlds are NOT I/O bound. They are *CPU* bound. This becomes > glaringly obvious when you mount /usr/src and /usr/obj over NFS > and look at the network traffic. > > You are right but that is because I haven't started keeping record on 4.0-Stable and we were comparing apples and oranges. A buildworld of 3.4-Stable required around 2000u seconds using gcc-2.8.2 on my system. Setiathome, which is running at a nice of 19, still consumed 90% of the cpu. A buildworld on 4.0-Stable required 3500u seconds using gcc-2.95.2 and setiathome didn't accrue any appreciable cpu time during the build. There were definitely some changes there :). Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
Gérard Roudier wrote: > > On Sat, 22 Apr 2000, Matthew Dillon wrote: > > > :> :extend (using truncate) and then mmap() the destination file, then > > :> :read() directly into the mmap()'d portion. > > :> : > > :> :I'd like to see what numbers you get. :) > > : > > :> read + write is a better way to do it. It is still possible to > > :> double buffer. In this case simply create a small anonymous shared > > :> mmap that fits in the L2 cache (like 128K), setup a pipe, fork, and > > :> have one process read() from the source while the other write()s to the > > :> destination. The added overhead is actually less then 'one buffer copy' > > :> worth if the added buffering fits in the L1 or L2 cache. > > : > > :It seems silly to implement something as trivial and straightforward as > > :copying a file in userland. The process designated to copy a file just > > :sits in a tight loop invoking the read()/write() syscalls > > :repeatedly. Since this operation is already system bound and very simple, > > :what's the arguement against absorbing it into the kernel? > > : > > :-MB > > > > I don't think anyone has suggested that it be absorbed into the kernel. > > We are talking about userland code here. > > > > The argument for double-buffering is a simple one - it allows the > > process read()ing from the source file to block without stalling the > > process write()ing to the destination file. > > > > I think the reality, though, is that at least insofar as copying a > > single large file the source is going to be relatively contiguous on > > the disk and thus will tend not to block. More specifically, the > > disk itself is probably the bottleneck. Disk writes tend to be > > somewhat slower then disk reads and the seeking alone (between source > > file and destination file), even when using a large block size, > > will reduce performance drastically verses simply reading or writing > > a single file linearly. Double buffering may help a disk-to-disk > > file copy, but I doubt it will help a disk-to-same-disk file copy. > > Speaking about requential file read, the asynchronous read-ahead mechanism > in the kernel already has the same effect as a double-buffering. In > addition, real disks do prefetch data based on physical position and this > also help when the file is not too fragmented. When I did my buildworld's on different IDE controllers, my flags were 0xa0ffa0ff on both controllers, which pretty much used everything the IDE drive could provide because of 32-bit transfers, UDMA-33, and 16 sector read aheads. Kent > > However, some bottleneck may exist when reads and writes transverse the > same controller or involve a single device. This problem _is_ addressed by > SCSI. The disconnection feature allows the BUS bandwidth not to be wasted > and tagged command queuing allows to provide devices with several IO > requests simultaneously. > It is also addressed by ATA using the same mechanisms, but I doubt > disconnections and tagged commands will ever be reliable enough to be > actually usable on this interface given that it targets personnal > computers that donnot require fast multi-streamed disk IOs. > > This let me think that: > - User-space double-bufferred cp will not help at all given a decent > IO sub-system and decent devices. > - It will also not help when the controller and/or the device (as legacy > IDE) just act as an IO bottleneck for cp (double bottleneck in case of > reading and writing to the same disk ;-) ). > > By experience, connecting a real hard disk like a Cheetah to a real SCSI > controller (LVD preferred) and using a real O/S help a lot better. ;-) > > Gérard. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
Matthew Dillon wrote: > > : > : > :> :extend (using truncate) and then mmap() the destination file, then > :> :read() directly into the mmap()'d portion. > :> : > :> :I'd like to see what numbers you get. :) > : > :> read + write is a better way to do it. It is still possible to > :> double buffer. In this case simply create a small anonymous shared > :> mmap that fits in the L2 cache (like 128K), setup a pipe, fork, and > :> have one process read() from the source while the other write()s to the > :> destination. The added overhead is actually less then 'one buffer copy' > :> worth if the added buffering fits in the L1 or L2 cache. > : > :It seems silly to implement something as trivial and straightforward as > :copying a file in userland. The process designated to copy a file just > :sits in a tight loop invoking the read()/write() syscalls > :repeatedly. Since this operation is already system bound and very simple, > :what's the arguement against absorbing it into the kernel? > : > :-MB > > I don't think anyone has suggested that it be absorbed into the kernel. > We are talking about userland code here. > > The argument for double-buffering is a simple one - it allows the > process read()ing from the source file to block without stalling the > process write()ing to the destination file. > > I think the reality, though, is that at least insofar as copying a > single large file the source is going to be relatively contiguous on > the disk and thus will tend not to block. More specifically, the > disk itself is probably the bottleneck. Disk writes tend to be > somewhat slower then disk reads and the seeking alone (between source > file and destination file), even when using a large block size, > will reduce performance drastically verses simply reading or writing > a single file linearly. Double buffering may help a disk-to-disk > file copy, but I doubt it will help a disk-to-same-disk file copy. I made some tests on my FreeBSD machine. In the past, double buffering only helps if you have concurrent I/O capability. You only have that if you have dual access to each I/O device (HD) via different data channels. We don't have that capability on PC's. The typical drives that we purchase have only one data path, i.e., the ribbon cable. I tested build worlds where I created my /usr/obj on one controller and left the /usr/src on a different controller. The buildworlds are pretty much I/O bound. They ran faster but not that much faster when different controllers were used. I have an IBM uw scsi on that system and I haven't tried to do a build world using it for one of the file systems. The test I like is iozone because it uses everything I normally use. I tell it to test using 160MB, which is 20+ times the available cache from top. Rawio doesn't mean anything when everything is cached. The tests showed the scsi system was slower than the UDMA-33 drives in everything except for randon I/O and then it was much faster. It could mean that the buffering logic on the scsi HD and scsi controller were smart enough that everything was in cache. It is too easy to split your obj and src filesystem on to different controllers and test if cached I/O between controllers helps on your system. I think that even cp is cached on a normal system and that means you already have "n" buffers available for reading and "N" buffers available for writing. Trying to make cp more complicated won't help because the copy of a file will still be twice the time to just write the file + the number of times that you had to wait for full revolutions of the disk before you could do your next scheduled read or write I/O operation. Kent > > -Matt > Matthew Dillon > <[EMAIL PROTECTED]> > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Temperature
David Kelly wrote: > > Peter Wemm writes: > > Ted Sikora wrote: > > > > > During the night periodically my temp warning has been going off. > > > I have it set to 118F. This happens only under FreeBSD. Linux continues > > > to run cool at the old temperatures. Apparantly some code change has > > > caused this. Does anyone know exactly where I should look? > > > > The main difference is that Linux halts the cpu in the idle loop, we don't. > > As a result the cpu is in a tight spin waiting for a process to become > > scheduleable. I have some patches half-done that I've been working on for > > 4.0 that should probably be able to be adapted to the 3.x series. > > I'll let others debate whether or not FreeBSD halts the CPU when idle > or not, or whether this has changed recently. > > OTOH Ted has a problem that is being ignored: that his CPU/Heatsink/Fan > combination is apparently not up to a 100% duty cycle. DOS would cook > it. As would most games. Or several "make buildworlds" in a row. Antec and Startech have some dual fans for P-II's. The old P-II style is hard to find but the K-7 Athalon apparently uses the same style of fan. One of the vendors has a monster fan for a P-III. I run setiathome in the background on all of my computers, which keeps the systems at 100% all of the time. I had a new 250W PS go out in three days. The fans that come on P-II OEM's is not that great. It also sounds like he isn't getting enough outside air. You can't cool if the inside air is hot. Kent > > -- > David Kelly N4HHE, [EMAIL PROTECTED] > = > The human mind ordinarily operates at only ten percent of its > capacity -- the rest is overhead for the operating system. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Intel Merced FreeBSD???
Mark Ovens wrote:
>
> On Fri, Aug 27, 1999 at 06:29:21PM -0700, Jordan K. Hubbard wrote:
> > > marder-1:/usr/marko{57}% ./a.out
> > > short == 2
> > > int == 4
> > > long == 4
> > > long long == 8
> > > marder-1:/usr/marko{57}%
> >
> > But on the Alpha:
> >
> > j...@beast-> ./foo
> > short == 2
> > int == 4
> > long == 8
> > long long == 8
> >
>
> Which is fair enough, given that Alpha is 64-bit. The original post
> implied that existing (32-bit) compilers had 64-bit longs (or a
> mode for 64-bit longs). man cc shows that this (and 64-bit ints)
> is only for MIPS systems and adds "These options don't work at
> present."
We went from a Cray to using an Alpha and there were several things
that Dec FORTRAN did. The most prominent besides the 64-bit floating
point operations was that you could mask (and, or, xor, and etc.)
64-bit integer values. This was something that was missing in 64-bit
longs on HP.
Kent
>
> > - Jordan
> >
>
> --
> STATE-OF-THE-ART: Any computer you can't afford.
> OBSOLETE: Any computer you own.
>
> FreeBSD - The Power To Serve http://www.freebsd.org
> My Webpage http://ukug.uk.freebsd.org/~mark/
> mailto:m...@ukug.uk.freebsd.org http://www.radan.com
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-questions" in the body of the message
--
Kent Stewart
Richland, WA
mailto:kstew...@3-cities.com
http://www.3-cities.com/~kstewart/index.html
SETI (Search for Extraterrestrial Intelligence) @ Home
http://setiathome.ssl.berkeley.edu/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Re: Intel Merced FreeBSD???
Mark Ovens wrote:
>
> On Fri, Aug 27, 1999 at 06:29:21PM -0700, Jordan K. Hubbard wrote:
> > > marder-1:/usr/marko{57}% ./a.out
> > > short == 2
> > > int == 4
> > > long == 4
> > > long long == 8
> > > marder-1:/usr/marko{57}%
> >
> > But on the Alpha:
> >
> > jkh@beast-> ./foo
> > short == 2
> > int == 4
> > long == 8
> > long long == 8
> >
>
> Which is fair enough, given that Alpha is 64-bit. The original post
> implied that existing (32-bit) compilers had 64-bit longs (or a
> mode for 64-bit longs). man cc shows that this (and 64-bit ints)
> is only for MIPS systems and adds "These options don't work at
> present."
We went from a Cray to using an Alpha and there were several things
that Dec FORTRAN did. The most prominent besides the 64-bit floating
point operations was that you could mask (and, or, xor, and etc.)
64-bit integer values. This was something that was missing in 64-bit
longs on HP.
Kent
>
> > - Jordan
> >
>
> --
> STATE-OF-THE-ART: Any computer you can't afford.
> OBSOLETE: Any computer you own.
>
> FreeBSD - The Power To Serve http://www.freebsd.org
> My Webpage http://ukug.uk.freebsd.org/~mark/
> mailto:[EMAIL PROTECTED] http://www.radan.com
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
--
Kent Stewart
Richland, WA
mailto:[EMAIL PROTECTED]
http://www.3-cities.com/~kstewart/index.html
SETI (Search for Extraterrestrial Intelligence) @ Home
http://setiathome.ssl.berkeley.edu/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
