Linux Sucks #1,932,453
Dec. 17th, 2005 10:19 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
loosechanjhttp://bugs.centos.org/view.php?id=1110
http://forums.fedoraforum.org/showthread.php?t=29434&page=2
What an ab-so-fucking-lutely craptastic saga of pain and tears to find that answer too. The question? Baby Jesus wants to read his ntfs drives. That's all. It's not that world shaking a request I don't think. But you think I'd be having multiple orgasms for all the trouble it took me.
[EDIT: But NOOOOOOOOOOOOOO, the fecking thing broke with the same "no aix module found" that the sources I d/l'ed from kernel.org did. Fucking shite.[1]
And while we're on the subject, just what in the fudge fucktory's manual o' fuckedness is the point of "Ok. Uncompressing linux"? Maybe I just haven't found that clue basket yet, but don't executables generally make pretty bad fodder for compression? And wouldn't compression just take time?
Also, wtf is the point of "redhat nash", other than making your boot take 10x as long?
And oh yeah, freebsd needs to support bigger fat32 drives, 'k?
/*Takes a half bottle of fuckitall and reboots into windows*/
[1] In contrast, getting openbsd to see my 200 gig fat32 partition (which freebsd chokes on as well!) was all of maybe 4 or 5 commands, including "mount". OpenBSD > *.
http://forums.fedoraforum.org/showthread.php?t=29434&page=2
What an ab-so-fucking-lutely craptastic saga of pain and tears to find that answer too. The question? Baby Jesus wants to read his ntfs drives. That's all. It's not that world shaking a request I don't think. But you think I'd be having multiple orgasms for all the trouble it took me.
[EDIT: But NOOOOOOOOOOOOOO, the fecking thing broke with the same "no aix module found" that the sources I d/l'ed from kernel.org did. Fucking shite.[1]
And while we're on the subject, just what in the fudge fucktory's manual o' fuckedness is the point of "Ok. Uncompressing linux"? Maybe I just haven't found that clue basket yet, but don't executables generally make pretty bad fodder for compression? And wouldn't compression just take time?
Also, wtf is the point of "redhat nash", other than making your boot take 10x as long?
And oh yeah, freebsd needs to support bigger fat32 drives, 'k?
/*Takes a half bottle of fuckitall and reboots into windows*/
[1] In contrast, getting openbsd to see my 200 gig fat32 partition (which freebsd chokes on as well!) was all of maybe 4 or 5 commands, including "mount". OpenBSD > *.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2005-12-20 12:59 am (UTC)Also, another kernel/userland linkage example... device management under Solaris (prtconf(1), devfsadm(1M), add_drv(1M), drvconfig(1M)), AIX (cfgmgr(1), lsdev(1)), and HP-UX (lsdev(1M), insf(1M)) are different, including (mostly) in the command line tools' names, but are all appropriate to the device recognition structure under each OS. The same is true under NetBSD (and Mac OS X, for that matter). But what's different here is that all of those do the same thing on all of their processor architectures (admittedly, Solaris is the only one with anything that even a two-fingered, zero-toed man would call "many" besides NetBSD, but ignore that for now). Linux distributions pretend that this is true... but they use different things on the same damn piece of hardware, never mind different architectures. I view this with distaste and disdain.