Re: devfs and /proc/ide/hda

2001-04-27 Thread Richard Gooch
AJ Lewis writes: > > --CblX+4bnyfN0pR09 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Thu, Mar 08, 2001 at 01:32:03PM +0100, Goswin Brederlow wrote: > > > What it should do is change based on whether devfs is

Re: devfs and /proc/ide/hda

2001-04-27 Thread AJ Lewis
On Thu, Mar 08, 2001 at 01:32:03PM +0100, Goswin Brederlow wrote: > > What it should do is change based on whether devfs is mounted > > or not. It doesn't make *any* sense to have > > /dev/ide/host0/foo/bar in your /proc/partitions entries if you > > aren't mounting devfs.

Re: devfs and /proc/ide/hda

2001-04-27 Thread Goswin Brederlow
> " " == AJ Lewis <[EMAIL PROTECTED]> writes: > On Wed, Feb 28, 2001 at 04:10:23PM +0100, Guest section DW > wrote: >> On Wed, Feb 28, 2001 at 08:52:54PM +1100, Glenn McGrath wrote: >> >> > Im running kernel 2.4.1, I have entries like /proc/ide/hda, > >>

Re: devfs and /proc/ide/hda

2001-04-27 Thread Goswin Brederlow
== AJ Lewis [EMAIL PROTECTED] writes: On Wed, Feb 28, 2001 at 04:10:23PM +0100, Guest section DW wrote: On Wed, Feb 28, 2001 at 08:52:54PM +1100, Glenn McGrath wrote: Im running kernel 2.4.1, I have entries like /proc/ide/hda, /proc/ide/ide0/hda etc

Re: devfs and /proc/ide/hda

2001-04-27 Thread AJ Lewis
On Thu, Mar 08, 2001 at 01:32:03PM +0100, Goswin Brederlow wrote: What it should do is change based on whether devfs is mounted or not. It doesn't make *any* sense to have /dev/ide/host0/foo/bar in your /proc/partitions entries if you aren't mounting devfs. The

Re: devfs and /proc/ide/hda

2001-04-27 Thread Richard Gooch
AJ Lewis writes: --CblX+4bnyfN0pR09 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 08, 2001 at 01:32:03PM +0100, Goswin Brederlow wrote: What it should do is change based on whether devfs is mounted

Re: devfs and /proc/ide/hda

2001-03-01 Thread AJ Lewis
On Wed, Feb 28, 2001 at 04:10:23PM +0100, Guest section DW wrote: > On Wed, Feb 28, 2001 at 08:52:54PM +1100, Glenn McGrath wrote: > > > Im running kernel 2.4.1, I have entries like /proc/ide/hda, > > /proc/ide/ide0/hda etc irrespective of wether im using devfs or > > traditional device names. >

Re: devfs and /proc/ide/hda

2001-03-01 Thread AJ Lewis
On Wed, Feb 28, 2001 at 04:10:23PM +0100, Guest section DW wrote: On Wed, Feb 28, 2001 at 08:52:54PM +1100, Glenn McGrath wrote: Im running kernel 2.4.1, I have entries like /proc/ide/hda, /proc/ide/ide0/hda etc irrespective of wether im using devfs or traditional device names. Is

Re: devfs and /proc/ide/hda

2001-02-28 Thread Guest section DW
On Wed, Feb 28, 2001 at 09:29:24PM +1100, Glenn McGrath wrote: > Well leaving it the way it is doesnt make much sense either really, it > refers to devices that dont exist. You are mistaken. The existence of a device is unrekated to the name someone uses to access it. You may well use

Re: devfs and /proc/ide/hda

2001-02-28 Thread Guest section DW
On Wed, Feb 28, 2001 at 08:52:54PM +1100, Glenn McGrath wrote: > Im running kernel 2.4.1, I have entries like /proc/ide/hda, > /proc/ide/ide0/hda etc irrespective of wether im using devfs or > traditional device names. > > Is always using traditional device names for /proc/ide intentional, or >

Re: devfs and /proc/ide/hda

2001-02-28 Thread Pierre Rousselet
Glenn McGrath wrote: > Helge Hafting wrote: > >> Glenn McGrath wrote: >> >>> Im running kernel 2.4.1, I have entries like /proc/ide/hda, >>> /proc/ide/ide0/hda etc irrespective of wether im using devfs or >>> traditional device names. >>> >>> Is always using traditional device names for

Re: devfs and /proc/ide/hda

2001-02-28 Thread Glenn McGrath
Helge Hafting wrote: > > Glenn McGrath wrote: > > > > Im running kernel 2.4.1, I have entries like /proc/ide/hda, > > /proc/ide/ide0/hda etc irrespective of wether im using devfs or > > traditional device names. > > > > Is always using traditional device names for /proc/ide intentional, or > >

Re: devfs and /proc/ide/hda

2001-02-28 Thread Helge Hafting
Glenn McGrath wrote: > > Im running kernel 2.4.1, I have entries like /proc/ide/hda, > /proc/ide/ide0/hda etc irrespective of wether im using devfs or > traditional device names. > > Is always using traditional device names for /proc/ide intentional, or > is it something nobody has gotten

Re: devfs and /proc/ide/hda

2001-02-28 Thread Helge Hafting
Glenn McGrath wrote: Im running kernel 2.4.1, I have entries like /proc/ide/hda, /proc/ide/ide0/hda etc irrespective of wether im using devfs or traditional device names. Is always using traditional device names for /proc/ide intentional, or is it something nobody has gotten around to

Re: devfs and /proc/ide/hda

2001-02-28 Thread Glenn McGrath
Helge Hafting wrote: Glenn McGrath wrote: Im running kernel 2.4.1, I have entries like /proc/ide/hda, /proc/ide/ide0/hda etc irrespective of wether im using devfs or traditional device names. Is always using traditional device names for /proc/ide intentional, or is it something

Re: devfs and /proc/ide/hda

2001-02-28 Thread Pierre Rousselet
Glenn McGrath wrote: Helge Hafting wrote: Glenn McGrath wrote: Im running kernel 2.4.1, I have entries like /proc/ide/hda, /proc/ide/ide0/hda etc irrespective of wether im using devfs or traditional device names. Is always using traditional device names for /proc/ide intentional, or

Re: devfs and /proc/ide/hda

2001-02-28 Thread Guest section DW
On Wed, Feb 28, 2001 at 08:52:54PM +1100, Glenn McGrath wrote: Im running kernel 2.4.1, I have entries like /proc/ide/hda, /proc/ide/ide0/hda etc irrespective of wether im using devfs or traditional device names. Is always using traditional device names for /proc/ide intentional, or is it

Re: devfs and /proc/ide/hda

2001-02-28 Thread Guest section DW
On Wed, Feb 28, 2001 at 09:29:24PM +1100, Glenn McGrath wrote: Well leaving it the way it is doesnt make much sense either really, it refers to devices that dont exist. You are mistaken. The existence of a device is unrekated to the name someone uses to access it. You may well use