Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash
Mark Felder wrote: On Thu, 29 Mar 2012 12:24:30 -0500, je...@seibercom.net wrote: I just started reading this tread, but I am wondering if I missed something here. What does this have to do with Windows 7? I emailed him off-list but I'm guessing he thought this was on VMWare Workstation or another product that would virtualize FreeBSD on top of Windows as the host OS. ___ Correct...My bad. jim ___ 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: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash
This sounds just like a race condition that happens under Windows 7 on this laptop. The race condition, as far as I can tell involves heavy disk access and heavy network access, and usually leaves the drive light on, while all activity monitors (alldisk, allcpu, allnetwork) are still active, although on this laptop disk takes priority, and network slows to a crawl. occasionally, the mouse will stop working, along with everything else, but usually not. keyboard is lower priority, and doesn't do anything. You might want to check with mickeysoft, this might just be their problem. This sounds so freaking similar to the issue I get, and I think it's a race condition (shared interrupts??). This laptop is a Compaq Presario C300 series, with the 945GM chipset and a T7600 Core2 Duo CPU, with 3G of RAM. Mark Felder wrote: Alright guys, I'm at the end of my rope here. For those that haven't seen my previous emails here's the (not so) quick breakdown: Overview: FreeBSD ?? - 7.4 never crash FreeBSD 8.0 - 8.2 crashes FreeBSD 8-STABLE, 8.3, and 9.0 are untested (Sorry, not possible in our production at this time, and we were hoping we could base some stuff on 8.3 for long term stability...) ESXi: Confirmed ESXi 4.0 - 5.0 has this problem. Haven't tested on others. History: Over the course of the last 2 years we've been banging our heads on the wall. VMWare is done debugging this. They claim it's not a VMWare issue. They can't identify what the heck happens. We had a glimmer of hope with ESXi 5.0 fixing it because we never saw any crashes in the handful of deployments, but our dreams were crushed today -- two days before an outage to begin migration to ESXi 5.0 -- when a customer's ESXi 5.0 server and FreeBSD 8.2 guest crashed. Crash Details: The keyboard/mouse usually stops responding for input on the console; normally we can't type in a username or password. However, we can switch VTs. If there's a shell on the console and we can type, we can only run things in memory. Any time we try to access the disk it will hang indefinitely. The server still has network access. We can ping it without issue. SSH of course kicks you out because it can't do any I/O. If we were to serve a lightweight http server off a memory backed filesystem I'm confident it would run just fine as long as it wasn't logging or anything. On ESXi you see that there is a CPU spike of 100% that goes on indefinitely. No idea what the FreeBSD OS itself thinks it is doing because we can't run top during the crash. This crash can affect a server and happen multiple times a week. It can also not show up for 180 days or more. But it does happen. The server can be 100% idle and crash. We have servers that do more I/O than the ones that crash could ever attempt to do and these don't crash at all. Completely inexplicable. Things we've looked into: Nothing about the installed software matters. We've tried cross referencing the crashed servers by the programs they run but the base OS is the only common denominator due to the wide variety of servers it has affected. Storage doesn't matter. We've tried different iSCSI SANs, we've tried different switches, we've tried local datastores on the ESXi servers themselves. HP servers, Dell servers -- doesn't seem to matter either. (All with latest firmwares, BIOSes, etc) VMWare gave us a ton of debugging tasks, and we've given them gigabytes of debugging info and data; they can't find anything. VMWare tools -- with, without, using open-vm-tools makes no difference. I think we've done a fair job ruling out VMWare. I think we've finally found enough data that this is definitely something in the FreeBSD world. I'm going to begin prepping some of the known crashy servers with more debugging. Any suggestions on what I should build the kernel with? They never do a proper panic, but I definitely want to at least *try* to get into the debugger the next time it crashes. And when it crashes, what the heck should I be running? I've never played with the KDB before... Thank you for any suggestions and help you can give me ___ 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 ___ 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: OS support for fault tolerance
Brandon Falk wrote: On 2/14/2012 12:05 PM, Jason Hellenthal wrote: On Tue, Feb 14, 2012 at 08:57:10AM -0800, Julian Elischer wrote: On 2/14/12 6:23 AM, Maninya M wrote: For multicore desktop computers, suppose one of the cores fails, the FreeBSD OS crashes. My question is about how I can make the OS tolerate this hardware fault. The strategy is to checkpoint the state of each core at specific intervals of time in main memory. Once a core fails, its previous state is retrieved from the main memory, and the processes that were running on it are rescheduled on the remaining cores. I read that the OS tolerates faults in large servers. I need to make it do this for a Desktop OS. I assume I would have to change the scheduler program. I am using FreeBSD 9.0 on an Intel core i5 quad core machine. How do I go about doing this? What exactly do I need to save for the state of the core? What else do I need to know? I have absolutely no experience with kernel programming or with FreeBSD. Any pointers to good sources about modifying the source-code of FreeBSD would be greatly appreciated. This question has always intrigued me, because I'm always amazed that people actually try. From my viewpoint, There's really not much you can do if the core that is currently holding the scheduler lock fails. And what do you mean by 'fails? do you run constant diagnostics? how do you tell when it is failed? It'd be hard to detect that 'multiply' has suddenly started giving bad results now and then. if it just stops then you might be able to have a watchdog that notices, but what do you do when it was half way through rearranging a list of items? First, you have to find out that it held the lock for the module and then you have to find out what it had done and clean up the mess. This requires rewriting many many parts of the kernel to remove 'transient inconsistent states. and even then, what do you do if it was half way through manipulating some hardware.. and when you've figured that all out, how do you cope with the mess it made because it was dying? Say for example it had started calculating bad memory offsets before writing out some stuff and written data out over random memory? but I'm interested in any answers people may have How about core redundancy ? effectively this would reduce the amount of available cores in half in you spread a process to run on two cores at the same time but with an option to adjust this per process etc... I don't see it as unfeasable. The overhead for all of the error checking and redundancy makes this idea pretty impractical. You'd have to have 2 cores to do the exact same thing, then some 'master' core that makes sure they're doing the right stuff, and if you really want to think about it... what if the core monitoring the cores fails... there's a threshold of when redundancy gets pointless. Perhaps I'm missing out on something, but you can't check the checker (without infinite redundancy). Honestly, if you're worried about a core failing, please take your server cluster out of the 1000 deg C forge. -Brandon ___ 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 Don't forget that cache would have to be redundant too. The redundant cores must not share an on-die cache. Oh, and the real biggie. What about the chipset and busses??? Those would NOT be redundant. ___ 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: OS support for fault tolerance
Mirrored SMP? Even NonStops require a supervisory CPU subsystem to manage what is working or not. SMP itself would have to be totally rethought. My suggestion is to study the examples of NonStop and Guardian-90. Julian Elischer wrote: On 2/14/12 6:23 AM, Maninya M wrote: For multicore desktop computers, suppose one of the cores fails, the FreeBSD OS crashes. My question is about how I can make the OS tolerate this hardware fault. The strategy is to checkpoint the state of each core at specific intervals of time in main memory. Once a core fails, its previous state is retrieved from the main memory, and the processes that were running on it are rescheduled on the remaining cores. I read that the OS tolerates faults in large servers. I need to make it do this for a Desktop OS. I assume I would have to change the scheduler program. I am using FreeBSD 9.0 on an Intel core i5 quad core machine. How do I go about doing this? What exactly do I need to save for the state of the core? What else do I need to know? I have absolutely no experience with kernel programming or with FreeBSD. Any pointers to good sources about modifying the source-code of FreeBSD would be greatly appreciated. This question has always intrigued me, because I'm always amazed that people actually try. From my viewpoint, There's really not much you can do if the core that is currently holding the scheduler lock fails. And what do you mean by 'fails? do you run constant diagnostics? how do you tell when it is failed? It'd be hard to detect that 'multiply' has suddenly started giving bad results now and then. if it just stops then you might be able to have a watchdog that notices, but what do you do when it was half way through rearranging a list of items? First, you have to find out that it held the lock for the module and then you have to find out what it had done and clean up the mess. This requires rewriting many many parts of the kernel to remove 'transient inconsistent states. and even then, what do you do if it was half way through manipulating some hardware.. and when you've figured that all out, how do you cope with the mess it made because it was dying? Say for example it had started calculating bad memory offsets before writing out some stuff and written data out over random memory? but I'm interested in any answers people may have ___ 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 ___ 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 . ___ 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
kvm_open errors on /proc/*/mem in top
i'm not sure which list this belongs to, so i'm posting to -hackers and -stable. i've noticed for a while now that during heavy activity (for instance buildworld), that top will get these kvm_read errors when reading proc mem entries. i have included a screenshot of what happens during such events... last pid: 92024; load averages: 4.79, 4.58, 4.10 up 0+00:49:07 15:30:53 225 processes: 10 running, 197 sleeping, 18 waiting CPU: 90.6% user, 0.0% nice, 9.4% system, 0.0% interrupt, 0.0% idle Mem: 493M Active, 1337M Inact, 604M Wired, 632K Cache, 315M Buf, 524M Free Swap: 4097M Total, 4097M Free kvm_open: cannot open /proc/86755/mem PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 91943 root 1 970 39536K 33620K RUN 1 0:01 7.37% [cc1plus] 2859 jbryant 1 480 406M 72332K select 0 3:10 5.96% kwin -session 1028b2382461f50001270420560001955_13 2747 root 1 460 419M 370M select 0 1:43 4.39% /usr/local/bin/X :0 -nolisten tcp -auth /var/run/xauth/A:0 1464 root 1 440 8068K 1384K select 0 0:03 0.39% /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.u 11219 jbryant 7 440 299M 109M select 1 0:17 0.29% /usr/local/lib/thunderbird/thunderbird-bin 2865 jbryant 1 450 453M 86140K select 0 0:21 0.20% kdeinit4: kdeinit4: plasma-desktop (kdeinit4) 2882 jbryant 1 440 391M 60996K select 0 0:17 0.10% kdeinit4: kdeinit4: kmix -session 102511e52251c60001304471 92001 root 1 970 23452K 22256K CPU11 0:00 0.00% [cc1] 92017 root 1 960 16172K 13440K RUN 0 0:00 0.00% [cc1] and such as this: last pid: 19348; load averages: 1.03, 1.93, 2.84 up 1+04:42:07 15:31:37 201 processes: 4 running, 178 sleeping, 19 waiting CPU: 47.4% user, 0.0% nice, 3.4% system, 0.0% interrupt, 49.3% idle Mem: 318M Active, 2400M Inact, 679M Wired, 1948K Cache, 407M Buf, 428M Free Swap: 8192M Total, 6488K Used, 8186M Free kvm_open: cannot open /proc/1141/memm kvm_open: cannot open /proc/92606/memRES STATE C TIME WCPU COMMAND 10 root 2 171 ki31 0K32K RUN 0 55.9H 103.81% [idle] 19344 root 1 960 17188K 14300K CPU10 0:00 0.00% [cc1] 19341 root 1 760 3204K 1068K select 1 0:00 0.00% make all DIRPRFX=fdc/ 19342 root 1 760 8340K 1848K wait1 0:00 0.00% sh -ev 19343 root 1 760 3204K 596K wait0 0:00 0.00% [cc] 19345 root 1 760 3204K 1292K piperd 0 0:00 0.00% /usr/obj/usr/src/tmp/usr/bin/as -Qy -o fdc.o the current fix for this is to [CTRL]-L. i assume that what is happening is that top just loosing track of what's running, and the procs are dead by the time it tries to read them, or that the proc ends during top reading. is there any way to fix this? it's annoying as f#k. ps: running 8-STABLE. ___ 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: How to disallow logout
Atom Smasher wrote: On Fri, 10 Sep 2010, Ivan Voras wrote: 1) power outage of the server 2) power outage on the client 3) network problems (ssh or TCP connection drop) 4) administrative command (e.g. root executes killall $shell) ? I don't think there is a way to protect from all of those, so any effort in protecting from only part of the problem looks useless. you forgot cosmic rays, nuclear war and zombie apocalypse, among other failure modes. *NOTHING* is capable of protecting against everything; a good solution will most always have pitfalls; as a sysadmin/engineer/manager one has to either accept the pitfalls or find a more acceptable solution, which usually means different pitfalls. that doesn't mean a given solution is useless. Bah. since you mentioned .logout, i'm assuming you are using tcsh. what i would suggest is that you create an md and check out the files into that. this solves the power fail issue completely, also, it solves the main issue. have the logout script simply umount and mdconfig -d the ramdisk. also, this way, security is enhanced because no fragments, even of deleted files, are left on disk after logout. the only question i have is if a bzero is done before returning the ram to the os, if not, simply dd if=/dev/zero of=/dev/md0 bs=whatever to be sure that the ram formeerly contained in the ramdisk isn't readable by later procs. have you considered trustedbsd? it should perform the bzero by default. TBSD MAC is in fbsd these days to control access to the mountpoint, but that might not help if you are worried about a lifted disk, MAC don't mean shit without physical security, the kind involved in the environments for which it was commissioned. ___ 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: disassembler
umm, dude you writing a boot sector virus or something? funny though http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/boot-boot0.html given your skill and goals are questionable, you can find it in the source tree yourself. Aryeh Friedman wrote: On Thu, Aug 26, 2010 at 11:36 PM, Aryeh Friedman aryeh.fried...@gmail.com wrote: On Thu, Aug 26, 2010 at 10:46 PM, Dirk Engling erdge...@erdgeist.org wrote: On 27.08.10 04:17, Aryeh Friedman wrote: Is there a disassembler in the base system if not what is a good option from ports? Try objdump -d, erdgeist flosoft# objdump -d /dev/da0 objdump: Warning: '/dev/da0' is not an ordinary file ___ 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 ___ 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: disassembler
ah, ok.
if it's a flash drive, the data may be toast. depends on how many dead
cells there are.
best of luck to you.
Aryeh Friedman wrote:
No the issue is a drive that has roughly 10 years of work on it died
and I was asked to see if it is readable/reviable... I already know
the format of the MBR but I need to also read the code to see if
something is wakey (I have written MBR's {with inline assemble in GCC)
for an OS I am working on but never disambled one)
On Fri, Aug 27, 2010 at 2:50 AM, Jim Bryant kc5vdj.free...@gmail.com wrote:
umm, dude
you writing a boot sector virus or something?
funny though
http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/boot-boot0.html
given your skill and goals are questionable, you can find it in the source
tree yourself.
Aryeh Friedman wrote:
On Thu, Aug 26, 2010 at 11:36 PM, Aryeh Friedman
aryeh.fried...@gmail.com wrote:
On Thu, Aug 26, 2010 at 10:46 PM, Dirk Engling erdge...@erdgeist.org
wrote:
On 27.08.10 04:17, Aryeh Friedman wrote:
Is there a disassembler in the base system if not what is a good
option from ports?
Try objdump -d,
erdgeist
flosoft# objdump -d /dev/da0
objdump: Warning: '/dev/da0' is not an ordinary file
___
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
___
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
Problem: fpa(4) on sparc64 6.1-RELEASE
I am getting a panic with a GENERIC with all non-available hardware drivers stripped out with device fddi and device fpa in the config. The only things I added to GENERIC after stripping out the unneeded things was the fddi, the sound, and the openfirmware. The system boots fine with the fddi stuff commented out of the config. Any suggestions? Is anyone working on this? Console log follows: screen not found. Can't open input device. Keyboard not present. Using ttya for input and output. SPARCengine(tm)Ultra(tm) AXi (UltraSPARC-IIi 300MHz), No Keyboard OpenBoot 3.10.4 SME, 256 MB memory installed, Serial #10425242. Ethernet address 8:0:20:9f:13:9a, Host ID: 809f139a. Initializing Memory ok boot Boot device: disk:a File and args: FreeBSD/sparc64 boot block Boot path: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:a Boot loader: /boot/loader Consoles: Open Firmware console FreeBSD/sparc64 bootstrap loader, Revision 1.0 ([EMAIL PROTECTED], Sun May 7 07:03:17 UTC 2006) bootpath=/[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:a Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0x36b508+0x52e58 syms=[0x8+0x59a60+0x8+0x4af83] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 9 seconds... Booting [/boot/kernel/kernel] in 8 seconds... Booting [/boot/kernel/kernel]... nothing to autoload yet. jumping to kernel entry at 0xc0058000. Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE #0: Tue Jun 20 02:01:14 CDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/REN Timecounter tick frequency 38484 Hz quality 1000 real memory = 268435456 (256 MB) avail memory = 241123328 (229 MB) cpu0: Sun Microsystems UltraSparc-IIi Processor (300.01 MHz CPU) nexus0: Open Firmware Nexus device pcib0: U2P UPA-PCI bridge on nexus0 pcib0: Sabre, impl 0, version 0, ign 0x7c0, bus A pcib0: [FAST] pcib0: [FAST] pcib0: [GIANT-LOCKED] pcib0: [GIANT-LOCKED] pcib0 dvma: DVMA map: 0xc000 to 0xc3ff pci0: OFW PCI bus on pcib0 pcib1: APB PCI-PCI bridge at device 1.1 on pci0 pci1: OFW PCI bus on pcib1 ebus0: PCI-EBus2 bridge mem 0xf000-0xf0ff,0xf100-0xf17f at device 1.0 on pci1 auxio0: Sun Auxiliary I/O addr 0x1400726000-0x1400726003,0x1400728000-0x1400728003,0x140072a000-0x140072a003,0x140072c000-0x140072c003,0x140072f000-0x140072f003 on ebus0 ebus0: power addr 0x1400724000-0x1400724003 irq 37 (no driver attached) ebus0: SUNW,pll addr 0x1400504000-0x1400504002 (no driver attached) puc0: Siemens SAB 82532 dual channel SCC addr 0x140040-0x140040007f irq 43 on ebus0 uart0: SAB 82532 v3.2, channel A on puc0 uart0: CTS oflow uart0: console (38400,n,8,1) uart1: SAB 82532 v3.2, channel B on puc0 uart1: CTS oflow uart2: 16550 or compatible addr 0x14003803f8-0x14003803ff irq 41 on ebus0 uart2: keyboard (1200,n,8,1) uart2: keyboard not present uart3: 16550 or compatible addr 0x14003602f8-0x14003602ff irq 42 on ebus0 ebus0: ecpp addr 0x1400340278-0x1400340287,0x140030015c-0x140030015d,0x140070-0x14007f irq 34 (no driver attached) ebus0: fdthree addr 0x14003203f0-0x14003203f7,0x1400706000-0x140070600f,0x140072-0x1400720003 irq 39 (no driver attached) eeprom0: EEPROM/clock addr 0x14-0x141fff on ebus0 eeprom0: model mk48t59 eeprom0: hostid 809f139a ebus0: flashprom addr 0x10-0x1f (no driver attached) ebus0: beeper addr 0x1400722000-0x1400722003 (no driver attached) ebus0: SUNW,rasctrl addr 0x140060-0x140063 irq 40,37 (no driver attached) hme0: Sun HME 10/100 Ethernet mem 0x40008000-0x4000 at device 1.1 on pci1 miibus0: MII bus on hme0 nsphy0: DP83840 10/100 media interface on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto hme0: Ethernet address: 08:00:20:9f:13:9a pcm0: AudioPCI ES1373-B port 0x800400-0x80043f at device 4.0 on pci1 pcm0: TriTech TR28023 AC97 Codec pcm0: Playback: DAC2 / Record: ADC pcib2: APB PCI-PCI bridge at device 1.0 on pci0 pci2: OFW PCI bus on pcib2 sym0: 875 port 0x400-0x4ff mem 0x1000-0x10ff,0x2000-0x2fff at device 1.0 on pci2 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym0: [GIANT-LOCKED] sym1: 875 port 0x800-0x8ff mem 0x3000-0x30ff,0x4000-0x4fff at device 1.1 on pci2 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: [GIANT-LOCKED] fpa0: Digital DEFPA PCI FDDI Controller port 0xc00-0xc7f mem 0x5000-0x507f,0x1-0x1 at device 2.0 on pci2 panic: trap: fast data access mmu miss Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Resetting ... ___ freebsd-hackers@freebsd.org mailing list
Re: tar and nodump flag
fergus wrote: - It doesn't support incremental backups. That isn't a problem in itself, but it's a feature our GNU tar currently has and people probably don't want to lose. I dunno... The entire incremental thing in tar is dependant on NOT using compression, which IMHO makes it pretty useless, especially if you prefer the much tighter software compression you get from gzip. 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, 1995 _ 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
Re: Unix Philosophers Please!
Nicpon, John wrote:
Please specifically define where data goes that is sent to /dev/null
Without actually looking at the code, the generic definition of /dev/null goes
something to the effect of:
open /dev/null
while(1)
{
select on /dev/null
read byte from /dev/null
}
So basically, it just reads what is there, but does absolutely nothing with it.
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, 1995
_
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
Re: Unix Philosophers Please!
It's similar to the space/time wormhole that appears in your clothes dryer, and randomly sucks out only one sock out of every pair into a parallel universe. Somewhere, there is a universe made up of nothing but odd socks, where they each lead a very happy odd-sockish singular life. I assume that input to /dev/null goes to a parallel universe consisting entirely of unwanted, wayward data. Nicpon, John wrote: ethersWhere does data go when it dies?/ethers -Original Message- From: Brian Reichert [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 3:08 PM To: Nicpon, John Cc: [EMAIL PROTECTED] Subject: Re: Unix Philosophers Please! On Wed, Oct 31, 2001 at 03:02:59PM -0600, Nicpon, John wrote: Please specifically define where data goes that is sent to /dev/null How 'specific' are you trying to get? /dev/null is a pseudo-device to which writes never fail. What question are you _really_ trying to ask? 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, 1995 _ 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
Re: Unix Philosophers Please!
Lamont Granquist wrote: On Wed, 31 Oct 2001, Stephen Montgomery-Smith wrote: Nicpon, John wrote: Please specifically define where data goes that is sent to /dev/null Answer 1. Data is not like energy. There is no conservation of data law. So the data simply disappears. Doesn't thermodynamics second law actually imply that data has to disappear and that with the heat death of the universe data will be at a minimum? For meaningful data to exist there needs to be order, while the 2nd law requires that systems evolve to less ordered states. The only uncertainty about this that I've got is that random systems can actually be very dense with data. Think about a compressed and encrypted file, which should be indistinguishable from /dev/random output. I guess the difference between those two is that there is only a single state which validly represents the comprssed and encrypted file. On the other hand there may be many states which represent the valid output of /dev/random (of course you only obtain one of these states). Since there are more states for /dev/random there is more entropy (and actually the compressed file having only one valid state would have minimal entropy). Did I get that right? My thermodynamics and info theory are a little rusty... Contribute to the Heat Death of the Universe! pipe everything to /dev/null! Nah, you have it all wrong... The data goes into a wormhole, much similar to the one that splits up your pairs of socks in the dryer, and the data wormhole simply sucks it into another universe. No need to worry about the collapse of our universe because of /dev/null BUT...Piping all that data to /dev/null MAY destroy the universe that keeps sending flying saucers to the houses of Art Bell fans in places like Lockjaw, Kentucky or Moose Turd, Montana... 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, 1995 _ 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
Re: FYI
No offense to you or your sales partners, but the way I see it, this means that tons of these will be available for a song on eBay soon, and will be in the hands of a lot of FreeBSD and Linux people [not all of which can afford top-of-the-line all of the time]. Doug Hass wrote: Ted, We're SBS' worldwide distributor. Others who resell them buy them from us or from one of our distributors. In any case, I can ASSURE you without a doubt that the WANic 400 series and the entire RISCom/N2 series are end of life as of the end of September. If you have questions, feel free to contact me at your convenience. Regards, Doug - Doug Hass ImageStream Internet Solutions [EMAIL PROTECTED] http://www.imagestream.com Office: 1-219-935-8484 Fax: 1-219-935-8488 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
Re: power supplies
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. 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
Re: No tools on 4.4-RELEASE ISO?
Jason Andresen wrote: Bruce A. Mah wrote: Note that the set of people affected is going to be people who can't do anonymous FTP, don't have bootable CDROMs, and *only* have the ISO images to work with. I don't know for sure, but I'd expect this set to be pretty small...if they don't have Internet access, how'd they get the ISO images? Probably more often that you'd expect. I know I had to install 4.4 in our lab (which blocks most net access) full of old machines. Fortunatly I have a 4.3 ISO sitting here that I just grabbed fdimage from and went on, but it did seem like a rather noticable oversight. What about the boot managers in that directory? Certainly people will want to dual boot their new FreeBSD installs? I've been in the same situation at a military site... Having the tools directory is very important. Many people also install freebsd on low-power old boxes, hell, we run our gateway/router/firewall at home on an old dell p-133 optiplex pizzabox we bought for $50, non-bootable cd-rom at that. We can just use dd to create the floppy, since it's running FreeBSD already for the task, but if someone had to start from scratch, the tool wouldn't be available. It may be a pain in the ass, especially after i've burned two copies of the distribution already, but i'll waste another handful of cd-r's to get something usable in every situation if new ISOs are made. 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
Re:
You may want to install FreeBSD-4.4, it was released yesterday, so this means that you are attempting to install something two versions behind. There are security issues with 4.2... damie odessa wrote: Hello, I am installing freebsd 4.2 and at the point of configuring the DHCP, it crashes with a Signal 11. Assist please. Or is there a site I could visit for troubleshooting Thanks Desperately yours damie 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
Re: OpenSSH + Kerberos 5 + PAM
David Terrell wrote: On Tue, Aug 28, 2001 at 04:56:06PM -0700, Gordon Tetlow wrote: I like Kerberos 5 and it's ability to use tickets so I don't have to type passwords whenever I login/su/need to authenticate myself. So it *really* annoys me that there is a pam_krb5 module that allows you to authenticate against a Kerberos 5 principal but it won't accept any tickets that I try to pass to it. I've done a bit of research on the matter and am told that it is a limitation of the PAM API. So be it. I suppose I can install kerberos' version of telnet/ftp/rsh/rlogin/etc, but again, I'm lazy (I *am* a system administrator). I was thinking that it would be nice to have Kerberos 5 authentication available in OpenSSH since that comes with the distribution and is even enabled by default. So, being lazy, I decided to trawl the net seeing if I could find anyone that has already done the work. Bingo! http://www.sxw.org.uk/computing/patches/openssh.html The author claims that it works with both KTH and MIT Kerberos 5 implementations (I've tried it on MIT and it works like a charm). I was wondering if there was any interest in integrating this, or if it is considered too large a patch. If there is interest, I would be willing to do the legwork to try and integrate it (although there is probably lots of cases to deal with). Patches have been circulated on openssh-unix-dev to apply kerb5 to the upstream OpenBSD source. In fact, krb5 support is in protocol 1 in the OpenBSD tree now, and I'd speculate that protocol 2 support will be in by the time 3.0 ships in December, since OpenBSD 3.0 will ship with Kerb5 (Heimdal) in the base. I'm not that current on krb5, but I do have to ask if the CERT issues have been resolved? My info on this is a little old, but I recall CERT advisories last year on serious vulnerabilities in krb5 at the time, it would be nice to know if they have been fixed. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: TCSH bug...
Charlie wrote: On Mon, Aug 27, 2001 at 05:41:21PM -0500, Steven Ames wrote: -current from saturday... And I've noticed it for a few months, just forgot about it until last night... Also, you failed to duplicate the test... Try answering NO when it asks... OK. Yep. I see the same results. I believe that when you say 'no' tcsh tries to get clever and remove that command from your command stack (history). The relevent code is in tc.func.c starting at line 1238. I don't see anything obviously silly... I'll do a bit of debugging though. Hrm... The code all looks good. The offending bit is in tc.func.c between lines 1245 and 1254 (one block). While removing items from a doubly linked list tmp-next gets set to an invalid pointer. The code itself looks good so the list getting passed to it must be flawed. That'll take some real effort to track down. Interesting datapoint though... tcsh from ports doesn't have this problem. Though I don't see any code changes between the two that could cause this, so it'd have to be in compile time options or 'config'. Yeah, I had looked at it, but couldn't really see anything major when I did... That was a few months ago when I first noticed the problem. Someone recently commented in the tcsh/csh thread concerning the fact that the FreeBSD tcsh is maintained separately from the port, and nobody is really sure who is responsible for keeping the FreeBSD version both in sync, AND, csh compatable when called with the executable name csh. Interesting to note that this has been fixed in the -port though, as opposed to the one that is installed by default. Steven Ames wrote: Under -CURRENT? virtual-voodoo# touch 0 1 2 3 4 5 6 7 8 9 virtual-voodoo# ls 0 1 2 3 4 5 6 7 8 9 virtual-voodoo# set rmstar virtual-voodoo# rm * Do you really want to delete all files? [n/y] y virtual-voodoo# ls virtual-voodoo# version tcsh 6.10.00 (Astron) 2000-11-19 (i386-intel-FreeBSD) options 8b,nls,dl,al,kan,sm,rh,color,dspm I'm not seeing this problem... This is from -CURRENT from about 2 hours ago. -Steve - Original Message - From: Jim Bryant [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, August 27, 2001 4:53 PM Subject: TCSH bug... Sorry if this doesn't go here... I don't know where else to put it... Please forward it to the correct people. With: set rmstar in your .cshrc, perform the following operations: -- 4:49:49pm wahoo(49): tcsh 4:49:51pm wahoo(1): mkdir bs 4:49:54pm wahoo(2): cd bs 4:49:56pm wahoo(3): touch 1 2 3 4 5 6 7 8 9 0 4:50:02pm wahoo(4): ls . .. 0 1 2 3 4 5 6 7 8 9 4:50:05pm wahoo(5): rm * Do you really want to delete all files? [n/y] n Bus error (core dumped) 4:50:10pm wahoo(50): cd bs 4:50:19pm wahoo(51): ls . .. 0 1 2 3 4 5 6 7 8 9 tcsh.core 4:50:20pm wahoo(52): --- Whazzup? This will always happen, iff you select to not rm * jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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 -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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 -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: Mounting FAT16 on USB connected Rio 600
Matthew Emmerton wrote: Hackers, The overwhelming lack of response on -questions suggests I might do better here. I though this would be an easy one. In short, I simply want to know what device to mount and what to do get that device configured. # usbdevs -v Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), Intel(0x), rev 0x0100 port 1 powered port 2 addr 2: self powered, config 1, Diamond Multimedia Digital Audio Player(0x5001), Diamond Multimedia(0x045a), rev 0x0100 /kernel: ugen0: at uhub0 port 2 (addr 2) disconnected /kernel: ugen0: detached /kernel: ugen0: Diamond Multimedia Diamond Multimedia Digital Audio Player, rev 1.00/1.00, addr 2 Since this device is recognized by the kernel as 'ugen0', it doesn't know that it's a storage unit, and explains why you can't mount it. In order to use this device, you'll have to update the USB subsystem to recognize this device as a storage unit, and perhaps do some other code hacking before you can access it as a SCSI disk. Hopefully someone else on the list can provide you with more details (as in, how do I do what I need to do to get this thing working!) For an example of how to do this, please see the changes to: /usr/src/sys/dev/usb/umass.c /usr/src/sys/dev/usb/usbdevs /usr/src/sys/dev/usb/usbdevs.h /usr/src/sys/dev/usb/usbdevs_data.h /usr/src/sys/cam/scsi/scsi_da.c These changes were just committed to solve the exact problem you are having, instead it was for the MicroTech CameraMate CompactFlash/SmardCard reader. grep -i microtech on those files and look in the vicinity of the hits for the changes. The two .h files don't have to be changed, just run the makefile in that directory after changing usbdevs. Since I don't have a Diamond MP3 player, I can't do this. Although I didn't write the changes for the MicroTech CameraMate, I did learn a bit from the experience testing them, and it really doesn't look that hard once you figure out what is going on. Oh yeah, once you have it working, come back here, and post the patches asking that they be further tested and committed! It can take a little while, but it'll be worth it for the next guy. You may also want to search the archives and see if anyone else has announced patches being available for testing, that's how I came across the CameraMate patches that were just committed as a result of my testing [and asking for them to be committed until a committer noticed I was asking]. I searched the archives, found that someone had done some patches, and advertised the fact asking for others to test them, this was from back in April. A few weeks ago, I wrote him, and asked for a copy, although they didn't go in straight from patch, they were easy enough to put in by hand, and generate -current patches. After testing them out and finding they work, it was just a matter of asking for them to be committed. Welcome to open-source, community-supported operating systems! Should you choose to take this assignment, Matt, the secretary will disavow your actions if you are caught. Good luck! ;^) jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: wacky warnings linking multithreaded code
if you have the linux-pthreads port installed, remove it. things will compile properly afterwards. linux-pthreads really needs a different library name and include file names... i lay odds that this known conflict is your problem. David Petrou wrote: cc -pthread test.c i tried that too. that works for test.c, which doesn't reference anything, but in more complex programs, it dies. i wish i knew why. check this out: this is the command to link testgthread from the glib library without -lc_r and without -pthread: -- amant 1/619 cs.cmu.edu/project/pdl-19/glib-1.2.10/gthread gmake /bin/sh ../libtool --mode=link gcc -g -O2 -Wall -D_THREAD_SAFE -D_REENTRANT -o testgthread testgthread.o ../libglib.la libgthread.la gcc -g -O2 -Wall -D_THREAD_SAFE -D_REENTRANT -o .libs/testgthread testgthread.o ../.libs/libglib.so .libs/libgthread.so -Wl,--rpath -Wl,/usr/local/lib testgthread.o: In function `new_thread': /afs/cs.cmu.edu/project/pdl-19/glib-1.2.10/gthread/testgthread.c(.text+0x3227): undefined reference to `pthread_attr_init' /afs/cs.cmu.edu/project/pdl-19/glib-1.2.10/gthread/testgthread.c(.text+0x3233): undefined reference to `pthread_create' testgthread.o: In function `private_constructor': /afs/cs.cmu.edu/project/pdl-19/glib-1.2.10/gthread/testgthread.c:139: undefined reference to `pthread_self' testgthread.o: In function `test_private': /afs/cs.cmu.edu/project/pdl-19/glib-1.2.10/gthread/testgthread.c(.text+0x3511): undefined reference to `pthread_join' .libs/libgthread.so: undefined reference to `pthread_cond_signal' .libs/libgthread.so: undefined reference to `pthread_getspecific' .libs/libgthread.so: undefined reference to `pthread_cond_broadcast' .libs/libgthread.so: undefined reference to `pthread_key_create' .libs/libgthread.so: undefined reference to `pthread_cond_init' .libs/libgthread.so: undefined reference to `pthread_mutex_unlock' .libs/libgthread.so: undefined reference to `pthread_mutex_destroy' .libs/libgthread.so: undefined reference to `pthread_mutex_lock' .libs/libgthread.so: undefined reference to `pthread_cond_wait' .libs/libgthread.so: undefined reference to `pthread_mutex_trylock' .libs/libgthread.so: undefined reference to `pthread_cond_destroy' .libs/libgthread.so: undefined reference to `pthread_mutex_init' .libs/libgthread.so: undefined reference to `pthread_cond_timedwait' .libs/libgthread.so: undefined reference to `pthread_setspecific' gmake: *** [testgthread] Error 1 -- now with -pthread: -- amant 1/621 cs.cmu.edu/project/pdl-19/glib-1.2.10/gthread /bin/sh ../libtool --mode=link gcc -g -O2 -Wall -D_THREAD_SAFE -D_REENTRANT -o testgthread testgthread.o ../libglib.la libgthread.la -pthread gcc -g -O2 -Wall -D_THREAD_SAFE -D_REENTRANT -o .libs/testgthread testgthread.o ../.libs/libglib.so .libs/libgthread.so -pthread -Wl,--rpath -Wl,/usr/local/lib /usr/lib/libc.so.4: WARNING! setkey(3) not present in the system! /usr/lib/libc.so.4: warning: this program uses gets(), which is unsafe. /usr/lib/libc.so.4: warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so.4: WARNING! des_setkey(3) not present in the system! /usr/lib/libc.so.4: WARNING! encrypt(3) not present in the system! /usr/lib/libc.so.4: warning: tmpnam() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so.4: warning: this program uses f_prealloc(), which is stupid. /usr/lib/libc.so.4: WARNING! des_cipher(3) not present in the system! /usr/lib/libc.so.4: warning: tempnam() possibly used unsafely; consider using mkstemp() creating testgthread -- $.02, /Mikko any ideas? i know the warnings are generated from libc (just grep around /usr/src/lib/libc). i can't find anything that references those symbols. also, i must not be understanding -pthread, because i thought it _replaced_ libc with libc_r. david p.s.: again, please remember to reply to me in addition to the lists. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Any ATAPI gurus out there?
Okay, here's the deal. My friend, whom I am trying to teach unix [4.3-stable] was having some problems on his secondary ATAPI bus. A Creative CD-ROM was the master, a HP burner was the slave. I'm a SCSI guy meself, and I think the following may be the problem, but as such, I don't know for sure... The CD-ROM was having data dropouts, and was due to old age, no doubt. Under Winblowz, the HP burner would only get 4x when it was able to burn. it's a 12x/8x/32x drive. Under BSD, the CD-ROM would be usable, but would be prone to dropouts. Under BSD, the HP burner came up with sense errors on boot, prior to a proper probe reply. It would hang for the duration of several timeouts at the point before it got the probe. Under BSD, the HP burner would cause a terminal wait state upon any access [such as a mount request, or a burncd command]. Red-button time... This last Friday, he bought a new CD-ROM, and a new burner, as we both thought both drives had issues. He gave me the burner [after a promise to pay him $50 for the under-a-year-old burner, assuming I could fix it]... He put his new drives in his box. Everything works now, under Winblowz AND BSD. I put the the HP burner in MY box, and voila! Nothing is wrong with it... Questions: 1). Can a flaky ATAPI Master cause a good ATAPI Slave to APPEAR [however incorrectly] that the Slave has a problem? 2). If #1 is true, then, why? One added benefit, I've been pushing him to go SCSI [with the good eBay prices on reliable used and new drives, as well as the independance of the drives, the speed, etc... This has gotten him one step closer to committing to SCSI, so not all is lost in this story.. He got two new drives, I got a helluva deal on a good burner, and he may convert to SCSI... I am relatively ignorant on ATAPI matters, and under SCSI the devices are independant, but we do have this question concerning the Master/Slave thing... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: Finding filesizes in C++ for files greater than 4gb
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. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: Finding filesizes in C++ for files greater than 4gb
Kent Stewart wrote: 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, my point is that the manual page should specify this. I think that's the point the original poster was trying to make once he was told. You should not have to grep ansi.h to determine the type for off_t, if anything, maybe adding BSD_OFF_T to types(5). types(5) states the following for off_t: typedef _BSD_OFF_T_ off_t; /* file offset */ Where does that say 64 bits? Let's see what the references are: SEE ALSO gdb(1), lseek(2), time(3), fs(5) hmmm... maybe lseek? Nope.. The only reference to off_t there is: SYNOPSIS #include unistd.h off_t lseek(int fildes, off_t offset, int whence); IMHO, the definition of BSD_* belongs in types(5), where it is referenced. But, in fs(5), I see a bit of a deviation from FreeBSD coding practice... u_int64_t fs_maxfilesize;/* maximum representable file size */ Why isn't that defined as off_t or BSD_OFF_T? Bottom line, he went to stat(2) to find this info. stat(2) gives this: SEE ALSO access(2), chmod(2), chown(2), utimes(2), symlink(7) In other words, I went on a hunch that it would be in types(5), but someone not knowing the manpage for types(5) was there would have never found this, nor would it have answered his question, as types(5) only lists BSD_OFF_T as the size, and for the life of me, I'm not sure which manpage specifies that, of course, I'm only an amateur, only having had running FBSD systems since 1.1.5.1-RELEASE. To go off on another tangent... In fs(5), I find this, which directly conflicts with the stat structure listed in stat(2) [quoted from my last post]: int32_t fs_size; /* number of blocks in fs */ So Which is it? I can see how someone could get confused, especially the newly initiated. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: Collecting System Statistics Programatically
Tabor Kelly wrote: I have found how to collect limited system statistics with sysctlbyname(), but I need to know how to do more. In specific I need to know how much memory is being used, and what percentage of processor cycles are being used. Any help is greatly appreciated, Thank You. Tabor Kelly I have always wanted to see some kind of kernel option to allow an HP-UX style metrics interface. IMHO, it should be a kernel option, but the hooks would have to be in every vital kernel function. HP Measureware is quite handy in load and capacity planning. With new SMP machines and HA tools being made available on a wide basis now, a tightly-coupled kernel-level Measureware-like interface could be a good idea whose time has come. As I said, this should either be a module or a compile-time option for the kernel, as it would introduce a small, but near-negligible, performance hit for the duration of a study, so it should be capable of being disabled for generic production use. My sources in HP say it's been used internally by HP to determine where to tune their kernel code with each successive release since the tightly-coupled measureware interface was established, so the idea would also have practical benefit to the core team and other kernel developers for future planning, and making FreeBSD even more efficient than it already is. At the current state of FreeBSD, this could be a good idea for FreeBSD-6.0. A fair assumption that SMP could be in commodity user-oriented gear by the time FreeBSD-6.0 is -RELEASE in at least 50% of the off the shelf products at the time wouldn't be a stretch assumption IMHO. This plus hardware speed improvements would make any performance hits near-negligible. I floated this idea a few years ago, but got burned up in the flames by people mainly using the performance-hit argument. In this day and age, and especially by the time 6.0-RELEASE is available, IMHO, that will be a dead argument against such a metrics interface at the kernel-level. It also opens the door to third-party userland metrics collection and analysis tools, both standalone, and clustering, both freeware and commercial. Anyone who is unfamiliar with the HP Measureware kernel interface should search on Measureware and HP-UX internals documents at hp.com, the interface is integral to the HP kernel, and covers almost any kernel statistic you can think of, because it is so tightly-coupled to the kernel. A userland daemon exists that can allow collecting such metrics over the wire from a cluster of computers, or from a network of standalone computers into a central capacity-planning workstation running a userland collection/analysis tool. Of course, the collection/analysis tool can exist on the same system being measured, but that in itself would introduce a performance hit [being an X app running on the production ox being measured], and thus is not recommended. I think this is an idea whose time has come. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: Downloads appear broked...but work...keep hitting reload...
Terry Lambert wrote: Jim Bryant wrote: Everybody and their dog must be downloading this. If you keep getting the java.lang.OutOfMemoryError, just keep hitting reload... I was just about to give up when it finally worked for me. Gee, garbage collection is special. I'm going to run right out and use Java in my next embedded system! -- Terry Yeah, I couldn't understand why it wasn't just a HTTP or FTP download like on the community source page. Hell, I didn't even have to enter my username and password. Is Sun slacking or something? Note that the other stuff was via HTTP download, on the same page. On the other hand, Java has it's uses... Coulda been MIX for all I'm concerned. Ideally, Java can run on near anything with no source or object code modifications. MIX, Java, whatever... The point is that it's a universal language, if there ever was such a beast. But then again, ever read the 100% pure manual? Kinda hard to do anything REALLY serious in 100% pure Java. IMHO, universal appeal was lost when Java gained arbitrary filesystem access. They could have saved it from that loss of practicality by implementing some sort of canned scratchpad storage, that would allow a storage object, yet without arbitrary filesystem access without explicit grants [CDC Cyber NOS/BE comes to mind as an ideal on this, and would be easily implemented]. The arbitrary filesystem access is the real killer when it comes to Java. To me, GC is a secondary issue. I'm not even going to go into the issues of the ability to run external system binaries from within Java. Count that as yet another primary issue. All this is a moot point anyhow... We is stuck with it. PicoBSD works well for embedded systems tho, I've done that :^) CompactFlash and a Simm... Look Ma! No spinning wheels! jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: Backup file formats: tar, cpio, pax, yadda, yadda, yadda
Warner Losh wrote: In message [EMAIL PROTECTED] Sergey Babkin writes: : Use dump. Otherwise, you will lose. : : Don't use dump. Or you'll never be able to restore these backups : on a non-FreeBSD machine. Unless it runs NetBSD, OpenBSD, Solaris, Linux or SunOS. ufsrestore is pretty universal. FreeBSD dumps also restore just fine under HP-UX, I've done so under 10.20 and 11.0. HP-UX restore will automatically do the byte-swapping. FreeBSD and GNU tar will not restore correctly to HP-UX, but dump/restore does work fine. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: Fwd: Sun Grid Engine 5.2.3 Available. Now Open Source
Terry Lambert wrote: Ron Chen wrote: Sun Grid Engine goes opensource. See SGE home page: http://www.sun.com/gridware I see no source code there, only Solaris and Linux binaries. I coulda sworn I saw that they had source code available for grid engine as well, as this weekend i was downloading stuff for Solaris 8 x86 [which i run on one of my disks]. I did also take note that they are offering sources for Solaris 8, but I can't download it at the moment, as I don't have a fax machine to return the form. Apparently the Solaris 8 sources are available for free, but you have to fax the damned form back for download access. Somewhere in my search for Sun free stuff for Solaris 8 over the weekend did turn up a Sun page saying Grid Engine sources were available, as I recall tho. Sun really does need to redo their page so it's easier to find stuff. I'll backtrack and see if I can come up with the page I saw it on. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: Fwd: Sun Grid Engine 5.2.3 Available. Now Open Source
Christoph Sold wrote: [Extensive cross-posting adress list dropped.] Jim Bryant wrote: Terry Lambert wrote: Ron Chen wrote: Sun Grid Engine goes opensource. See SGE home page: http://www.sun.com/gridware I see no source code there, only Solaris and Linux binaries. I coulda sworn I saw that they had source code available for grid engine as well, as this weekend i was downloading stuff for Solaris 8 x86 [which i run on one of my disks]. Direct from Suns Grid Engine FAQ: [Line breaks edited by me.] Q: Is Sun making the source for the now-current Sun Grid Engine software versions 5.2.2/5.2.3 available in open source? A: The source available in the Grid Engine open source project has received numerous modifications in order to prepare it for release as open source software. Organizations interested in obtaining the source for the now current 5.2.2/5.2.3 versions under a Sun source-access (non-open source) license should contact [EMAIL PROTECTED] Here is the URL referencing the Grid Engine Open Source project. Not much there, apparently it's one of those Real Soon Now(TM) items, but this is the URL: http://www.sun.com/software/gridware/gridengine_project.html jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: Fwd: Sun Grid Engine 5.2.3 Available. Now Open Source
Jim Bryant wrote: Christoph Sold wrote: [Extensive cross-posting adress list dropped.] Jim Bryant wrote: Terry Lambert wrote: Ron Chen wrote: Sun Grid Engine goes opensource. See SGE home page: http://www.sun.com/gridware I see no source code there, only Solaris and Linux binaries. I coulda sworn I saw that they had source code available for grid engine as well, as this weekend i was downloading stuff for Solaris 8 x86 [which i run on one of my disks]. Direct from Suns Grid Engine FAQ: [Line breaks edited by me.] Q: Is Sun making the source for the now-current Sun Grid Engine software versions 5.2.2/5.2.3 available in open source? A: The source available in the Grid Engine open source project has received numerous modifications in order to prepare it for release as open source software. Organizations interested in obtaining the source for the now current 5.2.2/5.2.3 versions under a Sun source-access (non-open source) license should contact [EMAIL PROTECTED] Here is the URL referencing the Grid Engine Open Source project. Not much there, apparently it's one of those Real Soon Now(TM) items, but this is the URL: http://www.sun.com/software/gridware/gridengine_project.html Apparently the Grid Engine Open Source Project was discussed in one of yesterday's sessions at the O'Reilly Open Source Convention in San Diego. It was the first conference at the convention. http://www.sun.com/software/star/events/oreillyopensource2001/ Anyone around here attending this convention that attended the Grid Engine session that can give us some info on this subject? Apparently the convention ends on Friday. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: Fwd: Sun Grid Engine 5.2.3 Available. Now Open Source
Ron Chen wrote: Sun Grid Engine goes opensource. See SGE home page: http://www.sun.com/gridware -Ron http://www.sun.com/smi/Press/sunflash/2001-07/sunflash.20010723.1.html SUN MICROSYSTEMS MAKES SUN[tm] GRID ENGINE SOFTWARE AVAILABLE TO OPEN SOURCE COMMUNITY Sun Works with CollabNet to Continue its Strong Support of Open Computing and Encourage Adoption of Powerful Grid Computing Model SAN DIEGO, CA -- O'REILLY OPEN SOURCE CONVENTION -- July 23, 2001 -- Reaffirming its commitment to the open source movement, Sun Microsystems, Inc. (NASDAQ: SUNW) announced today the Sun Grid Engine Project, an initiative to offer the source code for Sun[tm] Grid Engine software to users and the developer community. Sun Grid Engine software is an advanced distributed resource management (DRM) tool. It has been available as a free download at www.sun.com/software/gridware since its introduction in September 2000. A leader in the open source community, Sun will add this project's half million lines of code to its total of more than 8 million lines of code already contributed to open source efforts. Sun is coordinating this worldwide project with CollabNet, a leading provider of collaborative software development solutions based on open source concepts, in making the code available for download at www.gridengine.sunsource.net. The project is designed to further remove the cost and implementation barriers associated with deploying DRM software in a compute farm. Additionally, both open source users and Sun Grid Engine software customers should benefit from this open source project through enhanced industry support. For example, service and support providers should be able to customize the powerful software for specific customer needs, and software developers should be able to reduce complexity for end users by creating applications that are tightly integrated with Sun Grid Engine software. Over time, the open source effort should facilitate the adoption of open standards for DRM software, facilitating interoperability with applications and easing integration. As cluster computing scales up towards grid computing, tools like Sun Grid Engine software will become ubiquitous and essential, said Tim O'Reilly, founder and CEO of technology information firm O'Reilly Associates. Computing is moving towards the development of what you might call an Internet operating system. Sun recognizes that key components of that operating system shouldn't be controlled by any one company, and they're putting their money where their mouth is by releasing it as open source. Sun will continue to deliver products that support our core philosophy that the network is the computer, said Robbie Turner, vice president of Client and Technical Market Products at Sun Microsystems. Sun is encouraging the grid computing model via free downloads of Sun Grid Engine software--and now by making its code available to the open source community--because the productivity gains of the grid computing model will increasingly serve as a decisive factor in a business's ultimate success or failure. CollabNet is providing the Web infrastructure and comprehensive development platform that enables geographically dispersed groups of developers to collaborate on Grid Engine projects. Based on CollabNet's SourceCast environment, this platform includes tools for revision control, issue tracking, mailing list creation and management, and Web-based administration. This open source project follows on the heels of the successful OpenOffice.org initiative--also supported by CollabNet--which made available the source code for Sun's StarOffice[tm] software under the same industry-accepted Sun Industry Standards Source License. Full details of Sun's involvement with open source projects can be seen at www.sunsource.net. The Grid Engine Project continues to demonstrate Sun's true leadership within the open source community, said Brian Behlendorf, co-founder and CTO of CollabNet. CollabNet is delighted to be working with Sun on yet more compelling open source software. Sun's decision to open this previously proprietary software demonstrates its understanding of the technical community's fundamental need and interest in scalable DRM technology. Delivering Network-Wide Compute Power to the Desktop Sun Grid Engine software was introduced in September 2000 as the first product resulting from Sun's acquisition of Gridware, formerly a privately-owned commercial vendor of advanced DRM software tools. Since then, the software has been downloaded nearly 8,000 times in more than 90 countries. A comprehensive web-based training course for installing and managing the software is also available at no cost at www.sun.com/software/gridware. By distributing Sun Grid Engine software as a free download and with all Sun systems, Sun is changing the economics of technical computing and breaking down the barriers of employing distributed computing. Sun
Downloads appear broked...but work...keep hitting reload...
Jim Bryant wrote: Ron Chen wrote: Sun Grid Engine goes opensource. See SGE home page: http://www.sun.com/gridware -Ron http://www.sun.com/smi/Press/sunflash/2001-07/sunflash.20010723.1.html SUN MICROSYSTEMS MAKES SUN[tm] GRID ENGINE SOFTWARE AVAILABLE TO OPEN SOURCE COMMUNITY Sun Works with CollabNet to Continue its Strong Support of Open Computing and Encourage Adoption of Powerful Grid Computing Model SAN DIEGO, CA -- O'REILLY OPEN SOURCE CONVENTION -- July 23, 2001 -- Reaffirming its commitment to the open source movement, Sun Microsystems, Inc. (NASDAQ: SUNW) announced today the Sun Grid Engine Project, an initiative to offer the source code for Sun[tm] Grid Engine software to users and the developer community. Sun Grid Engine software is an advanced distributed resource management (DRM) tool. It has been available as a free download at www.sun.com/software/gridware since its introduction in September 2000. A leader in the open source community, Sun will add this project's half million lines of code to its total of more than 8 million lines of code already contributed to open source efforts. Sun is coordinating this worldwide project with CollabNet, a leading provider of collaborative software development solutions based on open source concepts, in making the code available for download at www.gridengine.sunsource.net. The project is designed to further remove the cost and implementation barriers associated with deploying DRM software in a compute farm. Additionally, both open source users and Sun Grid Engine software customers should benefit from this open source project through enhanced industry support. For example, service and support providers should be able to customize the powerful software for specific customer needs, and software developers should be able to reduce complexity for end users by creating applications that are tightly integrated with Sun Grid Engine software. Over time, the open source effort should facilitate the adoption of open standards for DRM software, facilitating interoperability with applications and easing integration. As cluster computing scales up towards grid computing, tools like Sun Grid Engine software will become ubiquitous and essential, said Tim O'Reilly, founder and CEO of technology information firm O'Reilly Associates. Computing is moving towards the development of what you might call an Internet operating system. Sun recognizes that key components of that operating system shouldn't be controlled by any one company, and they're putting their money where their mouth is by releasing it as open source. Sun will continue to deliver products that support our core philosophy that the network is the computer, said Robbie Turner, vice president of Client and Technical Market Products at Sun Microsystems. Sun is encouraging the grid computing model via free downloads of Sun Grid Engine software--and now by making its code available to the open source community--because the productivity gains of the grid computing model will increasingly serve as a decisive factor in a business's ultimate success or failure. CollabNet is providing the Web infrastructure and comprehensive development platform that enables geographically dispersed groups of developers to collaborate on Grid Engine projects. Based on CollabNet's SourceCast environment, this platform includes tools for revision control, issue tracking, mailing list creation and management, and Web-based administration. This open source project follows on the heels of the successful OpenOffice.org initiative--also supported by CollabNet--which made available the source code for Sun's StarOffice[tm] software under the same industry-accepted Sun Industry Standards Source License. Full details of Sun's involvement with open source projects can be seen at www.sunsource.net. The Grid Engine Project continues to demonstrate Sun's true leadership within the open source community, said Brian Behlendorf, co-founder and CTO of CollabNet. CollabNet is delighted to be working with Sun on yet more compelling open source software. Sun's decision to open this previously proprietary software demonstrates its understanding of the technical community's fundamental need and interest in scalable DRM technology. Delivering Network-Wide Compute Power to the Desktop Sun Grid Engine software was introduced in September 2000 as the first product resulting from Sun's acquisition of Gridware, formerly a privately-owned commercial vendor of advanced DRM software tools. Since then, the software has been downloaded nearly 8,000 times in more than 90 countries. A comprehensive web-based training course for installing and managing the software is also available at no cost at www.sun.com/software/gridware. By distributing Sun Grid Engine software as a free download and with all Sun systems, Sun is changing the economics of technical
Re: SmartDisk USB CompactFlash reader
Alfred Perlstein wrote: * Leif Neland [EMAIL PROTECTED] [010724 19:18] wrote: I've got such a device; it was nessecary, because my camera run out of batteries before I could retrieve 48MB of pictures over the normal serial port When I plug it in it displays: ugen0: SmartDisk Corp. SM/CF Combo USB Reader, rev 1.00/0.83, addr 2 Can this be read in FreeBSD? Try compiling in the 'umass' driver, you may be out of luck, SanDisk produced a version of thier reader that didn't use the USB disk specification and requires a proprietary driver for it, you may be stuck using this from windows. Good news is that you can get one that works in freebsd for only about 20$. I've been interested in this too... Which one is known to work under FreeBSD? jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Re: more on latency
Terry Lambert wrote: Kenneth Wayne Culver wrote: I think I found the reason that my FreeBSD box is performing so poorly as a NATing router. When I do an ipnat -l to see what active connections are there on the router, a list about 3 pages long (using ipnat -l | more) appears. I think maybe it's having trouble because for every packet coming in and out of the router, it's got to look at that list of active connections for the right one to send to and from. Is there any way to make connections that aren't being used go away from the NAT faster? Thanks a lot. Don't run unnecessary daemons. The pcb lookups are a linear traversal, as well, and for a large number of connections, the calllout wheel for timers sucks. -- Terry Is there a way to get similar stats from natd? jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ 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
Rijndael status in FreeBSD??
What are the plans for incorporating Rijndael, the finalist algorithm for the Advanced Encryption Standard, into FreeBSD? jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- [EMAIL PROTECTED] KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM HF/VHF: IC-706MkII VHF/UHF/SHF: IC-T81AKPC3+ PK-232MBXGrid: EM28px -- ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How a normal user can crash any linux system (fwd)
In reply: This is cross-posted to both linux-kernel and freebsd-hackers, please set your replies properly. I found the following by accident playing with PVM. If you start the 'gexample' from the examples directory with dimension=1 and no of tasks=32 on one machine, it becomes almost immediately completely un- usable and begins with heavy swapping. Considering how much memory would be necessary for this computation before starting it would have avoided the trouble. well, there are other ways to make a system slow to a crawl a good preventative measure is to never give shell accounts unless everyone is accountable. #!/bin/csh /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null /usr/games/primes 1 4294967295 /dev/null # etc, ... # # [get the idea?] jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- [EMAIL PROTECTED] KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM HF/VHF: IC-706MkII VHF/UHF/SHF: IC-T81AKPC3+ PK-232MBXGrid: EM28px -- ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Copy-on-write filesystem
In reply: Imagine: cp file file2, file and file2 reference the same exact blocks, but modified chunks of file2 would be given their own private blocks. This is not a microsoft innovation, actually, I believe it was a VMS innovation. It's called a generational filesystem. the original is stored, and later generations of the file are stored as diffs. This probably won't fit into current filesystems, but is it a sane idea worth pursuing in a new filesystem? I performed an analysis on a non-production server and determined that about 66 megs of a typical FreeBSD install is duplicate files (and yes, I ignored hard links and symlinks and non-regular files). it has it's advantages. and disavantages. one problem in VMS is determining the system-wide policy on such things, such as how many file generations will be kept. this isn't exactly apples to apples, but it's close enough to be discussed. a VMS style filesystem would be interesting. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM [EMAIL PROTECTED] IC-706MkII, IC-T81A, HTX-202, HTX-212, HTX-404, KPC3+, PK-232MBX Grid: EM28px -- ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Copy-on-write filesystem
In reply: On Fri, 3 Mar 2000, Michael Bacarella wrote: Can someone tell me why copy-on-write filesystems would be bad? It's a good idea. Peter Braam and I have written a device (called memdev) for linux (sorry!) that implements a virtual-memory-backed copy-on-write block device (like the loopback device, but uses anon vm pages for store). It's pretty interesting. It's quite fast, and copy-on-write does seem to work OK for a filesystem. I'm using this thing as one of two pieces of a new private name space implementation that would also work quite well on freebsd. Ever experience CDC Cyber NOS? Interesting private-space filesystem with many apps today. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM [EMAIL PROTECTED] IC-706MkII, IC-T81A, HTX-202, HTX-212, HTX-404, KPC3+, PK-232MBX Grid: EM28px -- ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: idea: official hardware manufacturer blacklist - let's wake em up!
In reply: On Sun, 27 Feb 2000, Michael Bacarella wrote: I love the idea myself, but I have no power over FreeBSD :( You may not like the shape of the world, but I don't think getting publicly nasty about it is going to have any positive effect. It WILL have a negative effect, as FreeBSD would gather the reputation of very vindictive; it's even very likely that, somewhere along that road, a lawsuit over some wording would arise. I call it consumer education. Include call logs in such a list, let the public decide if a honest effort was made to contact such companies for information before being put on such a list. Such call logs can also speak for themselves, maybe add a column to the list for number of times people are told "We only support Windows". Nothing at all vindictive about it, in fact, an open invitation can be posted to be forthcoming with information needed to create drivers, we can point out the fact that there are millions of us, and it's just that much more profit for them. Where people see just cause for a boycott, they tend to support it, thus any action taken against any such list [with documentation on why they are on the list], will gain more people on our side. We can even add a second list of those who open up after being put on the list, proving that we aren't vindictive or nasty, and that all we seek is the info it takes to create drivers with the same functionality as the windows driver which they both wrote and supply. It isn't as if we are asking them to hire support staffs just for FreeBSD. Don't read in things that are not being said, Chuck. Nobody mentioned getting nasty or vindictive, all I saw was a good educational proposal, that would educate the general public about a problem. A lawsuit over such would only make whoever brings it look bad. You just can't get what you want all the time. If you don't do what it takes to get something, you surely won't get a thing. The boycott is a time-tested technique of getting what it is one wants, especially from corporations. Unless you convince the owner of a corporation that his wallet COULD get lighter, or the shareholders the idea of lower returns, you won't get the time of day out of them. Which water fountain do you drink from? Oh wait, that doesn't matter anymore, some people got off their butts and changed things for the better back in the 50's and 60's, without getting nasty or vindictive, when in fact they had every right to come out shooting. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM [EMAIL PROTECTED] IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP -- ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: idea: official hardware manufacturer blacklist - let's wake em up!
In reply: On Mon, 28 Feb 2000, Karsten W. Rohrbach wrote: hm i mean, do the hardware people want their stuff supported or not? that's the main question some seem to choose the NOT. right, and that is their perogative ... you can't create a "blacklist" and publicize it, it makes us look bad, not them. What you can do is create a "recommended hardware", or "well supported hardware" list ... Don't show the negative, only show the positive ... promote those vendors that are open to FreeBSD, don't put down those that don't ... Translation: Be a good *BOY*, stay in your place. Read my last post, nothing has to be done negatively in posting a boycott list, in fact, it would be a highly positive experience. I would think that such corporations would be more than willing to open up after a little publicity. IMHO, I think the feds need to take a look at their Microsoft contracts. It's one thing to refuse to hire a support staff for anything other than windows, but totally different to not release information to create independantly supported drivers. The latter in the quantity of companies doing it could quite possibly fit the Fed Civil guidelines for proving conspiracy on say, restraint of trade. It doesn't take rocket science to know Microsoft is playing dirty and looking for new ways to maintain control. "Hi, I'm looking for programming information on the super-duper XYZ card so I can write a device driver for FreeBSD." "I'm sorry, we only support Windows." "I'm not looking for support, I support my own code." "I'm sorry, we only support Windows." "Is this the correct department to ask?" "Yes. I'm sorry, we only support Windows." Yeah, we all know the story, like I said, it ain't rocket science. If Morley Safer got that on the phone, he'd have a camera crew out there the very next day to ask it again in person. We get this every day of the week. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM [EMAIL PROTECTED] IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP -- ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: idea: official hardware manufacturer blacklist - let's wake em up!
In reply: ok guys, here's just a little idea on how to get the hardware manufacturer guys a little bit more responsive (in fact, i got somehow "inspired" by the alsa sound project guys because they got something similar)... let's put up a list of hardware manufacturers that do not answer our mails, that do not hear our pleas for driver development, that simply do not react. then we might publish a link to this thing on the freebsd.org Why not? One or two people calling a week doesn't attract that much attention within these companies. Maybe a list of manufacturers dealing exclusively with Gates would. I have some to add if this ever comes to pass. If we can make this a joint FreeBSD/Linux list, we can get even more media attention to this issue, this would be a good truce issue with the linux folks. We all know by now how MickeySoft does it's vendor deals, it's been well publicised, and it doesn't take rocket science to guess that they are playing dirty. Making such a list could open things up back to the old days when anyone could obtain register-level programming info on any card they wanted to. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM [EMAIL PROTECTED] IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP -- ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Wall Street Journal on Open source OS (9/10/99)
In reply: At 10:42 AM -0700 9/10/99, Sanjay Waghray wrote: Attached is an article from the Wall Street Journal Online Edition. --- September 10, 1999 Beyond Linux, Free Systems Do Their Bit to Build Web By LEE GOMES Staff Reporter of THE WALL STREET JOURNAL Unless you got the "express prior written consent of Dow Jones", as stated in the "Terms of Use" of their web site, it would be much better to point people at: - - - - There's also a link to the online version at http://freebsd.tesserae.com/ - - - - than to copy the entire article and mail it to everyone on this mailing list. give him a break. unless of course you intend to arrest all of those people who have ever photocopied and distributed a newspaper article [gee, does that include you?]. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- Inet: [EMAIL PROTECTED]AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Intel Merced FreeBSD??? Intel? - NOT
In reply: In article [EMAIL PROTECTED] you write: Actually, I was reading in a newsgroup, the VMS newsgroup I think it was, that the PA-RISC chip is on the Merced chip. Basically, Intel will sell Merced's with the chip disabled (kind of like the math co-processor on the 486 SX's) and HP will sell it with the PA-RISC chip enabled so it can run HP-UX. *sigh* Look, people, the Merced WILL NOT excuse PA-RISC code directly. It will be done via emulation/translation, and only a certain particular OS will be supported (HP-UX 11, I believe they stated -- since HP-UX 11 runs almost all HP-UX 10.* applications with no problem, I am _guessing_ that this means they will continue to work). I really don't know how people get started with this. HP has _never_ stated that the chip will handle it; all they have stated is that HPUX applications will continue to be supported. I suggest you people go read comp.arch for a while; there's a fair bit of information cropping up there. For example, there's a wonderful thread going on about HP's previous experience with architecture emulation, including some interesting comments by people at HP. Well, the way I understand things, HP-UX 11 comes in two flavors, 32 bits and 64 bits. I think that 32-bit code is handled in a legacy emulation under 64 bit 11, I'd have to double check that though with the book. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- Inet: [EMAIL PROTECTED]AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Intel Merced FreeBSD??? Intel? - NOT
In reply: On Fri, 27 Aug 1999, Sean Eric Fagan wrote: In article [EMAIL PROTECTED] you write: Look, people, the Merced WILL NOT excuse PA-RISC code directly. It will be done via emulation/translation, and only a certain particular OS will be supported (HP-UX 11, I believe they stated -- since HP-UX 11 runs almost all HP-UX 10.* applications with no problem, I am _guessing_ that this means they will continue to work). I just asked one of our HP people about this. He says that anything that runs on HP 11.0 PA-RISC will run on IA64. It is his understanding that this includes not only 10.x stuff, but also 9.x and 8.x stuff. We have stuff that runs on 11 that was originally compiled for 8.0. David Scheidt ummm... you really need to get that recompiled at the earliest convenience. preferbaly this year. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- Inet: [EMAIL PROTECTED]AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Intel Merced FreeBSD??? Intel? - NOT
In reply: In article pine.gso.3.96.990827103350.1456c-10.kithrup.freebsd.hack...@mission.mvnc.edu you write: Actually, I was reading in a newsgroup, the VMS newsgroup I think it was, that the PA-RISC chip is on the Merced chip. Basically, Intel will sell Merced's with the chip disabled (kind of like the math co-processor on the 486 SX's) and HP will sell it with the PA-RISC chip enabled so it can run HP-UX. *sigh* Look, people, the Merced WILL NOT excuse PA-RISC code directly. It will be done via emulation/translation, and only a certain particular OS will be supported (HP-UX 11, I believe they stated -- since HP-UX 11 runs almost all HP-UX 10.* applications with no problem, I am _guessing_ that this means they will continue to work). I really don't know how people get started with this. HP has _never_ stated that the chip will handle it; all they have stated is that HPUX applications will continue to be supported. I suggest you people go read comp.arch for a while; there's a fair bit of information cropping up there. For example, there's a wonderful thread going on about HP's previous experience with architecture emulation, including some interesting comments by people at HP. Well, the way I understand things, HP-UX 11 comes in two flavors, 32 bits and 64 bits. I think that 32-bit code is handled in a legacy emulation under 64 bit 11, I'd have to double check that though with the book. jim -- All opinions expressed are mine, if you| I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered! - #1, The Prisoner -- Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Intel Merced FreeBSD??? Intel? - NOT
In reply: On Fri, 27 Aug 1999, Sean Eric Fagan wrote: In article pine.gso.3.96.990827103350.1456c-10.kithrup.freebsd.hack...@mission.mvnc.edu you write: Look, people, the Merced WILL NOT excuse PA-RISC code directly. It will be done via emulation/translation, and only a certain particular OS will be supported (HP-UX 11, I believe they stated -- since HP-UX 11 runs almost all HP-UX 10.* applications with no problem, I am _guessing_ that this means they will continue to work). I just asked one of our HP people about this. He says that anything that runs on HP 11.0 PA-RISC will run on IA64. It is his understanding that this includes not only 10.x stuff, but also 9.x and 8.x stuff. We have stuff that runs on 11 that was originally compiled for 8.0. David Scheidt ummm... you really need to get that recompiled at the earliest convenience. preferbaly this year. jim -- All opinions expressed are mine, if you| I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered! - #1, The Prisoner -- Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
usb keyboard setup -or- HELP!
hi, i'm running 4.0-current on a dual p2-333 box. i run X, and am looking for help in setting up a usb keyboard for use with FreeBSD/Xfree86. if anyone has this running, i could use the help in setting it up. also, this keyboard has a ps2 mouse connector. does the mouse get recognized as a usb mouse? jim -- All opinions expressed are mine, if you| I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered! - #1, The Prisoner -- Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
usb keyboard setup -or- HELP!
hi, i'm running 4.0-current on a dual p2-333 box. i run X, and am looking for help in setting up a usb keyboard for use with FreeBSD/Xfree86. if anyone has this running, i could use the help in setting it up. also, this keyboard has a ps2 mouse connector. does the mouse get recognized as a usb mouse? jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- Inet: [EMAIL PROTECTED]AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
In reply: On Wed, 21 Jul 1999, Kip Macy wrote: My employer has gone through numerous motherboards, we have found the ASUS P2B (now the P2B-F) to be rock solid for Pentium II usage. This is probably more appropriate for -hardware or even just -chat.. but anyway, I'll second that recommendation. I've found the ASUS P2B series to be very solid. I've also used many ATrend BX boards for Winblows95 boxes (simply because they were cheaper than the ASUS boards), and haven't had a bit of trouble with them. YMMV. -- Chris Dillon - cdil...@wolves.k12.mo.us - cdil...@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) One should admire Windows users. It takes a great deal of courage to trust Windows with your data. don't leave out the tyan thunder2 and thunder100 boards. the only problem i even know of with the thunder2 is the sound chip still isn't recognized, and the id codes pnp returns on the sound chip may differ from board to board [others claim it works for them, but not here]. i have heard of no problems with the thunder100 board. jim -- All opinions expressed are mine, if you| I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered! - #1, The Prisoner -- Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
In reply: On Wed, 21 Jul 1999, Kip Macy wrote: My employer has gone through numerous motherboards, we have found the ASUS P2B (now the P2B-F) to be rock solid for Pentium II usage. This is probably more appropriate for -hardware or even just -chat.. but anyway, I'll second that recommendation. I've found the ASUS P2B series to be very solid. I've also used many ATrend BX boards for Winblows95 boxes (simply because they were cheaper than the ASUS boards), and haven't had a bit of trouble with them. YMMV. -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." don't leave out the tyan thunder2 and thunder100 boards. the only problem i even know of with the thunder2 is the sound chip still isn't recognized, and the id codes pnp returns on the sound chip may differ from board to board [others claim it works for them, but not here]. i have heard of no problems with the thunder100 board. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- Inet: [EMAIL PROTECTED]AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Someone want to add support for computer radio scaners?
In reply: Hello All, I was just looking at http://www.winradio.com/ and was thinking that it would be a nice addition to FreeBSD. I don't own one of the cards, otherwise I would have started to see what I could do. But if anyone out there has one/has access to one, it would be interesting to add into FreeBSD. They also supply information for programming use of the device (http://www.winradio.com/home/developer.htm). Well thats all for now, Mike what they supply is a dog/winblowz sdk. the api is documented, but the libraries are provided in binary form, and there is no register level documentation. it might be a fair assumption that these radios are dumber than people think from the dynamic range and other crucial numbers, these radios pretty much suck. you would get better performance out of a direct conversion or trf receiver, honestly. jim -- All opinions expressed are mine, if you| I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered! - #1, The Prisoner -- Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: KNE40BT in freebsd only getting 45KB/sec ftp transfer to win98 machine
duplex should work fine in a 2 machine point to point without a switch. In reply: Hi, Speed in what protocol? FTP? SMB? Appletalk? Have you checked the duplexing of cards on both machines? Use the DOS program that came with the ethernet cards to check. Unless your card is connected directly to a switch, it should be half duplex (I'm not sure on this, but that is my understanding). Jim Bryant wrote: In reply: I am running FreeBSD-current and for some reason I am only getting~45KB/sec transfer to a computer running Windows 98. I have a Kingston KNE40BTcard and I can find no hardware error as to why I am only reaching those speeds. Could you suggest what may be the error? Andrew Tamm ummm.. winblowz-98. jim -- All opinions expressed are mine, if you| I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered! - #1, The Prisoner -- Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: SMP and Celerons...
In reply: Heya, sorry I tried this one on -stable and -questions and noone seems to know, and they actually go so far as to ask me how I got two celerons in a motherboard... so I ask here. I have two PPGA(Socket 370) Celeron 333A's that are on MSI6905 Dual Socket 1 adaptors... a Tyan Thunder 2 motherboard (onboard scsi, sound, etc.) there is a problem with the freebsd sound support for this board, but i am told it is being worked on [?]. I boot an SMP kernel, it gets right past autoboot... then panics the message was that it could not find local apic... its kinda strange because essentially with these adaptors, the celerons should be 1) SMP capable, and 2) the same as a PII, except no L2 cache I know others that ran FreeBSD SMP with celerons... anyone know if theres some kind of patch I need or modification I have to make to get either -CURRENT or -STABLE working on this machine? Right now it is running a UP kernel instead of the SMP one and runs fine. strangeness. i run the same board with dual pII-333's, Tyan Thunder2, S1696DLUA. when i boot, i show two cpus and an apic. i have two theories: 1). these boards have a problem with celery. 2). you have a flaky mb. granted, i haven't heard about too many of them being flaky, but that they have an above average reliability level. but then, there is always someone that get s flake sooner or later. My experience [of about 12 days so far] is that this is a quality midrange system, as configured here, and is maybe even a tad more reliable than my workhorse p133 [which has had three spontaneous reboots in the same period, but running an older -current by a few weeks]. Unless you have some weird boards, -current currently works fine on my system [although -current is subject to overnight changes that produce catastrophic failures every now and then, always check which way the wind is blowing in the -current mailing list before doing a make installworld]. Can you borrow a couple of pII's? It would be interesting to see if the Thunder2's have a problem sith celery. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #41: Tue Jun 15 10:59:11 CDT 1999 jbry...@wahoo:/usr/src/sys/compile/WAHOO Timecounter i8254 frequency 1192991 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = GenuineIntel Id = 0x650 Stepping=0 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 268435456 (262144K bytes) avail memory = 257720320 (251680K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 . . . APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2 APIC_IO: routing 8254 via 8259 on pin 0 . . . changing root device to da0s1a [and normal boot] jim -- All opinions expressed are mine, if you| I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered! - #1, The Prisoner -- Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: coarse vs fine-grained locking in SMP systems
In reply: very fine-grain-locked systems often display convoying and are prone to priority inversion problems. coarse-grained systems exhibit all the granularity problems already described. (the first purdue dual-vax system plowed most of that ground) Was this a VAX 11/782 or a later machine? jim -- All opinions expressed are mine, if you| I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered! - #1, The Prisoner -- Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Wonder what ftp.cdrom.com's utilisation's like now?
In reply: Matthew Dillon wrote: You know, if ftp.cdrom.com shifted over to using more HTTP you could sell add space and recoup some or all of the bandwidth costs. Matt: What an evil suggestion. Somehow, somewhere, we will get you for this. Hackers: I vote we sentence him to working on VM code and fixing NFS bugs -- for free! That'll teach him to spout off. nah, david just loves vm too much, we couldn't let someone else take david's fun away from him :^) jim -- All opinions expressed are mine, if you| I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered! - #1, The Prisoner -- Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
