What corporation do you own 10% of that does not confer limited liability to you via the concept of corporate personhood? In order to sue you personally they'd have to "pierce the corporate veil" which doesn't happen very often. I think you're BSing here.

Um, dude. That statement by itself isn't racist. The policy that the statement is meant to defend by camouflaging it, RACIAL PROFILING, is racist. And the statement is wrong. Studies (that I do not have links for, sorry) have shown that after dark when the race of a person driving a car is harder to see the racial disparity in traffic stops decreases.

Of COURSE they don't know how much a voluntary insurance plan is going to cost, since they can't FORCE you to sign up for it! Blue Cross doesn't know how much their plan costs in advance either.

Oh jeez this sounds like tin-foil hat wearing conspiracy theories. Require. Force. Government Takeover. Give me a break!

constant fscking is the bug, not the intended behaviour, dude. If I had KNOWN it would fsck every reboot I would have done that. Now that people have heard my experience maybe they will choose that option.

I did, and the the cause of the fscks was...(drumroll)..ext4.

oh cool, thanks

Hey genius! It's called SARCASM! There is no need to insult me for sharing my experiences with ext4. I am not some idiot who thinks RAID is a backup either.

I am NOT happy with ext4, but in case you needed to know more about my system, my ext4 data is a MIRROR of the ext3 data, and I have a LTO-2 ultirum drive to backup my filesystem regularly. I have off-site backups in fireproof waterproof safes.

  I also use e2image to get the metadata off the drive in case I need to reconstruct the contents.

Well, the fsck times are really fast compared to ext3, and thank god, because EVERY time I reboot it requires an fsck, complaining about group descriptor checksums. Even if I unmount my ext4 filesystem and remount it without rebooting it gets all fscked up. I have a 3TB ext4 fs on LVM on RAID, that was NOT converted from ext3, but built on brand new drives. My similar ext3 filesystem has had so such problems.

ext4 takes about 7 minutes to fsck, ext3 took hours. I hope they fix this soon.