Miscellaneous > The Lounge
HAHAHA this is funny
jtpenrod:
quote: What? I've never had a problem with this. It sounds to me like you are running a UMSDOS installation of Linux, or
you have your Linux kernel booted from your Win partition using something like loadlin.exe, in which case running a
defrag would certainly cause this problem.
--- End quote ---
I have Mandrake on its own ext2 partition. According to Partition Magic, I have one primary partition that's just a bit over 3.0GB for Winders. The rest of the HD is an extended partition that includes the ext2 root and home partitions, and the swap partition. I'm using GRUB as the boot loader.
quote: But if you have your entire Linux distribution including the kernel and boot
code all on it's own ext2/ext3 partition defrag can't touch it. DOS/Win has no idea how to get outside of it's brain
dead filesystem.
--- End quote ---
It is. And it seems as if DOS/Win just learned a new trick here. Defrag just fucked *everything* up. I certainly wasn't expecting that either. But it did happen.
voidmain:
quote:Originally posted by Centurian:
Hmmm While I am on the subject what is the difference between the Ext2 and Ext3 filesystems?
--- End quote ---
It's the Linux version of JFS. It basically adds filesystem journaling to ext2 (which is a good thing). I'm running ext3 on all my RedHat 7.2 machines and I love it so far. If you trip over the power cable or the power goes out and your system goes down uncleanly you don't have to wait the minute or more of fsck time on the next system startup, it's nearly instant.
I used to use JFS on IBM RS6000s running AIX. IBMs JFS was more robust as it also allowed you to resize your filesystems on the fly on a running system in addition to the reliability in the event of a power outage and the like.
In fact it looks like IBM has ported their JFS to Linux as well as SGI porting XFS to Linux which are also journaled filesystems. According to http://www.mandrakeforum.com/article.php?sid=1212 ext3 is the lowest performing of the 4 filesystems (I haven't noticed any difference between ext2 and ext3 personally but I sure like the difference in fsck time of ext3 over ext2).
voidmain:
quote:Originally posted by jtpenrod:
It is. And it seems as if DOS/Win just learned a new trick here. Defrag just fucked *everything* up. I certainly wasn't expecting that either. But it did happen.
--- End quote ---
Hmm, what version of DOS/Win are you using? I've been dual booting lotsa machines since about '93 and maybe I've just been lucky that this hasn't happened to me. I assume you are using the Linux version of GRUB and the kernel along with GRUB reside on your linux partition in /boot, and /boot/grub?
Very interesting... Wonder if anyone else has had this problem. It truly is the first time I've heard of such a thing (shouldn't surprise me though, after all we are talking about Microshit).
jtpenrod:
quote:Hmm, what version of DOS/Win are you using? ...I assume you are using the Linux version of GRUB and the kernel along with GRUB reside on your linux partition in /boot, and /boot/grub?
--- End quote ---
I have Win 95B, and I'm using the version of GRUB that came on the Mandrake CDs, and there is indeed a /boot/grub partition. I set this up during the install in "expert" mode. (I did the default Mandrake install on the old system that had Win 95 in the first place - with just a hair over rwo gigs on the HD, there wasn't enough room for both.) I did the expert install twice on this rig.
When Win 95 was first released, M$ was in the midst of the battle of the bootloaders with the OEMs and BeOS. (Guess who lost? ;) :eek: ) That's why I wonder what's *really* going on here: is there something in Defrag that was secretly intended to nuke BeOS on the dual boot machines that the OEMs were offering at the time? Given the track record: the sabotaging of DR-DOS, Blue Mountain electronic greeting cards, the "service packs" that sabotaged Samba and Quick Time... really makes you wonder, doesn't it? Perhaps Win/DOS isn't quite so brain-dead after all?
voidmain:
I would think it is more likely that it was a "problem" with Defrag that caused your system to crap due to bad programming (bad programming is rampant at Microsoft). I will consider myself lucky that it didn't happen to me, the worst defrag has ever done to me was screw up my Windows installation.
One thing that is different on your scenerio, I can't say that I have ever run defrag with the GRUB loader installed. It has always been with LILO and have used various versions of DOS/Win95/98/NT/2k/OS2 multiboot configs and have never had a problem. I did use GRUB for a while after installing RH72 on many of my machines but I don't believe I ran a defrag in Windows since that time (very rarely am I in Windows natively, usually if I need to use it, it's in a VMware session).
Now, couple of nights ago I ditched GRUB (although I like it) for the LILO that comes with the SuSe distribution, for the cool animated graphical boot screens (screens downloaded separately, see the message posted a couple of days ago regarding this subject).
And personally, Windows is on the endagered species list in my house, it's nearly extinct.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version