| To: | Thomas Graichen <graichen@xxxxxxxxxxxxx>, thomas.graichen@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: linux XFS FAQ available |
| From: | "Nathan Scott" <nathans@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 9 Aug 2000 14:38:16 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | Thomas Graichen <news-innominate.list.sgi.xfs@innominate.de> "Re: linux XFS FAQ available" (Aug 9, 12:54am) |
| References: | <news-innominate.list.sgi.xfs@innominate.de> <200008081438.JAA04805@jen.americas.sgi.com> <news2mail-8mp6l1$e0n$1@mate.bln.innominate.de> |
| Sender: | owner-linux-xfs-announce@xxxxxxxxxxx |
hi Thomas, On Aug 9, 12:54am, Thomas Graichen wrote: > Subject: Re: linux XFS FAQ available > ... > >>> Q: How do i use XFS ? > >>> Just reboot the new build kernel and create a filesytem on an empty > >>> partition > >>> > >>> mkfs_xfs /dev/foo > > > If you install the commands via a make install in the command tree then > > mkfs_xfs is installed as mkfs.xfs which means you can also use > > > mkfs -t xfs /dev/foo > > added > When I check in my mkfs changes (unless someone protests) I was planning to change the cmd/xfs/mkfs/Makefile such that mkfs.xfs is the only binary anywhere (i.e. there'll no longer be a "mkfs_xfs") - hopefully this will prevent any confusion, man page and other documentation discrepencies, etc. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | inode/vnode/xfs_inode locking, Daniel Moore |
|---|---|
| Next by Date: | Re: inode/vnode/xfs_inode locking, Russell Cattelan |
| Previous by Thread: | Re: linux XFS FAQ available, Nathan Scott |
| Next by Thread: | Re: linux XFS FAQ available, Thomas Graichen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |