mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: barry bouwsma <free_beer_for_all@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Proposal: kernel config option for default UFS filesystem
Date: Wed, 13 Aug 2008 02:37:07 -0700 (PDT)	[thread overview]
Message-ID: <618349.28606.qm@web46105.mail.sp1.yahoo.com> (raw)

Servus, Sportsfreunde!

I'm sharing my x86 machine with several flavours of BSDen, and
thereby wishing to mount the UFS filesystems under Linux.

Normally one has to specify the filesystem type, lest it otherwise
default to `old', which is for me, not useful.  In my case, a 44bsd
default would match all my filesystems used by NetBSD and FreeBSD.

I've recently been running with a hack to Kconfig, which lets me
select at config time, whether I wish to default to a different
ufstype.  For me, with oldconfig, it spits out something like...

UFS file system support (read only) (UFS_FS) [M/n/y/?] m
  UFS file system write support (DANGEROUS) (UFS_FS_WRITE) [Y/n/?] y
  UFS debugging (UFS_DEBUG) [N/y/?] n
Default UFS filesystem type
> 1. Old default (UFS_UFSTYPE_OLD)
  2. Sun x86 (UFS_UFSTYPE_SUNx86)
  3. Sun (UFS_UFSTYPE_SUN)
  4. SunOS (UFS_UFSTYPE_SUNOS)
  5. 44BSD (Free-, Net-, OpenBSD and friends) (UFS_UFSTYPE_44BSD) (NEW)
  6. UFS2 as added to 44BSD systems (UFS_UFSTYPE_UFS2)
  7. HP (UFS_UFSTYPE_HP)
  8. NeXTStep CD (UFS_UFSTYPE_NEXTSTEP_CD)
  9. NeXTStep (UFS_UFSTYPE_NEXTSTEP)
  10. OpenStep (UFS_UFSTYPE_OPENSTEP)
choice[1-10?]: 5

Is this something worthy of further cluttering up the kernel config
for my convenience, or not, given that there is no way presently to
automagically determine the proper UFS filesystem type at mount?


If it is, I'll post my hacks for ridicule and derision.


thanks,
barry bouwsma


      


             reply	other threads:[~2008-08-13  9:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13  9:37 barry bouwsma [this message]
2008-08-13 15:25 ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=618349.28606.qm@web46105.mail.sp1.yahoo.com \
    --to=free_beer_for_all@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®