Re: [gentoo-user] SystemD + Gnome 3.8 I can log in as root but not as normal user

[Carlos Sura]

Hello Jochen,

Thank you for your help.

Here is the Xorg log: http://tny.cz/69b4662a

Regarding the gdm session.log I don't have it. Here is
the /var/log/gdm/:0.log : http://tny.cz/35e886e2

Here is my emerge --info: http://tny.cz/10262247




On 1 October 2013 00:52, Jochen Kirchner  wrote:

>  Am 01.10.2013 08:30, schrieb Carlos Sura:
>
> Hello Mates,
>
>  I finally thought that I got this working, so now I am dealing this
> issue:
> I choose the latest kernel with systemd and GDM starts good, but I cannot
> log in to gnome as a normal user, I can only log in to gnome as root.
>
>  What I have done before this started:
>
>  emerge -uDvaN world
> emerge --depclean --ask
> emerge @preserved-rebuild
>
>  Then it just happened.
>
>  What I've tried so far:
> - .xinitrc with exec gnome-session for user and root
> -  emerge -1 $( qlist -IC x11-drivers/ )
> - emerge @x11-module-rebuild
> -  X -configure
>
>
>  Another note:
> Starting gnome as normal user just hang, apparently it wants to start but
> it cannot start. Neither doing: startx.
>
>  I am using for xorg:
> VIDEO_CARDS="intel vesa"
>
>  Any help?
>
>  Regards
>
>  --
> Carlos Sura.-
> www.carlossura.com
> www.carlossura.com/blog
>
>
> Hi,
>
> have you looked in your /var/log/Xorg.0.log?
>
> And I think the GDM session log is in /home/*user*/.cache/gdm/session.log.
>
> Regards,
>
> Jochen
>
> --
> "There is only one god, and his name is Death.
> And there is only one thing we say to Death: 'Not today'."
> - Syrio Forel, Game of Thrones
> http://acidc0re.info
>
>


-- 
Carlos Sura.-
www.carlossura.com
www.carlossura.com/blog

Re: [gentoo-user] SystemD + Gnome 3.8 I can log in as root but not as normal user

[Carlos Sura]

In another note:

I've just installed enlightenment and it works fine. Gnome works fine ONLY
as root, but not as normal user.


On 1 October 2013 01:06, Carlos Sura  wrote:

> Hello Jochen,
>
> Thank you for your help.
>
> Here is the Xorg log: http://tny.cz/69b4662a
>
> Regarding the gdm session.log I don't have it. Here is
> the /var/log/gdm/:0.log : http://tny.cz/35e886e2
>
> Here is my emerge --info: http://tny.cz/10262247
>
>
>
>
> On 1 October 2013 00:52, Jochen Kirchner  wrote:
>
>>  Am 01.10.2013 08:30, schrieb Carlos Sura:
>>
>> Hello Mates,
>>
>>  I finally thought that I got this working, so now I am dealing this
>> issue:
>> I choose the latest kernel with systemd and GDM starts good, but I cannot
>> log in to gnome as a normal user, I can only log in to gnome as root.
>>
>>  What I have done before this started:
>>
>>  emerge -uDvaN world
>> emerge --depclean --ask
>> emerge @preserved-rebuild
>>
>>  Then it just happened.
>>
>>  What I've tried so far:
>> - .xinitrc with exec gnome-session for user and root
>> -  emerge -1 $( qlist -IC x11-drivers/ )
>> - emerge @x11-module-rebuild
>> -  X -configure
>>
>>
>>  Another note:
>> Starting gnome as normal user just hang, apparently it wants to start but
>> it cannot start. Neither doing: startx.
>>
>>  I am using for xorg:
>> VIDEO_CARDS="intel vesa"
>>
>>  Any help?
>>
>>  Regards
>>
>>  --
>> Carlos Sura.-
>> www.carlossura.com
>> www.carlossura.com/blog
>>
>>
>> Hi,
>>
>> have you looked in your /var/log/Xorg.0.log?
>>
>> And I think the GDM session log is in /home/*user*/.cache/gdm/session.log.
>>
>> Regards,
>>
>> Jochen
>>
>> --
>> "There is only one god, and his name is Death.
>> And there is only one thing we say to Death: 'Not today'."
>> - Syrio Forel, Game of Thrones
>> http://acidc0re.info
>>
>>
>
>
> --
> Carlos Sura.-
> www.carlossura.com
> www.carlossura.com/blog
>



-- 
Carlos Sura.-
www.carlossura.com
www.carlossura.com/blog

Re: [gentoo-user] Package Create on remote Host

[Neil Bothwick]

On Tue,  1 Oct 2013 03:30:32 +0200, siefke_lis...@web.de wrote:

> i have a Rootserver with Power. Can i built package on this Host and
> send Package  to my Notebooks? Can i built Packages on the Root without
> local install?

If you install into a chroot on the server, just like the first steps of
the install but never make it the root directory, you can then build
binary packages in that chroot. Add buildpkg to FEATURES on the build
host and set PKGDIR to somewhere accessible by all machines, say an NFS
share.

On the netbooks, add --usepkg=y to EMERGE_DEFAULT_OPTS in make.conf and
set PKGDIR to the same location.


-- 
Neil Bothwick

Last yur I kudnt spel modjerater now I are won.


signature.asc
Description: PGP signature

Re: [gentoo-user] separate / and /usr to require initramfs 2013-11-01

[Neil Bothwick]

On Mon, 30 Sep 2013 22:36:34 -0500, Bruce Hill wrote:

> Do you have some alias causing df output to use -h or how does that
> work?

% alias df
df='df --human-readable --no-sync --print-type'

Or, to put it another way - Yes.


-- 
Neil Bothwick

X-Modem- A device on the losing end of an encounter with lightning.


signature.asc
Description: PGP signature

Re: [gentoo-user] Managing multiple systems with identical hardware

[Neil Bothwick]

On Mon, 30 Sep 2013 23:07:14 -0700, Grant wrote:

> Build time itself really isn't a big deal.  I can have the
> clients update overnight.  Whether the clients emerge or emerge -K is
> the same amount of admnistrative work I would think.

I can think of one exception, the occasional ebuild that doesn't compile
for whatever reason. Using emerge -K will only install packages that have
successfully compiled on the build host. This won't protect against
install bug, because the portage build the package and then installs from
it, but it will catch most glitches.


-- 
Neil Bothwick

Those who live by the sword get shot by those who don't.


signature.asc
Description: PGP signature

[gentoo-user] ati-drivers:legacy fail to build with kernel 3.12

[Helmut Jarausch]

Hi,

in "good" tradition the new 3.12 Linux kernel breaks  ati-drivers again  
(as always in the past).

Does anybody know about a patch to make
x11-drivers/ati-drivers:legacy
compile with linux-3.12-rc3 ?

Trying to emerge ati-drivers-13.1_pre897 (currently the only legacy  
driver)

with 3.12-rc3 gives

  MODPOST 1 modules
FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol  
'acpi_bus_get_device'


Many thanks for a hint,
Helmut

Re: [gentoo-user] SystemD + Gnome 3.8 I can log in as root but not as normal user

[Jochen Kirchner]

Am 01.10.2013 09:07, schrieb Carlos Sura:

In another note:

I've just installed enlightenment and it works fine. Gnome works fine 
ONLY as root, but not as normal user.



On 1 October 2013 01:06, Carlos Sura > wrote:


Hello Jochen,

Thank you for your help.

Here is the Xorg log: http://tny.cz/69b4662a

Regarding the gdm session.log I don't have it. Here is
the /var/log/gdm/:0.log : http://tny.cz/35e886e2

Here is my emerge --info: http://tny.cz/10262247




On 1 October 2013 00:52, Jochen Kirchner mailto:j...@acidc0re.info>> wrote:

Am 01.10.2013 08:30, schrieb Carlos Sura:

Hello Mates,

I finally thought that I got this working, so now I am
dealing this issue:
I choose the latest kernel with systemd and GDM starts good,
but I cannot log in to gnome as a normal user, I can only log
in to gnome as root.

What I have done before this started:

emerge -uDvaN world
emerge --depclean --ask
emerge @preserved-rebuild

Then it just happened.

What I've tried so far:
- .xinitrc with exec gnome-session for user and root
- emerge -1 $( qlist -IC x11-drivers/ )
- emerge @x11-module-rebuild
-  X -configure


Another note:
Starting gnome as normal user just hang, apparently it wants
to start but it cannot start. Neither doing: startx.

I am using for xorg:
VIDEO_CARDS="intel vesa"

Any help?

Regards

-- 
Carlos Sura.-

www.carlossura.com 
www.carlossura.com/blog 


Hi,

have you looked in your /var/log/Xorg.0.log?

And I think the GDM session log is in
/home/*user*/.cache/gdm/session.log.

Regards,

Jochen

-- 
"There is only one god, and his name is Death.

And there is only one thing we say to Death: 'Not today'."
- Syrio Forel, Game of Thrones

http://acidc0re.info




-- 
Carlos Sura.-

www.carlossura.com 
www.carlossura.com/blog 




--
Carlos Sura.-
www.carlossura.com 
www.carlossura.com/blog 

hm, that's strange. Is your user in the video group?

And I don't think you need vesa in VIDEO_CARDS. intel should be sufficient.

Best Regards,
Jochen

--
"There is only one god, and his name is Death.
And there is only one thing we say to Death: 'Not today'."
- Syrio Forel, Game of Thrones

http://acidc0re.info

Re: [gentoo-user] Slow network transfers ... lost interrupts because of clocksource?

[Stefan G. Weichinger]

