#x27;all with (or write) the use
> of the adt_* audit interfaces. Let's stay intouch as you get
> to that part of the project.
>
> Gary..
>
-- next part --
A non-text attachment was scrubbed...
Name: ndmp_design.odt
Type: application/vnd.oasis.ope
This case was approved during today's PSARC meeting. Gary and I will
work offline with Alan to update the spec in the case directory.
- Bill
Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI
This information is Copyright 2007 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
SMF services for Xen addendum
1.2. Name of Document Author/Supplier:
Author: John Levon
1.3 Date of This Doc
On Wed, 2007-08-29 at 10:58 -0700, John Danielson wrote:
> On shutdown, we ask xend to shutdown all running domains and wait for this
> to complete (timing out after 6 minutes if no further progress is being
> made).
where did "6 minutes" come from? existing practice in the open-sourc
On Wed, Aug 29, 2007 at 02:09:11PM -0400, Bill Sommerfeld wrote:
> > On shutdown, we ask xend to shutdown all running domains and wait for
> > this
> > to complete (timing out after 6 minutes if no further progress is being
> > made).
>
> where did "6 minutes" come from? existing pr
I am sponsoring this case for Norm Jacobs.
Requested binding is minor, timeout 09/06/2007.
-Artem
Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI
This information is Copyright 2007 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
Automatic discovery of netw
> 1.1 Project/Component Working Name:
> Deletion of a KSTAT_FLAG_PERSISTENT kstat
This case was approved at today's PSARC meeting.
-Chris
Artem Kachitchkine writes:
> In order to better support these devices, this case seeks to extend the
> current HAL offering by adding a network attached device discovery
> service addon module and a probe module to probe network attached
> printers for identifying data. These modules will be conne
> Network Device Discovery
>
>
> Actual network device discovery will be handled by the HAL addon module
> named hald-addon-network-discovery. This module will be tied into the
> HAL device tree at /org/freedesktop/hal/devices/network_attached by
> configuration stored in
James Carlson wrote:
> Artem Kachitchkine writes:
>
>> In order to better support these devices, this case seeks to extend the
>> current HAL offering by adding a network attached device discovery
>> service addon module and a probe module to probe network attached
>> printers for identifying da
Norm Jacobs writes:
> James Carlson wrote:
> > I didn't see a reference here to RFC 1759 or 3805. Will this project
> > use any of the standardized Printer MIB interfaces, or does it only
> > support the enumerated vendor MIB entries and Host Resources?
> >
> The Printer-MIB prtInputVendorName,
Danek Duvall wrote:
>> Network Device Discovery
>>
>>
>> Actual network device discovery will be handled by the HAL addon module
>> named hald-addon-network-discovery. This module will be tied into the
>> HAL device tree at /org/freedesktop/hal/devices/network_attached by
On Wed, Aug 29, 2007 at 04:19:46PM -0500, Norm Jacobs wrote:
> The hald-addon-network-discovery module could be used to detect other types
> of network attached devices, like scanners or storage, but it is
> specifically looking for printers. The hald-probe-network-printer module
> is tied to
Danek Duvall wrote:
> If you can uniquely identify by serial number in some large percentage of
> the printers out there, that's probably good enough -- I bet people are
> more likely to recognize a printer by IP address than MAC address, if they
> need to get down to it.
The printers found autom
On Wed, Aug 29, 2007 at 02:56:24PM -0700, John Plocher wrote:
>The NIS maps have all 5,000 printers in them,
>I drop into a remote office and need to print,
>network discovery shows me the 3 printers that
>are somehow "near" me, making it rather
>intuitive which ones to
Danek Duvall wrote:
> in our environment, would all 5000
> printers show up, or some subset of those?
I assume that, like today, if the user has a ~/.printers file,
its "all:" entry will be used. If this is done naively, it could
completely hide any auto-discovered printers...
I'm a bit worrie
On Wed, 2007-08-29 at 14:40 -0700, Danek Duvall wrote:
> If you can uniquely identify by serial number in some large percentage of
> the printers out there, that's probably good enough -- I bet people are
> more likely to recognize a printer by IP address than MAC address, if they
> need to get dow
On Wed, Aug 29, 2007 at 06:34:37PM -0400, Bill Sommerfeld wrote:
> But I think we could do better than to force users to pick printers by
> mac address or ip address.
That's not what this is about -- I think that as long as a human-readable
name is available, that will be used on the usual label
Bill Sommerfeld wrote:
> On Wed, 2007-08-29 at 14:40 -0700, Danek Duvall wrote:
>
>> If you can uniquely identify by serial number in some large percentage of
>> the printers out there, that's probably good enough -- I bet people are
>> more likely to recognize a printer by IP address than MAC a
On Thu, Aug 30, 2007 at 08:30:46AM +1000, Boyd Adamson wrote:
> One thing I've heard a few times from customers using zones is that
> sometimes they would like to be able to offer ordering and dependency of
> zone startup, so that zone A has to finish starting before zone B is
> started.
>
> It se
Danek Duvall wrote:
> On Wed, Aug 29, 2007 at 06:34:37PM -0400, Bill Sommerfeld wrote:
>
>
>> But I think we could do better than to force users to pick printers by
>> mac address or ip address.
>>
>
> That's not what this is about -- I think that as long as a human-readable
> name is avail
John Plocher wrote:
> Danek Duvall wrote:
>> in our environment, would all 5000
>> printers show up, or some subset of those?
>
>
> I assume that, like today, if the user has a ~/.printers file,
> its "all:" entry will be used. If this is done naively, it could
> completely hide any auto-discover
Bill Sommerfeld wrote:
> But I think we could do better than to force users to pick printers by
> mac address or ip address.
Out of the box, my new HP printer had the name "HP Color Laserjet
3700 (BDB692)", my existing mono one said "HP Laserjet 2100", and
the Lexmark had "LXK0DD9EE".
I have not
On Wed, Aug 29, 2007 at 06:03:40PM -0500, Norm Jacobs wrote:
> The SWAN's 5000 printers that you are referring to are not physical
> printers, but queues "advertised" in the network name services.
But presumably a large number of those printers so represented are also
network printers that would
Danek Duvall wrote:
> On Wed, Aug 29, 2007 at 06:03:40PM -0500, Norm Jacobs wrote:
>
>
>> The SWAN's 5000 printers that you are referring to are not physical
>> printers, but queues "advertised" in the network name services.
>>
>
> But presumably a large number of those printers so represe
25 matches
Mail list logo
