View Single Post
Old 10-31-2012, 02:04 PM   #12
EternalCyclist
Member
EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.
 
Posts: 17
Karma: 17948
Join Date: Oct 2012
Device: KT
Quote:
Originally Posted by geekmaster View Post
You may need to adjust the values in /var/local/mntusb.params (I think) to match your new partition layout...
On my K5 I have only /var/local/system/mntusb.params and the first line says
"# auto-generated file -- do not modify!"

then:
Code:
# computed values
MNTUS_PART_START=16
MNTUS_PART_SIZE=1257496
MNTUS_PART_OFFSET=8192
The computation is actually pretty good. ;-)

PART_SIZE matches fdisk size output.

PART_OFFSET is the position of the secondary FAT.

Not matching the second part of mntusb.params could bring some speed loss - I gess.
Code:
# constant values
# FAT32 fs
MNTUS_FATSIZE=32
# Align fs data to 4MB boundary
MNTUS_ALIGNMENT_MB=4
# Use 8k cluster size for better write performance
MNTUS_SECTORS_PER_CLUSTER=16
EternalCyclist is offline   Reply With Quote