View Single Post

   
  #9 (permalink)  
Old 02-20-2008, 07:31 AM
+Alan Hicks+
 
Posts: n/a
Default Re: SATA +slack 10.1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Trim your posts. There is absolutely no need to quote everything, only
that which is necessary to maintain context.

In alt.os.linux.slackware, BenneJezzerette dared to utter,
>> So in other words, aside from supporting _one_ additional piece of
>> hardware and the JFS filesystem, jfs.s is identical to bare.i. Now
>> tell me, why in Bob's name would you recomend some one use the jfs.s
>> kernel and reiserfs?

>
> Ok, aside from the rant on me, bare.i did not even like my system.
> reiserfs and jfs.s were the only settings I could actually get to work.


Immaterial. Correlationg does not necessarily indicate causation.
Unless by chance you had a hard drive on the one scsi controller that
jfs.s supports that bare.i doesn't, there's no reason why bare.i
wouldn't work on your hardware.

> The nice thing is the Journaling file system. Rather than a bunch of
> small partitions like old UNIX was.


This has nothing to do with journaling. ext2 supports rather large
partitions just like reiserfs. In fact, I don't know when a
filesystem's maximum partition size has ever come up IME outside of DOS
and FAT filesystems.

> Mixing bare.i, or speak or any other one, the system
> gets a 40 40 40 40 40 40 40 40 40 40 40 boot error. Does this help?


Indeed. JFGI[0] and you'll figure it out I'm sure. This is a
boot-loader error message that indicates that for some reason, LILO was
not able to locate the kernel (or possibly the System.map file, I
forget which, though I suspect the kernel).

[0] http://jfgi.us

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCVZCdvgVcFKpJf4gRAmN/AKCs+diE/lxDwPioT3NSflEtKXwTWQCfcO1c
qBVdhIFlfSDcRA5331HxIrU=
=RzpO
-----END PGP SIGNATURE-----
Reply With Quote