On Wed, 14 May 2008, james hughes wrote:
> If the target market is Linux web 2.0 developer. The application
> developers I know of (personal experience included) rely heavily on
> sudo.
The likes of Ubuntu don't really target integration with network
authentication though...
reg
rther, you're suggesting a large proportion of OpenSolaris
contributors are "corrupted" by their employment, and do /not/ always
have the long-term interests of the project at heart. Even if you were
right, that just doesn't seem a way to win friends and influence people.
NB: Opinio
ar (identical?) but new utility?
regards,
--
Paul Jakma,
Solaris Networking Sun Microsystems, Scotland
http://opensolaris.org/os/project/quagga tel: EMEA x73150 / +44 15066 73150
implementation usually isn't
architecture.
However, in the long-run, shipping broken, approaching-useless software
ought to raise architectural flags. If it's quite broke and we aren't
going to fix it, it shouldn't be in Solaris.
That's just MHO though ;).
I'
:)
The thing needs fixing or chucking away really, rather than moving..
regards,
--
Paul Jakma,
Solaris Networking Sun Microsystems, Scotland
http://opensolaris.org/os/project/quagga tel: EMEA x73150 / +44 15066 73150
an on fixing it, it
should be on *removing* it.
If I had a vote, and I were to ignore fact that PSARC doesn't decide on
implementation, it'd be: Big huge -1 to this proposal..
regards,
--
Paul Jakma,
Solaris Networking Sun Microsystems, Scotland
http://opensolar
address configured for the management redirect.
regards,
--
Paul Jakma,
Solaris Networking Sun Microsystems, Scotland
http://opensolaris.org/os/project/quagga tel: EMEA x73150 / +44 15066 73150
operating system, within a second or two (or thereabouts) AMT
> figures out that the host is out to lunch, and the ME takes over.
Ok, that's reassuring.
regards,
--
Paul Jakma,
Solaris Networking Sun Microsystems, Scotland
http://opensolaris.org/os/project/quagga tel
the host OS needs to re-enable the ARP intercept in
the NIC hardware on shutdown. I'm very curious if that means a sudden
host stop will render the AMT LOM inaccessible in short order..
regards,
--
Paul Jakma,
Solaris Networking Sun Microsystems, Scotland
http://opensolari
didn't get hijacked.
Does obviously preclude reliable Out-of-Band use of AMT. Indeed, I
really wonder how the LOM firmware can know whether or not it needs to
do ARP for a shared IP.
regards,
--
Paul Jakma,
Solaris Networking Sun Microsystems, Scotland
http://opensolaris.
On Wed, 17 Oct 2007, Nicolas Williams wrote:
> My impression was that the AMT chip gets its own IPv4 address.
I'd be curious if the MAC address is still shared for this case or not
though.
regards,
--
Paul Jakma,
Solaris Networking Sun Microsystems, Scotl
On Wed, 17 Oct 2007, Nicolas Williams wrote:
> My impression was that the AMT chip gets its own IPv4 address.
It can be configured to share an IP with the host.
regards,
--
Paul Jakma,
Solaris Networking Sun Microsystems, Scotland
http://opensolaris.org/os/project/qua
On Wed, 17 Oct 2007, Paul Jakma wrote:
> Firmware 'near' the NIC (I've never seen an explanation of the exact
> mechanism) interposes itself between hardware and OS and 'hijacks'
> traffic to that port. It never makes it to the OS.
Ah, googling suggests th
in the second.
IMLU.
(The clean answer of course would have been to just add dual-MAC
capability to the NIC, and let the LOMish/OoB-management firmware have
it's own MAC address and IP).
regards,
--
Paul Jakma,
Solaris Networking Sun Microsystems, Scotland
http://opensolaris.org/os/project/quagga tel: EMEA x73150 / +44 15066 73150
NB: Reply-To set to divert this thread over to install-discuss, as per
jek3's earlier email. For the broken-MUA afflicted (mutt, etc..), please
honour manually ;).
On Thu, 22 Mar 2007, Ed Gould wrote:
> Paul Jakma wrote:
> The RPM tools do this horribly badly. They alwa
oyment..
IMHO we really need to stop dealing implicitely with dependency
resolution by dint of big wads...
regards,
--
Paul Jakma,
Solaris Networking
http://opensolaris.org/os/project/quagga tel: EMEA x19190 / +353 1 819 9190
On Wed, 21 Mar 2007, Casper.Dik at Sun.COM wrote:
> So this function cannot be called from a signalhandler
> to provide a stacktrace?
You'd use printstack() for that. ;)
backtrace_symbols() can't be used either in such a case, you need to use
backtrace_symbols_fd().
regards
ect the /real/ reason for /usr/bin advocacy is simply so as to
avoid continued, ongoing /usr/XYZ namespace discussions, but I still
have to read the ARC case Jim cited. /usr/bin avoids those, at the cost
of lumping /everyone/ with ginormous number of binaries in their PATH.
regards,
--
Paul Ja
On Fri, 27 Oct 2006, Paul Jakma wrote:
> derive the 'context' for. E.g. if the above figure is presented to you
> by, say, Apache's directory-indexing module - which prefix is it?
Bah. Just for the record: it's actually GNU ls which using 10**(3*n)
prefixes, not
constrained apps).
For all others it'd be nice if we poor non-gurus didn't have to scratch
our heads wondering what the application intended (when the difference
matters).
regards,
--
Paul Jakma,
Network Approachability, KISS. Sun Microsystems, Dublin, Ireland.
http://opensolaris.org/os/project/quagga tel: EMEA x19190 / +353 1 819 9190
On Fri, 27 Oct 2006, Paul Jakma wrote:
> The base might be well-known for certain long-standing applications, where
> the context of:
>
> - who wrote it?
> - what audience was it written for?
>
> but for arbitrary applications the prefix is just is meaningless. What does
nsumers.
Then let's ask the consumers, I guess.
It's confusing enough that hard-disks typically have to explain the
difference on their labels..
regards,
--
Paul Jakma,
Network Approachability, KISS. Sun Microsystems, Dublin, Ireland.
http://opensolaris.org/os/project/quagga tel: EMEA x19190 / +353 1 819 9190
On Thu, 19 Oct 2006, Nicolas Williams wrote:
> How about:
>
> Make 'B' for K, M, etc..., make it Obsolete, and discourage its use.
> It should be used only where converting code that used to display K,
> M, etc...
>
> Make 'b' for Ki, Mi, and so on and make it Committed.
Good compromise. +1 fro
On Thu, 19 Oct 2006, Eric Lowe wrote:
> Clearly this is NOT the behavior you would want when you are
> expressing KB in the computer sense, etc.
"KiB" is pretty clear, whether you're aware of SI/IEC or not. If you
are, it's even "more clear".
Using the same letters for both SI (10^(3**n)) and
Hi Eric,
Just to note again:
On Tue, 17 Oct 2006, Eric Lowe wrote:
This:
> o An optional 'b' character, which will express the result
>as radix-2 rather than radix-10 (radix 2 uses 1024^N
>whereas the default of radix 10 uses 1000^N to convert
>the n
On Wed, 11 Oct 2006, Ienup Sung wrote:
> Meter is also quite commonly used in many other countries and as a
> matter of fact more than metre in many countries.
Yep, sorry: I was just confused.
Within the SI system it is always "metre" though. The nice thing about
"SI" is it avoids (mostly) all
On Wed, 11 Oct 2006, Paul Jakma wrote:
> There's just one country which does not use the normal SI spelling of 'metre'
Never mind: there's lots more, the germanic language ones for example.
:)
--paulj
On Wed, 11 Oct 2006, Paul Jakma wrote:
> deliberately): the thousand seperator is ' ', the decimal radix is '.'.
Humbug: The radix char may be either '.' or ','.
--paulj
On Tue, 10 Oct 2006, Nicolas Williams wrote:
>> If we define the function to /strictly/ be SI, which all the world
>> recognises and uses so a reasonable constraint, then there'd no
>> localisation issues for prefix symbols.
^^
> What about the decimal char
On Tue, 10 Oct 2006, Ienup Sung wrote:
> Regarding the optional unit character, in particular, 'K',
> it seems people tolearate Km, km, and KM for Kilometer/kilometer.
You mean kilometre. ;)
There's just one country which does not use the normal SI spelling of
'metre' and that country does not
On Tue, 10 Oct 2006, Nicolas Williams wrote:
> Ienup brought up that question.
>
> This is definitely in the realm of L10N. So new items for
> nl_langinfo(3C) seem to be in order.
If we define the function to /strictly/ be SI, which all the world
recognises and uses so a reasonable constraint,
31 matches
Mail list logo
