On 01/27/2013 01:06 AM, staticsafe wrote:
> I just grabbed vanilla 3.7.4 from kernel.org, the kernel build itself
> went fine but when I did a modules-rebuild, the nvidia module failed to
> build. As requested by the error message:
I had the same problem, I had success with this:
https://devtalk.
On Wednesday 30 January 2013 07:46:48 AM IST, Philip Webb wrote:
> A few weeks ago, there was a brief thread re a change in a pkg
> which stopped 'su' from working. It didn't affect my desktop system,
> so I didn't pay much attention, but it's just hit my netbook.
>
> Can anyone remind me what I n
hey..
I wonder about the last update of fcron.It is an update to 3.1.1, there
is a new /etc/crontab file, which is mixed
with /etc/fcronfcrontab, without update notice. The latest stable
version is 3.0.6 on the fcron homepage.
bye, jens.
A few weeks ago, there was a brief thread re a change in a pkg
which stopped 'su' from working. It didn't affect my desktop system,
so I didn't pay much attention, but it's just hit my netbook.
Can anyone remind me what I need to do to restore it ?
--
,,=
On 30/01/13 05:14, Kevin Chadwick wrote:
>> So anyway, my memory of this is all very wishy-washy, but ebtables
>> turned out to be the best way to implement those inter-VM restrictions.
>> It could probably have been done in iptables, but ebtables made it easy
>> to say "don't let these two talk."
On Tue, Jan 29, 2013 at 3:10 PM, Kevin Chadwick wrote:
> [...] but lets just agree to disagree [...]
Agreed.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
> So anyway, my memory of this is all very wishy-washy, but ebtables
> turned out to be the best way to implement those inter-VM restrictions.
> It could probably have been done in iptables, but ebtables made it easy
> to say "don't let these two talk."
I don;t know the details but I expect that w
> And, BTW, I didn't mean "behind" in the sense that Gentoo doesn't
> support systemd; I meant "behind" in the sense that us systemd users
> get a lot flak just by mention it in the list.
And that's exactly why I see Gentoo as being ahead and actually your
talking about a few of the IMO more moro
On Tue, Jan 29, 2013 at 2:00 PM, Alon Bar-Lev wrote:
> On Tue, Jan 29, 2013 at 9:49 PM, Canek Peláez Valdés wrote:
>
>> I would not bet on that ;) too much resistance. However it is
>> certainly getting better and better: the LWN article on The Biggest
>> Myths about systemd had an overwhelmingly
On Tue, Jan 29, 2013 at 9:49 PM, Canek Peláez Valdés wrote:
> I would not bet on that ;) too much resistance. However it is
> certainly getting better and better: the LWN article on The Biggest
> Myths about systemd had an overwhelmingly majority of comments
> positive to systemd, and just a hand
On Tue, Jan 29, 2013 at 1:33 PM, Stefan G. Weichinger wrote:
> Am 29.01.2013 20:23, schrieb Canek Peláez Valdés:
>
>> I really believe the most important thing abount systemd unit files is
>> that they are small and simple. You can also check the exit status
>> from each command in the script, or
Am 29.01.2013 20:33, schrieb Canek Peláez Valdés:
> On Tue, Jan 29, 2013 at 1:22 PM, Stefan G. Weichinger wrote:
>> When I debugged my way up to the current draft it was helpful to see
>> which line/command failed etc.
>
> That's my point; you don't need (and I would venture to say, you don't
> w
On Tue, Jan 29, 2013 at 1:22 PM, Stefan G. Weichinger wrote:
> Am 29.01.2013 20:05, schrieb Michael Mol:
>
>> I'll note that in your version, you're ignoring the exit statuses of
>> each of those commands. From a correctness standpoint, I prefer
>> Stefan's version.
>
> Thanks ;-)
>
> Also thanks
Am 29.01.2013 20:23, schrieb Canek Peláez Valdés:
> I really believe the most important thing abount systemd unit files is
> that they are small and simple. You can also check the exit status
> from each command in the script, or even better, you can do a test
> after all the commands are done to
On Tue, Jan 29, 2013 at 1:05 PM, Michael Mol wrote:
> On Tue, Jan 29, 2013 at 1:57 PM, Canek Peláez Valdés wrote:
>> On Tue, Jan 29, 2013 at 10:32 AM, Stefan G. Weichinger
>> wrote:
>>> Am 28.01.2013 22:49, schrieb Stefan G. Weichinger:
>>>
>> ps: my bigger hurdle will be the bridging-setup
Am 29.01.2013 20:05, schrieb Michael Mol:
> I'll note that in your version, you're ignoring the exit statuses of
> each of those commands. From a correctness standpoint, I prefer
> Stefan's version.
Thanks ;-)
Also thanks to Canek for the script-version ... I knew that way but
wanted to fully ta
On Tue, 29 Jan 2013 16:36:06 +
Mick wrote:
> On Tuesday 29 Jan 2013 10:19:16 Alan McKinnon wrote:
> > On Tue, 29 Jan 2013 06:37:47 +
> >
> > Mick wrote:
> > > Hi All,
> > >
> > > I got this message when net-mail/mailbase-1.1 was emerged:
> > >
> > > * Messages for package net-mail/mai
On Tue, Jan 29, 2013 at 1:57 PM, Canek Peláez Valdés wrote:
> On Tue, Jan 29, 2013 at 10:32 AM, Stefan G. Weichinger wrote:
>> Am 28.01.2013 22:49, schrieb Stefan G. Weichinger:
>>
> ps: my bigger hurdle will be the bridging-setup for running
> KVM-virtualization. This was one of the reas
On Tue, Jan 29, 2013 at 10:32 AM, Stefan G. Weichinger wrote:
> Am 28.01.2013 22:49, schrieb Stefan G. Weichinger:
>
ps: my bigger hurdle will be the bridging-setup for running
KVM-virtualization. This was one of the reasons to go back to openrc
back then.
>>>
>>> I have no experien
On 01/29/2013 09:45 AM, James wrote:
> Hello,
>
> From here: http://ebtables.sourceforge.net/
>
>
> We read:
> The ebtables tool can be combined with the other Linux filtering tools
> (iptables, ip6tables and arptables) to make a bridging firewall that is also
> capable of filtering these highe
Michael Mol gmail.com> writes:
> iptables and ip6tables operate at the data layer, layer 3.
> ebtables operates at the link layer, layer 2.
> http://upload.wikimedia.org/wikipedia/commons/3/37/Netfilter-packet-flow.svg
Nice diagram.
I'm surveying what's new/available for wired and wirele
On Tue, Jan 29, 2013 at 9:45 AM, James wrote:
> Hello,
>
> From here: http://ebtables.sourceforge.net/
>
>
> We read:
> The ebtables tool can be combined with the other Linux filtering tools
> (iptables, ip6tables and arptables) to make a bridging firewall that is also
> capable of filtering these
On Tuesday 29 Jan 2013 10:19:16 Alan McKinnon wrote:
> On Tue, 29 Jan 2013 06:37:47 +
>
> Mick wrote:
> > Hi All,
> >
> > I got this message when net-mail/mailbase-1.1 was emerged:
> >
> > * Messages for package net-mail/mailbase-1.1:
> > * Your //var/spool/mail/ directory permissions diff
Am 28.01.2013 22:49, schrieb Stefan G. Weichinger:
>>> ps: my bigger hurdle will be the bridging-setup for running
>>> KVM-virtualization. This was one of the reasons to go back to openrc
>>> back then.
>>
>> I have no experience with that, but if it works in OpenRC it should
>> work in systemd. P
Hello,
>From here: http://ebtables.sourceforge.net/
We read:
The ebtables tool can be combined with the other Linux filtering tools
(iptables, ip6tables and arptables) to make a bridging firewall that is also
capable of filtering these higher network layers. This is enabled through the
bridge-n
On Tue, 29 Jan 2013 06:37:47 +
Mick wrote:
> Hi All,
>
> I got this message when net-mail/mailbase-1.1 was emerged:
>
> * Messages for package net-mail/mailbase-1.1:
>
> * Your //var/spool/mail/ directory permissions differ from
> * those which mailbase wants to set it to (03775).
> *
26 matches
Mail list logo