Am 30.09.2013 22:03, schrieb Stefan G. Weichinger:

> I will simply let the scp take its time over night ... and I hope the
> KVM-performance will be OK when I start the converted VM.

I used split and tar to split the image-file into 100 MB parts and rsync
them over right now.

Maybe I have something wrong in my kernel ... the server shows a load of
around 3 ... while only the rsync is running and my mosh-session ...

This is a 24-core-system ... it shouldn't even blink ...

2 CPUs: AMD Opteron(tm) Processor 6344

I have:

CFLAGS="-O2 -march=native -pipe"
CXXFLAGS="-O2 -march=native -pipe"
CHOST="x86_64-pc-linux-gnu"

maybe one of you would be so kind and helpful and check my kernel-config
for obvious stupidity:

https://dl.dropboxusercontent.com/u/24516209/config

Thanks in advance, Stefan

Re: [gentoo-user] SystemD + Gnome 3.8 I can log in as root but not as normal user

[Walter Dnes]

On Tue, Oct 01, 2013 at 12:30:51AM -0600, Carlos Sura wrote
> Hello Mates,
> 
> I finally thought that I got this working, so now I am dealing this issue:
> I choose the latest kernel with systemd and GDM starts good, but I cannot
> log in to gnome as a normal user, I can only log in to gnome as root.
> 
> What I have done before this started:
> 
> emerge -uDvaN world
> emerge --depclean --ask
> emerge @preserved-rebuild
> 
> Then it just happened.
> 
> What I've tried so far:
> - .xinitrc with exec gnome-session for user and root
> -  emerge -1 $( qlist -IC x11-drivers/ )
> - emerge @x11-module-rebuild
> -  X -configure
> 
> 
> Another note:
> Starting gnome as normal user just hang, apparently it wants to start but
> it cannot start. Neither doing: startx.

  Can you temporarily rename your Gnome config file/directory on your
system, and see if it'll work with a fresh start?

  Another option to try, just as a test only, is...

USE="suid" emerge -pv --update --changed-use world

  Does that bring up anything related to Gnome?

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] some of the stuff in /usr that's become a problem

[Greg Woodbury]

On 09/29/2013 11:13 PM, William Hubbs wrote:
> On Sun, Sep 29, 2013 at 09:21:01PM -0500, Daniel Campbell wrote:
>>> /usr/lib/udev.
>>> /usr/lib/systemd.
>>>
>>> were both placed in /usr despite objections from a number of folks.
>>>
>>> So claims that udev and systemd are not responsible are not true.
> 
> Udev is installed in / in gentoo. I am a co-maintainer of udev and that
> was fixed quite some time back, it is the Gentoo systemd team that installs
> their version of udev in /usr.
> 
> Installing udev or eudev, however, doesn't really solve the issue
> though, because it is possible to run arbitrary programs from within
> udev rules.
> 
> Another unrelated concern is if you install a program in / that needs to
> access something in /usr/share, this will be broken by not having /usr
> mounted. This means that, for example, the locale logic of most software
> can't work without /usr since it accesses files in /usr/share/locale.
> 
> William
> 
All that is required is that the programs and libraries necessary to
locate and mount root and then to find and mount other filesystems be in
root.  This was a fundamental piece of the design of UNIX and was
inherited by many UNIX derived systems.  While debugging System IV
systematizing, we had meetings with the folks from Murray Hill and they
insisted that this had to be maintained. (circa 1982)

The actual details of what has broken are not as important as the fact
that the breakage happened and complaints about the breakage have be
dismissed with disrespect and disparaging remarks about clinging to
ancient history.  That has been done at least twice in this set of threads.

Certainly, Linux is an evolving and growing system, but there seems to
be no natural selection process to cull the things that don't work.
Change is NOT the problem, without change there can be no progress.  But
to change something for no good reason, simply to change it, is not healthy.

-- 
G.Wolfe Woodbury
redwo...@gmail.com

Re: [gentoo-user] some of the stuff in /usr that's become a problem

[Greg Woodbury]

On 09/29/2013 11:40 PM, Daniel Campbell wrote:

> You're right, though; it's a problem that lots of programs have. I
> guess it's the natural result of modular software that has
> interdependencies. You basically need *everything* available on boot.

You don't need everything (obviously -- otherwise dracut/init* would not
work)  Only the things necessary to get the system bootstrapped.

