On Fri, 16 Jan 2009 21:28:07 -0800
Grant wrote:
> Should I do that via an ssh config setting, in shorewall, or somewhere else?
I believe the right way would be to add 'account required
pam_access.so' line to /etc/pam.d/system-auth and define login
restrictions in /etc/securety/access.conf (it's
On Fri, 16 Jan 2009 21:34:59 -0800
Grant wrote:
> I think this leaves a squid proxy setup as my only option?
Sorry, I haven't noticed the fact that there are machines behind the
firewall that need to be restricted, and aforementioned rule certainly
won't do that.
Squid setup should certainly be
>> That sounds good, how can I do that?
>
> iptables module "owner" handles that stuff, just "man iptables" if
> you'll have any trouble.
>
> iptables -A OUTPUT -m owner --uid-owner someuser -m tcp --dport http -j
> REJECT
I brought this to the shorewall list for config advice, but I was told:
One of the users set up on my router is for whoever is sitting in
front of the router and wants to log in. For that reason, the
password needs to be simple and I'd like to prevent that user from
being able to log in if they aren't in front of the system since the
password is simple and should be e
>> Whenever I get the following message in dmesg:
>>
>> wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
>>
>> the music playing on mpd skips. Does anyone know more about this?
>>
>> - Grant
>
> I think this is fixed by downgrading from madwifi-ng-svn- to
> madwifi-ng
Dirk Heinrichs writes:
>> I like to use that and put `-$MYHOST' as string. I wondered if there
>> is any way to set a numericly incrementing string. Maybe some trick
>> syntax that can go in that spot?
>
> The build system does that automatically as long as you don't "make
> mrproper",
> see
On Friday January 16 2009 18:58:55 Dirk Heinrichs wrote:
> The build system does that automatically as long as you don't "make
> mrproper",
You can backup .version
Am Freitag, 16. Januar 2009 21:43:56 schrieb rea...@newsguy.com:
> In the first section during a `makeconfig' session, there is a line
> (the second one) that says:
>
> Local Version - append to kernel release
>
> I like to use that and put `-$MYHOST' as string. I wondered if there
> is any way
In the first section during a `makeconfig' session, there is a line
(the second one) that says:
Local Version - append to kernel release
I like to use that and put `-$MYHOST' as string. I wondered if there
is any way to set a numericly incrementing string. Maybe some trick
syntax that can go
On Fri, Jan 16, 2009 at 1:04 PM, wrote:
> I tried to install hwinfo today and failed with the latest
> ~hwinfo-14.19. I couldn't make anything usefull of the failure
> message so backed off to the stable version 13.28. I got the same
> failure so wondering if anyone can make sense of the (parti
On Fri, Jan 16, 2009 at 12:33 PM, wrote:
> Paul Hartman writes:
>
>> I'm ashamed to admit I made the most basic mistake. I compiled uvesafb
>> as a module. Oops! Compiled it as "Y" instead of "M" and now I have a
>> pair of Tux sitting atop my kernel boot screen and no more 80x25
>> horror. :)
>
On Fri, 2009-01-16 at 10:59 -0800, Mark Knecht wrote:
[...]
> >>
> > If I'm not mistaken, comments #4 and #5 (the last two comments) pertain
> > to you.
>
> Well, yes, but they don't say anything (to me) as best I read. Or
> maybe I don't understand how the folks that work in those areas talk
> th
I tried to install hwinfo today and failed with the latest
~hwinfo-14.19. I couldn't make anything usefull of the failure
message so backed off to the stable version 13.28. I got the same
failure so wondering if anyone can make sense of the (partial)
output below.
Does it mean this file is missi
On Fri, Jan 16, 2009 at 10:36 AM, Albert Hopkins wrote:
> On Fri, 2009-01-16 at 07:56 -0800, Mark Knecht wrote:
> [...]
>> > A word of advice, when a bugzilla is resolved as DUPLICATE you should
>> > (almost always) immediately click on the bug that it's a duplicate of
>> > because that's where al
On Fri, 2009-01-16 at 07:56 -0800, Mark Knecht wrote:
[...]
> > A word of advice, when a bugzilla is resolved as DUPLICATE you should
> > (almost always) immediately click on the bug that it's a duplicate of
> > because that's where all the action is taking place:
> >
> > http://bugs.gentoo.org/sho
Paul Hartman writes:
> I'm ashamed to admit I made the most basic mistake. I compiled uvesafb
> as a module. Oops! Compiled it as "Y" instead of "M" and now I have a
> pair of Tux sitting atop my kernel boot screen and no more 80x25
> horror. :)
Is there some difference in uvesafb and vesafb? I
On Wednesday 14 January 2009, Mick wrote:
> On Monday 12 January 2009, Walter Dnes wrote:
> > The only suggestion I've found via Google is iptables "mangle". Does
> > it manage to change MSS without changing MTU? If so, what is the
> > invocation in the "mangle" table?
> It would probably be
On Fri, Jan 16, 2009 at 7:32 AM, Albert Hopkins wrote:
> On Fri, 2009-01-16 at 07:24 -0800, Mark Knecht wrote:
>> Hi,
>>I've completed my updates of this older Mac Mini. The machine boots
>> and runs fine but there's a small problem in the boot console:
>>
>> * Loading key mappings
>> * /bin/l
On Fri, 2009-01-16 at 07:24 -0800, Mark Knecht wrote:
> Hi,
>I've completed my updates of this older Mac Mini. The machine boots
> and runs fine but there's a small problem in the boot console:
>
> * Loading key mappings
> * /bin/loadkeys not found
> ** ERROR: cannot start consolefont as keyma
Hi,
I've completed my updates of this older Mac Mini. The machine boots
and runs fine but there's a small problem in the boot console:
* Loading key mappings
* /bin/loadkeys not found
** ERROR: cannot start consolefont as keymaps could not start
None of this occurred prior to the emerge -Du
On Thu, 2009-01-15 at 21:53 -0800, Hilco Wijbenga wrote:
> Hi all,
>
> In Bash /dev/tcp/host/port can be used to write to a TCP socket. This
> works nicely so I was very curious whether it would work the other way
> too: is it possible to have a Bash script listen on a particular port
> as if it w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Neil Bothwick wrote:
> The only amd64 ebuild of notification-daemon, 0.3.7, does not have a
> gstreamer USE flag. That's only present in the 0.4.0 ebuild, which is
> ~amd64. Are you trying to mix stable and testing packages?
No, at this point, I am
On Friday 16 January 2009 14:22:27 Helmut Jarausch wrote:
> On 16 Jan, Alan McKinnon wrote:
> > On Friday 16 January 2009 13:49:04 Helmut Jarausch wrote:
> >> Hi,
> >>
> >> I'm still struggling with the logic of dependencies in ebuild files
> >> e.g.
> >>
> >> kde-base/kdelibs-3.5.10-r2.ebuild co
On 16 Jan, Alan McKinnon wrote:
> On Friday 16 January 2009 13:49:04 Helmut Jarausch wrote:
>> Hi,
>>
>> I'm still struggling with the logic of dependencies in ebuild files
>> e.g.
>>
>> kde-base/kdelibs-3.5.10-r2.ebuild contains the line
>> !avahi? ( !bindist? ( net-misc/mDNSResponder !kde
2009/1/16 Dale
> Alejandro wrote:
> >
> >
> > 2009/1/15 Neil Bothwick mailto:n...@digimed.co.uk>>
> >
> > On Fri, 16 Jan 2009 00:00:07 +0100, Geralt wrote:
> >
> > > > You don't need to remove anything, just let portage handle the
> > block
> > > > for you. Blocks marked with a b
2009/1/16 Helmut Jarausch :
> Hi,
>
> I'm still struggling with the logic of dependencies in ebuild files
> e.g.
>
> kde-base/kdelibs-3.5.10-r2.ebuild contains the line
>!avahi? ( !bindist? ( net-misc/mDNSResponder !kde-misc/kdnssd-avahi ) )
>
> This causes a dependency loop since I do h
On Friday 16 January 2009 13:49:04 Helmut Jarausch wrote:
> Hi,
>
> I'm still struggling with the logic of dependencies in ebuild files
> e.g.
>
> kde-base/kdelibs-3.5.10-r2.ebuild contains the line
> !avahi? ( !bindist? ( net-misc/mDNSResponder !kde-misc/kdnssd-avahi ) )
>
> This causes a
Hi,
I'm still struggling with the logic of dependencies in ebuild files
e.g.
kde-base/kdelibs-3.5.10-r2.ebuild contains the line
!avahi? ( !bindist? ( net-misc/mDNSResponder !kde-misc/kdnssd-avahi ) )
This causes a dependency loop since I do have 'avahi' installed
which blocks net-mis
On Fri, 16 Jan 2009 05:27:12 -0500, Chris Walters wrote:
> I was wondering if anyone else was having this problem. I am running
> an AMD64 arch, and when I try to "emerge notification-daemon", it will
> not compile because libnotify is not present. If I try to emerge
> libnotify, it tries to me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
I was wondering if anyone else was having this problem. I am running an AMD64
arch, and when I try to "emerge notification-daemon", it will not compile
because libnotify is not present. If I try to emerge libnotify, it tries to
merge notif
On Fri, Jan 16, 2009 at 2:20 AM, Dale wrote:
> Paul Hartman wrote:
>> On Fri, Jan 16, 2009 at 1:58 AM, Paul Hartman
>> wrote:
>>
>>> On Fri, Jan 16, 2009 at 1:36 AM, Dale wrote:
>>>
Paul Hartman wrote:
> On Fri, Jan 16, 2009 at 12:59 AM, Dale wrote:
>
>
>> Wolfgang Lie
2009/1/16 Dale :
>
> So if evdev failed for some reason, it would fall back to the keyboard
> and mouse drivers you think? That I would be willing to try if that is
> the case.
>
I don't think there is a fallback option. You can either use the new
or the old way. Somebody correct me if I am wrong
On Thu, 15 Jan 2009 18:37:20 -0500, Michael P. Soulier wrote:
> The libavcodec library went from version 51 to 52, which broke
> transcode. The --deep argument did not find the dependency there and
> rebuild transcode.
>
> On my FreeBSD server, portupgrade has the -r and -R arguments to force
>
Alejandro wrote:
>
>
> 2009/1/15 Neil Bothwick mailto:n...@digimed.co.uk>>
>
> On Fri, 16 Jan 2009 00:00:07 +0100, Geralt wrote:
>
> > > You don't need to remove anything, just let portage handle the
> block
> > > for you. Blocks marked with a b (instead of a B) can be handled by
>
On Thu, 15 Jan 2009 23:59:32 -0200, Alejandro wrote:
> > That's right, but now the new portage is stable so it is handled on
> > stable systems. The block was handled automatically when it first
> > appeared on ~arch systems.
> Which version of portage do this? I am on amd64 stable and have the
>
Paul Hartman wrote:
> On Fri, Jan 16, 2009 at 1:58 AM, Paul Hartman
> wrote:
>
>> On Fri, Jan 16, 2009 at 1:36 AM, Dale wrote:
>>
>>> Paul Hartman wrote:
>>>
On Fri, Jan 16, 2009 at 12:59 AM, Dale wrote:
> Wolfgang Liebich wrote:
>
>
On Fri, Jan 16, 2009 at 1:58 AM, Paul Hartman
wrote:
> On Fri, Jan 16, 2009 at 1:36 AM, Dale wrote:
>> Paul Hartman wrote:
>>> On Fri, Jan 16, 2009 at 12:59 AM, Dale wrote:
>>>
Wolfgang Liebich wrote:
> On Thu, Jan 15, 2009 at 09:35:11AM -0600, Paul Hartman wrote:
>
>
>
37 matches
Mail list logo