een supported for several years now. I strongly recommend
you look at upgrading to at least 6.3.
>So, my question is: Is there any way to get file name knowing its descriptor?
The simple answer is no. That said, you could try having a look at
how lsof works (whilst it runs in userland, it n
:well, not really, at least not the name by which it was looked up.
:you MIGHT (sometimes) be able to use the directory name cache to work
:it out.. At one stage it was possible to do this for some percentage
:of the files but I dont remember if it was possible in 4.x.
:
:the idea is that you can
Uladzislau Rezki wrote:
Hi all,
I've been writing a small kernel module, that provides information about
modification of the filesystem to user_land/userspace through the
character device. I'm using FreeBSD 4.10
So, my question is: Is there any way to get file name knowing its
On Thu, 3 Jul 2008, Uladzislau Rezki wrote:
I've been writing a small kernel module, that provides information about
modification of the filesystem to user_land/userspace through the character
device. I'm using FreeBSD 4.10
So, my question is: Is there any way to get file name k
Hi all,
I've been writing a small kernel module, that provides information about
modification of the filesystem to user_land/userspace through the
character device. I'm using FreeBSD 4.10
So, my question is: Is there any way to get file name knowing its descriptor?
static int
xxx_wri
Hi all,
I've been writing a small kernel module, that provides information about
modification of the filesystem to user_land/userspace through the
character device. I'm using FreeBSD 4.10
So, my question is: Is there any way to get file name knowing its descriptor?
static int
xxx_wri
File a bug and I'll take a look at it.
Bonus if you can check this on -CURRENT; I
have fixed a bunch of problems in -CURRENT
that aren't yet merged into 6.x but I can't
remember right now if this is one of them.
Ti
Steven Hartland wrote:
Just had a really strange one, on a fresh 6.1 install
ta
On Sat, Jul 08, 2006 at 01:26:21AM +0100, Steven Hartland wrote:
> Just had a really strange one, on a fresh 6.1 install
> tar will not extract named files e.g.
> tar -xvzPf my.tar.gz /usr/local/etc/apache/httpd.conf
>
> The above fails to extract the file which quite
> clearly exists:
> tar -tvzP
Just had a really strange one, on a fresh 6.1 install
tar will not extract named files e.g.
tar -xvzPf my.tar.gz /usr/local/etc/apache/httpd.conf
The above fails to extract the file which quite
clearly exists:
tar -tvzPf my.tar.gz | grep /usr/local/etc/httpd.conf
-rw-r--r-- 0 root wheel 3720
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
org writes:
>Hi, as you know, we can create arbitaly file name on devfs.
>But for now, all file names on a devfs are encoded in ASCII.
>
>If we want to put Japanese file names in devfs, how should it
>be encoded? UTF-8 or som
Hi, as you know, we can create arbitaly file name on devfs.
But for now, all file names on a devfs are encoded in ASCII.
If we want to put Japanese file names in devfs, how should it
be encoded? UTF-8 or something convinient for the source encoding
ectory in the -I chain that the include file is
not in until it is found. If we could eliminate all those readdir scans
performance would improve dramatically.
Fundamentally, what I want to support is both UNIX clients (say, via NFS
etc) and Windows clients to be able to share files in the sa
Pawe³ Jakub Dawidek wrote:
> Nope. We are in kernel area.
> I want to control for example open() syscall:
> static int my_open(register struct proc *p, register struct open_args *ea)
> {
> [...]
> }
> Name of file to open is in ea->path, but this name can be: ./somefile
> and i need a full path to
) or like
+> that, and munmap() the memory. This is neither proper nor efficient way
+> to do that, but it's easy and it works. Note that in case of ./ or
+> several ../ in the file name you may need to do some extra processing
+> to get "correct" full path.
+>
Working!
d it works. Note that in case of ./ or
several ../ in the file name you may need to do some extra processing
to get "correct" full path.
Regards,
Eugene
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Mon, Feb 04, 2002 at 01:27:39AM -0800, Terry Lambert wrote:
+> char *saved_name;
+>
+> func()
+> {
+> char *foo;
+>
+> ...
+>
+> fd = open( foo, O_RDWR, 0664);
+> saved_name = strdup( foo);
+>
+> ...
+>
+>
Pawe³ Jakub Dawidek wrote:
> I can get vnode of changed file.
> I can get inode number of changed file.
> But how can i get file name?
>
> There is a way to get inode when i have file name and p (struct proc), so
> maybe there is a way to get file name from inode number and p
On Sun, Feb 03, 2002 at 11:54:58PM -0800, Alfred Perlstein wrote:
+> However there's a dirty way to get at it via the vfs lookup cache
+> entries hung off the vnode. Paul Saab showed me a delta that
+> did something nasty like this, but I've got no clue as to where
+> it is now.
+>
Hmm...
And w
* Pawel Jakub Dawidek <[EMAIL PROTECTED]> [020203 23:49] wrote:
> On Sun, Feb 03, 2002 at 10:11:37PM +0100, Pawel Jakub Dawidek wrote:
> +> But how can i get file name?
> +>
> [...]
> +> I got file name, but how can I get full path name for this file?
> +>
On Sun, Feb 03, 2002 at 10:11:37PM +0100, Paweł Jakub Dawidek wrote:
+> But how can i get file name?
+>
[...]
+> I got file name, but how can I get full path name for this file?
+>
Answer that there is no way to get that will be nice too.
--
Paweł Jakub Dawidek
Network Adminis
.
But how can i get file name?
There is a way to get inode when i have file name and p (struct proc), so
maybe there is a way to get file name from inode number and p.
And another thing for chflags syscall.
I got file name, but how can I get full path name for this file?
--
Paweł Jakub Dawidek
21 matches
Mail list logo