It occurs to me that anything dracut fetches from /usr/* to put in the
initrd is the stuff that has caused the breakage.

To me, the requirement for an initramfs/initrd is an admission of
failure.  Breaking the rules is what made it required.

-- 
G.Wolfe Woodbury
redwo...@gmail.com

Re: [gentoo-user] some of the stuff in /usr that's become a problem

[Alan McKinnon]

On 01/10/2013 10:30, Greg Woodbury wrote:
> All that is required is that the programs and libraries necessary to
> locate and mount root and then to find and mount other filesystems be in
> root.


Please provide the full and complete list of all code on all Gentoo
systems that are required in all supported configurations to support
that end. Keep in mind you are dealing with an open-ended problem.

Then provide patches to all ebuilds that will move said code to /

Then provide a means by which any new code in the future can be detected
to fall into this same category and alert the develops before too much
breakage happens.

Those three sentences above are not facetious. That is exactly what you
are expecting the Gentoo maintainers to do. I don't think you grasp the
full extent of this problem on modern Linux systems, it is not just a
case of doing what you have to do to mount all other filesystems, it's a
case of finding everything the must happen to do that and enforcing that
none of it creeps into /usr. Which includes all manner of things users
might validly want to so, most of it that you and I have never thought of.

Recall how Unix treats everything as a file and lets you pipe, tee and
redirect data in wonderful ways to produce output not envisaged by tool
designers?

The start-up sequence on modern Linuxes is starting to lean heavily in
an analogous direction. The simple days of 1982 when everything in early
boot was predictable are long gone.

-- 
Alan McKinnon
alan.mckin...@gmail.com

[gentoo-user] Re: Slow network transfers ... lost interrupts because of clocksource?

[Nicolas Sebrecht]

The 01/10/13, Stefan G. Weichinger wrote:

> I used split and tar to split the image-file into 100 MB parts and rsync
> them over right now.
> 
> Maybe I have something wrong in my kernel ... the server shows a load of
> around 3 ... while only the rsync is running and my mosh-session ...
> 
> This is a 24-core-system ... it shouldn't even blink ...

If you are sure the load don't come from userland (htop?), I would
think about reporting a kernel bug. This might be an issue with the NIC
driver.

-- 
Nicolas Sebrecht

PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Tanstaafl]

On 2013-09-30 3:14 PM, Alan McKinnon  wrote:

On 30/09/2013 19:25, Volker Armin Hemmann wrote:

>> Alan wrote:
>>> Charles wrote:

But... is /usr/portage the default/recommended location? If so, then I
don't think I want to move it - I generally never change defaults unless
there is a very good reason to do so.



It's /var/portage for new installs. If you want it to be somewhere else,
just move it and adjust make.conf



really? so when I moved PORTDIR to /var/portage I was ahead of the rest?
Wow...



You were ahead of me for sure :-)


So... if the change from /usr/portage to /var/portage was official, is 
there any (official) documentation on precisely how to move it?


Hmmm more importantly, when did this change occur? Is it possibly 
tied to portage 2.2? The reason I ask is, I'm still on 2.1, and man 
portage still has references to:


/usr/portage/sets
/usr/portage/metadata
/usr/portage/profiles
/usr/share/portage/config

and man make.conf still says:

PKGDIR = [path] 
  Defaults to /usr/portage/packages.

and most importantly:

PORTDIR = [path] 
  Defaults to /usr/portage.

So... are you quite certain that this default has in fact changed?

I know that it is probably trivial, but I like to read official docs for 
things like this...


Thanks again...

Re: [gentoo-user] SystemD + Gnome 3.8 I can log in as root but not as normal user

[Shawn Wilson]

rm ~/.Xauthority 

Walter Dnes  wrote:
>On Tue, Oct 01, 2013 at 12:30:51AM -0600, Carlos Sura wrote
>> Hello Mates,
>> 
>> I finally thought that I got this working, so now I am dealing this
>issue:
>> I choose the latest kernel with systemd and GDM starts good, but I
>cannot
>> log in to gnome as a normal user, I can only log in to gnome as root.
>> 
>> What I have done before this started:
>> 
>> emerge -uDvaN world
>> emerge --depclean --ask
>> emerge @preserved-rebuild
>> 
>> Then it just happened.
>> 
>> What I've tried so far:
>> - .xinitrc with exec gnome-session for user and root
>> -  emerge -1 $( qlist -IC x11-drivers/ )
>> - emerge @x11-module-rebuild
>> -  X -configure
>> 
>> 
>> Another note:
>> Starting gnome as normal user just hang, apparently it wants to start
>but
>> it cannot start. Neither doing: startx.
>
>  Can you temporarily rename your Gnome config file/directory on your
>system, and see if it'll work with a fresh start?
>
>  Another option to try, just as a test only, is...
>
>USE="suid" emerge -pv --update --changed-use world
>
>  Does that bring up anything related to Gnome?

Re: [gentoo-user] SystemD + Gnome 3.8 I can log in as root but not as normal user

[Canek Peláez Valdés]

On Tue, Oct 1, 2013 at 1:30 AM, Carlos Sura  wrote:
> Hello Mates,
>
> I finally thought that I got this working, so now I am dealing this issue:
> I choose the latest kernel with systemd and GDM starts good, but I cannot
> log in to gnome as a normal user, I can only log in to gnome as root.
>
> What I have done before this started:
>
> emerge -uDvaN world
> emerge --depclean --ask
> emerge @preserved-rebuild
>
> Then it just happened.
>
> What I've tried so far:
> - .xinitrc with exec gnome-session for user and root
> -  emerge -1 $( qlist -IC x11-drivers/ )
> - emerge @x11-module-rebuild
> -  X -configure
>
>
> Another note:
> Starting gnome as normal user just hang, apparently it wants to start but it
> cannot start. Neither doing: startx.
>
> I am using for xorg:
> VIDEO_CARDS="intel vesa"
>
> Any help?

Could you please boot up your machine, let GDM start, and then from a
console do "systemctl --all --full", and post here its output? Also,
can you try to do:

USE="systemd -consolekit policykit" emerge -uDNvp world

Does any package wants to be reemerged?

Lastly, does your kernel contains all the configuration options
required by systemd/udev?

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Alan McKinnon]

On 01/10/2013 14:35, Tanstaafl wrote:
> On 2013-09-30 3:14 PM, Alan McKinnon  wrote:
>> On 30/09/2013 19:25, Volker Armin Hemmann wrote:
>>> Alan wrote:
 Charles wrote:
> But... is /usr/portage the default/recommended location? If so, then I
> don't think I want to move it - I generally never change defaults
> unless
> there is a very good reason to do so.
> 
 It's /var/portage for new installs. If you want it to be somewhere
 else,
 just move it and adjust make.conf
> 
>>> really? so when I moved PORTDIR to /var/portage I was ahead of the rest?
>>> Wow...
> 
>> You were ahead of me for sure :-)
> 
> So... if the change from /usr/portage to /var/portage was official, is
> there any (official) documentation on precisely how to move it?
> 
> Hmmm more importantly, when did this change occur? Is it possibly
> tied to portage 2.2? The reason I ask is, I'm still on 2.1, and man
> portage still has references to:
> 
> /usr/portage/sets
> /usr/portage/metadata
> /usr/portage/profiles
> /usr/share/portage/config
> 
> and man make.conf still says:
> 
> PKGDIR = [path] 
>   Defaults to /usr/portage/packages.
> 
> and most importantly:
> 
> PORTDIR = [path] 
>   Defaults to /usr/portage.
> 
> So... are you quite certain that this default has in fact changed?

Yes. The docs are out of date.

> I know that it is probably trivial, but I like to read official docs for
> things like this...


It is trivial. All that it is, is a path to where some stuff is. That's
all, nothing more.

Change this in make.conf:

PORTDIR="/var/portage"
DISTDIR="/var/distfiles"
PKGDIR="/var/packages"

move the directories to the new location and run any old emerge command
of your choice. If you left something out, you'll get a message on the
screen.


You can have these directories any place you want and nothing breaks by
moving them around. The only change is the shipped default. So there are
loads of this you could worry about in IT, this ain't one of 'em





-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Dragostin Yanev]

On Tue, 01 Oct 2013 08:35:16 -0400
Tanstaafl  wrote:

> On 2013-09-30 3:14 PM, Alan McKinnon  wrote:
> > On 30/09/2013 19:25, Volker Armin Hemmann wrote:
>  >> Alan wrote:
>  >>> Charles wrote:
>  But... is /usr/portage the default/recommended location? If so,
>  then I don't think I want to move it - I generally never change
>  defaults unless there is a very good reason to do so.
> 
> >>> It's /var/portage for new installs. If you want it to be
> >>> somewhere else, just move it and adjust make.conf
> 
> >> really? so when I moved PORTDIR to /var/portage I was ahead of the
> >> rest? Wow...
> 
> > You were ahead of me for sure :-)
> 
> So... if the change from /usr/portage to /var/portage was official,
> is there any (official) documentation on precisely how to move it?
> 
> Hmmm more importantly, when did this change occur? Is it possibly 
> tied to portage 2.2? The reason I ask is, I'm still on 2.1, and man 
> portage still has references to:
> 
> /usr/portage/sets
> /usr/portage/metadata
> /usr/portage/profiles
> /usr/share/portage/config
> 
> and man make.conf still says:
> 
> PKGDIR = [path] 
>Defaults to /usr/portage/packages.
> 
> and most importantly:
> 
> PORTDIR = [path] 
>Defaults to /usr/portage.
> 
> So... are you quite certain that this default has in fact changed?
> 
> I know that it is probably trivial, but I like to read official docs
> for things like this...
> 
> Thanks again...
> 

Hi,
I haven't kept up with documentation but moving portage is
fairly straightforward.
Here's how I'd do it:

 mkdir /var/portage
 chown portage:portage /var/portage
 rsync -aHx /usr/portage/ /var/portage/ #add flags if using ext attr.

edit /etc/make.conf 
 PORTDIR="/var/portage"
 DISTDIR=${PORTDIR}/distfiles
 PKGDIR=${PORTDIR}/packages

edit /etc/portage/repos.conf/* accordingly

change default profile with eselect profile list
or manually link /etc/make.profile to the correct path

emerge --sync

when everything is working ok clean /usr/portage

Hope i was helpful,
netixen

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Tanstaafl]

On 2013-10-01 8:46 AM, Alan McKinnon  wrote:

I know that it is probably trivial, but I like to read official docs for
things like this...



It is trivial. All that it is, is a path to where some stuff is. That's
all, nothing more.


Ok, thanks... but (call me anal, because I am) I still think this 
deserves at least a tiny mention in the formal documentation somewhere, 
even if its just on a a wiki page or whatever.


Also, obviously the man docs for portage and make.conf should be updated...


Change this in make.conf:

PORTDIR="/var/portage"
DISTDIR="/var/distfiles"
PKGDIR="/var/packages"


Hmmm...

Currently, everything is in /usr/portage:

/usr/portage
/usr/portage/distfiles
/usr/portage/packages

But the new defaults are 3 separate directories as you specified above?

Or was that a typo, and they should be:

/var/portage
/var/portage/distfiles
/var/portage/packages

?

Another question...

Since these are the new defaults, how do new installs define them? Are 
they explicitly set in make.conf now? Or is it somewhere else more 
low-level - and if so, wouldn't it be better to change it there once 
I've moved everything and confirmed it is working properly?



move the directories to the new location


Is a cp -rp /usr/portage /var/portage (repeat for the others) sufficient?


and run any old emerge command of your choice. If you left something
out, you'll get a message on the screen.

You can have these directories any place you want and nothing breaks by
moving them around. The only change is the shipped default. So there are
loads of this you could worry about in IT, this ain't one of 'em


Heh... ok, thanks, but you see, I worry about *everything* (maybe that 
is one reason I rarely get bit badly doing things like this).

Re: [gentoo-user] Re: Slow network transfers ... lost interrupts because of clocksource?

[Stefan G. Weichinger]

Am 01.10.2013 14:32, schrieb Nicolas Sebrecht:
> The 01/10/13, Stefan G. Weichinger wrote:
> 
>> I used split and tar to split the image-file into 100 MB parts and rsync
>> them over right now.
>>
>> Maybe I have something wrong in my kernel ... the server shows a load of
>> around 3 ... while only the rsync is running and my mosh-session ...
>>
>> This is a 24-core-system ... it shouldn't even blink ...
> 
> If you are sure the load don't come from userland (htop?), I would
> think about reporting a kernel bug. This might be an issue with the NIC
> driver.

lspci shows:

Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)

This is a 4-port NIC ... maybe I need some specific drivers and not only
the tg3-kernel-module?

Stefan

Re: [gentoo-user] Managing multiple systems with identical hardware

[Michael Orlitzky]

Jumping in randomly:

With portage-2.2 stable, you can now put sets in overlays. This has
greatly simplified our shared configuration, because I can push out a
base set of packages to every system just by including it in our overlay
(which is configured on every machine).

If you can push out package sets, you can push out configuration. I've
recently started pushing out our Apache configs this way. I have a
package called apache2-macros, and an ebuild in our overlay for
apache2-macros-x.y.z. This is part of the set that gets installed on all
web servers, so when I update the apache2-macros package and ebuild, it
automatically gets pushed to the web servers during the next update.

You can use - instead for convenience, but then you'll have to
remember to re-emerge it now and then.

For the config files that /differ/, I just use a makefile. I have a git
repo laid out like the filesystem hierarchy, i.e. in the root of the
repo I have "etc", and "usr" directories containing any config files
that need to be copied to /etc or /usr. The makefile isn't very
complicated, one magic rule handles most of the files which are plain
text and wind up in /etc. Here's a short example.

  FILES = /etc/conf.d/net \
  /etc/portage/env

  all: $(FILES)

  /%: ./%
cp $< $@
chmod 644 $@

You can add more files without touching the rules unless you need
different permissions.

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Michael Orlitzky]

On 10/01/2013 08:35 AM, Tanstaafl wrote:
> 
> So... if the change from /usr/portage to /var/portage was official, is 
> there any (official) documentation on precisely how to move it?
> 
> Hmmm more importantly, when did this change occur? Is it possibly 
> tied to portage 2.2? The reason I ask is, I'm still on 2.1, and man 
> portage still has references to:
> 

Everyone agrees it should go under /var somewhere, and that the
distfiles shouldn't be in the tree,

  http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg54610.html

but no one location was chosen IIRC.

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Alan McKinnon]

On 01/10/2013 15:52, Tanstaafl wrote:
> On 2013-10-01 8:46 AM, Alan McKinnon  wrote:
>>> I know that it is probably trivial, but I like to read official docs for
>>> things like this...
> 
>> It is trivial. All that it is, is a path to where some stuff is. That's
>> all, nothing more.
> 
> Ok, thanks... but (call me anal, because I am) I still think this
> deserves at least a tiny mention in the formal documentation somewhere,
> even if its just on a a wiki page or whatever.
> 
> Also, obviously the man docs for portage and make.conf should be updated...


Err, yeah, that should have been done.

But none of that fazes me anymore. You should see some of the docs I'm
forced to use for "professional" "carrier grade" "premium level support"
products

> 
>> Change this in make.conf:
>>
>> PORTDIR="/var/portage"
>> DISTDIR="/var/distfiles"
>> PKGDIR="/var/packages"
> 
> Hmmm...
> 
> Currently, everything is in /usr/portage:
> 
> /usr/portage
> /usr/portage/distfiles
> /usr/portage/packages
> 
> But the new defaults are 3 separate directories as you specified above?
> 
> Or was that a typo, and they should be:
> 
> /var/portage
> /var/portage/distfiles
> /var/portage/packages

No, I have them the way I posted.

For years portage shipped with this really dumbass stupid notion of
shoving local overlays, binpkgs and distfiles all in with the tree.
Dumb, dumb, dumb. It makes using rsync needlessly difficult and you
can't deal with the tree as a single directory unit without putting an
exclusion in.

So I split them up and rigged things so each category of thing is in
it's own distinct directory tree. Like I said earlier, they are just
paths and you can put them anywhere you like. You too can put yours
anywhere it makes sense to you.

> 
> ?
> 
> Another question...
> 
> Since these are the new defaults, how do new installs define them? Are
> they explicitly set in make.conf now? Or is it somewhere else more
> low-level - and if so, wouldn't it be better to change it there once
> I've moved everything and confirmed it is working properly?

The default is in the portage code somewhere. I don't care where.

What I do know is how to make mine something different, and that's what
I did.

Look, this is not hard. It's like having a photo app default to storing
your photos in "~/.local/share/my-app/DCIM/data/local/photos/public/"
and you take one look at this and decide that's for the birds. So you
click View->Settings and see "Photo Library location", make it
"~/photos" and promptly forget that the stupid default ever existed.

This is exactly like that.


> 
>> move the directories to the new location
> 
> Is a cp -rp /usr/portage /var/portage (repeat for the others) sufficient?
> 
>> and run any old emerge command of your choice. If you left something
>> out, you'll get a message on the screen.
>>
>> You can have these directories any place you want and nothing breaks by
>> moving them around. The only change is the shipped default. So there are
>> loads of this you could worry about in IT, this ain't one of 'em
> 
> Heh... ok, thanks, but you see, I worry about *everything* (maybe that
> is one reason I rarely get bit badly doing things like this).
> 


-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Neil Bothwick]

On Tue, 01 Oct 2013 09:52:47 -0400, Tanstaafl wrote:

> On 2013-10-01 8:46 AM, Alan McKinnon  wrote:
> >> I know that it is probably trivial, but I like to read official docs
> >> for things like this...
> 
> > It is trivial. All that it is, is a path to where some stuff is.
> > That's all, nothing more.
> 
> Ok, thanks... but (call me anal, because I am) I still think this 
> deserves at least a tiny mention in the formal documentation somewhere, 
> even if its just on a a wiki page or whatever.
> 
> Also, obviously the man docs for portage and make.conf should be
> updated...

man make.conf

PORTDIR = [path]
 Defines the location of the Portage tree. This is the repository for all
 profile information as well as all ebuilds. If you change this, you must
 update your /etc/portage/make.profile symlink accordingly.

That's it. he portage tree is just a directory full of files, all you
need to tell portage is where to find it.

mv /usr/portage /var/
Change PORTDIR in make.conf
eselect profile list and set

> > You can have these directories any place you want and nothing breaks
> > by moving them around. The only change is the shipped default. So
> > there are loads of this you could worry about in IT, this ain't one
> > of 'em
 
> Heh... ok, thanks, but you see, I worry about *everything* (maybe that 
> is one reason I rarely get bit badly doing things like this).
 
What's the worst that can happen? Portage stops working until you move it
back or correct PORTDIR. That's not system-critical, you can't break your
system by moving a bunch of bash scripts that are never used unless you
explicitly tell portage to do so.


-- 
Neil Bothwick

c:>Press Enter to Exit


signature.asc
Description: PGP signature

[gentoo-user] emerge --sync issue on only one comp on LAN

[Bruce Hill]

There are 3 (or more) computers which sync (sometimes daily) on my LAN at
work: server, router, and workstation. server has issues almost all the time
getting a rsync server (for lack of better way to state it). All three comps
have the exact same SYNC in make.conf:

mingdao@server ~ $ grep SYNC /etc/make.conf
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"

mingdao@router ~ $ grep SYNC /etc/portage/make.conf
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"

mingdao@workstation ~ $ grep SYNC /etc/portage/make.conf
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"

When I first noticed, it was that with the same command (alias ud) run on each
computer, server *always* took a good deal longer than workstation and router.

Here's the output from the emerge --sync portion of my "ud" alias today:

alias ud='eix-sync && emerge -aDjuv --changed-use @world && dispatch-conf && 
emerge -a --depclean && revdep-rebuild -i && clear && exit'

server ~ # ud
 * Running emerge --sync
>>> Synchronization of repository 'gentoo' located in '/usr/portage'...
>>> Starting rsync with rsync://128.61.111.9/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(549) 
[Receiver=3.0.9]
>>> Retrying...


>>> Starting retry 1 of 9 with rsync://209.59.138.21/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(549) 
[Receiver=3.0.9]
>>> Retrying...


>>> Starting retry 2 of 9 with rsync://128.175.60.112/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(549) 
[Receiver=3.0.9]
>>> Retrying...


>>> Starting retry 3 of 9 with rsync://129.21.171.98/gentoo-portage
>>> Checking server timestamp ...

receiving incremental file list
timestamp.chk

Number of files: 1
Number of files transferred: 1
Total file size: 32 bytes
Total transferred file size: 32 bytes
Literal data: 32 bytes
Matched data: 0 bytes
File list size: 27
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 98
Total bytes received: 140

sent 98 bytes  received 140 bytes  158.67 bytes/sec
total size is 32  speedup is 0.13

receiving incremental file list




router ~ # ud
 * Running emerge --sync
>>> Synchronization of repository 'gentoo' located in '/usr/portage'...
>>> Starting rsync with rsync://208.100.4.53/gentoo-portage...
>>> Checking server timestamp ...
 
 Welcome! This is a gentoo-portage and CentOS mirror, hosted by 
 Steadfast Networks!

 http://steadfast.net

   Hostname: mirror.steadfast.net & rsync11.us.gentoo.org
   IP Addresses: 208.100.4.53 & 2607:f128:1:3::2
   Location: Chicago, IL, US
   Bandwidth:1000 Mbps
   Hardware: Dual Opteron 2212, 8 GB RAM
   User Limit:   40

 If you experience any trouble with this mirror, please contact 
 mir...@steadfast.net.

receiving incremental file list
timestamp.chk

Number of files: 1
Number of files transferred: 1
Total file size: 32 bytes
Total transferred file size: 32 bytes
Literal data: 32 bytes
Matched data: 0 bytes
File list size: 27
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 98
Total bytes received: 570

sent 98 bytes  received 570 bytes  445.33 bytes/sec
total size is 32  speedup is 0.05
 
 Welcome! This is a gentoo-portage and CentOS mirror, hosted by 
 Steadfast Networks!

 http://steadfast.net

   Hostname: mirror.steadfast.net & rsync11.us.gentoo.org
   IP Addresses: 208.100.4.53 & 2607:f128:1:3::2
   Location: Chicago, IL, US
   Bandwidth:1000 Mbps
   Hardware: Dual Opteron 2212, 8 GB RAM
   User Limit:   40

 If you experience any trouble with this mirror, please contact 
 mir...@steadfast.net.

receiving incremental file list




workstation ~ # ud
 * Running emerge --sync
>>> Synchronization of repository 'gentoo' located in '/usr/portage'...
>>> Starting rsync with rsync://209.221.142.124/gentoo-portage...
>>> Checking server timestamp ...
Gentoo Portage/CPAN rsync mirror
Server: gentoo.llarian.net & cpan.llarian.net
IP(s): 209.221.142.124 & 2001:5d8:11::13
Bandwidth: 1000Mbps via multiple carriers
User Limit: 30
Location: Seattle, WA, USA
Admin Contact: Dylan Vanderhoof 


receiving incremental file list
timestamp.chk

Number of files: 1
Number of files transferred: 1
Total file size: 32 bytes
Total transferred file size: 32 bytes
Literal data: 32 bytes
Matched data: 0 bytes
File list size: 27
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 98
Total bytes received: 392

sent 98 bytes  received 392 bytes  326.67 bytes/sec
total size is 32  speedup is 0.07
Gentoo Portage/CPAN rsync mirror
Server: gentoo.llarian.net & cpan.llarian.net
IP(s): 209.221.142.124 & 2001:5d8:11::13
Bandwidth: 1000Mbps via multiple carriers
User Limit: 30
Location: Seattle, WA, USA
Admin Contact: Dylan Vanderhoof 


receiv

Re: [gentoo-user] emerge --sync issue on only one comp on LAN

[Alan McKinnon]

On 01/10/2013 16:20, Bruce Hill wrote:
> There are 3 (or more) computers which sync (sometimes daily) on my LAN at
> work: server, router, and workstation. server has issues almost all the time
> getting a rsync server (for lack of better way to state it). All three comps
> have the exact same SYNC in make.conf:
> 
> mingdao@server ~ $ grep SYNC /etc/make.conf
> SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
> 
> mingdao@router ~ $ grep SYNC /etc/portage/make.conf
> SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
> 
> mingdao@workstation ~ $ grep SYNC /etc/portage/make.conf
> SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"


Most likely obvious cause:

You have outbound firewall rules on your server/router affecting the server.















> 
> When I first noticed, it was that with the same command (alias ud) run on each
> computer, server *always* took a good deal longer than workstation and router.
> 
> Here's the output from the emerge --sync portion of my "ud" alias today:
> 
> alias ud='eix-sync && emerge -aDjuv --changed-use @world && dispatch-conf && 
> emerge -a --depclean && revdep-rebuild -i && clear && exit'
> 
> server ~ # ud
>  * Running emerge --sync
 Synchronization of repository 'gentoo' located in '/usr/portage'...
 Starting rsync with rsync://128.61.111.9/gentoo-portage...
 Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(549) 
> [Receiver=3.0.9]
 Retrying...
> 
> 
 Starting retry 1 of 9 with rsync://209.59.138.21/gentoo-portage
 Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(549) 
> [Receiver=3.0.9]
 Retrying...
> 
> 
 Starting retry 2 of 9 with rsync://128.175.60.112/gentoo-portage
 Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(549) 
> [Receiver=3.0.9]
 Retrying...
> 
> 
 Starting retry 3 of 9 with rsync://129.21.171.98/gentoo-portage
 Checking server timestamp ...
> 
> receiving incremental file list
> timestamp.chk
> 
> Number of files: 1
> Number of files transferred: 1
> Total file size: 32 bytes
> Total transferred file size: 32 bytes
> Literal data: 32 bytes
> Matched data: 0 bytes
> File list size: 27
> File list generation time: 0.001 seconds
> File list transfer time: 0.000 seconds
> Total bytes sent: 98
> Total bytes received: 140
> 
> sent 98 bytes  received 140 bytes  158.67 bytes/sec
> total size is 32  speedup is 0.13
> 
> receiving incremental file list
> 
> 
> 
> 
> router ~ # ud
>  * Running emerge --sync
 Synchronization of repository 'gentoo' located in '/usr/portage'...
 Starting rsync with rsync://208.100.4.53/gentoo-portage...
 Checking server timestamp ...
>  
>  Welcome! This is a gentoo-portage and CentOS mirror, hosted by 
>  Steadfast Networks!
> 
>  http://steadfast.net
> 
>Hostname: mirror.steadfast.net & rsync11.us.gentoo.org
>IP Addresses: 208.100.4.53 & 2607:f128:1:3::2
>Location: Chicago, IL, US
>Bandwidth:1000 Mbps
>Hardware: Dual Opteron 2212, 8 GB RAM
>User Limit:   40
> 
>  If you experience any trouble with this mirror, please contact 
>  mir...@steadfast.net.
> 
> receiving incremental file list
> timestamp.chk
> 
> Number of files: 1
> Number of files transferred: 1
> Total file size: 32 bytes
> Total transferred file size: 32 bytes
> Literal data: 32 bytes
> Matched data: 0 bytes
> File list size: 27
> File list generation time: 0.001 seconds
> File list transfer time: 0.000 seconds
> Total bytes sent: 98
> Total bytes received: 570
> 
> sent 98 bytes  received 570 bytes  445.33 bytes/sec
> total size is 32  speedup is 0.05
>  
>  Welcome! This is a gentoo-portage and CentOS mirror, hosted by 
>  Steadfast Networks!
> 
>  http://steadfast.net
> 
>Hostname: mirror.steadfast.net & rsync11.us.gentoo.org
>IP Addresses: 208.100.4.53 & 2607:f128:1:3::2
>Location: Chicago, IL, US
>Bandwidth:1000 Mbps
>Hardware: Dual Opteron 2212, 8 GB RAM
>User Limit:   40
> 
>  If you experience any trouble with this mirror, please contact 
>  mir...@steadfast.net.
> 
> receiving incremental file list
> 
> 
> 
> 
> workstation ~ # ud
>  * Running emerge --sync
 Synchronization of repository 'gentoo' located in '/usr/portage'...
 Starting rsync with rsync://209.221.142.124/gentoo-portage...
 Checking server timestamp ...
> Gentoo Portage/CPAN rsync mirror
> Server: gentoo.llarian.net & cpan.llarian.net
> IP(s): 209.221.142.124 & 2001:5d8:11::13
> Bandwidth: 1000Mbps via multiple carriers
> User Limit: 30
> Location: Seattle, WA, USA
> Admin Contact: Dylan Vanderhoof 
> 
> 
> receiving incremental file list
> timestamp.chk
> 
> Number of files: 1
> Number of files transferred: 1
> Total file size: 32 bytes
> Total transferred file size: 32 bytes
> Literal data: 32 bytes
> Matched data: 0 bytes
> File list size: 27

Re: [gentoo-user] gcc-bin for stupid user

[Alain Didierjean]

- Mail original -
> De: "Bruce Hill" 
> À: gentoo-user@lists.gentoo.org
> Envoyé: Dimanche 29 Septembre 2013 21:53:39
> Objet: Re: [gentoo-user] gcc-bin for stupid user
> 
> On Sun, Sep 29, 2013 at 04:44:29PM +0200, Alain Didierjean wrote:
> > I'm in trouble for having stupidly unmerged gcc and gcc-config !
> > What's the easiest way, if any, to grab and install a binary gcc
> > allowing me to emerge... gcc !
> > We're talking about amd64.
> 
> I don't know if you solved your issue, or exactly what you have, but
> this
> weekend's gcc-4.7 move to stable caused me to have to:
> 
> gcc-config x86_64-pc-linux-gnu-4.7.3
> . /etc/profile
> 

I didn't solved my issue: I downloaded and installed gcc and gcc-config from 
tinderbox and now the whole kde apps don't work, libc++ being out of reach 
(it's in /usr/lib64 all right). What did I possibly mess up ? I can't find any 
significant difference between /etc and /mnt/key/etc (a recent backup)...
I will reinstall only if I can't help it, as one of the reason I've been using 
gentoo for 8-10 years is I only have to reinstall when renewing the hardware.

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Neil Bothwick]

On Tue, 01 Oct 2013 16:11:56 +0200, Alan McKinnon wrote:

> So I split them up and rigged things so each category of thing is in
> it's own distinct directory tree. Like I said earlier, they are just
> paths and you can put them anywhere you like. You too can put yours
> anywhere it makes sense to you.

And if you have more that one Gentoo box on the network, it makes sense
to have DISTDIR and a NFS share for all of them, so save downloading the
same files multiple times.


-- 
Neil Bothwick

There are some micro-organisms that exhibit characteristics of both
plants and animals.  When exposed to light they undergo photosynthesis;
and when the lights go out, they turn into animals.  But then again,
don't we all?


signature.asc
Description: PGP signature

Re: [gentoo-user] gcc-bin for stupid user

[Neil Bothwick]

On Tue, 1 Oct 2013 16:52:53 +0200 (CEST), Alain Didierjean wrote:

> I didn't solved my issue: I downloaded and installed gcc and gcc-config
> from tinderbox and now the whole kde apps don't work, libc++ being out
> of reach (it's in /usr/lib64 all right). What did I possibly mess up ?
> I can't find any significant difference between /etc and /mnt/key/etc
> (a recent backup)...

Downloading a binary from tinderbox is only a stopgap, to allow you to
emerge the correct gcc for your system. do that now and all else should
fall into place.


-- 
Neil Bothwick

Windows Error #10: Insufficient money spent in hardware.


signature.asc
Description: PGP signature

Re: [gentoo-user] Managing multiple systems with identical hardware

[Neil Bothwick]

On Tue, 01 Oct 2013 10:04:54 -0400, Michael Orlitzky wrote:

> With portage-2.2 stable, you can now put sets in overlays.

Nice! I missed that.


-- 
Neil Bothwick

System halted - Press all keys at once to continue.


signature.asc
Description: PGP signature

Re: [gentoo-user] emerge --sync issue on only one comp on LAN

[Greg Turner]

On Tue, Oct 1, 2013 at 7:20 AM, Bruce Hill
 wrote:
> There are 3 (or more) computers which sync (sometimes daily) on my LAN at
> work: server, router, and workstation. server has issues almost all the time
> getting a rsync server (for lack of better way to state it). All three comps
> have the exact same SYNC in make.conf:

Seriously?  Your problem is that an incredible build-up of bad karma
has polluted your network.  You are selfishly and pointlessly wasting
the rsync.us.gentoo.org mirror network's resources, and your own
bandwidth as well.

Run rsyncd somewhere.  Sync the other two systems to it.  If the
server has problems with outbound connectivity, use the router, I
guess.

Rsync mirrors don't grow on trees, man.  People pay good money to
provide that service to us.  You should seriously be embarrassed to
have posted this.

-gmt

Re: [gentoo-user] emerge --sync issue on only one comp on LAN

[Alan McKinnon]

On 01/10/2013 17:17, Greg Turner wrote:
> On Tue, Oct 1, 2013 at 7:20 AM, Bruce Hill
>  wrote:
>> There are 3 (or more) computers which sync (sometimes daily) on my LAN at
>> work: server, router, and workstation. server has issues almost all the time
>> getting a rsync server (for lack of better way to state it). All three comps
>> have the exact same SYNC in make.conf:
> 
> Seriously?  Your problem is that an incredible build-up of bad karma
> has polluted your network.  You are selfishly and pointlessly wasting
> the rsync.us.gentoo.org mirror network's resources, and your own
> bandwidth as well.
> 
> Run rsyncd somewhere.  Sync the other two systems to it.  If the
> server has problems with outbound connectivity, use the router, I
> guess.
> 
> Rsync mirrors don't grow on trees, man.  People pay good money to
> provide that service to us.  You should seriously be embarrassed to
> have posted this.



Really?


Then you can all use mine with the greatest of pleasure:

SYNC="rsync://ftp.is.co.za/gentoo-portage"


I have the NetOps team BEGGING me weekly to try and generate more
traffic out of our network going international. The in-out ratio on the
peering links is seriously screwed and they badly want something to even
it out a bit :-)




-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Re: Flexibility and robustness in the Linux organisim

[Volker Armin Hemmann]

Am 01.10.2013 01:21, schrieb Francisco Blas Izquierdo Riera (klondike):
> El 30/09/13 00:47, Volker Armin Hemmann escribió:
>> Am 29.09.2013 18:41, schrieb Francisco Blas Izquierdo Riera (klondike):
>>> El 29/09/13 18:03, Volker Armin Hemmann escribió:
 Am 29.09.2013 17:12, schrieb Greg Woodbury:
> On 09/29/2013 07:58 AM, Volker Armin Hemmann wrote:
>
>> things were broken way before that. As much as I hate systemd, it is not
>> the root cause of the problem.
>>
>> The problems were caused by people saying that seperate /usr was a good
>> idea, so / would not fill up and similar idiocies. The problems were
>> caused by people saying that lvm is a good idea - for desktops. Those
>> people who are fighting against the kernel auto assembling raids are to
>> blame too.
>>
>> Systemd is just another point in a very long list.
>>
> The usr filesystem was separate from root from the very early days of
> UNIX.  Disks were *tiny* (compared to today) and spreading certain
> things across separate spindles provided major benefits. Certainly,
> the original need to require a separate usr went away fairly quickly,
> but other benefits continued to encourage a seperation between root
> and usr.
>
 in the very early days /usr did not exist in the first space and was
 only created because someone added a harddisk.

 Not really a good reason to keep it around.
>>> I'm going to show the lack of sense of this argument:
>>> in the very early days linux did not exist in the first space and was
>>> only created because someone got a 386.
>>>
>>> Not really a good reason to keep it around.
>> wrong analogy and it goes down from here. Really.
> Ohh, but they are inspired on YOUR analogy, so guess how wrong yours was.

your trolling is weak. And since I never saw anything worth reading
posted by you, you are very close to plonk territory right now.

>>> in the very early days GNU did not exist in the first space and was
>>> only created because someone jammed a printer.
>>>
>>> Not really a good reason to keep it around.
>>>
>>> in the very early days Gentoo did not exist in the first space and was
>>> only created because someone added a processor.
>>>
>>> Not really a good reason to keep it around.
>>>
>>> in the very early days hardening did not exist in the first space and was
>>> only created because someone added security.
>>>
>>> Not really a good reason to keep it around.
>>>
>>> in the very early days Gnome did not exist in the first space and was
>>> only created because someone got a graphics card.
>>>
>>> Not really a good reason to keep it around.
>>>
>>> I'm sure you'll be able to figure out the pattern there.
>>>
>>> Ohh and BTW, /usr was not just added because someone added a harddrive,
>>> in most cases it was used to allow machines contain a very small system
>>> on / which was enough to just boot and mount a networked system (/usr)
>>> containing most of the software. This allowed for cheaper deployment of
>>> machines since the hard drive could be smaller as it wouldn't need to
>>> have all the data locally. Yeah, if this sounds familiar is because this
>>> was later moved to initramfs.
>> no, network'ed file systems came a lot later.
>> Initially /usr was added because one harddisk was full. Really, that is
>> the whole reason for its (broken) existance.
> Please provide some reference about "Initially /usr was added because
> one harddisk was full." without it your statement is moot to me.

see Mark David Dumlao's mails.

But it is interesting, that you are attacking others with your superior
knowledge - and then show that you lack exactly that. You are talking
about stuff you have no clue at all about.

>
> The setup of a separate /usr on a networked system was used in amongst
> other places a few swedish universities.

seperate /usr on network has been used in a lot of places. So what? Does
that prove anything?
Nope, it doesn't.

> The var filesystem was for variable system data, and was never
> terribly big and its inclusion on the root volume happened.  The home
> filesystem  became traditionally separate because data expands to fill
> all availab;e space, and users collect *things*
 and a seperate /home does not create any problems.
 /var is much more prone to accidentally fill up then /usr ever was.
>>> You are jst getting it wrong, /var was kept locally as the data there
>>> was supposed to change from machine to machine.
>> no, you just don't understand what I wrote.
>> People told other people to keep /usr seperate so / may not fill up by
>> accident.
>>
>> That advise always was murky at best. Outright stupid is a good
>> description too.
>>
>> /usr is not prone to much changes. So if your / fits the contents of
>> /usr just fine, there is pretty much no risk.
>> /var on the other hand tends to explode - but a lot of people never got
>> told to put /var on a seperate disk.
>>
>

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Tanstaafl]

On 2013-10-01 10:14 AM, Michael Orlitzky  wrote:

On 10/01/2013 08:35 AM, Tanstaafl wrote:


So... if the change from /usr/portage to /var/portage was official, is
there any (official) documentation on precisely how to move it?

Hmmm more importantly, when did this change occur? Is it possibly
tied to portage 2.2? The reason I ask is, I'm still on 2.1, and man
portage still has references to:



Everyone agrees it should go under /var somewhere, and that the
distfiles shouldn't be in the tree,

   http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg54610.html

but no one location was chosen IIRC.


?

I'm interested in what the DEFAULTS are, ie, for a new/from scratch 
installation.


Someone had to decide the defaults - so, what are they? Anyone?

Re: [gentoo-user] ati-drivers:legacy fail to build with kernel 3.12

[Volker Armin Hemmann]

Am 01.10.2013 10:00, schrieb Helmut Jarausch:
> Hi,
>
> in "good" tradition the new 3.12 Linux kernel breaks  ati-drivers
> again (as always in the past).
> Does anybody know about a patch to make
> x11-drivers/ati-drivers:legacy
> compile with linux-3.12-rc3 ?
>
> Trying to emerge ati-drivers-13.1_pre897 (currently the only legacy
> driver)
> with 3.12-rc3 gives
>
>   MODPOST 1 modules
> FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol
> 'acpi_bus_get_device'
>
> Many thanks for a hint,
> Helmut
>

so you are using a driver meant for stable (old) systems, with a pre
release kernel - and you don't even know what do do with that message?

Does that do no seem a bit silly? hm?

acpi_bus_get_device is gpl only. You can undo that. If you want.

But seriously, what is wrong with using stable releases like 3.10.x? If
you use ati-drivers, you don't need the amd driver improvements in 3.11
or 3.12.

Re: [gentoo-user] Managing multiple systems with identical hardware

[joost]

Alan McKinnon  wrote:
>On 30/09/2013 19:31, Grant wrote:
 Keeping all of the laptops 100% identical as far as hardware is
 central to this plan.  I know I'm setting myself up for big
>problems
 otherwise.

 I'm hoping I can emerge every package on my laptop that every other
 laptop needs.  That way I can fix any build problems and update any
 config files right on my own system.  Then I would push config file
 differences to all of the other laptops.  Then each laptop could
 emerge its own stuff unattended.
>>>
>>> I see what you desire now - essentially you want to clone your
>laptop
>>> (or big chunks of it) over to your other workstations.
>> 
>> That sounds about right.
>> 
>>> To get a feel for how it works, visit puppet's web site and download
>>> some of the test appliances they have there and run them in vm
>software.
>>> Set up a server and a few clients, and start experimenting in that
>>> sandbox. You'll quickly get a feel for how it all hangs together
>(it's
>>> hard to describe in text how puppet gets the job done, so much
>easier to
>>> do it for real and watch the results)
>> 
>> Puppet seems like overkill for what I need.  I think all I really
>need
>> is something to manage config file differences and user accounts.  At
>> this point I'm thinking I shouldn't push packages themselves, but
>> portage config files and then let each laptop emerge unattended based
>> on those portage configs.  I'm going to bring this to the 'salt'
>> mailing list to see if it might be a good fit.  It seems like a much
>> lighter weight application.
>
>Two general points I can add:
>
>1. Sharing config files turns out to be really hard. By far the easiest
>way is to just share /etc but that is an all or nothing approach, and
>you just need one file to be different to break it. Like /etc/hostname
>
>You *could* create a "share" directory inside /etc and symlink common
>files in there, but that gets very tedious quickly.
>
>Rather go for a centralized repo solution that pushes configs out, you
>must just find the one that's right for you.
>
>2. Binary packages are almost perfect for your needs IMHO, running
>emerge gets very tedious quickly, and your spec is that all
>workstations
>have the same USE. You'd be amazed how much time you save by doing
>this:
>
>emerge -b on your laptop and share your /var/packages
>emerge -K on the workstations when your laptop is on the network
>
>step 2 goes amazingly quickly - eyeball the list to be emerged, they
>should all be purple, press enter. About a minute or two per
>workstation, as opposed to however many hours the build took.
>
>3. (OK, three points). Share your portage tree over the network. No
>point in syncing multiple times when you actually just need to do it
>once.
>
>
>> 
>> I'm soaking up a lot of your time (again).  I'll return with any real
>> Gentoo questions I run into and to run down the final plan before I
>> execute it.  Thanks so much for your help.  Not sure what I'd do
>> without you. :)
>
>I'm sure Neil would step in if I'm hit by a bus
>He'd say the same things, and use about 1/4 of the words it takes me
>;-)
>
>
>-- 
>Alan McKinnon
>alan.mckin...@gmail.com

Grant,

Additionally. You might want to consider sharing /etc/portage and 
/var/lib/portage/world (the file)
I do that between my build host and the other machines. (Along with the portage 
tree, packages and distfiles)

That way all workstations end up with the same packages each time you run 
"emerge -vauDk world" on them.

And like Alan said, it goes really quick.

--
Joost

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Neil Bothwick]

On Tue, 01 Oct 2013 14:15:49 -0400, Tanstaafl wrote:

> I'm interested in what the DEFAULTS are, ie, for a new/from scratch 
> installation.

Why? If ever there was a distro for people that didn't want to use
defaults, Gentoo is it.

> Someone had to decide the defaults - so, what are they? Anyone?

I installed a VM a couple of weeks ago and I'm sure portage was still
in /usr. It's easy enough to tell, unpack a stage 3 and see where the
portage directory lives, but the handbook still refers to /usr/portage.


-- 
Neil Bothwick

Is it possible to be totally partial?


signature.asc
Description: PGP signature

Re: [gentoo-user] Re: Slow network transfers ... lost interrupts because of clocksource?

[Stefan G. Weichinger]

Am 01.10.2013 16:00, schrieb Stefan G. Weichinger:

> Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
> 
> This is a 4-port NIC ... maybe I need some specific drivers and not only
> the tg3-kernel-module?

for the records and if someone wants to join in:

recompiled the kernel, put in some ACPI-stuff and chose "generic X86_64"
for the processor type. This somehow helped ... the load is lower now
and the system is more responsive.

I am considering to change the (auto-generated? by systemd) mount
options for the ext4-fs: data=ordered ...

-

Right now I am re-cat-ing my splitted image file ... we'll see.

Stefan

Re: [gentoo-user] Re: Flexibility and robustness in the Linux organisim

[Mark David Dumlao]

On Mon, Sep 30, 2013 at 2:31 PM, pk  wrote:
> On 2013-09-30 00:04, Alan McKinnon wrote:
>
>> It's the general idea that you can leave /usr unmounted until some
>> random arb time later in the startup sequence and just expect things to
>> work out fine that is broken.
>>
>> It just happened to work OK for years because nothing happened to use
>> the code in /usr at that point in the sequence. More and more we are
>> seeing that this is no longer the case.
>
> So basically it wasn't broke before stuff started to use the code in
> /usr. How isn't that breaking?
>
>> So no-one broke it with a specific commit. It has always been broken by
>> design becuase it's a damn stupid idea that just happened to work by
>> fluke. IT and computing is rife with this kind of error.
>
> If what you are saying is true then *everything* is broken "by design"
> if something isn't available at boot time (may be /usr, may be /var or
> whatever).

Let me make an analogy between programs and recipes.

You see, a program is a lot like a recipe. It's a set of instructions
for a computer to follow. And if you have a recipe where if you follow
it, and anyone that eats the food says it tastes good, then you have a
good recipe.

Let me make an analogy between a restaurant franchise and a
distribution. You see, a franchise is a set of instructions for a
restaurateur to follow. A lot of those instructions are recipes. They
tell the restaurateur how to cook foods. But not all of those
instructions are. Some of them are instructions on the ideal
conditions to cook. Or some of them are instructions on how to get
materials, or how to talk to customers, or how to keep employees
happy. Now if you follow those instructions, and have the right
resources, you get to create a restaurant. In the same way, a
distribution can be thought of as a set of instructions. If you follow
those instructions, and have the right resources, you get to install a
lot of programs on a computer.

If everybody that follows the instructions on a recipe creates a food
that a lot of people think tastes great, then you have a great recipe.
And if everybody that follows the instuctions on a franchise creates a
restaurant that a lot of customers buy from and think the food is
great, then you have a great franchise.

Now let's say you have a franchise with very specific instructions to
buy ingredients from the nearest organic store. Now for many
restaurants that follow these instructions, they end up with great
food that makes an okay amount of money. But in some cities the
organic store doesn't have very good lettuce. Or the carrots are too
expensive. Or there isn't any organic store at all, so the restaurant
owner has to go to the next city and waste a lot of time and money to
get eggs. So those restaurants fail. But for many restaurants the
instructions work.

Now the restaurant owners get together and complain that their
restaurant isn't working. Why? they ask. It's because the head
franchise added pizza to the menu! The menu was working fine without
the pizza, but when they added pizza it became to expensive or
impractical to turn a profit. They might say that the franchise was
broken by the pizza. But many restaurant owners do fine by pizza. In
fact for many of them it's their hottest and most profitable product.

You see, the problem isn't the inclusion of a specific recipe. The
addition of pizza didn't break the restaurant. Nor did the addition of
burgers, or coke, or fries or whatever. The problem was with
instructions on how to manage the recipe ingredients. In short, while
they were practical for a lot of restaurant owners, they weren't
practical _in general_. The instructions could be better improved by
saying something like "buy ingredients from stores that give you this
much return," or "buy ingredients from our approved suppliers since
they give the best return on your money". If those instructions were
given instead of just vaguely saying to purchase from an organic
store, they'd have better control over the quality and profitability
of the restaurants.

And this is something like what is wrong with /usr. The individual
programs may be good. Many parts of the system taken together may be
good. But the instructions on how to manage programs going to /usr or
to / is too vague. There is no definitive quality control behind it.
Even if you follow the instructions, as best as you can, you will end
up making stupid decisions for the distribution.

Likewise with the franchise restaurants. The individual foods may be
good. Many of the instructions on managing people, foods, customers,
may be good.  But the whole concept of "purchase from some a supplier
with undefined levels of cost and quality" is NOT a good instruction.
Maybe that works for a lot of restaurants, but as a general rule it
doesn't work for all of them. If you follow it to the letter, you will
end up making stupid decisions for the restaurant.

And here's your problem. The franchise instructions aren't su

Re: [gentoo-user] Re: Flexibility and robustness in the Linux organisim

[Mark David Dumlao]

On Wed, Oct 2, 2013 at 3:22 AM, Mark David Dumlao  wrote:
> On Mon, Sep 30, 2013 at 2:31 PM, pk  wrote:
>> On 2013-09-30 00:04, Alan McKinnon wrote:
>>
>>> It's the general idea that you can leave /usr unmounted until some
>>> random arb time later in the startup sequence and just expect things to
>>> work out fine that is broken.
>>>
>>> It just happened to work OK for years because nothing happened to use
>>> the code in /usr at that point in the sequence. More and more we are
>>> seeing that this is no longer the case.
>>
>> So basically it wasn't broke before stuff started to use the code in
>> /usr. How isn't that breaking?
>>
>>> So no-one broke it with a specific commit. It has always been broken by
>>> design becuase it's a damn stupid idea that just happened to work by
>>> fluke. IT and computing is rife with this kind of error.
>>
>> If what you are saying is true then *everything* is broken "by design"
>> if something isn't available at boot time (may be /usr, may be /var or
>> whatever).
>
> Let me make an analogy between programs and recipes.
>
> You see, a program is a lot like a recipe. It's a set of instructions
> for a computer to follow. And if you have a recipe where if you follow
> it, and anyone that eats the food says it tastes good, then you have a
> good recipe.
>
> Let me make an analogy between a restaurant franchise and a
> distribution. You see, a franchise is a set of instructions for a
> restaurateur to follow. A lot of those instructions are recipes. They
> tell the restaurateur how to cook foods. But not all of those
> instructions are. Some of them are instructions on the ideal
> conditions to cook. Or some of them are instructions on how to get
> materials, or how to talk to customers, or how to keep employees
> happy. Now if you follow those instructions, and have the right
> resources, you get to create a restaurant. In the same way, a
> distribution can be thought of as a set of instructions. If you follow
> those instructions, and have the right resources, you get to install a
> lot of programs on a computer.
>
> If everybody that follows the instructions on a recipe creates a food
> that a lot of people think tastes great, then you have a great recipe.
> And if everybody that follows the instuctions on a franchise creates a
> restaurant that a lot of customers buy from and think the food is
> great, then you have a great franchise.
>
> Now let's say you have a franchise with very specific instructions to
> buy ingredients from the nearest organic store. Now for many
> restaurants that follow these instructions, they end up with great
> food that makes an okay amount of money. But in some cities the
> organic store doesn't have very good lettuce. Or the carrots are too
> expensive. Or there isn't any organic store at all, so the restaurant
> owner has to go to the next city and waste a lot of time and money to
> get eggs. So those restaurants fail. But for many restaurants the
> instructions work.
>
> Now the restaurant owners get together and complain that their
> restaurant isn't working. Why? they ask. It's because the head
> franchise added pizza to the menu! The menu was working fine without
> the pizza, but when they added pizza it became to expensive or
> impractical to turn a profit. They might say that the franchise was
> broken by the pizza. But many restaurant owners do fine by pizza. In
> fact for many of them it's their hottest and most profitable product.
>
> You see, the problem isn't the inclusion of a specific recipe. The
> addition of pizza didn't break the restaurant. Nor did the addition of
> burgers, or coke, or fries or whatever. The problem was with
> instructions on how to manage the recipe ingredients. In short, while
> they were practical for a lot of restaurant owners, they weren't
> practical _in general_. The instructions could be better improved by
> saying something like "buy ingredients from stores that give you this
> much return," or "buy ingredients from our approved suppliers since
> they give the best return on your money". If those instructions were
> given instead of just vaguely saying to purchase from an organic
> store, they'd have better control over the quality and profitability
> of the restaurants.
>
> And this is something like what is wrong with /usr. The individual
> programs may be good. Many parts of the system taken together may be
> good. But the instructions on how to manage programs going to /usr or
> to / is too vague. There is no definitive quality control behind it.
> Even if you follow the instructions, as best as you can, you will end
> up making stupid decisions for the distribution.
>
> Likewise with the franchise restaurants. The individual foods may be
> good. Many of the instructions on managing people, foods, customers,
> may be good.  But the whole concept of "purchase from some a supplier
> with undefined levels of cost and quality" is NOT a good instruction.
> Maybe that works for a lot of restaurants

Re: [gentoo-user] Continuous beeping with kernel 3.10 and 3.11

[Peter Weilbacher]

On 2013-09-26 15:35, Bruce Hill wrote:
Check the manual for your BIOS/motherboard to see if it's some 
indication of

hardware failure.


Hmm, I'm sure that I have seen some beeps documented, but I cannot find 
that anywhere in the manual now. But I have a hard time believing that 
it's the hardware when going back to kernel 3.8.x fixes the beeping.


   Peter.

Re: [gentoo-user] Continuous beeping with kernel 3.10 and 3.11

[Peter Weilbacher]

On 2013-09-26 15:24, the wrote:


Might be related with some kind of io error.
What does dmesg show?


Nothing out of the ordinary. :-(

Can it have something to do with the graphics card instead? Because it 
stops right when the screen blanks?

   Peter.

Re: [gentoo-user] systemd installation location

[pk]

On 2013-10-01 08:16, Alan McKinnon wrote:

> There are many examples in /usr you could have used to illustrate your
> point, such as many fuse modules. And yet you chose an imaginary space
> invader game.
> 
> Let's rather stick within the bounds of what is feasible, OK?

What can I say, I like to exaggerate... :-)
But it seems you got my point. Although I would not rule out "Space
Invaders" as either imaginary (it came out in 1978) nor infeasible (at
boot).

> But it's not just you. You are not running LFS, you are running Gentoo.
> It has ebuilds and ebuilds put the generated files somewhere, and that
> destination is the same for every user of that ebuild.

Which is why I said what I said further down in the mail you replied to...

> Unix, by design and unlike a traditional mainframe OS, does not
> distinguish between different types of files and does limit where you
> can put files. This has two consequences - you can do virtually anything
> you like with it as everything is a file, and filesystem files and
> structure have been moved out to human space in the hands of the
> sysadmin/packager/maintainer/user or whatever. Some sanity must prevail.

Yes, sanity is what I'm after but it seems I'm in the minority...

> The Linux boot process can conceivably run any arbitrary code it needs
> to run to get userspace into a runnable state. This can easily be code
> that we haven't conceived of yet and becuase it is Unix, it could reside
> anywhere. Also because it's Unix and because sysadmins have learned over
> the years we constrain ourselves to putting the code in the bin, sbin
> and lib directories in / and in /usr.
> 
> Clearly, there is a massive distinction between code there and in say
> /opt or /var/lib, that is why you won't find boot-critical code there.
> But there is no such clear distinction between / and /usr. What *you*
> think is not boot critical may be criticial for someone else.

I couldn't agree more. However, since some devs (and I don't mean anyone
in particular) have started to expect /usr to always be available for
"boot-critical" software then what is to say that the next one *will*
require /opt and/or /var/lib at boot time? And where do we make a
distinction between a boot-critical thing and a non-boot-critical thing.
For all I know there may actually be someone out there seriously
considering adding "Space Invaders" as a boot thing for, say sysops that
want to reboot a really big server and want to play while booting... I'm
only kidding of course and hope noone takes this seriously!? ;-)

> And here's the kicker:
> 
> You don't get to decide for the other guy. But the packager gets to
> support him, and has to edit ebuilds to install all the necessary code
> not in /usr but in /. And they have to do this over and over and over,
> and while they are doing that they have to answer users like you who are
> complinaing about unneccessary rebuilds just to change the desitnation
> of a few files.
> 
> This is a no-win-ever situation for devs and they have decided they are
> not doing it anymore and have made a decision to not support separate
> /usr without initramfs. that is their right as you do not pay them a salary.
> 
> This is the correct decision for Gentoo to have made, as the problem is
> open ended and is never completed, plus there is no clear distinction
> between what is boot critical in the general case and what is not. if
> you can't see or understand that, then we have nothing more to discuss.
> 
> If you don't like what Gentoo has done then I recommend you take it like
> a man and fork. Assume the maintenanceburden yourself.

I've already come to that conclusion myself (as, again, I mentioned in
my mail further down).

Bye, so long and thanks for the f*sh!

Best regards

Peter K

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Alan McKinnon]

On 01/10/2013 20:48, Neil Bothwick wrote:
> On Tue, 01 Oct 2013 14:15:49 -0400, Tanstaafl wrote:
> 
>> I'm interested in what the DEFAULTS are, ie, for a new/from scratch 
>> installation.
> 
> Why? If ever there was a distro for people that didn't want to use
> defaults, Gentoo is it.
> 
>> Someone had to decide the defaults - so, what are they? Anyone?
> 
> I installed a VM a couple of weeks ago and I'm sure portage was still
> in /usr. It's easy enough to tell, unpack a stage 3 and see where the
> portage directory lives, but the handbook still refers to /usr/portage.
> 
> 

Please say it isn't so, otherwise I'm going to look like a right royal
chump.

Or maybe I just change it all on automatic these days and forget it do
it. But it was definitely discussed on -dev at length. i could be wrong
about the end result 



-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Greg Turner]

On Tue, Oct 1, 2013 at 2:24 PM, Alan McKinnon  wrote:
> On 01/10/2013 20:48, Neil Bothwick wrote:
>> On Tue, 01 Oct 2013 14:15:49 -0400, Tanstaafl wrote:
>>
>>> I'm interested in what the DEFAULTS are, ie, for a new/from scratch
>>> installation.
>>
>> Why? If ever there was a distro for people that didn't want to use
>> defaults, Gentoo is it.
>>
>>> Someone had to decide the defaults - so, what are they? Anyone?
>>
>> I installed a VM a couple of weeks ago and I'm sure portage was still
>> in /usr. It's easy enough to tell, unpack a stage 3 and see where the
>> portage directory lives, but the handbook still refers to /usr/portage.
>>
>>
>
> Please say it isn't so, otherwise I'm going to look like a right royal
> chump.
>
> Or maybe I just change it all on automatic these days and forget it do
> it. But it was definitely discussed on -dev at length. i could be wrong
> about the end result 
>
Looks like it's still usr/portage here...

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=blob;f=pym/portage/repository/config.py;h=0d6edf4e3e6dcffb0758caf859a597a8f0996bc0;hb=HEAD#l615

and here

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=blob;f=cnf/repos.conf;h=8c657daae3259e42e01ea05c689b74293b5224a7;hb=HEAD#l5

I don't see repos.conf in gx86 and I don't see PORTDIR in any
gx86-provided make.defaults'es as of yesterday.

So I guess it's still usr/portage.

I do think I vaguely recall that discussion about /var too though...
frankly, /var seems more sensible ... but maybe that's a can of worms
I should not be opening in this thread :)

-gmt

Re: PORTDIR default - changing PORTDIR variable - WAS Re: [gentoo-user] Re: separate / and /usr to require initramfs 2013-11-01

[Neil Bothwick]

On Tue, 1 Oct 2013 15:51:01 -0700, Greg Turner wrote:

> I do think I vaguely recall that discussion about /var too though...
> frankly, /var seems more sensible ... but maybe that's a can of worms
> I should not be opening in this thread :)

I think it was one of those discussion where every could agree that /usr
was wrong but no one cold agree on where was right.

/var makes sense to me, it's where I put the tree (but not packages or
distfiles).


-- 
Neil Bothwick

I'm not closed minded, you're just wrong.


signature.asc
Description: PGP signature

Re: [gentoo-user] Continuous beeping with kernel 3.10 and 3.11

[Dale]

Peter Weilbacher wrote:
> On one of my machines, I get continuous beeping from the internal
> loudspeaker when I boot a newer kernel (I'm using vanilla-sources). I
> first had that with 3.10.8 and also with 3.10.10, and it continues
> with 3.11.1.
>
> When I first had that problem I tried to remove all config options
> that had to do with the internal speaker, like
>   CONFIG_HAVE_PCSPKR_PLATFORM
>   CONFIG_PCSPKR_PLATFORM
>   CONFIG_INPUT_PCSPKR
> but that didn't help.
>
> In the meantime I left the machine on long enough to discover that it
> stops beeping whenever it is idle long enough and blanks the display.
>
> Does that ring a bell with someone?
>Peter.
>
>

I wish I could recall the fix because I ran into this once before.  I
changed something in the kernel config but I can't recall what it was. 
I'm thinking on it and if it hits me, maybe after hitting send, I'll be
glad to share.  This was maybe a year ago that I hit this tho. 

I hate getting older.  lol 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how 
you interpreted my words!

[gentoo-user] salt has Gentoo support

[Grant]

I've been researching the very well-regarded configuration management
framework 'salt' and I wanted to report that it has Gentoo support:

Portage Config Module:
http://docs.saltstack.com/ref/modules/all/salt.modules.portage_config.html

Portage Config State:
http://docs.saltstack.com/ref/states/all/salt.states.portage_config.html

ebuild module: 
http://docs.saltstack.com/ref/modules/all/salt.modules.ebuild.html

- Grant

[gentoo-user] s6 et al

[Bruce Hill]

Just stumbled across some very interesting software/ideas:

http://skarnet.org/poweredby.html
-- 
Happy Penguin Computers   >')
126 Fenco Drive   ( \
Tupelo, MS 38801   ^^
supp...@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting