Re: textvp_fullpath

On 16 August 2008 01:09:39 Robert Watson wrote: > On Fri, 15 Aug 2008, Uladzislau Rezki wrote: > > We have to to do a few thinks: > > > > 1) do original "write" sys call; > > 2) get full path (/etc/passwd); > > 3) put all this information to user land

Re: textvp_fullpath

On 14 August 2008 21:43:29 Roman Divacky wrote: > On Thu, Aug 14, 2008 at 09:20:12PM +0300, Uladzislau Rezki wrote: > > Hello folks, > > > > I'm using "textvp_fullpath" function to get full path from vnode up to > > root dir. The problem is that, someti

textvp_fullpath

ways to get full path? I haven't had any ideas yet, that is why I am asking you. Thanks. -- Uladzislau Rezki ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"

how can i get file name knowing its descriptor?

e to get a few web resources concerning FreeBSD kernel programming. Thanks. -- Uladzislau Rezki ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"

how can i get a file name knowing its descriptor?

gt;fd_ofiles[uap->fd]; /* get the vnode */ vn = (struct vnode *) file->f_data; /* do we have a regular */ if (vn->v_type == VREG) { ... ... ... } As you can see we just know uap->fd.

Re: block device

Rink Springer <[EMAIL PROTECTED]> writes: > Hi, > > On Thu, Dec 14, 2006 at 01:21:24PM +0200, Uladzislau Rezki wrote: >> ad0 is a character device. Why ad0 isn't a block device? > > FreeBSD 5 and up no longer make a distinction between character/block > device

block device

- 1 root operator0, 93 Dec 14 11:47 ad0s1c ad0 is a character device. Why ad0 isn't a block device? -- Uladzislau Rezki ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, s