Date: 24 Dec 2001 23:20:36 +0000 From: Wayne Pascoe <freebsd@molemanarmy.com> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Repost - f_type value in statfs structure Message-ID: <86n108ryrf.fsf@pan.home.penguinpowered.org.uk> In-Reply-To: <20011224090319.A7670@colnta.acns.ab.ca> References: <20011223023352.A5404@colnta.acns.ab.ca> <20011224000418.T2506-100000@coredump.scriptkiddie.org> <20011224090319.A7670@colnta.acns.ab.ca>
index | next in thread | previous in thread | raw e-mail
Chad David <davidc@acns.ab.ca> writes:
> > > They are local :). Local means that the fs originates on the local
> > > machine.
yes. I realise this now. Note to self, define what it is you are
trying to do before trying to do it :( I could have saved so much time
if I'd been clearer on that earlier.
> > > I think you should be able to call getvfsbyname() and check the flags in
> > > the resulting vfsconf struct for VFCF_SYNTHETIC, but I'm not sure how
> > > reliable that is. I'm pretty sure devfs is ok, but procfs might not be?
Hmm. I've ended up using getfsfile. I'm just checking that the first
4 characters of .fs_spec are /dev
I am working on the assumption that all filesystems I want to check
would be mounted out of /dev. Other things like proc and devfs
wouldn't be, so they would be skipped.
Is this a safe assumption ?
> > try vn_isdisk(vp, &error) where vp is the vnode pointer to the block
> > device?
> >
>
> He is trying to do this from userland, I think...?
Yes, I am. The kernel is faaaaaar beyond me for the forseeable
future.
Thanks for all the help. Merry Christmas and a hacky new year to all :)
--
- Wayne Pascoe
| WINDOWS: Where do you want to go today?
freebsd@molemanarmy.com | LINUX: Where do you want to go tomorrow?
http://www.molemanarmy.com | FreeBSD: Are you guys coming or what?
|
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86n108ryrf.fsf>