Skip to contentSkip to conversation

make cramfs look less hostile

PATCH Pascal Schmidt 2 participants 2 messages Jun 15, 2003 – Jun 16, 2003 8 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#8 lore raw

On Sun, 15 Jun 2003 20:30:11 +0200, you wrote in linux.kernel:

Quoted 3 lines

The only places where this should happen is mounting the rootfs. mount(8) has it's own filesystem type detection code and doesn't call mount(2) unless it found a matching filesystem type.

Not everybody uses mount(8) from util-linux... I don't think the more simplicistic versions in embedded systems will even want to do their own type detection. ;)

Signature · 2 lines
Ciao,
Pascal
#9 lore raw
Quoted 9 lines · Pascal Schmidt

On Sun, 15 Jun 2003 20:30:11 +0200, you wrote in linux.kernel:

Quoted 3 lines

The only places where this should happen is mounting the rootfs. mount(8) has it's own filesystem type detection code and doesn't call mount(2) unless it found a matching filesystem type.

Not everybody uses mount(8) from util-linux... I don't think the more simplicistic versions in embedded systems will even want to do their own type detection. ;)

These mount versions should at least pass down MS_VERBOSE then..