Simo Sorce wrote:
All very nice, but the current situation is that this info *is* sent to
the log.
So I applaud if you want to go and fix applications, in the meanwhile we
cannot relax security around that log IMO.
The current situation (from where I'm sitting) is that the private info
is *not
On Wed, Oct 17, 2012 at 2:38 PM, Jesse Keating wrote:
> On 10/17/2012 11:32 AM, Chris Adams wrote:
>>
>> I would think the only "sane" way would be to just change the packaing,
>> not actually build multiple kernels (or even multiple packages with
>> kernels).
We already build multiple kernels.
On Wed, Oct 17, 2012 at 3:43 PM, Reindl Harald wrote:
> Am 17.10.2012 18:52, schrieb Dave Jones:
>> With virtualised environments supporting pci/usb passthrough, where do you
>> draw the line on what hardware to support in a hypothetical kernel-cloud
>> package ?
>
> with vmxnet3, vmw_pvscsi, vmw
Again, this is with the prefix that this isn't a big deal; it's a matter of
polish. But, here's the difference between `man` and `git log` automatically
sending output to a pager:
Man is a document reader. When you run it, you start at the top and read
down. A pager is natural.
The git log comman
On Wed, 2012-10-17 at 18:20 -0400, Andrew Schultz wrote:
> Simo Sorce wrote:
> > All very nice, but the current situation is that this info *is* sent to
> > the log.
> > So I applaud if you want to go and fix applications, in the meanwhile we
> > cannot relax security around that log IMO.
>
> The
On 10/17/2012 07:44 AM, Matthew Miller wrote:
> With the stipulation that rsyslog would still be available to provide a
> traditional syslog-style text logs, what are reasonable hard requirements
> for making systemd the main logging system installed by default? (Or, an
> alternate softer implement
101 - 106 of 106 matches
Mail list logo
