Bug#661575: lsof on Hurd

2012-04-24 Thread Nicholas Bamber

tag 661575 +help
forwarded 661575 a...@purdue.edu
thanks

Abe,
Thanks again for your work on lsof.

	There seems to be no support in the lsof code for the Hurd operating 
system. I cannot say I am surprised but it does I believe meet your 
criteria for support as it is readily available for download and 
installation as per http://www.debian.org/ports/hurd/ .


	I have copied the Debian Hurd mailing list as they are most likely to 
be able to provide patches and advice.


Thanks. Nicholas



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#661575: lsof on Hurd

2012-04-24 Thread Samuel Thibault
Nicholas Bamber, le Tue 24 Apr 2012 22:33:15 +0100, a écrit :
   There seems to be no support in the lsof code for the Hurd operating
 system. I cannot say I am surprised but it does I believe meet your criteria
 for support as it is readily available for download and installation as per
 http://www.debian.org/ports/hurd/ .
 
   I have copied the Debian Hurd mailing list as they are most likely to be
 able to provide patches and advice.

Well, I don't think the Hurd already has interfaces for lsof to get any
information.  That would have to be added first...

Samuel



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#661575: lsof on Hurd

2012-04-24 Thread Nicholas Bamber

On 24/04/12 23:14, Samuel Thibault wrote:

Nicholas Bamber, le Tue 24 Apr 2012 22:33:15 +0100, a écrit :

There seems to be no support in the lsof code for the Hurd operating
system. I cannot say I am surprised but it does I believe meet your criteria
for support as it is readily available for download and installation as per
http://www.debian.org/ports/hurd/ .

I have copied the Debian Hurd mailing list as they are most likely to be
able to provide patches and advice.


Well, I don't think the Hurd already has interfaces for lsof to get any
information.  That would have to be added first...

Samuel


Samuel,
	AFAIK I think if the /proc filesystem had /proc/*/fd you'd be pretty 
much there. I guess I should have copied an upstream Hurd mailing list 
as well.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#661575: lsof on Hurd

2012-04-24 Thread Samuel Thibault
Nicholas Bamber, le Tue 24 Apr 2012 23:16:42 +0100, a écrit :
   AFAIK I think if the /proc filesystem had /proc/*/fd you'd be pretty 
 much
 there.

Of course, but that doesn't change the actual issue: I don't think there
is any interface to actually implement /proc/*/fd either.

 I guess I should have copied an upstream Hurd mailing list as well.

It does not matter very much actually: most upstream Hurd people are
also subscribed to debian-hurd.

Samuel



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#661575: lsof on Hurd

2012-04-24 Thread Roland McGrath
 Of course, but that doesn't change the actual issue: I don't think there
 is any interface to actually implement /proc/*/fd either.

See msg.defs.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#661575: lsof on Hurd

2012-04-24 Thread Samuel Thibault
Roland McGrath, le Tue 24 Apr 2012 16:34:52 -0700, a écrit :
  Of course, but that doesn't change the actual issue: I don't think there
  is any interface to actually implement /proc/*/fd either.
 
 See msg.defs.

That will give only ports to the fds.  How to get back to actual file
paths?

Samuel



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#661575: lsof on Hurd

2012-04-24 Thread Nicholas Bamber

On 25/04/12 00:42, Samuel Thibault wrote:

Roland McGrath, le Tue 24 Apr 2012 16:34:52 -0700, a écrit :

Of course, but that doesn't change the actual issue: I don't think there
is any interface to actually implement /proc/*/fd either.


See msg.defs.


That will give only ports to the fds.  How to get back to actual file
paths?

Samuel






That actually rings a bell from some other Hurd issue. Isn't there some 
bit of purest thinking that we have no right to assume that a file 
descripter actually implies a physical file, hence the question just 
cannot be asked. If that is so then the best Hurd might ever be able to 
offer lsof is the current /proc file system.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#661575: lsof on Hurd

2012-04-24 Thread Roland McGrath
 Roland McGrath, le Tue 24 Apr 2012 16:34:52 -0700, a écrit :
   Of course, but that doesn't change the actual issue: I don't think there
   is any interface to actually implement /proc/*/fd either.
  
  See msg.defs.
 
 That will give only ports to the fds.  How to get back to actual file
 paths?

Oh, well that's a different story (and one best discussed on bug-hurd).
There were past proposals about this, but I don't have a pointer.


Thanks,
Roland



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#661575: lsof on Hurd

2012-04-24 Thread Vic Abell
Nicholas,

You write:

   Thanks again for your work on lsof.
 
   There seems to be no support in the lsof code for the 
 Hurd operating 
 system. I cannot say I am surprised but it does I believe meet your 
 criteria for support as it is readily available for download and 
 installation as per http://www.debian.org/ports/hurd/ .
 
   I have copied the Debian Hurd mailing list as they are 
 most likely to 
 be able to provide patches and advice.
 
   Thanks. Nicholas

Thanks for the inquiry.  I am now 8 years into retirement and
have reduced lsof work to the minimum necessary to support a
few remaining dialects, including mainstream Linux.  As a
result I'm not inclined to take on a new port.

Since the lsof sources are open software with just a few
restrictions imposed by the Purdue copyright, it would be
permissible for someone else to do the Hurd port.

Regards,

Vic




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#661575: lsof on Hurd

2012-04-24 Thread Samuel Thibault
Nicholas Bamber, le Wed 25 Apr 2012 00:53:59 +0100, a écrit :
 That actually rings a bell from some other Hurd issue. Isn't there some bit
 of purest thinking that we have no right to assume that a file descripter
 actually implies a physical file, hence the question just cannot be asked.

There is sense in that, yes.  That can also happen on Linux actually,
when the file is removed.

The best you can have is what path was used to open it.  In the Hurd,
only the process itself knows.

 If that is so then the best Hurd might ever be able to offer lsof is the
 current /proc file system.

The process can be asked for the path.  It just has to avoid throwing it
away after opening it, and define an interface to fetch it.

Samuel



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org