Welcome, Guest. Please login or register.

Author Topic: SFS boot partition?  (Read 3774 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Croyzers

  • Newbie
  • *
  • Join Date: Dec 2002
  • Posts: 49
    • Show all replies
Re: SFS boot partition?
« on: August 20, 2003, 02:15:22 PM »
Doesn't the boot partition have to be FFS for Kickstart to be able to read it? I'm pretty sure it does. Anyway, you could have a really small boot partition that contains the startup-sequence but then have your C: Fonts: an another partition. You would have to load up the drivers for SFS file-system somehow (on the FFS partition) and modify the Paths in startup-sequence to point to the new partition. Just a thought.
 

Offline Croyzers

  • Newbie
  • *
  • Join Date: Dec 2002
  • Posts: 49
    • Show all replies
Re: SFS boot partition?
« Reply #1 on: August 20, 2003, 02:57:52 PM »
@Rassilon
Quote

No the boot partition doesn't have to be FFS. As long as SFS is installed in the RDB of the HD, kickstart will be able to read it and access the drive.



Oh yeah, of course! You are quite right in that respect. It must have completely slipped my mind. I think I was getting confused with the ~4 Gig limit of the boot partition. This is because the scsi.device in Kickstart is only 32 bits. DON'T, whatever you do, have a boot partition bigger than 4 Gigs. Trust me, you will regret it.  A friend of mine was very upset after leaving a batch script working overnight, found out some of his boot partition had been overwritten. (And no, it wasn't a virus). This was even using a DirectScsi patch aswell, so he must have used PFS.

[edit] I've just checked and I've got my first red & white checker! Yeeah!