Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On Sun, 2013-07-28 at 11:16 -0500, Canek Peláez Valdés wrote: > On Sun, Jul 28, 2013 at 8:23 AM, Michael Hampicke wrote: > > Am 28.07.2013 10:07, schrieb Stefan G. Weichinger: > >> Am 28.07.2013 10:04, schrieb Canek Peláez Valdés: > >> > >>> The only "special" thing I'm doing is to mask >sys-apps/systemd-204, > >>> since 205 introduced the new cgroups management code (with systemd as > >>> the only writer of the cgroups hierarchy), and it seems to cause some > >>> minor problems with logind. Other than that, it works withouth a > >>> glitch: gnome-base/gnome-3.8.0, sys-apps/systemd-204, no consolekit at > >>> all. > >> > >> Same here, yes. I run systemd-206 but I didn't notice an problem(s) yet. > >> Maybe there are some and I don't get it ;-) > >> > > > > I had one problem, but I am not sure, if it's related to systemd > 204, > > the removal of consolekit, or gnome at all. > > > > But when logging into my gnome session, /usr/libexec/gvfsd-fuse can not > > be started, because the permissions of /dev/fuse are rw-- root:root > > > > Other distros like ubuntu have a fuse group for that, which does not > > exist on gentoo. So I assume the default permissions for /dev/fuse on > > gentoo machines should be rw-rw-rw- root:root? > > My problem was that *sometimes* (not always) I was unable to unlock my > session after suspending my laptop or desktop. Reverting back to > systemd-204 solved it, so I'm assuming that's the problem, although I > didn't really investigated the issue. This turned out to be an upstream issue. See: https://bugs.freedesktop.org/show_bug.cgi?id=67267 and the corresponding Gentoo bug: https://bugs.gentoo.org/show_bug.cgi?id=477954 Upstream has already fixed it on git, so we'll either have to wait until systemd-207 or see if the systemd maintainers cherry pick the patch as 206-r1 on portage. --Mark
Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On Sunday 28 Jul 2013 17:16:55 Canek Peláez Valdés wrote: > On Sun, Jul 28, 2013 at 8:23 AM, Michael Hampicke wrote: > > Am 28.07.2013 10:07, schrieb Stefan G. Weichinger: > >> Am 28.07.2013 10:04, schrieb Canek Peláez Valdés: > >>> The only "special" thing I'm doing is to mask >sys-apps/systemd-204, > >>> since 205 introduced the new cgroups management code (with systemd as > >>> the only writer of the cgroups hierarchy), and it seems to cause some > >>> minor problems with logind. Other than that, it works withouth a > >>> glitch: gnome-base/gnome-3.8.0, sys-apps/systemd-204, no consolekit at > >>> all. > >> > >> Same here, yes. I run systemd-206 but I didn't notice an problem(s) yet. > >> Maybe there are some and I don't get it ;-) > > > > I had one problem, but I am not sure, if it's related to systemd > 204, > > the removal of consolekit, or gnome at all. > > > > But when logging into my gnome session, /usr/libexec/gvfsd-fuse can not > > be started, because the permissions of /dev/fuse are rw-- root:root > > > > Other distros like ubuntu have a fuse group for that, which does not > > exist on gentoo. So I assume the default permissions for /dev/fuse on > > gentoo machines should be rw-rw-rw- root:root? > > My problem was that *sometimes* (not always) I was unable to unlock my > session after suspending my laptop or desktop. Reverting back to > systemd-204 solved it, so I'm assuming that's the problem, although I > didn't really investigated the issue. On my vanilla stable Gentoo with openrc, /dev/fuse permissions are: $ ls -la /dev/fuse crw-rw-rw- 1 root root 10, 229 Jul 29 08:22 /dev/fuse -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Re: gentoo-systemd-only deprecation
On 28/07/13 11:22, Canek Peláez Valdés wrote: Basically, systemd is now a first class citizen in Gentoo (on par with OpenRC) This is great. Thanks to everyone involved! Does someone know whether a KDE system can work reliably with systemd, or there still issues?
[gentoo-user] a couple of systemd questions
I want to -- at least in initial testing -- have systemd not try to do things in parallell -- one at a time is very nice -- I even have openrc configured that way. Any way to do this? Also, I do want an interactive boot like the I -- is confirm-spawn the way to do this? Thanks in advance for any suggestions. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] Creating binary packages before updating them
Normally, when I'm about to update an important package, I back it up first using quickpkg. I'm often in a situation though where many important packages are being updated in a world update. Normally, I have to manually quickpkg every one of them. Is there a way to tell emerge to do this on its own? That is, create binary packages of every package that it is replacing?
Re: [gentoo-user] Creating binary packages before updating them
On 07/29/2013 01:18 PM, Nikos Chantziaras wrote: > Normally, when I'm about to update an important package, I back it up > first using quickpkg. I'm often in a situation though where many > important packages are being updated in a world update. Normally, I > have to manually quickpkg every one of them. > > Is there a way to tell emerge to do this on its own? That is, create > binary packages of every package that it is replacing? Isn't it --buildpkg?
Re: [gentoo-user] Creating binary packages before updating them
On 2013-07-29 7:18 AM, Nikos Chantziaras wrote: Normally, when I'm about to update an important package, I back it up first using quickpkg. I'm often in a situation though where many important packages are being updated in a world update. Normally, I have to manually quickpkg every one of them. Is there a way to tell emerge to do this on its own? That is, create binary packages of every package that it is replacing? Add FEATURES="buildpkg" to make.conf...
[gentoo-user] Re: Creating binary packages before updating them
On 29/07/13 14:24, Raffaele BELARDI wrote: On 07/29/2013 01:18 PM, Nikos Chantziaras wrote: Normally, when I'm about to update an important package, I back it up first using quickpkg. I'm often in a situation though where many important packages are being updated in a world update. Normally, I have to manually quickpkg every one of them. Is there a way to tell emerge to do this on its own? That is, create binary packages of every package that it is replacing? Isn't it --buildpkg? Unfortunately, no. --buildpkg only builds binary packages after they've been replaced already. I want binary packages of the packages that are being replaced instead.
Re: [gentoo-user] Creating binary packages before updating them
On Mon, 29 Jul 2013 14:18:03 +0300, Nikos Chantziaras wrote: > Normally, when I'm about to update an important package, I back it up > first using quickpkg. I'm often in a situation though where many > important packages are being updated in a world update. Normally, I > have to manually quickpkg every one of them. > > Is there a way to tell emerge to do this on its own? That is, create > binary packages of every package that it is replacing? You could parse the emerge output to build a list of packages and pass that to quickpkg. You could even do his as a script in /etc/portage/postsync.d to have it done automatically, but the simplest long term solution is to add buildpkg to FEATURES, then you don't have to try to anticipate which packages you need to backup. You can process all existing packages with quickpkg \*/\* I suspect you could also do this be defining a custom src_setup function in /etc/portage/bashrc - FEATURES="buildpkg" is a lot less hassle unless you are really tight on disk space. -- Neil Bothwick If ignorance is bliss, you must be orgasmic. signature.asc Description: PGP signature
[gentoo-user] Re: Creating binary packages before updating them
On 29/07/13 14:27, Tanstaafl wrote: On 2013-07-29 7:18 AM, Nikos Chantziaras wrote: Normally, when I'm about to update an important package, I back it up first using quickpkg. I'm often in a situation though where many important packages are being updated in a world update. Normally, I have to manually quickpkg every one of them. Is there a way to tell emerge to do this on its own? That is, create binary packages of every package that it is replacing? Add FEATURES="buildpkg" to make.conf... This creates packages for everything and only *after* they've been merged. I need to create tbzs for packages that are being replaced, and only when I want to.
[gentoo-user] Re: Creating binary packages before updating them
On 29/07/13 14:35, Neil Bothwick wrote: On Mon, 29 Jul 2013 14:18:03 +0300, Nikos Chantziaras wrote: Normally, when I'm about to update an important package, I back it up first using quickpkg. I'm often in a situation though where many important packages are being updated in a world update. Normally, I have to manually quickpkg every one of them. Is there a way to tell emerge to do this on its own? That is, create binary packages of every package that it is replacing? You could parse the emerge output to build a list of packages and pass that to quickpkg. You could even do his as a script in /etc/portage/postsync.d to have it done automatically, but the simplest long term solution is to add buildpkg to FEATURES, then you don't have to try to anticipate which packages you need to backup. You can process all existing packages with quickpkg \*/\* I suspect you could also do this be defining a custom src_setup function in /etc/portage/bashrc - FEATURES="buildpkg" is a lot less hassle unless you are really tight on disk space. Too big a hammer. I suppose the answer is just "no." I was hoping for some obscure emerge option that I wasn't seeing (happened before), like "--buildpkg-replaced" or something. I'll keep using quickpkg then. I only need this very rarely.
Re: [gentoo-user] Re: Creating binary packages before updating them
Nikos Chantziaras wrote: > On 29/07/13 14:35, Neil Bothwick wrote: >> On Mon, 29 Jul 2013 14:18:03 +0300, Nikos Chantziaras wrote: >> >>> Normally, when I'm about to update an important package, I back it up >>> first using quickpkg. I'm often in a situation though where many >>> important packages are being updated in a world update. Normally, I >>> have to manually quickpkg every one of them. >>> >>> Is there a way to tell emerge to do this on its own? That is, create >>> binary packages of every package that it is replacing? >> >> You could parse the emerge output to build a list of packages and pass >> that to quickpkg. You could even do his as a script >> in /etc/portage/postsync.d to have it done automatically, but the >> simplest long term solution is to add buildpkg to FEATURES, then you >> don't have to try to anticipate which packages you need to backup. >> >> You can process all existing packages with >> >> quickpkg \*/\* >> >> I suspect you could also do this be defining a custom src_setup function >> in /etc/portage/bashrc - FEATURES="buildpkg" is a lot less hassle unless >> you are really tight on disk space. > > Too big a hammer. I suppose the answer is just "no." I was hoping > for some obscure emerge option that I wasn't seeing (happened before), > like "--buildpkg-replaced" or something. I'll keep using quickpkg > then. I only need this very rarely. > > > If you set buildpkg in make.conf, you should already have a binary stored. Example. You do a install with buildpkg in make.conf. From that point on, when you do a update or new package install it stores a binary package for everything. Then later on if you do a update and it goes goofy, you can just use the -K option and it will restore the binary it stored without compiling the package again. I have that set here and it should do what you want in the long run. It just does it differently. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Re: [gentoo-user] Creating binary packages before updating them
On Monday 29 Jul 2013 07:27:23 Tanstaafl wrote: > On 2013-07-29 7:18 AM, Nikos Chantziaras wrote: > > Normally, when I'm about to update an important package, I back it up > > first using quickpkg. I'm often in a situation though where many > > important packages are being updated in a world update. Normally, I > > have to manually quickpkg every one of them. > > > > Is there a way to tell emerge to do this on its own? That is, create > > binary packages of every package that it is replacing? > > Add FEATURES="buildpkg" to make.conf... That way you'll gradually build up a /usr/portage/packages directory with a package for everything installed. Or if you don't want to wait months for that: # emerge -eB world when your box is not too busy. My KDE amd64 box (not ~amd64, for the most part) has 918 packages installed and the .../packages directory occupies 2GB. -- Regards, Peter
Re: [gentoo-user] Re: Creating binary packages before updating them
On Monday 29 Jul 2013 13:07:44 Dale wrote: > Nikos Chantziaras wrote: > > On 29/07/13 14:35, Neil Bothwick wrote: > >> On Mon, 29 Jul 2013 14:18:03 +0300, Nikos Chantziaras wrote: > >>> Normally, when I'm about to update an important package, I back it up > >>> first using quickpkg. I'm often in a situation though where many > >>> important packages are being updated in a world update. Normally, I > >>> have to manually quickpkg every one of them. > >>> > >>> Is there a way to tell emerge to do this on its own? That is, create > >>> binary packages of every package that it is replacing? > >> > >> You could parse the emerge output to build a list of packages and pass > >> that to quickpkg. You could even do his as a script > >> in /etc/portage/postsync.d to have it done automatically, but the > >> simplest long term solution is to add buildpkg to FEATURES, then you > >> don't have to try to anticipate which packages you need to backup. > >> > >> You can process all existing packages with > >> > >> quickpkg \*/\* > >> > >> I suspect you could also do this be defining a custom src_setup function > >> in /etc/portage/bashrc - FEATURES="buildpkg" is a lot less hassle unless > >> you are really tight on disk space. > > > > Too big a hammer. I suppose the answer is just "no." I was hoping > > for some obscure emerge option that I wasn't seeing (happened before), > > like "--buildpkg-replaced" or something. I'll keep using quickpkg > > then. I only need this very rarely. > > If you set buildpkg in make.conf, you should already have a binary > stored. Example. You do a install with buildpkg in make.conf. From > that point on, when you do a update or new package install it stores a > binary package for everything. Then later on if you do a update and it > goes goofy, you can just use the -K option and it will restore the > binary it stored without compiling the package again. > > I have that set here and it should do what you want in the long run. It > just does it differently. > > Dale It's been so long since I've used this feature I forgot how binary packages are purged. Do they stay in $PKGDIR for ever, until something like eclean deals with them, or can you specify (where?) to only keep the last n versions? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Creating binary packages before updating them
Mick wrote: > On Monday 29 Jul 2013 13:07:44 Dale wrote: >> >> >> If you set buildpkg in make.conf, you should already have a binary >> stored. Example. You do a install with buildpkg in make.conf. From >> that point on, when you do a update or new package install it stores a >> binary package for everything. Then later on if you do a update and it >> goes goofy, you can just use the -K option and it will restore the >> binary it stored without compiling the package again. >> >> I have that set here and it should do what you want in the long run. It >> just does it differently. >> >> Dale > > It's been so long since I've used this feature I forgot how binary packages > are purged. Do they stay in $PKGDIR for ever, until something like eclean > deals with them, or can you specify (where?) to only keep the last n versions? > As far as I know, eclean is the only way to clean them. It's a manual thing but I guess one could script it and do a cron job. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
[gentoo-user] Gallium and nVidia
Hi All, I would like to some clarification to support my feeling regarding gallium related use flags in mesa package. For some reason I have to rebuild a few packages on my machine and xorg-server and mesa are among them. I experienced that if the "xorg" USE flag of mesa is enabled then I got compiling error. After a little searching I could see that this use flag enables gallium3d. My question is that, as a nvidia user - I have an nvidia card and I use a nvidia driver from nvidia-drivers package - do I need this use flag? Do I need the gallium related use flags in mesa? Thanks in advance for any help! András -- -- Csanyi Andras (Sayusi Ando) -- http://sayusi.hu -- http://facebook.com/andras.csanyi -- ""Trust in God and keep your gunpowder dry!" - Cromwell
Re: [gentoo-user] Re: Creating binary packages before updating them
On 29/07/2013 16:56, Mick wrote: > On Monday 29 Jul 2013 13:07:44 Dale wrote: >> Nikos Chantziaras wrote: >>> On 29/07/13 14:35, Neil Bothwick wrote: On Mon, 29 Jul 2013 14:18:03 +0300, Nikos Chantziaras wrote: > Normally, when I'm about to update an important package, I back it up > first using quickpkg. I'm often in a situation though where many > important packages are being updated in a world update. Normally, I > have to manually quickpkg every one of them. > > Is there a way to tell emerge to do this on its own? That is, create > binary packages of every package that it is replacing? You could parse the emerge output to build a list of packages and pass that to quickpkg. You could even do his as a script in /etc/portage/postsync.d to have it done automatically, but the simplest long term solution is to add buildpkg to FEATURES, then you don't have to try to anticipate which packages you need to backup. You can process all existing packages with quickpkg \*/\* I suspect you could also do this be defining a custom src_setup function in /etc/portage/bashrc - FEATURES="buildpkg" is a lot less hassle unless you are really tight on disk space. >>> >>> Too big a hammer. I suppose the answer is just "no." I was hoping >>> for some obscure emerge option that I wasn't seeing (happened before), >>> like "--buildpkg-replaced" or something. I'll keep using quickpkg >>> then. I only need this very rarely. >> >> If you set buildpkg in make.conf, you should already have a binary >> stored. Example. You do a install with buildpkg in make.conf. From >> that point on, when you do a update or new package install it stores a >> binary package for everything. Then later on if you do a update and it >> goes goofy, you can just use the -K option and it will restore the >> binary it stored without compiling the package again. >> >> I have that set here and it should do what you want in the long run. It >> just does it differently. >> >> Dale > > It's been so long since I've used this feature I forgot how binary packages > are purged. Do they stay in $PKGDIR for ever, until something like eclean > deals with them, or can you specify (where?) to only keep the last n versions? > 2 easy methods: rm eclean packages eclean works the same as for distfiles, it can delete binpkgs that are no longer in the tree, that you don't have installed, or all previous versions of what you do have installed. But they never automagically get purged, the admin has to do it (manually or by cron or whatever0 -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Gallium and nVidia
On 29/07/2013 17:38, András Csányi wrote: > Hi All, > > I would like to some clarification to support my feeling regarding > gallium related use flags in mesa package. > > For some reason I have to rebuild a few packages on my machine and > xorg-server and mesa are among them. I experienced that if the "xorg" > USE flag of mesa is enabled then I got compiling error. After a little > searching I could see that this use flag enables gallium3d. > > My question is that, as a nvidia user - I have an nvidia card and I > use a nvidia driver from nvidia-drivers package - do I need this use > flag? Do I need the gallium related use flags in mesa? > > Thanks in advance for any help! > > András > Don't use gallium with nVidia's proprietary driver. Gallium is the architecture used by mesa for all open source 3D drivers (intel, radeon, nouveau, etc). nVidia bypasses all of that and does their own thing. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On Mon, Jul 29, 2013 at 3:28 AM, Mark Pariente wrote: > On Sun, 2013-07-28 at 11:16 -0500, Canek Peláez Valdés wrote: >> On Sun, Jul 28, 2013 at 8:23 AM, Michael Hampicke wrote: >> > Am 28.07.2013 10:07, schrieb Stefan G. Weichinger: >> >> Am 28.07.2013 10:04, schrieb Canek Peláez Valdés: >> >> >> >>> The only "special" thing I'm doing is to mask >sys-apps/systemd-204, >> >>> since 205 introduced the new cgroups management code (with systemd as >> >>> the only writer of the cgroups hierarchy), and it seems to cause some >> >>> minor problems with logind. Other than that, it works withouth a >> >>> glitch: gnome-base/gnome-3.8.0, sys-apps/systemd-204, no consolekit at >> >>> all. >> >> >> >> Same here, yes. I run systemd-206 but I didn't notice an problem(s) yet. >> >> Maybe there are some and I don't get it ;-) >> >> >> > >> > I had one problem, but I am not sure, if it's related to systemd > 204, >> > the removal of consolekit, or gnome at all. >> > >> > But when logging into my gnome session, /usr/libexec/gvfsd-fuse can not >> > be started, because the permissions of /dev/fuse are rw-- root:root >> > >> > Other distros like ubuntu have a fuse group for that, which does not >> > exist on gentoo. So I assume the default permissions for /dev/fuse on >> > gentoo machines should be rw-rw-rw- root:root? >> >> My problem was that *sometimes* (not always) I was unable to unlock my >> session after suspending my laptop or desktop. Reverting back to >> systemd-204 solved it, so I'm assuming that's the problem, although I >> didn't really investigated the issue. > > This turned out to be an upstream issue. See: > > https://bugs.freedesktop.org/show_bug.cgi?id=67267 Yeah, I suspected so; that was my theory in the mail I sent yesterday: http://article.gmane.org/gmane.linux.gentoo.user/267762 So it is indeed the new slices code. I'm staying on 204 until 207 comes out. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] a couple of systemd questions
On Mon, Jul 29, 2013 at 6:11 AM, wrote: > I want to -- at least in initial testing -- have systemd not try to do > things in parallell -- one at a time is very nice -- I even have openrc > configured that way. Any way to do this? No if you don't use --confirm-spawn AFAIK; the whole parallel start thingy is deeply integrated in systemd's design. And, why would you want to start things sequentially? And BTW, people who configure OpenRC to start things in parallel are going against the recommendations of its own maintaner: https://bugs.gentoo.org/show_bug.cgi?id=391945#c10 "rc_parallel has never officially been declared a stable feature (see the comments in rc.conf regarding this)." OpenRC has never been able to reliable start services in parallel; on the other hand, you can argue that systemd was designed specifically to start services in parallel. > Also, I do want an interactive boot like the I -- is confirm-spawn the > way to do this? Yes; you need to specify it on GRUB, LILO, or whatever boot loader you use, although I've never used it. > Thanks in advance for any suggestions. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] a couple of systemd questions
Canek Peláez Valdés wrote: > On Mon, Jul 29, 2013 at 6:11 AM, wrote: > > I want to -- at least in initial testing -- have systemd not try to do > > things in parallell -- one at a time is very nice -- I even have openrc > > configured that way. Any way to do this? > > No if you don't use --confirm-spawn AFAIK; the whole parallel start > thingy is deeply integrated in systemd's design. And, why would you > want to start things sequentially? Because its much easier to figure out things -- particularly if something has gone wrong -- and I don't boot that often, so I don't really care if it takes a bit longer -- its certainly a lot less than that other OS. And thanks for your response. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] Re: Gallium and nVidia
On 29/07/13 18:38, András Csányi wrote: Hi All, I would like to some clarification to support my feeling regarding gallium related use flags in mesa package. For some reason I have to rebuild a few packages on my machine and xorg-server and mesa are among them. I experienced that if the "xorg" USE flag of mesa is enabled then I got compiling error. After a little searching I could see that this use flag enables gallium3d. My question is that, as a nvidia user - I have an nvidia card and I use a nvidia driver from nvidia-drivers package - do I need this use flag? Do I need the gallium related use flags in mesa? I have "gallium" enabled and am also using nvidia-drivers. It doesn't do anything when running those drivers though. What it can do though is provide software OpenGL rendering, in case you need a fallback. In any event, it doesn't conflict with nvidia-drivers, since it's not used if you did: eselect opengl nvidia (Which I assume you did, since otherwise you wouldn't have 3D support with the nvidia drivers.)
Re: [gentoo-user] Re: Creating binary packages before updating them
On Mon, 29 Jul 2013 14:45:53 +0300, Nikos Chantziaras wrote: > > I suspect you could also do this by defining a custom src_setup > > function in /etc/portage/bashrc - FEATURES="buildpkg" is a lot less > > hassle unless you are really tight on disk space. > > Too big a hammer. I suppose the answer is just "no." I was hoping for > some obscure emerge option that I wasn't seeing (happened before), like > "--buildpkg-replaced" or something. I'll keep using quickpkg then. I > only need this very rarely. Checking the portage man page, I see you can set up per-package bashrc files. Once you get the first one scripted, you can just copy/symlink it for every package you want a per-emerge package for. The exact implementation is left as an exercise for the reader :) -- Neil Bothwick Always be sincere even if you don't mean it. signature.asc Description: PGP signature
Re: [gentoo-user] Creating binary packages before updating them
On Mon, 29 Jul 2013 15:21:59 +0100, Peter Humphrey wrote: > > Add FEATURES="buildpkg" to make.conf... > > That way you'll gradually build up a /usr/portage/packages directory > with a package for everything installed. Or if you don't want to wait > months for that: > > # emerge -eB world It isn't necessary to recompile everything just to build packages of them, quickpkg will do that. -- Neil Bothwick One difference between a man and a machine is that a machine is quiet when well oiled. signature.asc Description: PGP signature
Re: [gentoo-user] Creating binary packages before updating them
On 29/07/2013 21:46, Neil Bothwick wrote: > On Mon, 29 Jul 2013 15:21:59 +0100, Peter Humphrey wrote: > >>> Add FEATURES="buildpkg" to make.conf... >> >> That way you'll gradually build up a /usr/portage/packages directory >> with a package for everything installed. Or if you don't want to wait >> months for that: >> >> # emerge -eB world > > It isn't necessary to recompile everything just to build packages of > them, quickpkg will do that. > > Just make sure that quickpkg does what you want with config files... been there, done that, made the mistakes :-) -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] SQL Server Advice for Small Business
Hey guys, I'm planning to set up an SQL server for my dad's small canvas awning business, and I've never done this before. Most of my sysadmin-type skills are self-taught. I could use some advice. My dad needs infrastructure to allow ~ 15 of his employees to schedule appointments, track order status, and analyze random things about job status and customer base. I intend to set up a PostgreSQL server and write simple graphical front ends for the employees. I'll do most of the advanced customer base analysis for him. Eventually, I want to be generating heat maps of cashflow from cities and telling him where most of his materials are being used, etc. Operating system: I feel more comfortable on gentoo than anywhere else, so I'd like to put gentoo on the server. How often should I update packages? How often should I update the kernel? Any general management advice? I'm not really familiar with all the RAID options. Which should I be using? Should it be implemented in hardware or software? I'm also planning on using samba to give everyone a shared directory, but that should be easy. Hardware: What kind of hardware should I be looking at? One of Dell's PowerEdge models? How much of the hardware will need to be enterprise grade? I believe the hard drives will be the most important, right? I installed one of NASA's servers in Antarctica once, but someone else spec'd the hardware ($6k PowerEdge) and put ubuntu on it. Table structure: I'm diving into database design and normalization rules now. I'll need to store binary files (pictures of job site, scanned documents), and am currently planning on base64 encoding them (or something similar) and storing them in the database to keep it ACID compliant. Any other random advice or good resources would be much appreciated. Randy
Re: [gentoo-user] SQL Server Advice for Small Business
On Mon, Jul 29, 2013 at 4:22 PM, Randy Westlund wrote: > Hey guys, > > I'm planning to set up an SQL server for my dad's small canvas awning > business, and I've never done this before. Most of my sysadmin-type skills > are self-taught. I could use some advice. > Heh, based on the capitalized subject line I was going to ask why you were asking about Microsoft SQL Server on this list. ;-) > Table structure: > > I'm diving into database design and normalization rules now. I'll need to > store binary files (pictures of job site, scanned documents), and am > currently planning on base64 encoding them (or something similar) and storing > them in the database to keep it ACID compliant. If you really want to store binary data in the database, use a binary (BLOB) data type. Base64 will increase their size significantly.
Re: [gentoo-user] Creating binary packages before updating them
or you can make yourself a wrapper script that, depending on an option calls quickpkg before emerge or not. Even better, not calling emerge, but ebuild - with the different steps, and before merging into filesystem, call quickpkg. 2013/7/29 Alan McKinnon > On 29/07/2013 21:46, Neil Bothwick wrote: > > On Mon, 29 Jul 2013 15:21:59 +0100, Peter Humphrey wrote: > > > >>> Add FEATURES="buildpkg" to make.conf... > >> > >> That way you'll gradually build up a /usr/portage/packages directory > >> with a package for everything installed. Or if you don't want to wait > >> months for that: > >> > >> # emerge -eB world > > > > It isn't necessary to recompile everything just to build packages of > > them, quickpkg will do that. > > > > > > > Just make sure that quickpkg does what you want with config files... > > been there, done that, made the mistakes :-) > > -- > Alan McKinnon > alan.mckin...@gmail.com > > >
Re: [gentoo-user] Re: Creating binary packages before updating them
On Mon, Jul 29, 2013 at 7:29 AM, Nikos Chantziaras wrote: > On 29/07/13 14:24, Raffaele BELARDI wrote: >> >> On 07/29/2013 01:18 PM, Nikos Chantziaras wrote: >>> >>> Normally, when I'm about to update an important package, I back it up >>> first using quickpkg. I'm often in a situation though where many >>> important packages are being updated in a world update. Normally, I >>> have to manually quickpkg every one of them. >>> >>> Is there a way to tell emerge to do this on its own? That is, create >>> binary packages of every package that it is replacing? >> >> >> Isn't it --buildpkg? > > > Unfortunately, no. --buildpkg only builds binary packages after they've > been replaced already. I want binary packages of the packages that are > being replaced instead. > > It is probably easier/safer to just use FEATURES=buildpkg and then do emerge -e world. From that point forward, you will have a binpkg for every version of every package you ever install.
Re: [gentoo-user] a couple of systemd questions
The proper way to figure out what failed to start and why is to use systemctl # list of running services systemctl # status of particular service systemctl status name-of-service Now if your concern is the service loading order, then you're really talking about problems in your unit files, i.e., there's a dependency or sequencing instruction that wasn't included. Unlike sysvinit, you don't need a reboot to determine or solve load order problems. On Tue, Jul 30, 2013 at 2:29 AM, wrote: > Canek Peláez Valdés wrote: > >> On Mon, Jul 29, 2013 at 6:11 AM, wrote: >> > I want to -- at least in initial testing -- have systemd not try to do >> > things in parallell -- one at a time is very nice -- I even have openrc >> > configured that way. Any way to do this? >> >> No if you don't use --confirm-spawn AFAIK; the whole parallel start >> thingy is deeply integrated in systemd's design. And, why would you >> want to start things sequentially? > > Because its much easier to figure out things -- particularly if > something has gone wrong -- and I don't boot that often, so I don't > really care if it takes a bit longer -- its certainly a lot less than > that other OS. > > And thanks for your response. > > > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici > cov...@ccs.covici.com > -- This email is:[ ] actionable [ ] fyi[ ] social Response needed: [ ] yes [ ] up to you [ ] no Time-sensitive: [ ] immediate[ ] soon [ ] none
Re: [gentoo-user] [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
I am a gnome-3 user, who wants to continue with gnome-3. I understand now that to move to 3.8 requires I move from openRC to systemd and am trying to accomplish that now. I have so far only done the easy first steps. 0. I always back up my user files and /etc daily 1. I confirmed that my system still boots off my installation CD (just in case). 2. I added enough entries to /etc/portage/package.mask to prevent systemd being required (list at the end if others are interested). 3. Performed the kernel prerequisites from the wiki (most of which were already enabled). 4. My /run directory was already present and populated. Now I hit my first question The wiki says that "upstream suggests that the /etc/mtab file should be a simlink to /proc/self/mounts." It then points out problems with and without the symlink. My current system has both files but with slightly different contents, specifically the entries for my filesystems, root (includes /usr) and several lvm2 lvs, say "commit=0 0 2" in /etc/mtab but say "data=ordered 0 0" in /proc/self/mounts Do you advising leaving it alone or executing ln -sf /proc/self/mounts /etc/mtab After that comes the big one emerge systemd USE="... systemd ..." emerge --change-use /etc/init.d/udev restart Can the system be rebooted at this point (I realize init will still not use systemd) or must the entire conversion (including changing init) be completed before the system is bootable? I am hoping it is the former. thanks in advance for any help. allan My file /etc/portage/package.mask/gnome-3.8 >=gnome-base/gnome-3.8 >=gnome-base/gnome-core-apps-3.8 >=gnome-base/gnome-control-center-3.8 >=gnome-base/gnome-shell-3.8 >=x11-terms/gnome-terminal-3.8 >=gnome-extra/gnome-power-manager-3.8 >=media-gfx/eog-3.8 >=media-video/totem-3.8 >=app-crypt/seahorse-3.8 >=net-im/empathy-3.8 >=app-editors/gedit-3.8.3 >=gnome-extra/gnome-shell-extensions-3.8 >=gnome-base/gnome-extra-apps-3.8.0-r1:3.0 >=gnome-extra/evolution-data-server-3.8 >=dev-libs/folks-0.9 >=gnome-extra/gnome-calculator-3.8 >=gnome-extra/gnome-tweak-tool-3.8 >=gnome-base/gdm-3.8 >=gnome-extra/gnome-documents-3.8 >=gnome-extra/nautilus-tracker-tags-0.16 >=app-misc/tracker-0.16 >=dev-libs/totem-pl-parser-3.4.5 >=dev-libs/libpeas-1.8 >=gnome-extra/yelp-3.8 >=gnome-extra/gnome-contacts-3.8 >=app-cdr/brasero-3.8 >=net-misc/vinagre-3.8 >=app-dicts/gnome-dictionary-3.8 >=app-arch/file-roller-3.8 >=net-analyzer/gnome-nettool-3.8 >=gnome-extra/gnome-system-monitor-3.8 >=gnome-extra/gucharmap-3.8 >=media-gfx/gnome-font-viewer-3.8 >=net-misc/vino-3.8 >=media-gfx/gnome-screenshot-3.8 >=sys-apps/baobab-3.8 >=www-client/epiphany-3.8 >=dev-cpp/gtkmm-3.8 >=app-admin/gnome-system-log-3.8 >=media-video/cheese-3.8 >=net-libs/libzapojit-0.0.3 >=gnome-extra/sushi-3.8 >=mail-client/evolution-3.8 >=gnome-base/gnome-core-libs-3.8 >=gnome-base/gvfs-1.16 >=net-wireless/gnome-bluetooth-3.8 >=app-text/evince-3.8 >=net-libs/gnome-online-accounts-3.8 >=gnome-extra/gnome-color-manager-3.8 >=x11-wm/mutter-3.8 >=gnome-base/libgnome-keyring-3.8 >=net-libs/webkit-gtk-2.0.4:3/25 >=gnome-extra/zenity-3.8 >=gnome-base/gnome-session-3.8 >=x11-libs/gtksourceview-3.8 >=media-libs/clutter-gtk-1.4.4:1.0 >=x11-themes/gnome-themes-standard-3.8 >=media-video/cheese-3.8 >=gnome-extra/yelp-xsl-3.8 >=x11-themes/gnome-icon-theme-3.8 >=x11-themes/gnome-icon-theme-symbolic-3.8 >=gnome-base/gsettings-desktop-schemas-3.8 >=gnome-base/gsettings-desktop-3.8 >=gnome-base/gnome-desktop-3.8 >=x11-themes/gnome-backgrounds-3.8 >=gnome-extra/gnome-user-docs-3.8 >=gnome-base/gnome-common-3.7 >=x11-libs/gtk+-3.8 >=gnome-base/gnome-keyring-3.8 >=gnome-base/nautilus-3.8 >=app-crypt/gcr-3.8 >=net-libs/libsoup-2.42 >=gnome-base/gnome-settings-daemon-3.8 >=net-libs/webkit-gtk-2.0.3 >=media-libs/clutter-1.14 >=dev-libs/libgweather-3.8 >=media-libs/cogl-1.14
[gentoo-user] [Preliminary report] Gnome-3.8 update works with openrc :)
As I posted in another thread, after successfully updating to gnome-3.8 on a virtual gentoo machine that's been running systemd for months, I tackled my openrc gentoo virtual machine just to see if I could do it. I just did it :) Gnome-3.8 is running on the openrc machine without running systemd at all. However, gnome-3.8 *does* require systemd to be installed because it has officially replaced the udev project. (All of the udev files are now installed by the systemd package.) Also, very important, you must set the systemd useflag globally or the conflicts between packages and useflags will drive you insane (like me). Another problem I've noted is that I've had a few unexplained freezes when the VBox guests are running kernel 3.10.3, and backing down to kernel 3.9.11-r1 seems to avoid those, but that's just my impression, nothing more. (I'm running 3.9.11-gentoo-r1 on both host machines because the ati-drivers and nvidia-drivers won't compile against 3.10.x the last time I checked.) Please note: I have done only superficial testing on the openrc machine, and I would not recommend that you try this trick on any machine you really need to be solid! This is just me playing around with stuff that is not supported by the gentoo devs. Be warned! I'm going to test cinnamon next, and I'll post results in a day or two.
[gentoo-user] Re: Creating binary packages before updating them
On 30/07/13 01:18, Mike Gilbert wrote: On Mon, Jul 29, 2013 at 7:29 AM, Nikos Chantziaras wrote: On 29/07/13 14:24, Raffaele BELARDI wrote: On 07/29/2013 01:18 PM, Nikos Chantziaras wrote: Normally, when I'm about to update an important package, I back it up first using quickpkg. I'm often in a situation though where many important packages are being updated in a world update. Normally, I have to manually quickpkg every one of them. Is there a way to tell emerge to do this on its own? That is, create binary packages of every package that it is replacing? Isn't it --buildpkg? Unfortunately, no. --buildpkg only builds binary packages after they've been replaced already. I want binary packages of the packages that are being replaced instead. It is probably easier/safer to just use FEATURES=buildpkg and then do emerge -e world. From that point forward, you will have a binpkg for every version of every package you ever install. Thanks everyone, though this isn't what I need or want. I'll stick with quickpkg.
Re: [gentoo-user] [Preliminary report] Gnome-3.8 update works with openrc :)
walt, are you using pam_systemd? I have a hunch that systemd-logind should still work.
Re: [gentoo-user] [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On Mon, Jul 29 2013, gottl...@nyu.edu wrote: > I am a gnome-3 user, who wants to continue with gnome-3. I understand > now that to move to 3.8 requires I move from openRC to systemd and am > trying to accomplish that now. I have so far only done the easy first > steps. OK. Walt proved this wrong by managing, with some effort and doubtless considerable skill, to get 3.8 on an openrc machine but he does note that moving to systemd is the procedure supported by the gentoo devs. I am still trying to move to systemd and would appreciate help as mentioned in my previous msg. thanks again, allan
[gentoo-user] Any .config for vbox gentoo guest
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.
[gentoo-user] conf.d/net and systemd
Hi there. I would like to know how I can use my existing conf.d/net if I were to use systemd, or is there some better way to do this? I have two static networks an internal and external one and use the postup for things which must go online once the external network is up. I had to use modules="!iproute2" to get the route to add properly, but it is working now using openrc. Thanks in advance for any suggestions. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On Mon, Jul 29, 2013 at 7:56 PM, wrote: > I am a gnome-3 user, who wants to continue with gnome-3. I understand > now that to move to 3.8 requires I move from openRC to systemd and am > trying to accomplish that now. I have so far only done the easy first > steps. > > 0. I always back up my user files and /etc daily > > 1. I confirmed that my system still boots off my installation CD > (just in case). > > 2. I added enough entries to /etc/portage/package.mask to prevent > systemd being required (list at the end if others are interested). > > 3. Performed the kernel prerequisites from the wiki (most of which > were already enabled). > > 4. My /run directory was already present and populated. Sounds reasonable. > Now I hit my first question > > The wiki says that "upstream suggests that the /etc/mtab file should > be a simlink to /proc/self/mounts." It then points out problems with > and without the symlink. > > My current system has both files but with slightly different contents, > specifically the entries for my filesystems, root (includes /usr) and several > lvm2 lvs, say "commit=0 0 2" in /etc/mtab but say "data=ordered 0 0" > in /proc/self/mounts > > Do you advising leaving it alone or executing >ln -sf /proc/self/mounts /etc/mtab AFAIU, systemd will print the following warning if /etc/mtab is not a symlink to /proc/self/mounts: "/etc/mtab is not a symlink or not pointing to /proc/self/mounts. This is not supported anymore. Please make sure to replace this file by a symlink to avoid incorrect or misleading mount(8) output." Also, upstream will reject flatly any support for systems where this happens. Lastly, if I understand correctly, /proc/self/mounts is how the mounts are really mounted, so if they differ, /proc/self/mounts contains the correct information. If you switch to systemd, you will need to make /etc/mtab a symlink to /proc/self/mounts. > After that comes the big one > > emerge systemd > USE="... systemd ..." > emerge --change-use > /etc/init.d/udev restart > > Can the system be rebooted at this point (I realize init will still not > use systemd) or must the entire conversion (including changing init) be > completed before the system is bootable? I am hoping it is the former. If you install systemd, sys-fs/udev will be uninstalled first (they block each other). At this point, /etc/init.d/udev doesn't exists anymore in your system. If you reboot, I don't believe there is any chance your system will boot up correctly. /etc/init.d/udev is installed by sys-fs/udev; sys-apps/systemd doesn't provide anything similar. I recommend installing everything necessary (and uninstalling everything that is not) before trying the reboot. Also, instead of emerge --changed-use (not --change-use, BTW), try: emerge --update --deep --newuse --verbose Or its shorter equivalent, emerge -uDNv world. --deep will force a check on the entire dependency tree, --newuse will trigger reinstallation for flags you didn't set. I think, in this case at least, it's better to cover as many possible packages affected by the switch. Although I update my systems always with --deep and --newuse. Also, I would do the whole shebang in a one step, removing all the masked packages you did. You can try to boot to multi-user.target instead of graphical.target, if you want to test that systemd works correctly independently of GNOME. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] [Preliminary report] Gnome-3.8 update works with openrc :)
Am 30.07.2013 03:04, schrieb walt: > As I posted in another thread, after successfully updating to gnome-3.8 > on a virtual gentoo machine that's been running systemd for months, I > tackled my openrc gentoo virtual machine just to see if I could do it. > > I just did it :) Gnome-3.8 is running on the openrc machine without > running systemd at all. Try suspending/hibernating the machine via Gnome menu. Does that work for you? Never got that to work when I used openrc. signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] [Preliminary report] Gnome-3.8 update works with openrc :)
On Tue, Jul 30, 2013 at 12:26 AM, Michael Hampicke wrote: > Am 30.07.2013 03:04, schrieb walt: >> As I posted in another thread, after successfully updating to gnome-3.8 >> on a virtual gentoo machine that's been running systemd for months, I >> tackled my openrc gentoo virtual machine just to see if I could do it. >> >> I just did it :) Gnome-3.8 is running on the openrc machine without >> running systemd at all. > > Try suspending/hibernating the machine via Gnome menu. Does that work > for you? Never got that to work when I used openrc. Also: • Can you mount (as a normal user) USB drives, CDs, sftp remote directories? • Can you add a new wireless or wired networks with NetworkManager? • Can you shut down the machine from the GNOME menu? • Bluetooth? Printers? All of this stuff involves logind, and ConsoleKit before it. I'm pretty sure most of them, if not all, will fail with OpenRC. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] SQL Server Advice for Small Business
On Mon, July 29, 2013 22:22, Randy Westlund wrote: > Hey guys, > > I'm planning to set up an SQL server for my dad's small canvas awning > business, and I've never done this before. Most of my sysadmin-type > skills are self-taught. I could use some advice. > > My dad needs infrastructure to allow ~ 15 of his employees to schedule > appointments, track order status, and analyze random things about job > status and customer base. I intend to set up a PostgreSQL server and > write simple graphical front ends for the employees. I'll do most of the > advanced customer base analysis for him. Eventually, I want to be > generating heat maps of cashflow from cities and telling him where most of > his materials are being used, etc. For that, you could, in time, look into PostGIS (or similar). > Operating system: > > I feel more comfortable on gentoo than anywhere else, so I'd like to put > gentoo on the server. How often should I update packages? How often > should I update the kernel? Any general management advice? Will the server be internet-facing? I would make sure you have a firewall and only open the port needed for the front-end. Don't update the kernel too often, keep an eye out for security fixes and apply where necessary. Keep a seperate machine/VM where you build binary packages. This will significantly reduce the time needed to upgrade the software. > I'm not really familiar with all the RAID options. Which should I be > using? Should it be implemented in hardware or software? That depends on your budget and requirements. For databases, RAID-10 is generally considered the best performance. Also avoid filling the disks and try to use the first half of the disk, rather then the whole. (First half is faster then 2nd half) RAID-10 in software (eg. Linux Software Raid in the kernel) outperforms the cheaper RAID-cards easily. If you have the budget, you could invest in a dedicated hardware raid card (but make sure it is 100% hardware and doesn't use the CPU for the calculations) > I'm also planning on using samba to give everyone a shared directory, but > that should be easy. Depends on how much you want in there. If just a simple share, then it will be simple. If you also want the MS Windows machines to authenticate against it, things get a little more complicated. > Hardware: > > What kind of hardware should I be looking at? One of Dell's PowerEdge > models? How much of the hardware will need to be enterprise grade? I > believe the hard drives will be the most important, right? I installed > one of NASA's servers in Antarctica once, but someone else spec'd the > hardware ($6k PowerEdge) and put ubuntu on it. How mission-critical will this be? For my server (which has become quite critical over the years), I currently use a self-build server with good reliable components. TYAN-mainboard (with built-in iKVM), WD-RED drives, Areca hardware raid-card. When I started running my own server, it was on a cheap no-brand mainboard with simple desktop disks connected via IDE. (yes, ancient :) ) > Table structure: > > I'm diving into database design and normalization rules now. You want to try to keep the database design optimized for the usage pattern of the client-tools. Which usually means not too much normalization. That helps with reporting, not when you need to do mostly inserts. > I'll need to > store binary files (pictures of job site, scanned documents), and am > currently planning on base64 encoding them (or something similar) and > storing them in the database to keep it ACID compliant. How big will those documents be? Either, as already mentioned, store them as blobs, or on a (samba) share and put metadata (filepath,name,description,...) in the database. > Any other random advice or good resources would be much appreciated. Advice: 1) Backup 2) Backup 3) Did I mention backup? ;) A tip, when you decide to put the documents on a share, to ensure the backups are in sync, do the following: 1) stop access to the database 2) snapshot the fileshare (LVM helps here) 3) backup the database 4) allow access to the database again 5) backup the snapshot 6) remove the snapshot Total downtime with this should be less then 1 minute. A full backup using the Postgresql tools is really quick. Step 5 can then take as long as it takes. The environment will still be running. Also think about how to store certain types of data (like addresses) and how to enforce data quality rules. Eg. everyone using the same way of writing the names of towns/streets/people. You'd be surprised how often I find various forms of: - Mr, Mister, Sir, Msr, Mstr,... (All supposedly meaning the same ;) ) Or, like in the Netherlands, there are cities with multiple names that are officially accepted: - The Hague (as it's known internationally) - Den Haag - s' Gravenhage (yes, those are the same city) My advice, have either a translation table where various forms are entered to allow easy identification. Or pre-fill a tab
[gentoo-user] which VM do you recommend?
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 situation is more than strange. Sometime using a backed up Virtualbox image the network seems to work but only for a very short time (some minutes?) Windows error analyzing tools don't see any network problems but it does not work. Trying ping -n 100 only a few packets come back but with a large delay (40-50 times larger delay compared to ping on the GenToo host) I've tried the most recent Virtualbox 4.2.16 as well the oldest one (in the tree) which is 4.1.26 So probably it looks best to me to change to a different (free) VM. What do you recommend? Many thanks for a hint, Helmut
Re: [gentoo-user] conf.d/net and systemd
On Tuesday 30 July 2013 00:53:08 cov...@ccs.covici.com wrote: > Hi there. I would like to know how I can use my existing conf.d/net if > I were to use systemd, or is there some better way to do this? I have > two static networks an internal and external one and use the postup for > things which must go online once the external network is up. I had to > use modules="!iproute2" to get the route to add properly, but it is > working now using openrc. > > Thanks in advance for any suggestions. There's no way currently to use config from /etc/conf.d/net if you don't make your own systemd unit. I suggest installing net-misc/netctl. Postup will be possible.
Re: [gentoo-user] conf.d/net and systemd
On Mon, Jul 29, 2013 at 11:53 PM, wrote: > Hi there. I would like to know how I can use my existing conf.d/net if > I were to use systemd, or is there some better way to do this? I have > two static networks an internal and external one and use the postup for > things which must go online once the external network is up. I had to > use modules="!iproute2" to get the route to add properly, but it is > working now using openrc. If both networks are static I would use two service files for each, and the things that must go online can go in another service file (which calls a script for all of them), or with several (a service file for each thing), and which depends on the external network. You then not need to install anything else. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
