On 9/13/2018 11:35 PM, Michael van Elst wrote:
netbsd-embed...@gmx.com (Don NetBSD) writes:
| > SMART [...] so it is clearly possible.
|
| I think only via wd(4)?
Oh, you mean, not sd(4) - yes, possibly. Sorry, I have no idea how
one would access that kind of data over scsi.
netbsd-embed...@gmx.com (Don NetBSD) writes:
>>| > SMART [...] so it is clearly possible.
>>|
>>| I think only via wd(4)?
>>
>> Oh, you mean, not sd(4) - yes, possibly. Sorry, I have no idea how
>> one would access that kind of data over scsi.
>I will have to keep poking through
On 9/11/2018 11:16 AM, Mike Pumford wrote:
[attrs elided]
I've done a lot of work with SAS disk enclosures that support SES. They
often have an SES command that can turn off the drive in a bay prior to
removal (but support is optional).
Aren't standards *wonderful*? What value to
On 9/11/2018 6:28 AM, Robert Elz wrote:
Date:Tue, 11 Sep 2018 00:19:57 -0700
From:Don NetBSD
Message-ID: <3cedac34-90d8-78ff-b320-de2c5ac8c...@gmx.com>
| [should I be "reply all" or just the list? I guess a matter of personal
| preferences?]
It usually
On 10/09/2018 23:39, Don NetBSD wrote:
On 9/10/2018 11:33 AM, Mike Pumford wrote:
On 10/09/2018 01:49, Don NetBSD wrote:
I'm not concerned with automatically detecting insertion/removal; that's
the job that the operator performs (above) -- along with the tagging of
the media, etc.
I've
Date:Tue, 11 Sep 2018 00:19:57 -0700
From:Don NetBSD
Message-ID: <3cedac34-90d8-78ff-b320-de2c5ac8c...@gmx.com>
| [should I be "reply all" or just the list? I guess a matter of personal
| preferences?]
It usually makes little difference - it certainly makes no
On 9/10/2018 11:03 PM, Michael van Elst wrote:
On Mon, Sep 10, 2018 at 05:37:53PM -0700, Don NetBSD wrote:
So, I can use the 'd' partition to access the medium (after unlocking the label
portion). But, I can't count on anything else "displayed" by disklabel. And,
I can't count on even the
Date:Mon, 10 Sep 2018 17:37:53 -0700
From:Don NetBSD
Message-ID:
| So, I can use the 'd' partition to access the medium (after unlocking the
label
| portion). But, I can't count on anything else "displayed" by disklabel.
And,
| I can't count on even the
On 9/9/2018 10:26 PM, Michael van Elst wrote:
On Sun, Sep 09, 2018 at 05:49:15PM -0700, Don NetBSD wrote:
On 9/9/2018 1:52 PM, Michael van Elst wrote:
On Sun, Sep 09, 2018 at 12:08:14PM -0700, Don NetBSD wrote:
Said another way, are these "in-kernel" values (which no longer reflect
the
On 9/10/2018 11:33 AM, Mike Pumford wrote:
On 10/09/2018 01:49, Don NetBSD wrote:
I'm not concerned with automatically detecting insertion/removal; that's
the job that the operator performs (above) -- along with the tagging of
the media, etc.
I've done a lot of work with SAS disk enclosures
On 10/09/2018 01:49, Don NetBSD wrote:
I'm not concerned with automatically detecting insertion/removal; that's
the job that the operator performs (above) -- along with the tagging of
the media, etc.
I've done a lot of work with SAS disk enclosures that support SES. They
often have an SES
On Sun, Sep 09, 2018 at 05:49:15PM -0700, Don NetBSD wrote:
> On 9/9/2018 1:52 PM, Michael van Elst wrote:
> > On Sun, Sep 09, 2018 at 12:08:14PM -0700, Don NetBSD wrote:
> > > Said another way, are these "in-kernel" values (which no longer reflect
> > > the physical medium) ever reported in other
On Sun, Sep 09, 2018 at 12:08:14PM -0700, Don NetBSD wrote:
> Which begs the question, why are these presumably immutable parameters
> allowed to be altered in even the in-kernel copy of the label? Why are
> attempts at altering them (sectors/track, etc.) not ignored completely?
It could be a
On 9/8/2018 11:55 PM, Michael van Elst wrote:
netbsd-embed...@gmx.com ("Don NetBSD") writes:
My understanding is that the 'd' partition is intended to reference the
entire medium. But, a simple test (disklabel -e) indicates that I can
create an arbitrary (start,size) for that partition. So,
netbsd-embed...@gmx.com ("Don NetBSD") writes:
>My understanding is that the 'd' partition is intended to reference the entire
>medium. But, a simple test (disklabel -e) indicates that I can create an
>arbitrary (start,size) for that partition. So, I could potentially encounter
>a foreign
I have to design an appliance to accept "foreign" disks (sd(4) and wd(4)) and
massage them into a form/content suitable for deployment (in yet another
appliance).
My understanding is that the 'd' partition is intended to reference the entire
medium. But, a simple test (disklabel -e) indicates
16 matches
Mail list logo
