--I have vmware 3.x running on a Debian Linux 2.4 kernel (host.) Client environment boots Knoppix DVD beta fine with a 2.4 kernel, but crashes with a kernel panic on 2.6 kernels.
Note: Host == 2.4 kernel, VM client == 2.6 for testing (crashing.) Is there any 3rd-party fix for v3, or do I need v4 to test 2.6 kernels in the VM environment? (For various reasons I'm unwilling to migrate the host itself to 2.6.) TIA
> I believe the majority of VMWare workstation sales are on Windows.
--Perhaps. I prefer to be in the minority though; my Vmware Workstation 3.x license is for a Linux host. I wouldn't even *consider* running Vmware on a typical Windows install (as a host) - when, not if, the box crashes, it would take the VM environment(s) with it. Linux == stability, for me.
--I agree, this article seems a bit premature since there's nothing to DL on the Serenity website yet. Their logo looks pretty cool tho. Eventually it will be nice for VMware to have some competition.
--I have a Toshiba Tecra P166 laptop that has Cardbus/PCMCIA switchable in the BIOS. When I bought it 2ndhand it was set to PCMCIA. A quick BIOS change and a reinstall of W98SE, and now it runs Cardbus.
--You can really notice the speed difference; I have an SMC Ethernet PCCard that's compatible with both settings, and it runs noticeably better under 32-bit mode.
--Oops, sorry - after reading grc for a while, it appears that click-death it NOT a problem with the disk, more of a problem with the drive firmware. They put it as: "Click Death is almost, but not quite, never contagious." Sorry.
--I have an original parallel Zip 100 drive that still works reliably (altho admittedly I don't use it much these days.)
--In addition, I have an internal ATAPI drive and a USB 1.1 external drive, both 100's, that are used several times a week for critical-file Linux backups. Never had a ClickOfDeath on any of 'em. However, I bought pretty much all of my Zip disks early on - the original disks are still running fine.:)
--I could be wrong, but IIRC the COD problem was with the *disks*, not the drives. A bad disk could trash several drives. See grc.com for more details.
--It actually shouldn't be *that* hard to get rescued, at least within a 12-24 hour period. Simply tell a friend you're going to Chernobyl; and if they don't hear from you by $time, send out the search party.
--Ah yes, Lotus Notes and Wine - I bet if you check, (run "top" and then hit the M key) there's your memory hog. There's no need to buy a new system, however - that's not what I was saying.
--But notice - even with all that running at once, you're still using much less than 256MB of swap. You could probably resize that 1GB down to half that, or even 300MB - and still have plenty of leeway. If you're using KDE, I'd consider switching to a more lightweight WM (I use Sawfish, but that's prolly too bare-bones for most people) and you'll save even more resources.
--Ah yes, vmware does work better with large amounts of memory. But as far as swap goes, it's still something that should be monitored:
Before vmware (Win98 session, with 164MB of Ram alloc:) free
total used free shared buffers cached Mem: 516196 232612 283584 0 24876 85448 -/+ buffers/cache: 122288 393908 Swap: 771040 0 771040
--Same machine, with vmware session running (no programs active in the VM yet, just OS) free
total used free shared buffers cached Mem: 516196 400996 115200 0 30616 233340 -/+ buffers/cache: 137040 379156 Swap: 771040 0 771040
--And now Opera running in the VM session, with 6 windows open: free
total used free shared buffers cached Mem: 516196 460160 56036 0 32272 288116 -/+ buffers/cache: 139772 376424 Swap: 771040 0 771040
--Note that the swap usage is *still* Zero.
--As far as EMACS goes... Well, there's always "jstar".:-)
--Granted, all I have running ATM is Opera, rxvt, Konsole, Sawfish and a few daemons. But even recompiling the kernel will only use <100MB of RAM (usually much less.)
--Monitor how much swap you use on a daily basis with various tasks. I'll bet you can resize your swap partition down to == the RAM or even a bit less, if you're not worried about suspend-to-disk.
--From personal experience, the more RAM you have - the less swap you need. If you have installed 256MB-512MB of RAM, unless you're *really* pushing the machine, you only "need" about 300MB of swap.
--If you've got ~128MB of RAM (typical older Windoze machine), 300-400MB of swap should be fine even if you're running KDE, XMMS, and a kernel compile all at once.
--1GB of swap actually being *used* is almost unheard of, even if you only have 64MB of RAM; the machine would be so slow as to be almost unusable, and eventually the hard drive would go up in flames from disk thrash. (I've seen it happen with XP. I think the client had only 128MB of RAM installed, and XP swap thrash forced us to reinstall and repartition the disk around the bad sectors.)
--AFA putting the swap on its own drive - Make sure the drive can handle DMA. If you implement it and it works well enough that you don't notice the difference, go for it.:)
--Heh; yes, I was referring to "Turbo Basic" or "Power Basic", where you don't need line numbers and can do things like "gosub thisarea" and call named functions.:)
--It was quite a bit better than MS's native QuickBasic, although QB had some interesting features - such as viewing/editing user-defined functions in their own window.
--In case *you* didn't know, command syntax such as ' mem/c ' _without_ the space, was perfectly acceptable in DOS. Still works in Win98, in fact, at a command.com prompt.
--But if he's typing that from Start\Run, it could be an issue. Personally, for any kind of dos command, I always start command.com (or cmd.exe) 1st so I can see the error msgs (if any.)
--No, the TRUE BOFH's motto is something like this:
--"We're not happy until you're:" ( Choose 1 or more )
o Finished paying our blackmail fees
o Not calling us anymore, because we've "dealt with you" (and your now-deleted files) before
o Insane from having your critical files / password / pr0n collection repeatedly wiped; and gee, the backup seems to be (tragically) gone missing / erased as well...
o Seriously injured by a freak "accident" involving $computer-equipment
> The amazing end of the story was that my package was still stored at the motel when stopped to check when I returned the following year. I wasn't even staying at that motel that year.
--Hey, with that kind of service, maybe you should...
Slashdot Mirror
--I have vmware 3.x running on a Debian Linux 2.4 kernel (host.) Client environment boots Knoppix DVD beta fine with a 2.4 kernel, but crashes with a kernel panic on 2.6 kernels.
Note: Host == 2.4 kernel, VM client == 2.6 for testing (crashing.) Is there any 3rd-party fix for v3, or do I need v4 to test 2.6 kernels in the VM environment? (For various reasons I'm unwilling to migrate the host itself to 2.6.) TIA
> I believe the majority of VMWare workstation sales are on Windows.
--Perhaps. I prefer to be in the minority though; my Vmware Workstation 3.x license is for a Linux host. I wouldn't even *consider* running Vmware on a typical Windows install (as a host) - when, not if, the box crashes, it would take the VM environment(s) with it. Linux == stability, for me.
--I agree, this article seems a bit premature since there's nothing to DL on the Serenity website yet. Their logo looks pretty cool tho. Eventually it will be nice for VMware to have some competition.
--Yah - the lawyers. They're the only ones left though.
--I have a Toshiba Tecra P166 laptop that has Cardbus/PCMCIA switchable in the BIOS. When I bought it 2ndhand it was set to PCMCIA. A quick BIOS change and a reinstall of W98SE, and now it runs Cardbus.
--You can really notice the speed difference; I have an SMC Ethernet PCCard that's compatible with both settings, and it runs noticeably better under 32-bit mode.
--The original Heavy Metal movie, IMHO, is *much* better than the "sequel." Watch them in order if you can.
Slashdot poll - should "Debian Experimental be named Dexter?" (After Dexter's Lab cartoon ;-)
--Oops, sorry - after reading grc for a while, it appears that click-death it NOT a problem with the disk, more of a problem with the drive firmware. They put it as: "Click Death is almost, but not quite, never contagious." Sorry.
http://grc.com/tip/codfaq4.htm
--I have an original parallel Zip 100 drive that still works reliably (altho admittedly I don't use it much these days.)
:)
--In addition, I have an internal ATAPI drive and a USB 1.1 external drive, both 100's, that are used several times a week for critical-file Linux backups. Never had a ClickOfDeath on any of 'em. However, I bought pretty much all of my Zip disks early on - the original disks are still running fine.
--I could be wrong, but IIRC the COD problem was with the *disks*, not the drives. A bad disk could trash several drives. See grc.com for more details.
http://grc.com/tip/clickdeath.htm
"No sir! I didn't see you playing with your dolls again!" == Colonel Sandurz, in what may possibly be *the* single most disturbing scene in Spaceballs
--What, you work for Baxter Labs??
--One word that helps me to retain my fragile sanity in a sea of economic madness:
Motorcycling.
--If you think you might enjoy it, take a safety course to get your license. It is *definitely* worth the training.
--It actually shouldn't be *that* hard to get rescued, at least within a 12-24 hour period. Simply tell a friend you're going to Chernobyl; and if they don't hear from you by $time, send out the search party.
--Yep, I'm a biker myself; and nothing turns me on faster than a biker-chick - especially if she's got red hair.
--Ah yes, Lotus Notes and Wine - I bet if you check, (run "top" and then hit the M key) there's your memory hog. There's no need to buy a new system, however - that's not what I was saying.
--But notice - even with all that running at once, you're still using much less than 256MB of swap. You could probably resize that 1GB down to half that, or even 300MB - and still have plenty of leeway. If you're using KDE, I'd consider switching to a more lightweight WM (I use Sawfish, but that's prolly too bare-bones for most people) and you'll save even more resources.
+6 Insightful / Informative (Funny? yet sadly true)
--You should write a nasty complaint letter to the president, mebbe they'll come around again... :b
--Ah yes, vmware does work better with large amounts of memory. But as far as swap goes, it's still something that should be monitored:
:-)
Before vmware (Win98 session, with 164MB of Ram alloc:)
free
total used free shared buffers cached
Mem: 516196 232612 283584 0 24876 85448
-/+ buffers/cache: 122288 393908
Swap: 771040 0 771040
--Same machine, with vmware session running (no programs active in the VM yet, just OS)
free
total used free shared buffers cached
Mem: 516196 400996 115200 0 30616 233340
-/+ buffers/cache: 137040 379156
Swap: 771040 0 771040
--And now Opera running in the VM session, with 6 windows open:
free
total used free shared buffers cached
Mem: 516196 460160 56036 0 32272 288116
-/+ buffers/cache: 139772 376424
Swap: 771040 0 771040
--Note that the swap usage is *still* Zero.
--As far as EMACS goes... Well, there's always "jstar".
--You shouldn't follow such advice blindly, without monitoring how much swap actually gets USED... Otherwise that 1GB of disk is completely wasted.
/dev/hda5 partition 257000 0 3
/dev/hdb5 partition 514040 0 3
:)
k g- hateititssodamnstupid-fixtheidiotlamenessfilteryou lazy-ass-sysadmins
--Example: 900MHz AMD Duron, 512MB RAM
swapon -s
Filename Type Size Used Priority
free
total used free shared buffers cached
Mem: 516196 232612 283584 0 24876 85448
-/+ buffers/cache: 122288 393908
Swap: 771040 0 771040
--Note that the swap "Used" count is Zero.
--Granted, all I have running ATM is Opera, rxvt, Konsole, Sawfish and a few daemons. But even recompiling the kernel will only use <100MB of RAM (usually much less.)
--Monitor how much swap you use on a daily basis with various tasks. I'll bet you can resize your swap partition down to == the RAM or even a bit less, if you're not worried about suspend-to-disk.
--From personal experience, the more RAM you have - the less swap you need. If you have installed 256MB-512MB of RAM, unless you're *really* pushing the machine, you only "need" about 300MB of swap.
--If you've got ~128MB of RAM (typical older Windoze machine), 300-400MB of swap should be fine even if you're running KDE, XMMS, and a kernel compile all at once.
--1GB of swap actually being *used* is almost unheard of, even if you only have 64MB of RAM; the machine would be so slow as to be almost unusable, and eventually the hard drive would go up in flames from disk thrash. (I've seen it happen with XP. I think the client had only 128MB of RAM installed, and XP swap thrash forced us to reinstall and repartition the disk around the bad sectors.)
--AFA putting the swap on its own drive - Make sure the drive can handle DMA. If you implement it and it works well enough that you don't notice the difference, go for it.
stupidassfkgslashdotlamenessfilter-POS-Ireallyf
--Heh; yes, I was referring to "Turbo Basic" or "Power Basic", where you don't need line numbers and can do things like "gosub thisarea" and call named functions. :)
--It was quite a bit better than MS's native QuickBasic, although QB had some interesting features - such as viewing/editing user-defined functions in their own window.
--In case *you* didn't know, command syntax such as ' mem/c ' _without_ the space, was perfectly acceptable in DOS. Still works in Win98, in fact, at a command.com prompt.
--But if he's typing that from Start\Run, it could be an issue. Personally, for any kind of dos command, I always start command.com (or cmd.exe) 1st so I can see the error msgs (if any.)
--No, the TRUE BOFH's motto is something like this:
--"We're not happy until you're:" ( Choose 1 or more )
o Finished paying our blackmail fees
o Not calling us anymore, because we've "dealt with you" (and your now-deleted files) before
o Insane from having your critical files / password / pr0n collection repeatedly wiped; and gee, the backup seems to be (tragically) gone missing / erased as well...
o Seriously injured by a freak "accident" involving $computer-equipment
o Gone / Mysteriously Disappeared / Fired
o Dead (see "Freak accident", above)
~;-)
BOFH
--Dude - when's the last time you had a vacation??
> The amazing end of the story was that my package was still stored at the motel when stopped to check when I returned the following year. I wasn't even staying at that motel that year.
--Hey, with that kind of service, maybe you should...
--Hey, did they ever find out who shot him?
;-)