On Fri, Aug 2, 2013 at 6:17 AM, William Kenworthy wrote:
> On 02/08/13 11:01, Samuli Suominen wrote:
>> On 02/08/13 05:48, Dale wrote:
>>> Samuli Suominen wrote:
Huh? USE="firmware-loader" is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interfac
On Fri, Aug 2, 2013 at 6:14 AM, Dale wrote:
> Samuli Suominen wrote:
>> On 02/08/13 05:48, Dale wrote:
>>> Samuli Suominen wrote:
Huh? USE="firmware-loader" is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interface names work as designed, not a
On 02/08/13 08:28, Dale wrote:
Samuli Suominen wrote:
On 02/08/13 06:14, Dale wrote:
Samuli Suominen wrote:
On 02/08/13 05:48, Dale wrote:
Samuli Suominen wrote:
Huh? USE="firmware-loader" is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interface names work
Samuli Suominen wrote:
> On 02/08/13 06:14, Dale wrote:
>> Samuli Suominen wrote:
>>> On 02/08/13 05:48, Dale wrote:
Samuli Suominen wrote:
>
> Huh? USE="firmware-loader" is optional and enabled by default in
> sys-fs/udev
> Futhermore predictable network interface names work a
Samuli Suominen writes:
> Futhermore predictable network interface names work as designed, not a
> single valid bug filed about them.
>
> Stop spreading FUD.
In what way are network interface names predictable? A new system
arrives on your desk, what is the name of the first (or only) Ethernet
i
Canek Peláez Valdés wrote:
> On Thu, Aug 1, 2013 at 4:43 AM, Walter Dnes wrote:
> > On Wed, Jul 31, 2013 at 02:00:23AM -0500, Canek Peláez Valdés wrote
> >> On Wed, Jul 31, 2013 at 1:24 AM, Daniel Campbell wrote:
> >
> >> You need an OpenRC use flag to install OpenRC init scripts? That's
> >> s
On 02/08/13 06:14, Dale wrote:
Samuli Suominen wrote:
On 02/08/13 05:48, Dale wrote:
Samuli Suominen wrote:
Huh? USE="firmware-loader" is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interface names work as designed, not a
single valid bug filed about them.
S
On 02/08/13 11:01, Samuli Suominen wrote:
> On 02/08/13 05:48, Dale wrote:
>> Samuli Suominen wrote:
>>>
>>> Huh? USE="firmware-loader" is optional and enabled by default in
>>> sys-fs/udev
>>> Futhermore predictable network interface names work as designed, not a
>>> single valid bug filed about t
Samuli Suominen wrote:
> On 02/08/13 05:48, Dale wrote:
>> Samuli Suominen wrote:
>>>
>>> Huh? USE="firmware-loader" is optional and enabled by default in
>>> sys-fs/udev
>>> Futhermore predictable network interface names work as designed, not a
>>> single valid bug filed about them.
>>>
>>> Stop s
On 02/08/13 05:48, Dale wrote:
Samuli Suominen wrote:
Huh? USE="firmware-loader" is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interface names work as designed, not a
single valid bug filed about them.
Stop spreading FUD.
Looking forward to lastrite sys-fs/e
Samuli Suominen wrote:
>
> Huh? USE="firmware-loader" is optional and enabled by default in
> sys-fs/udev
> Futhermore predictable network interface names work as designed, not a
> single valid bug filed about them.
>
> Stop spreading FUD.
>
> Looking forward to lastrite sys-fs/eudev just like
> sy
On 02/08/13 04:01, Walter Dnes wrote:
On Fri, Aug 02, 2013 at 02:42:36AM +0300, Samuli Suominen wrote
nope, you just believed all the FUD there has been out there. i've said
it many times, and i'll say it again:
the only real different is USE="rule-generator" and that's it
and sys-fs/eudev i
On Thu, Aug 01, 2013 at 12:28:38PM -0400, Tanstaafl wrote
> Hi all,
>
> Ok, rehashing this, but please don't turn it into another udev vs
> systemd thread.
>
> I have an older server that I have been putting off this update,
> debating on whether to update to the regular udev, or to eudev.
>
>
On Fri, Aug 02, 2013 at 02:42:36AM +0300, Samuli Suominen wrote
> nope, you just believed all the FUD there has been out there. i've said
> it many times, and i'll say it again:
>
> the only real different is USE="rule-generator" and that's it
>
> and sys-fs/eudev is constantly out of date and
On 02/08/13 03:19, William Kenworthy wrote:
On 02/08/13 07:42, Samuli Suominen wrote:
On 02/08/13 02:27, William Kenworthy wrote:
On 02/08/13 00:28, Tanstaafl wrote:
Hi all,
Ok, rehashing this, but please don't turn it into another udev vs
systemd thread.
I have an older server that I have b
On 02/08/13 07:42, Samuli Suominen wrote:
> On 02/08/13 02:27, William Kenworthy wrote:
>> On 02/08/13 00:28, Tanstaafl wrote:
>>> Hi all,
>>>
>>> Ok, rehashing this, but please don't turn it into another udev vs
>>> systemd thread.
>>>
>>> I have an older server that I have been putting off this u
On 08/01/2013 03:08 PM, Kerin Millar wrote:
> On 30/07/2013 22:04, walt wrote:
>> On 07/29/2013 06:29 PM, Harry Putnam wrote:
>>> Can anyone post a .config for a 3.8.13 kernel that is known to work on
>>> a vbox install of gentoo as guest.
>>>
>>> Working on a fresh install but don't have gentoo ru
On 02/08/13 07:42, Samuli Suominen wrote:
> On 02/08/13 02:27, William Kenworthy wrote:
>> On 02/08/13 00:28, Tanstaafl wrote:
...
>
> so why follow with unreliable fork, when there is the official package
> available with equal features?
>
>
easy - it works and while I had machines running som
On 02/08/13 02:27, William Kenworthy wrote:
On 02/08/13 00:28, Tanstaafl wrote:
Hi all,
Ok, rehashing this, but please don't turn it into another udev vs
systemd thread.
I have an older server that I have been putting off this update,
debating on whether to update to the regular udev, or to eu
On 01/08/13 23:02, Alexander Puchmayr wrote:
Hi there,
When I start X (or start kdm), I get a segmentation fault and no X.
[...]
Kernel 3.8.18, nvidia-drivers 304.88 (Last to support the GeForce7600, newer
drivers do not support it any more).
Any ideas?
Try manually rolling your own ebuild fo
On 02/08/13 00:28, Tanstaafl wrote:
> Hi all,
>
> Ok, rehashing this, but please don't turn it into another udev vs
> systemd thread.
>
> I have an older server that I have been putting off this update,
> debating on whether to update to the regular udev, or to eudev.
>
> I've googled until my f
Hi there,
When I start X (or start kdm), I get a segmentation fault and no X.
The Xorg-log says:
[ 8675.702] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 8675.702] (==) NVIDIA(0): RGB weight 888
[ 8675.702] (==) NVIDIA(0): Default visual is TrueColor
[ 8675.702] (==) NVIDIA(0): Using g
On 01/08/2013 22:38, Walter Dnes wrote:
On Thu, Aug 01, 2013 at 08:41:56AM +0200, Michael Hampicke wrote
You can use march=native on your gentoo hosts, that's no problem, as
long as you don't use it on your guests. That's the hole idea of VMs:
being able to move the virtual machine to another m
On 02/08/13 00:49, Dale wrote:
Samuli Suominen wrote:
On 01/08/13 19:28, Tanstaafl wrote:
Hi all,
Ok, rehashing this, but please don't turn it into another udev vs
systemd thread.
I have an older server that I have been putting off this update,
debating on whether to update to the regular ude
On 30/07/2013 22:04, walt wrote:
On 07/29/2013 06:29 PM, Harry Putnam wrote:
Can anyone post a .config for a 3.8.13 kernel that is known to work on
a vbox install of gentoo as guest.
Working on a fresh install but don't have gentoo running anywhere to
rob a .config from.
This one worked for m
Samuli Suominen wrote:
> On 01/08/13 19:28, Tanstaafl wrote:
>> Hi all,
>>
>> Ok, rehashing this, but please don't turn it into another udev vs
>> systemd thread.
>>
>> I have an older server that I have been putting off this update,
>> debating on whether to update to the regular udev, or to eudev
Tanstaafl wrote:
> On 2013-08-01 4:04 PM, Dale wrote:
>
>> I switched when it was still fresh and it wasn't to bad from what I
>> recall. Just emerge -C udev and emerge eudev. I think I masked udev to
>> make sure it didn't get pulled in any more by something else but other
>> than that, it just
On Thu, Aug 01, 2013 at 08:41:56AM +0200, Michael Hampicke wrote
> You can use march=native on your gentoo hosts, that's no problem, as
> long as you don't use it on your guests. That's the hole idea of VMs:
> being able to move the virtual machine to another machine, that might be
> completely di
On 01/08/13 19:28, Tanstaafl wrote:
Hi all,
Ok, rehashing this, but please don't turn it into another udev vs
systemd thread.
I have an older server that I have been putting off this update,
debating on whether to update to the regular udev, or to eudev.
I've googled until my fingers are blue,
On 2013-08-01 4:04 PM, Dale wrote:
I switched when it was still fresh and it wasn't to bad from what I
recall. Just emerge -C udev and emerge eudev. I think I masked udev to
make sure it didn't get pulled in any more by something else but other
than that, it just worked.
I would recommend go
Tanstaafl wrote:
> Hi all,
>
> Ok, rehashing this, but please don't turn it into another udev vs
> systemd thread.
>
> I have an older server that I have been putting off this update,
> debating on whether to update to the regular udev, or to eudev.
>
> I've googled until my fingers are blue, but c
on 08/01/2013 07:38 PM Volker Armin Hemmann wrote the following:
> Am 01.08.2013 09:37, schrieb Thanasis:
>> on 08/01/2013 12:59 AM Paul Hartman wrote the following:
>>
>>> If no disks are attached, I wonder if something is probing it?
>>>
>>> I checked my dmesg and every time I plug in my eSATA en
on 08/01/2013 05:43 PM Bruce Hill wrote the following:
> On Thu, Aug 01, 2013 at 10:37:34AM +0300, Thanasis wrote:
>>
>> Me too. That's exactly how I use this Sata port, so it must be related
>> to the way the kernel handles/probes it.
>>
>> BTW, I use a cable which is sata <-> eSata, i.e. sata for
On Thu, 01 Aug 2013 12:28:38 -0400, Tanstaafl wrote:
> I've googled until my fingers are blue, but cannot for the life of me
> find any explicit instructions for *how* to switch from udev to eudev.
emerge -Ca udev
emerge -1a eudev
But there's not a lot of point as eudev isn't that different to
On 01/08/13 at 08:07pm, meino.cra...@gmx.de wrote:
> Hi,
>
> System is an AMD64.
>
> I am trying to follow these instructions:
>
> http://dev.gentoo.org/~armin76/arm/beagleboneblack/install.xml
>
> and get problems while executing
>
>
> Build a crosscompiler
>
> Code Listing 3.2:
On Thursday 01 August 2013 12:28:38 Tanstaafl wrote:
> Hi all,
>
> Ok, rehashing this, but please don't turn it into another udev vs
> systemd thread.
>
> I have an older server that I have been putting off this update,
> debating on whether to update to the regular udev, or to eudev.
>
> I've g
Hi,
System is an AMD64.
I am trying to follow these instructions:
http://dev.gentoo.org/~armin76/arm/beagleboneblack/install.xml
and get problems while executing
Build a crosscompiler
Code Listing 3.2: Building a crosscompiler
# crossdev -S armv7a-hardfloat-linux-gnueabi
Am 01.08.2013 19:16, schrieb Marc Stürmer:
net.ifnames=0
Worked like a charm to me.
Forgot to mention the more thorough documentation though, so here it is:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
http://wiki.gentoo.org/wiki/Udev/upgrade
You shoul
Am 01.08.2013 18:28, schrieb Tanstaafl:
I have an older server that I have been putting off this update,
debating on whether to update to the regular udev, or to eudev.
I've googled until my fingers are blue, but cannot for the life of me
find any explicit instructions for *how* to switch from u
On 2013-08-01 12:28 PM, Tanstaafl wrote:
I have an older server that I have been putting off this update,
debating on whether to update to the regular udev, or to eudev.
Neglected to mention, it is still running 171-r10
On Thu, Aug 1, 2013 at 11:28 AM, Tanstaafl wrote:
> Hi all,
>
> Ok, rehashing this, but please don't turn it into another udev vs systemd
> thread.
>
> I have an older server that I have been putting off this update, debating on
> whether to update to the regular udev, or to eudev.
>
> I've google
Am 01.08.2013 09:37, schrieb Thanasis:
> on 08/01/2013 12:59 AM Paul Hartman wrote the following:
>
>> If no disks are attached, I wonder if something is probing it?
>>
>> I checked my dmesg and every time I plug in my eSATA enclosure, I see
>> this very similar message:
>>
>> [156541.724580] ata7:
On Thu, Aug 1, 2013 at 11:04 AM, walt wrote:
> For months I've been using apps that need the tun and fuse kernel modules,
> and I've never needed to modprobe those two modules until about a week ago.
> The modules were loaded automagically when those apps started up. (I never
> understood how that
Hi all,
Ok, rehashing this, but please don't turn it into another udev vs
systemd thread.
I have an older server that I have been putting off this update,
debating on whether to update to the regular udev, or to eudev.
I've googled until my fingers are blue, but cannot for the life of me
f
On Thu, Aug 1, 2013 at 4:43 AM, Walter Dnes wrote:
> On Wed, Jul 31, 2013 at 02:00:23AM -0500, Canek Peláez Valdés wrote
>> On Wed, Jul 31, 2013 at 1:24 AM, Daniel Campbell wrote:
>
>> You need an OpenRC use flag to install OpenRC init scripts? That's
>> simply a lie.
>
> An apology to Daniel m
On Thu, 1 Aug 2013 10:46:04 -0500, »Q« wrote:
> > "Everything is a file", nor does the man page say anything about not
> > using it to mask out directories. Bearing in mind that this is the
> > means chosen by the devs, it is reasonable to assume that it is
> > practicable.
>
> Elsewhere, man m
For months I've been using apps that need the tun and fuse kernel modules,
and I've never needed to modprobe those two modules until about a week ago.
The modules were loaded automagically when those apps started up. (I never
understood how that happened, BTW.)
Suddenly those two apps won't start
On Thu, 1 Aug 2013 12:15:28 +0100
Neil Bothwick w
> On Thu, 1 Aug 2013 06:24:17 -0400, Walter Dnes wrote:
>
> > > You can use it to prevent ebuilds from installing unit files
> > > or open-rc scripts from doing so (based on what you want to
> > > opt-out of).
> >
> > From the man page...
On Thu, Aug 01, 2013 at 10:37:34AM +0300, Thanasis wrote:
>
> Me too. That's exactly how I use this Sata port, so it must be related
> to the way the kernel handles/probes it.
>
> BTW, I use a cable which is sata <-> eSata, i.e. sata for the
> motherboard side and eSata for the external disk side
On Thu, Aug 01, 2013 at 10:51:56AM +0300, Thanasis wrote:
>
> I keep the cable connected to both the motherboard's sata port and to
> the external eSata disk enclosure.
The _only_ time that I am _certain_ I've received that particular error is in
a very similar case. My workstation has 2 SATA cab
On 1 August 2013 16:16, Paul Hartman wrote:
>
> When I upgraded portage yesterday, it added this PORTDIR line to
> make.conf for me when I ran etc-update. Did you update your config
> files after upgrading portage?
I remember there was an etc-update, but make.conf was not among those
files where
On Thu, Aug 1, 2013 at 2:42 AM, András Csányi wrote:
> Hi All,
>
> Yesterday there was an portage upgrade and after that I got it if I
> would like to use euse:
>
> sayusi-desktop sayusi # euse -E gtk3
> ERROR: $PORTDIR couldn't be determined
>
> What is it and why that variable not determined? I
On Thu, Aug 1, 2013 at 2:51 AM, Thanasis wrote:
> on 08/01/2013 01:10 AM Bruce Hill wrote the following:
>> On Wed, Jul 31, 2013 at 11:17:02PM +0300, Thanasis wrote:
>>> on 07/31/2013 10:06 PM Paul Hartman wrote the following:
There are a few approaches to try figuring it out explained h
Hello,
On Wed, 31 Jul 2013, Paul Hartman wrote:
>http://serverfault.com/questions/244944/linux-ata-errors-translating-to-a-device-name
All flawed IMHO. My version (works with PATA too), possibly flawed too:
~/bin/ataid_to_drive.sh
#!/bin/bash
oIFS="$IFS"
IFS=$'\n'
CTRLS=( $(/sbin/lspci
On 08/01/2013 03:15 PM, Nicolas Sebrecht wrote:
> The 01/08/13, hasufell wrote:
>
>> You can use the command line too.
>>
>> www-client/pybugz
>
> I know this tool. I did try it. At that time it was buggy and did not
> work for me. Though, this would still be a busy process as this is just
> anot
The 01/08/13, hasufell wrote:
> You can use the command line too.
>
> www-client/pybugz
I know this tool. I did try it. At that time it was buggy and did not
work for me. Though, this would still be a busy process as this is just
another interface og the bugzilla thing.
> Git workflow has been
On 08/01/2013 02:11 PM, Nicolas Sebrecht wrote:
> The 01/08/13, Alon Bar-Lev wrote:
>
>> I don't see the major difference between that and opening a bug and
>> attaching the patch. Only that bugzilla allow to manage the process,
>> not have leftovers, and future people can resume past discussions.
The 01/08/13, Alon Bar-Lev wrote:
> I don't see the major difference between that and opening a bug and
> attaching the patch. Only that bugzilla allow to manage the process,
> not have leftovers, and future people can resume past discussions.
The bugzilla thing is what makes the difference, IMHO
On 1 August 2013 11:18, Helmut Jarausch wrote:
> On 08/01/2013 09:42:35 AM, András Csányi wrote:
>>
>> Hi All,
>>
>> Yesterday there was an portage upgrade and after that I got it if I
>> would like to use euse:
>>
>> sayusi-desktop sayusi # euse -E gtk3
>> ERROR: $PORTDIR couldn't be determined
>
On Thu, Aug 1, 2013 at 2:17 PM, Nicolas Sebrecht wrote:
> The 01/08/13, Hans de Graaff wrote:
>
>> http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2
>> documents this from the new developer perspective. Note how it says to
>> contact the recruiters if you don't already have
The 01/08/13, Hans de Graaff wrote:
> http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2
> documents this from the new developer perspective. Note how it says to
> contact the recruiters if you don't already have found a mentor yourself.
>
> There is also http://www.gentoo
On Thu, 1 Aug 2013 06:24:17 -0400, Walter Dnes wrote:
> > You can use it to prevent ebuilds from installing unit files
> > or open-rc scripts from doing so (based on what you want to opt-out
> > of).
>
> From the man page...
> > INSTALL_MASK = [space delimited list of file names]
>
> I
On Tuesday 30 Jul 2013 07:45:39 Helmut Jarausch wrote:
> Hi,
>
> I've been running a Windows 7 (professional)guest with Virtualbox on my
> GenToo system for some years.
> But recently I have a broken network either due to Virtualbox or due to
> some
> (automatic) Windows updates.
>
> The situati
On Wed, Jul 31, 2013 at 06:11:02PM +0530, Yohan Pereira wrote
> On 31/07/13 at 08:30am, Tanstaafl wrote:
> > So, how should this be used to 'opt out of systemd completely'?
>
> from main make.conf
> "Use this variable if you want to selectively prevent certain
> files from being copied into
On Wed, Jul 31, 2013 at 02:00:23AM -0500, Canek Peláez Valdés wrote
> On Wed, Jul 31, 2013 at 1:24 AM, Daniel Campbell wrote:
> You need an OpenRC use flag to install OpenRC init scripts? That's
> simply a lie.
An apology to Daniel might be in order. I start my USE flag with "-*".
During a re
On 08/01/2013 09:42:35 AM, András Csányi wrote:
Hi All,
Yesterday there was an portage upgrade and after that I got it if I
would like to use euse:
sayusi-desktop sayusi # euse -E gtk3
ERROR: $PORTDIR couldn't be determined
What is it and why that variable not determined? I did not do anything
Wang Xuerui wrote:
> 在 2013-8-1 上午10:26， 写道：
> >
> > Can a shell script tell if systemd is the init? I have a couple of
> > places where it would be nice to know this.
> >
> > Thanks in advance for any suggestions.
>
> Check /proc/1/comm or something like that, IIRC...
OK, thanks.
--
Your li
on 08/01/2013 01:10 AM Bruce Hill wrote the following:
> On Wed, Jul 31, 2013 at 11:17:02PM +0300, Thanasis wrote:
>> on 07/31/2013 10:06 PM Paul Hartman wrote the following:
>>>
>>> There are a few approaches to try figuring it out explained here:
>>>
>>> http://serverfault.com/questions/244944/li
Hi All,
Yesterday there was an portage upgrade and after that I got it if I
would like to use euse:
sayusi-desktop sayusi # euse -E gtk3
ERROR: $PORTDIR couldn't be determined
What is it and why that variable not determined? I did not do anything
and my machine was estarted since portage upgrade
on 08/01/2013 12:59 AM Paul Hartman wrote the following:
> If no disks are attached, I wonder if something is probing it?
>
> I checked my dmesg and every time I plug in my eSATA enclosure, I see
> this very similar message:
>
> [156541.724580] ata7: exception Emask 0x10 SAct 0x0 SErr 0x404
On Wed, 31 Jul 2013 14:34:41 -0400, Michael Orlitzky wrote:
> It seems a little rude to pop in, address them personally, and ask them
> each if they'd devote months of their time towards mentoring me. (Doing
> so can pressure someone into agreeing to something he doesn't want to
> do, or makes hi
On Tue, 30 Jul 2013 19:48:19 -0400, Michael Orlitzky wrote:
> I want to become a dev, what's my next step? There is none. Help out,
> and maybe someone will notice you? Ok, I'm on it. Been doing it for
> years, and I know several other people in the same situation. It doesn't
> work, and recruitme
72 matches
Mail list logo
