Re: [gentoo-user] btrfs conversion: first impressions

2014-05-15 Thread Stefan G. Weichinger
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 14.05.2014 11:30, schrieb Stefan G. Weichinger:

 But the encryption topic for me is interesting because I right now 
 have it mixed on my thinkpad:
 
 sda1 - /boot/efi sda2 - btrfs - root etc sda3 -
 cryptsetup-partition - /home on it with ext4-fs

I just now converted the ext4 to btrfs and edited pam_mount.conf.xml
... works!

I just have to clean up the top level volume of btrfs as one should
use a subvolume for the actual data.

Now to changing the luks-passphrase and teaching gnome-something to
unlock it. Weak old passphrase/password ...



-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTdFwNAAoJEClcuD1V0PzmTJEQALC4p9+CxPJYhQrD7GIi4oqH
tulczyMgi21GmmGKmsonhR//ZlwIWn2XAljwvEpmHREaDq/o+7dqh1aLABVjFeQN
a+adtBZBNEBW8gWuRksXpf4AjQSB1OKRvcZ6nabnrgKTUMgiB7OcaxE7JBowPwwk
BlxyVGmcmXKuFEXyMsQCdfcEU5/jPVFNB14hcMS4DmxLjVlLMhgEyGVY8qKjdPOs
vFlxX3t01KQWam5kHtQ2BoUmBGVRTO4DqPtrLHuRVBOT6MToBhbTJZJupzx54kDE
kLjie57K3gmoptAdLEVJjcv44hzK+VpPa+d0Fusl6VXNkB1CTaJl2CF53f5rZWXj
aWc+psEgEsXibyXQSoj6vctQft9OMgn0bpTwKd7nA11jS+ANOcusOJbL8rDnSXNu
zMk4KSL+CPLo+XkwtBIjI8k+fJMNh1rufvdcTvqBADiJSi67wMIsdlH8hal4O2Cb
/X8BqApZQfTSWyDEq8KVUecMEIK5fINENqU+PQHHvAs36OemFMQ2Bf+Z6gjN9w3T
cA14SOQquXVBkK2sd4BLmVReY0Gd8ulGw1EmVxSJ7l0VMk/amSsvq689UsFfxLC0
aCkn57ih4aEPRbOzwlsQg1tNhjD7D3rTVfJWUtblZSDddgKTyzqnzeHtwHMwIbJ7
xaRJGuOn8Lf7DXHbbMti
=hUHb
-END PGP SIGNATURE-



Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread Canek Peláez Valdés
On Wed, May 14, 2014 at 5:26 PM,  cov...@ccs.covici.com wrote:
[snip]

 Well, the workaround sort of worked -- it went through the initrd -- I
 had debug in the kernel command line, but it did not stop for nothing!
 When it went to the real root, however it did not activate any of the
 lvm volumes I had except for what I specified in the kernel command
 line, causing things not to work well.  Also, I noticed that if insisted
 on using the predictable network names, even though I have
 /etc/udev/rules.d/70-persistent-net.rules and
 /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
 me back my eth* names.  So all in all, it was a mess and took me to an
 emergency shell and that was the end of that.  I did eventually activate
 some volumes by lvchange -aay, but obviously that would not work well.

OK, I was a little mystified about why dracut-036 worked on my system
and 037 didn't. Before I tried any workaround, I wanted to know what
changed from the previous version to the current one.

So I generated an initramfs with dracut-036-r4 and another one with
dracut-037-r1, and I tried to see what changed from one to the other.
The answer is surprisingly easy: in /etc/cmdline.d/, the following
files where in the 036-r4 version, but not in the 037-r4:

90crypt.conf
90lvm.conf
90mdraid.conf
base.conf

Te contents of those files are (90crypt.conf is empty):

90lvm.conf
   rd.lvm.lv=vg/vol1
   rd.lvm.lv=vg/vol4
   rd.lvm.lv=vg/vol3

90mdraid.conf
   rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

base.conf
   ro

So I just changed my /etc/default/grub file:

GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

I regenerated my GRUB2 config, and now again my LVM test system works
perfectly with the latest dracut version.

The thing is, I *ALWAYS* use the -H (host only) option, so it was my
understanding that the command line should be automatically generated,
and it was on 036, but now it doesn't in 037. I think that's a bug.

John, with respect to your case: did you used dracut --print-cmdline
to get the command line? Also, have you tried to use -H to generate
your initramfs?

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México



Re: [gentoo-user] boot problems

2014-05-15 Thread Canek Peláez Valdés
On Mon, May 5, 2014 at 1:40 AM, Canek Peláez Valdés can...@gmail.com wrote:

[ It's been more than a week since I last participated in the thread,
so I'm just replying to my last participation. ]

Stefan, have you tried to run dracut --print-cmdline and add that to
your kernel command line?

By the last thread related to systemd+dracut, that solved my problems
when using dracut 037. Could you try to see if it solves your issues?

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México



Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread Canek Peláez Valdés
On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés can...@gmail.com wrote:
 On Wed, May 14, 2014 at 5:26 PM,  cov...@ccs.covici.com wrote:
 [snip]

 Well, the workaround sort of worked -- it went through the initrd -- I
 had debug in the kernel command line, but it did not stop for nothing!
 When it went to the real root, however it did not activate any of the
 lvm volumes I had except for what I specified in the kernel command
 line, causing things not to work well.  Also, I noticed that if insisted
 on using the predictable network names, even though I have
 /etc/udev/rules.d/70-persistent-net.rules and
 /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
 me back my eth* names.  So all in all, it was a mess and took me to an
 emergency shell and that was the end of that.  I did eventually activate
 some volumes by lvchange -aay, but obviously that would not work well.

 OK, I was a little mystified about why dracut-036 worked on my system
 and 037 didn't. Before I tried any workaround, I wanted to know what
 changed from the previous version to the current one.

 So I generated an initramfs with dracut-036-r4 and another one with
 dracut-037-r1, and I tried to see what changed from one to the other.
 The answer is surprisingly easy: in /etc/cmdline.d/, the following
 files where in the 036-r4 version, but not in the 037-r4:

 90crypt.conf
 90lvm.conf
 90mdraid.conf
 base.conf

 Te contents of those files are (90crypt.conf is empty):

 90lvm.conf
rd.lvm.lv=vg/vol1
rd.lvm.lv=vg/vol4
rd.lvm.lv=vg/vol3

 90mdraid.conf
rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

 base.conf
ro

 So I just changed my /etc/default/grub file:

 GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
 rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
 rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

 I regenerated my GRUB2 config, and now again my LVM test system works
 perfectly with the latest dracut version.

I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
BTW Jc, you used host_cmdline, I think the former is the correct one.

So, to resume: there is no bug, is just that before hostonly_cmdline
was yes by default, and now is no by default. This change was
documented, but I failed to notice it (and I think the ebuild in
Gentoo should print an einfo message).

Anyway, I think that explains all my problems; John, I don't know if
it will solve yours. Again: did you used dracut --print-cmdline to
get the command line? Also, have you tried to use -H to generate your
initramfs? And finally, have you tried with --hostonly-cmdline?

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México



Re: [gentoo-user] boot problems

2014-05-15 Thread Canek Peláez Valdés
On Thu, May 15, 2014 at 1:21 AM, Canek Peláez Valdés can...@gmail.com wrote:
 On Mon, May 5, 2014 at 1:40 AM, Canek Peláez Valdés can...@gmail.com wrote:

 [ It's been more than a week since I last participated in the thread,
 so I'm just replying to my last participation. ]

 Stefan, have you tried to run dracut --print-cmdline and add that to
 your kernel command line?

 By the last thread related to systemd+dracut, that solved my problems
 when using dracut 037. Could you try to see if it solves your issues?

Also, I just noticed the --hostonly-cmdline option. Have you tried that?

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México



Re: [gentoo-user] boot problems

2014-05-15 Thread Stefan G. Weichinger
Am 15.05.2014 08:49, schrieb Canek Peláez Valdés:
 On Thu, May 15, 2014 at 1:21 AM, Canek Peláez Valdés can...@gmail.com wrote:
 On Mon, May 5, 2014 at 1:40 AM, Canek Peláez Valdés can...@gmail.com wrote:

 [ It's been more than a week since I last participated in the thread,
 so I'm just replying to my last participation. ]

 Stefan, have you tried to run dracut --print-cmdline and add that to
 your kernel command line?

 By the last thread related to systemd+dracut, that solved my problems
 when using dracut 037. Could you try to see if it solves your issues?
 
 Also, I just noticed the --hostonly-cmdline option. Have you tried that?

Nope.

I am away from LVM  RAID now as mentioned in the other thread ... btrfs
everywhere ;-)

Stefan




Re: [gentoo-user] Having Trouble with Wireless Interface

2014-05-15 Thread Stroller

On Wed, 14 May 2014, at 12:36 pm, Alexander Kapshuk 
alexander.kaps...@gmail.com wrote:
 … 
 If you like to check if RTL8192CE is enabled in  your kernel's .config
 file. If it isn't, you probably want to compile it as a module, and then
 add rtl8192ce to /etc/conf.d/modules as well.
 Am pretty sure there's no need to add this one to /etc/conf.d/modules - IME 
 it'll just be found and loaded automagically by the kernel.
 
 Thanks for pointing that out. I wasn't aware of that. As I mentioned in
 my previous post, I do not use genkernel myself.

Neither do I - for this reason I found it a little frustrating trying to help 
in a recent thread, myself.

However, I'm pretty sure that loadable kernel modules behave the same whether 
your kernel is built by hand or by genkernel - if you have modules listed in 
/etc/conf.d/modules then I have to wonder if you really need them there.

I haven't used that file for years, and I prefer to compile everything as a 
module, too.

Stroller.




Re: [gentoo-user] boot problems

2014-05-15 Thread Stefan G. Weichinger
Am 15.05.2014 09:08, schrieb Stefan G. Weichinger:
 Am 15.05.2014 08:49, schrieb Canek Peláez Valdés:
 On Thu, May 15, 2014 at 1:21 AM, Canek Peláez Valdés can...@gmail.com 
 wrote:
 On Mon, May 5, 2014 at 1:40 AM, Canek Peláez Valdés can...@gmail.com 
 wrote:

 [ It's been more than a week since I last participated in the thread,
 so I'm just replying to my last participation. ]

 Stefan, have you tried to run dracut --print-cmdline and add that to
 your kernel command line?

 By the last thread related to systemd+dracut, that solved my problems
 when using dracut 037. Could you try to see if it solves your issues?

 Also, I just noticed the --hostonly-cmdline option. Have you tried that?
 
 Nope.
 
 I am away from LVM  RAID now as mentioned in the other thread ... btrfs
 everywhere ;-)

Aside from that: I always use your tool kerninst so I have -H set as
well.

Stefan




Re: [gentoo-user] Having Trouble with Wireless Interface

2014-05-15 Thread Alan McKinnon
On 15/05/2014 10:39, Stroller wrote:
 
 On Wed, 14 May 2014, at 12:36 pm, Alexander Kapshuk 
 alexander.kaps...@gmail.com wrote:
 … 
 If you like to check if RTL8192CE is enabled in  your kernel's .config
 file. If it isn't, you probably want to compile it as a module, and then
 add rtl8192ce to /etc/conf.d/modules as well.
 Am pretty sure there's no need to add this one to /etc/conf.d/modules - IME 
 it'll just be found and loaded automagically by the kernel.

 Thanks for pointing that out. I wasn't aware of that. As I mentioned in
 my previous post, I do not use genkernel myself.
 
 Neither do I - for this reason I found it a little frustrating trying to help 
 in a recent thread, myself.
 
 However, I'm pretty sure that loadable kernel modules behave the same whether 
 your kernel is built by hand or by genkernel - if you have modules listed 
 in /etc/conf.d/modules then I have to wonder if you really need them there.
 
 I haven't used that file for years, and I prefer to compile everything as a 
 module, too.


Some modules don't autoload, usually because there's no hardware they
drive and so nothing to probe.

netfilter modules come to mind, as well as VirtualBox. One of the vbox
modules doesn't autoload by just stating VirtualBox, so the easiest is
to put it in /etc/conf.d/modules so it's always available. It's an edge
case, so the vast majority of modules load properly without intervention
form us.




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




Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread covici
Canek Peláez Valdés can...@gmail.com wrote:

 On Wed, May 14, 2014 at 5:26 PM,  cov...@ccs.covici.com wrote:
 [snip]
 
  Well, the workaround sort of worked -- it went through the initrd -- I
  had debug in the kernel command line, but it did not stop for nothing!
  When it went to the real root, however it did not activate any of the
  lvm volumes I had except for what I specified in the kernel command
  line, causing things not to work well.  Also, I noticed that if insisted
  on using the predictable network names, even though I have
  /etc/udev/rules.d/70-persistent-net.rules and
  /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
  me back my eth* names.  So all in all, it was a mess and took me to an
  emergency shell and that was the end of that.  I did eventually activate
  some volumes by lvchange -aay, but obviously that would not work well.
 
 OK, I was a little mystified about why dracut-036 worked on my system
 and 037 didn't. Before I tried any workaround, I wanted to know what
 changed from the previous version to the current one.
 
 So I generated an initramfs with dracut-036-r4 and another one with
 dracut-037-r1, and I tried to see what changed from one to the other.
 The answer is surprisingly easy: in /etc/cmdline.d/, the following
 files where in the 036-r4 version, but not in the 037-r4:
 
 90crypt.conf
 90lvm.conf
 90mdraid.conf
 base.conf
 
 Te contents of those files are (90crypt.conf is empty):
 
 90lvm.conf
rd.lvm.lv=vg/vol1
rd.lvm.lv=vg/vol4
rd.lvm.lv=vg/vol3
 
 90mdraid.conf
rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
 base.conf
ro
 
 So I just changed my /etc/default/grub file:
 
 GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
 rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
 rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
 I regenerated my GRUB2 config, and now again my LVM test system works
 perfectly with the latest dracut version.
 
 The thing is, I *ALWAYS* use the -H (host only) option, so it was my
 understanding that the command line should be automatically generated,
 and it was on 036, but now it doesn't in 037. I think that's a bug.
 
 John, with respect to your case: did you used dracut --print-cmdline
 to get the command line? Also, have you tried to use -H to generate
 your initramfs?

I did not try the -H, I may test with that later.


I did look at the --print-cmdline and copied the volumes they mentioned,
but I have other lvm volumes in my fstab and none of them were activated,
only the ones I specified in the command line!  This is where I have run
into problems.  I have quite a few lvms, I want them all activated!

Also, since I wrote the last message, I have been looking at the
journalctl output and discovered a couple of things which I would like
some help on, but getting the lvms to work is more important.

First, whatever happened to DefaultControllers -- I want to disable
those cpu hierarchies, but that option seems to have disappeared without
a trace, although you can google and see it in some documentation.

The keyword also was not accepted in an install section I have, what is
the matter with that?  I want to use my sysklogd for my syslog, how can
I use that with systemd?

Thanks so much for all your help on these things.


-- 
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] problems getting systemd to work

2014-05-15 Thread covici
Canek Peláez Valdés can...@gmail.com wrote:

 On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés can...@gmail.com wrote:
  On Wed, May 14, 2014 at 5:26 PM,  cov...@ccs.covici.com wrote:
  [snip]
 
  Well, the workaround sort of worked -- it went through the initrd -- I
  had debug in the kernel command line, but it did not stop for nothing!
  When it went to the real root, however it did not activate any of the
  lvm volumes I had except for what I specified in the kernel command
  line, causing things not to work well.  Also, I noticed that if insisted
  on using the predictable network names, even though I have
  /etc/udev/rules.d/70-persistent-net.rules and
  /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
  me back my eth* names.  So all in all, it was a mess and took me to an
  emergency shell and that was the end of that.  I did eventually activate
  some volumes by lvchange -aay, but obviously that would not work well.
 
  OK, I was a little mystified about why dracut-036 worked on my system
  and 037 didn't. Before I tried any workaround, I wanted to know what
  changed from the previous version to the current one.
 
  So I generated an initramfs with dracut-036-r4 and another one with
  dracut-037-r1, and I tried to see what changed from one to the other.
  The answer is surprisingly easy: in /etc/cmdline.d/, the following
  files where in the 036-r4 version, but not in the 037-r4:
 
  90crypt.conf
  90lvm.conf
  90mdraid.conf
  base.conf
 
  Te contents of those files are (90crypt.conf is empty):
 
  90lvm.conf
 rd.lvm.lv=vg/vol1
 rd.lvm.lv=vg/vol4
 rd.lvm.lv=vg/vol3
 
  90mdraid.conf
 rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
  base.conf
 ro
 
  So I just changed my /etc/default/grub file:
 
  GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
  rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
  rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
  I regenerated my GRUB2 config, and now again my LVM test system works
  perfectly with the latest dracut version.
 
 I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
 BTW Jc, you used host_cmdline, I think the former is the correct one.
 
 So, to resume: there is no bug, is just that before hostonly_cmdline
 was yes by default, and now is no by default. This change was
 documented, but I failed to notice it (and I think the ebuild in
 Gentoo should print an einfo message).
 
 Anyway, I think that explains all my problems; John, I don't know if
 it will solve yours. Again: did you used dracut --print-cmdline to
 get the command line? Also, have you tried to use -H to generate your
 initramfs? And finally, have you tried with --hostonly-cmdline?

I did not use --hostonly-cmdline because I have other parameters and
wanted to keep everyting together -- should that make a difference?  If
I did use that then would I have append= in lilo.conf  or the grub
equivalemt?


-- 
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] boot problems

2014-05-15 Thread covici
Stefan G. Weichinger li...@xunil.at wrote:

 Am 15.05.2014 09:08, schrieb Stefan G. Weichinger:
  Am 15.05.2014 08:49, schrieb Canek Peláez Valdés:
  On Thu, May 15, 2014 at 1:21 AM, Canek Peláez Valdés can...@gmail.com 
  wrote:
  On Mon, May 5, 2014 at 1:40 AM, Canek Peláez Valdés can...@gmail.com 
  wrote:
 
  [ It's been more than a week since I last participated in the thread,
  so I'm just replying to my last participation. ]
 
  Stefan, have you tried to run dracut --print-cmdline and add that to
  your kernel command line?
 
  By the last thread related to systemd+dracut, that solved my problems
  when using dracut 037. Could you try to see if it solves your issues?
 
  Also, I just noticed the --hostonly-cmdline option. Have you tried that?
  
  Nope.
  
  I am away from LVM  RAID now as mentioned in the other thread ... btrfs
  everywhere ;-)
 
 Aside from that: I always use your tool kerninst so I have -H set as
 well.
What is kerninst?   I do not see it in the repository.

-- 
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] problems getting systemd to work

2014-05-15 Thread Stefan G. Weichinger
Am 15.05.2014 11:39, schrieb cov...@ccs.covici.com:

 I did not try the -H, I may test with that later.
 
 
 I did look at the --print-cmdline and copied the volumes they mentioned,
 but I have other lvm volumes in my fstab and none of them were activated,
 only the ones I specified in the command line!  This is where I have run
 into problems.  I have quite a few lvms, I want them all activated!

Sure. I remember having an extra lvm.service for systemd to have all the
LVs activated ... with that unit-file it worked more reliably for me
(maybe not needed since some time).

For sure that service file is only run *after* the initrd has
found/activated/mounted your LVM-based root ... might be a workaround to
specify the root-LV in the kernel command line (plus maybe rd.auto
rd.lvm=1 ?) and then let the service file activate the rest of the LVs.

Just to get you started at last ;-)


 Also, since I wrote the last message, I have been looking at the
 journalctl output and discovered a couple of things which I would like
 some help on, but getting the lvms to work is more important.
 
 First, whatever happened to DefaultControllers -- I want to disable
 those cpu hierarchies, but that option seems to have disappeared without
 a trace, although you can google and see it in some documentation.
 
 The keyword also was not accepted in an install section I have, what is
 the matter with that?

What keyword? I don't understand right now.

  I want to use my sysklogd for my syslog, how can
 I use that with systemd?

systemd's journal will be written to a socket if you configure it in
/etc/systemd/journald.conf

I would check man journald.conf and the option:

ForwardToSyslog=

and then let your chosen log-daemon listen there.

IMO you should take a look at journalctl then anyway ... new concepts,
but powerful features.

Stefan




Re: [gentoo-user] boot problems

2014-05-15 Thread Stefan G. Weichinger
Am 15.05.2014 11:58, schrieb cov...@ccs.covici.com:

 What is kerninst?   I do not see it in the repository.


https://github.com/canek-pelaez/kerninst

... but it uses GRUB2



Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread covici
Stefan G. Weichinger li...@xunil.at wrote:

 Am 15.05.2014 11:39, schrieb cov...@ccs.covici.com:
 
  I did not try the -H, I may test with that later.
  
  
  I did look at the --print-cmdline and copied the volumes they mentioned,
  but I have other lvm volumes in my fstab and none of them were activated,
  only the ones I specified in the command line!  This is where I have run
  into problems.  I have quite a few lvms, I want them all activated!
 
 Sure. I remember having an extra lvm.service for systemd to have all the
 LVs activated ... with that unit-file it worked more reliably for me
 (maybe not needed since some time).
 
 For sure that service file is only run *after* the initrd has
 found/activated/mounted your LVM-based root ... might be a workaround to
 specify the root-LV in the kernel command line (plus maybe rd.auto
 rd.lvm=1 ?) and then let the service file activate the rest of the LVs.
 
 Just to get you started at last ;-)
 
 
  Also, since I wrote the last message, I have been looking at the
  journalctl output and discovered a couple of things which I would like
  some help on, but getting the lvms to work is more important.
  
  First, whatever happened to DefaultControllers -- I want to disable
  those cpu hierarchies, but that option seems to have disappeared without
  a trace, although you can google and see it in some documentation.
  
  The keyword also was not accepted in an install section I have, what is
  the matter with that?
 
 What keyword? I don't understand right now.
 
   I want to use my sysklogd for my syslog, how can
  I use that with systemd?
 
 systemd's journal will be written to a socket if you configure it in
 /etc/systemd/journald.conf
 
 I would check man journald.conf and the option:
 
 ForwardToSyslog=
 
 and then let your chosen log-daemon listen there.
 
 IMO you should take a look at journalctl then anyway ... new concepts,
 but powerful features.

Sure, but what I was looking for was a way to start syslogd and klogd
using systemd -- I do have a socket option so they can listen on the
socket so that should be OK.

-- 
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] Having Trouble with Wireless Interface

2014-05-15 Thread Hunter Jozwiak
I got the networking interface to function correct.y now. Thanks all for the
help!

-Original Message-
From: Alan McKinnon [mailto:alan.mckin...@gmail.com] 
Sent: Thursday, May 15, 2014 5:29 AM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Having Trouble with Wireless Interface

On 15/05/2014 10:39, Stroller wrote:
 
 On Wed, 14 May 2014, at 12:36 pm, Alexander Kapshuk
alexander.kaps...@gmail.com wrote:
 .
 If you like to check if RTL8192CE is enabled in  your kernel's 
 .config file. If it isn't, you probably want to compile it as a 
 module, and then add rtl8192ce to /etc/conf.d/modules as well.
 Am pretty sure there's no need to add this one to /etc/conf.d/modules -
IME it'll just be found and loaded automagically by the kernel.

 Thanks for pointing that out. I wasn't aware of that. As I mentioned 
 in my previous post, I do not use genkernel myself.
 
 Neither do I - for this reason I found it a little frustrating trying to
help in a recent thread, myself.
 
 However, I'm pretty sure that loadable kernel modules behave the same
whether your kernel is built by hand or by genkernel - if you have modules
listed in /etc/conf.d/modules then I have to wonder if you really need them
there.
 
 I haven't used that file for years, and I prefer to compile everything as
a module, too.


Some modules don't autoload, usually because there's no hardware they drive
and so nothing to probe.

netfilter modules come to mind, as well as VirtualBox. One of the vbox
modules doesn't autoload by just stating VirtualBox, so the easiest is to
put it in /etc/conf.d/modules so it's always available. It's an edge case,
so the vast majority of modules load properly without intervention form us.




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






Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread covici
Canek Peláez Valdés can...@gmail.com wrote:

 On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés can...@gmail.com wrote:
  On Wed, May 14, 2014 at 5:26 PM,  cov...@ccs.covici.com wrote:
  [snip]
 
  Well, the workaround sort of worked -- it went through the initrd -- I
  had debug in the kernel command line, but it did not stop for nothing!
  When it went to the real root, however it did not activate any of the
  lvm volumes I had except for what I specified in the kernel command
  line, causing things not to work well.  Also, I noticed that if insisted
  on using the predictable network names, even though I have
  /etc/udev/rules.d/70-persistent-net.rules and
  /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
  me back my eth* names.  So all in all, it was a mess and took me to an
  emergency shell and that was the end of that.  I did eventually activate
  some volumes by lvchange -aay, but obviously that would not work well.
 
  OK, I was a little mystified about why dracut-036 worked on my system
  and 037 didn't. Before I tried any workaround, I wanted to know what
  changed from the previous version to the current one.
 
  So I generated an initramfs with dracut-036-r4 and another one with
  dracut-037-r1, and I tried to see what changed from one to the other.
  The answer is surprisingly easy: in /etc/cmdline.d/, the following
  files where in the 036-r4 version, but not in the 037-r4:
 
  90crypt.conf
  90lvm.conf
  90mdraid.conf
  base.conf
 
  Te contents of those files are (90crypt.conf is empty):
 
  90lvm.conf
 rd.lvm.lv=vg/vol1
 rd.lvm.lv=vg/vol4
 rd.lvm.lv=vg/vol3
 
  90mdraid.conf
 rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
  base.conf
 ro
 
  So I just changed my /etc/default/grub file:
 
  GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
  rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
  rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
  I regenerated my GRUB2 config, and now again my LVM test system works
  perfectly with the latest dracut version.
 
 I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
 BTW Jc, you used host_cmdline, I think the former is the correct one.
 
 So, to resume: there is no bug, is just that before hostonly_cmdline
 was yes by default, and now is no by default. This change was
 documented, but I failed to notice it (and I think the ebuild in
 Gentoo should print an einfo message).
 
 Anyway, I think that explains all my problems; John, I don't know if
 it will solve yours. Again: did you used dracut --print-cmdline to
 get the command line? Also, have you tried to use -H to generate your
 initramfs? And finally, have you tried with --hostonly-cmdline?

OK, I was looking through the journal output and I think the key to the
lvm's not activating is the following:
4 12:54:57 ccs systemd[1]: Got notification message for unit
systemd-journald.service
4 12:54:57 ccs systemd[1]: systemd-journald.service: Got notification
message from PID 1750 (WATCHDOG=1...)
4 12:54:57 ccs systemd[1]: systemd-journald.service: got WATCHDOG=1
4 12:54:57 ccs systemd[1]: Received SIGCHLD from PID 2603 (lvm).
4 12:54:57 ccs systemd[1]: Child 2602 (lvm) died (code=exited,
status=5/NOTINSSTALLED)
4 12:54:57 ccs systemd[1]: Child 2603 (lvm) died (code=exited,
status=5/NOTINSSTALLED)
4 12:54:57 ccs systemd[1]: Child 2610 (lvm) died (code=exited,
status=5/NOTINSSTALLED)
4 12:54:57 ccs systemd[1]: Job
dev-mapper-linux\x2d\x2dfiles\x2dportage.device/start timed out.

So what is not installed?

Also, for the first two lines, I get hundreds of thatpair of lines, how
can I prevent such.
So, between the lvm problem and the udev renaming my eth0 devices these
are the key as to why things are going wrong -- with openrc udev is not
renaming eth0 at all.


-- 
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] problems getting systemd to work

2014-05-15 Thread Stefan G. Weichinger
Am 15.05.2014 12:19, schrieb cov...@ccs.covici.com:

 Sure, but what I was looking for was a way to start syslogd and klogd
 using systemd -- I do have a socket option so they can listen on the
 socket so that should be OK.

So you look for service files?

A quick google finds examples for these 2 daemons here:

http://www.linuxfromscratch.org/hints/downloads/files/systemd.txt

If they work it would be great to file a bug for adding systemd unit
files to app-admin/sysklogd at bugs.gentoo.org ( I didn't check if the
ebuild brings unit-files but at least I see it doesn't have a systemd
USE flag).

Stefan





Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread Stefan G. Weichinger
Am 15.05.2014 13:50, schrieb cov...@ccs.covici.com:
 Canek Peláez Valdés can...@gmail.com wrote:
 
 On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés can...@gmail.com 
 wrote:
 On Wed, May 14, 2014 at 5:26 PM,  cov...@ccs.covici.com wrote:
 [snip]

 Well, the workaround sort of worked -- it went through the initrd -- I
 had debug in the kernel command line, but it did not stop for nothing!
 When it went to the real root, however it did not activate any of the
 lvm volumes I had except for what I specified in the kernel command
 line, causing things not to work well.  Also, I noticed that if insisted
 on using the predictable network names, even though I have
 /etc/udev/rules.d/70-persistent-net.rules and
 /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
 me back my eth* names.  So all in all, it was a mess and took me to an
 emergency shell and that was the end of that.  I did eventually activate
 some volumes by lvchange -aay, but obviously that would not work well.

 OK, I was a little mystified about why dracut-036 worked on my system
 and 037 didn't. Before I tried any workaround, I wanted to know what
 changed from the previous version to the current one.

 So I generated an initramfs with dracut-036-r4 and another one with
 dracut-037-r1, and I tried to see what changed from one to the other.
 The answer is surprisingly easy: in /etc/cmdline.d/, the following
 files where in the 036-r4 version, but not in the 037-r4:

 90crypt.conf
 90lvm.conf
 90mdraid.conf
 base.conf

 Te contents of those files are (90crypt.conf is empty):

 90lvm.conf
rd.lvm.lv=vg/vol1
rd.lvm.lv=vg/vol4
rd.lvm.lv=vg/vol3

 90mdraid.conf
rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

 base.conf
ro

 So I just changed my /etc/default/grub file:

 GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
 rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
 rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

 I regenerated my GRUB2 config, and now again my LVM test system works
 perfectly with the latest dracut version.

 I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
 BTW Jc, you used host_cmdline, I think the former is the correct one.

 So, to resume: there is no bug, is just that before hostonly_cmdline
 was yes by default, and now is no by default. This change was
 documented, but I failed to notice it (and I think the ebuild in
 Gentoo should print an einfo message).

 Anyway, I think that explains all my problems; John, I don't know if
 it will solve yours. Again: did you used dracut --print-cmdline to
 get the command line? Also, have you tried to use -H to generate your
 initramfs? And finally, have you tried with --hostonly-cmdline?
 
 OK, I was looking through the journal output and I think the key to the
 lvm's not activating is the following:
 4 12:54:57 ccs systemd[1]: Got notification message for unit
 systemd-journald.service
 4 12:54:57 ccs systemd[1]: systemd-journald.service: Got notification
 message from PID 1750 (WATCHDOG=1...)
 4 12:54:57 ccs systemd[1]: systemd-journald.service: got WATCHDOG=1
 4 12:54:57 ccs systemd[1]: Received SIGCHLD from PID 2603 (lvm).
 4 12:54:57 ccs systemd[1]: Child 2602 (lvm) died (code=exited,
 status=5/NOTINSSTALLED)
 4 12:54:57 ccs systemd[1]: Child 2603 (lvm) died (code=exited,
 status=5/NOTINSSTALLED)
 4 12:54:57 ccs systemd[1]: Child 2610 (lvm) died (code=exited,
 status=5/NOTINSSTALLED)
 4 12:54:57 ccs systemd[1]: Job
 dev-mapper-linux\x2d\x2dfiles\x2dportage.device/start timed out.
 
 So what is not installed?

My search tells me that this might be a misinterpreted return code.
I might repeat myself but the thread gets quite large now:

Did you enable lvm2-lvmetad.service or socket (and set use_lvmetad=1 in
lvm.conf)?

I think you don't have to, I just ask to check.

What release of lvm2, btw?

 Also, for the first two lines, I get hundreds of thatpair of lines, how
 can I prevent such.

The PID1 stuff ?

 So, between the lvm problem and the udev renaming my eth0 devices these
 are the key as to why things are going wrong -- with openrc udev is not
 renaming eth0 at all.

We'll take care of eth0 as well as soon your box boots correctly ;-)


Stefan



Re: [gentoo-user] udev or Gentoo issue?

2014-05-15 Thread Grant
 I'm having a problem starting the USB network interfaces properly on
 one of my systems.  I brought the problem to the udev list and they're
 indicating that it's a Gentoo problem:

 https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg18840.html

 Should I file a bug?

 - Grant

 Like pointed out in the upstream thread, it's either wrongly built
 net-misc/dhcpcd (should be with USE=udev)
 and if not using dhcpcd, it might be a bug in net-misc/netifrc's
 /etc/init.d/net.lo depend() { } section --
 it's possible it's missing dependency that forces /etc/init.d/udev start
 first, specially if OpenRC is using parallel
 startup

 So not really a udev bug, rather a misconfiguration in dhcpcd USE flags
 OR bug in dependencies of netifrc's net.lo script
 I'm starting two interfaces, one that uses dhcpcd and one that does
 not.  Both fail to start in the default runlevel until they are
 hotplugged later.  I do have dhcpcd built with USE=udev.  The string
 udev does not occur in /etc/init.d/net.lo so maybe that's the
 problem?  Please confirm that I should file a Gentoo bug for this.

 - Grant

 Try adding 'after udev' to net.lo's depend() { } section and see if that
 helps, if it does, file a bug
 saying so.

 I added it like this and rebooted:

 depend()
 {
 after udev

 but the result was the same.  I also have udev and udev-mount in the
 sysinit runlevel.


 It was more of an educated guess than 100% accurate knowledge. I can't
 think of an another
 way to force netifrc to behave, since it's not coded in C, and it can't
 link to libudev, so...

 However since you say *both*, even the one with dhcpcd fail to start,
 before filing that bug,
 see if disabling netifrc hotplugging works:

 # ln -s /dev/null /etc/udev/rules.d/90-network.rules

 Will that disable interface renaming or hotplugging?  The system with
 the issue is remote and if the interfaces aren't renamed or if
 hotplugging doesn't happen then I won't be able to access the system
 for up to 24 hours.  That's fine and I'm happy to test stuff like this
 anyway but I don't think this particular test will be informative
 because:

 It will disable the hotplugging, it means you *must* have the net.*
 stuff added
 to the default to runlevel yourself, like eg.

 # rc-update add net.foobar default


 They're in the default runlevel:

 # rc-update|grep net.enp
   net.enp0s20u2u1 |  default
   net.enp0s20u2u2 |  default

 I can disable hotplugging with rc_hotplug in rc.conf.  Hotplugging is
 actually disabled by default there and my network interfaces won't
 start automatically that way.


 Does your kernel have timing info enabled? If so, it would be
 interesting to look at your dmesg output.

 My guess is that your kernel is taking a really long time (several
 seconds) to initialize your network cards.


I have this:

# dmesg | grep enp
[4.297862] systemd-udevd[659]: renamed network interface eth0 to enp0s20u2u1
[4.778289] systemd-udevd[660]: renamed network interface eth0 to enp0s20u2u2
[6.496193] ax88179_178a 3-2.1:1.0 enp0s20u2u1: ax88179 - Link status is: 1
[7.905393] ax88179_178a 3-2.2:1.0 enp0s20u2u2: ax88179 - Link status is: 1
#

That doesn't tell us when the network initscripts tried and failed to
start but this from /var/log/messages/everything/current shows the
first time in the boot sequence that a dependent service failed to
start because of the networking failure so it should be before this:

[kernel] [0.787433] serio: i8042 AUX port at 0x60,0x64 irq 12
[/etc/init.d/unbound] ERROR: cannot start unbound as net.enp0s20u2u1
would not start
[kernel] [0.792081] rtc_cmos 00:04: alarms up to one month, y3k,
242 bytes nvram, hpet irqs

- Grant



Re: [gentoo-user] virtual problem : how can I unmerge Nano ?

2014-05-15 Thread Philip Webb
140429 Philip Webb wrote:
 140429 Neil Bothwick wrote:
PW The ebuild has a long list of possible editors,
 incl Vim Ed Nano, but nothing singling out Nano.
NB Except that nano is first in the list and portage takes
 the first available dependency as satisfying the virtual.
PW Doesn't Portage check whether any of the others are installed ?!
NB Apparently not. As long as the dependency is satisfied, so is portage.
 Extra checking would only slow down dependency resolution even more.

I have submitted Bug 510390.

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca




Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread covici
Stefan G. Weichinger li...@xunil.at wrote:

 Am 15.05.2014 12:19, schrieb cov...@ccs.covici.com:
 
  Sure, but what I was looking for was a way to start syslogd and klogd
  using systemd -- I do have a socket option so they can listen on the
  socket so that should be OK.
 
 So you look for service files?
 
 A quick google finds examples for these 2 daemons here:
 
 http://www.linuxfromscratch.org/hints/downloads/files/systemd.txt
 
 If they work it would be great to file a bug for adding systemd unit
 files to app-admin/sysklogd at bugs.gentoo.org ( I didn't check if the
 ebuild brings unit-files but at least I see it doesn't have a systemd
 USE flag).


OK, I will check, I did not see that in my search last time.

-- 
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] problems getting systemd to work

2014-05-15 Thread covici
Stefan G. Weichinger li...@xunil.at wrote:

 Am 15.05.2014 13:50, schrieb cov...@ccs.covici.com:
  Canek Peláez Valdés can...@gmail.com wrote:
  
  On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés can...@gmail.com 
  wrote:
  On Wed, May 14, 2014 at 5:26 PM,  cov...@ccs.covici.com wrote:
  [snip]
 
  Well, the workaround sort of worked -- it went through the initrd -- I
  had debug in the kernel command line, but it did not stop for nothing!
  When it went to the real root, however it did not activate any of the
  lvm volumes I had except for what I specified in the kernel command
  line, causing things not to work well.  Also, I noticed that if insisted
  on using the predictable network names, even though I have
  /etc/udev/rules.d/70-persistent-net.rules and
  /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
  me back my eth* names.  So all in all, it was a mess and took me to an
  emergency shell and that was the end of that.  I did eventually activate
  some volumes by lvchange -aay, but obviously that would not work well.
 
  OK, I was a little mystified about why dracut-036 worked on my system
  and 037 didn't. Before I tried any workaround, I wanted to know what
  changed from the previous version to the current one.
 
  So I generated an initramfs with dracut-036-r4 and another one with
  dracut-037-r1, and I tried to see what changed from one to the other.
  The answer is surprisingly easy: in /etc/cmdline.d/, the following
  files where in the 036-r4 version, but not in the 037-r4:
 
  90crypt.conf
  90lvm.conf
  90mdraid.conf
  base.conf
 
  Te contents of those files are (90crypt.conf is empty):
 
  90lvm.conf
 rd.lvm.lv=vg/vol1
 rd.lvm.lv=vg/vol4
 rd.lvm.lv=vg/vol3
 
  90mdraid.conf
 rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
  base.conf
 ro
 
  So I just changed my /etc/default/grub file:
 
  GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
  rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
  rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
  I regenerated my GRUB2 config, and now again my LVM test system works
  perfectly with the latest dracut version.
 
  I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
  BTW Jc, you used host_cmdline, I think the former is the correct one.
 
  So, to resume: there is no bug, is just that before hostonly_cmdline
  was yes by default, and now is no by default. This change was
  documented, but I failed to notice it (and I think the ebuild in
  Gentoo should print an einfo message).
 
  Anyway, I think that explains all my problems; John, I don't know if
  it will solve yours. Again: did you used dracut --print-cmdline to
  get the command line? Also, have you tried to use -H to generate your
  initramfs? And finally, have you tried with --hostonly-cmdline?
  
  OK, I was looking through the journal output and I think the key to the
  lvm's not activating is the following:
  4 12:54:57 ccs systemd[1]: Got notification message for unit
  systemd-journald.service
  4 12:54:57 ccs systemd[1]: systemd-journald.service: Got notification
  message from PID 1750 (WATCHDOG=1...)
  4 12:54:57 ccs systemd[1]: systemd-journald.service: got WATCHDOG=1
  4 12:54:57 ccs systemd[1]: Received SIGCHLD from PID 2603 (lvm).
  4 12:54:57 ccs systemd[1]: Child 2602 (lvm) died (code=exited,
  status=5/NOTINSSTALLED)
  4 12:54:57 ccs systemd[1]: Child 2603 (lvm) died (code=exited,
  status=5/NOTINSSTALLED)
  4 12:54:57 ccs systemd[1]: Child 2610 (lvm) died (code=exited,
  status=5/NOTINSSTALLED)
  4 12:54:57 ccs systemd[1]: Job
  dev-mapper-linux\x2d\x2dfiles\x2dportage.device/start timed out.
  
  So what is not installed?
 
 My search tells me that this might be a misinterpreted return code.
 I might repeat myself but the thread gets quite large now:
 
 Did you enable lvm2-lvmetad.service or socket (and set use_lvmetad=1 in
 lvm.conf)?
Yep, did not see that starting.

 
 I think you don't have to, I just ask to check.
 
 What release of lvm2, btw?
105-r2


 
  Also, for the first two lines, I get hundreds of thatpair of lines, how
  can I prevent such.
 
 The PID1 stuff ?

Nope, the notifications about journald and watchdog=1

 
  So, between the lvm problem and the udev renaming my eth0 devices these
  are the key as to why things are going wrong -- with openrc udev is not
  renaming eth0 at all.
 
 We'll take care of eth0 as well as soon your box boots correctly ;-)
 
 
 Stefan

-- 
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] problems getting systemd to work

2014-05-15 Thread Stefan G. Weichinger
Am 15.05.2014 14:38, schrieb cov...@ccs.covici.com:
 Stefan G. Weichinger li...@xunil.at wrote:
 
 Am 15.05.2014 13:50, schrieb cov...@ccs.covici.com:
 Canek Peláez Valdés can...@gmail.com wrote:

 On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés can...@gmail.com 
 wrote:
 On Wed, May 14, 2014 at 5:26 PM,  cov...@ccs.covici.com wrote:
 [snip]

 Well, the workaround sort of worked -- it went through the initrd -- I
 had debug in the kernel command line, but it did not stop for nothing!
 When it went to the real root, however it did not activate any of the
 lvm volumes I had except for what I specified in the kernel command
 line, causing things not to work well.  Also, I noticed that if insisted
 on using the predictable network names, even though I have
 /etc/udev/rules.d/70-persistent-net.rules and
 /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
 me back my eth* names.  So all in all, it was a mess and took me to an
 emergency shell and that was the end of that.  I did eventually activate
 some volumes by lvchange -aay, but obviously that would not work well.

 OK, I was a little mystified about why dracut-036 worked on my system
 and 037 didn't. Before I tried any workaround, I wanted to know what
 changed from the previous version to the current one.

 So I generated an initramfs with dracut-036-r4 and another one with
 dracut-037-r1, and I tried to see what changed from one to the other.
 The answer is surprisingly easy: in /etc/cmdline.d/, the following
 files where in the 036-r4 version, but not in the 037-r4:

 90crypt.conf
 90lvm.conf
 90mdraid.conf
 base.conf

 Te contents of those files are (90crypt.conf is empty):

 90lvm.conf
rd.lvm.lv=vg/vol1
rd.lvm.lv=vg/vol4
rd.lvm.lv=vg/vol3

 90mdraid.conf
rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

 base.conf
ro

 So I just changed my /etc/default/grub file:

 GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
 rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
 rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

 I regenerated my GRUB2 config, and now again my LVM test system works
 perfectly with the latest dracut version.

 I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
 BTW Jc, you used host_cmdline, I think the former is the correct one.

 So, to resume: there is no bug, is just that before hostonly_cmdline
 was yes by default, and now is no by default. This change was
 documented, but I failed to notice it (and I think the ebuild in
 Gentoo should print an einfo message).

 Anyway, I think that explains all my problems; John, I don't know if
 it will solve yours. Again: did you used dracut --print-cmdline to
 get the command line? Also, have you tried to use -H to generate your
 initramfs? And finally, have you tried with --hostonly-cmdline?

 OK, I was looking through the journal output and I think the key to the
 lvm's not activating is the following:
 4 12:54:57 ccs systemd[1]: Got notification message for unit
 systemd-journald.service
 4 12:54:57 ccs systemd[1]: systemd-journald.service: Got notification
 message from PID 1750 (WATCHDOG=1...)
 4 12:54:57 ccs systemd[1]: systemd-journald.service: got WATCHDOG=1
 4 12:54:57 ccs systemd[1]: Received SIGCHLD from PID 2603 (lvm).
 4 12:54:57 ccs systemd[1]: Child 2602 (lvm) died (code=exited,
 status=5/NOTINSSTALLED)
 4 12:54:57 ccs systemd[1]: Child 2603 (lvm) died (code=exited,
 status=5/NOTINSSTALLED)
 4 12:54:57 ccs systemd[1]: Child 2610 (lvm) died (code=exited,
 status=5/NOTINSSTALLED)
 4 12:54:57 ccs systemd[1]: Job
 dev-mapper-linux\x2d\x2dfiles\x2dportage.device/start timed out.

 So what is not installed?

 My search tells me that this might be a misinterpreted return code.
 I might repeat myself but the thread gets quite large now:

 Did you enable lvm2-lvmetad.service or socket (and set use_lvmetad=1 in
 lvm.conf)?
 Yep, did not see that starting.
 

 I think you don't have to, I just ask to check.

 What release of lvm2, btw?
 105-r2

Would you test downgrading to 2.02.104 for checking if that changes
something? Or 2.02.106 ...

I find various bugs on b.g.o. around lvm2 

Stefan






Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread Jc García
2014-05-15 0:47 GMT-06:00 Canek Peláez Valdés can...@gmail.com:

 I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
 BTW Jc, you used host_cmdline, I think the former is the correct one.


I don't know right now how host_cmdline got in my config(that was a
crazy day between dracut, systemd, and lvm documentations), who knows
where I saw it or if I mistyped it, anyway thanks for the correction.

 So, to resume: there is no bug, is just that before hostonly_cmdline
 was yes by default, and now is no by default. This change was
 documented, but I failed to notice it (and I think the ebuild in
 Gentoo should print an einfo message).

I agree, that notification in the ebulid would have saved trouble, and
I think it should be included since for sure many will run into these
problems in future.
So, would this qualify for a gentoo bug, and make the developer
include that notification?

Again, thanks for clarifying more the working of dracut.

 Anyway, I think that explains all my problems; John, I don't know if
 it will solve yours. Again: did you used dracut --print-cmdline to
 get the command line? Also, have you tried to use -H to generate your
 initramfs? And finally, have you tried with --hostonly-cmdline?

 Regards.
 --
 Canek Peláez Valdés
 Profesor de asignatura, Facultad de Ciencias
 Universidad Nacional Autónoma de México




Re: [gentoo-user] Having Trouble with Wireless Interface

2014-05-15 Thread Alexander Kapshuk

On 05/15/2014 11:39 AM, Stroller wrote:
 On Wed, 14 May 2014, at 12:36 pm, Alexander Kapshuk 
 alexander.kaps...@gmail.com wrote:
 … 
 If you like to check if RTL8192CE is enabled in  your kernel's .config
 file. If it isn't, you probably want to compile it as a module, and then
 add rtl8192ce to /etc/conf.d/modules as well.
 Am pretty sure there's no need to add this one to /etc/conf.d/modules - IME 
 it'll just be found and loaded automagically by the kernel.
 Thanks for pointing that out. I wasn't aware of that. As I mentioned in
 my previous post, I do not use genkernel myself.
 Neither do I - for this reason I found it a little frustrating trying to help 
 in a recent thread, myself.

 However, I'm pretty sure that loadable kernel modules behave the same whether 
 your kernel is built by hand or by genkernel - if you have modules listed 
 in /etc/conf.d/modules then I have to wonder if you really need them there.

 I haven't used that file for years, and I prefer to compile everything as a 
 module, too.

 Stroller.


That's interesting. I wasn't aware of that either.

So far, I've just been following the instructions given in the handbook,
section 7.d, which do recommend explicitly specifying the kernel modules
to be loaded at boot time in /etc/conf.d/modules.

How does the kernel know then what modules to load at boot time, if it
doesn't rely on /etc/conf.d/modules to supply the list of modules to be
loaded?

Does it use udev, or some other mechanism for that?

Thanks.




Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread Jc García
2014-05-15 6:38 GMT-06:00  cov...@ccs.covici.com:

 Did you enable lvm2-lvmetad.service or socket (and set use_lvmetad=1 in
 lvm.conf)?
 Yep, did not see that starting.

I have seen an odd behaviour regarding this sometimes, particulary
when I upgrade kernel, for some reason in my first reboot, my other
LVs (I have another 2 VGs) aren't activated, but on the second
reboot(Ctrl+Alt+Supr when it has got stuck), it works fine. this has
happened to me in the last 4 kernel upgrades.



Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread Tom H
On Thu, May 15, 2014 at 2:18 AM, Canek Peláez Valdés can...@gmail.com wrote:

 OK, I was a little mystified about why dracut-036 worked on my system
 and 037 didn't. Before I tried any workaround, I wanted to know what
 changed from the previous version to the current one.

 So I generated an initramfs with dracut-036-r4 and another one with
 dracut-037-r1, and I tried to see what changed from one to the other.
 The answer is surprisingly easy: in /etc/cmdline.d/, the following
 files where in the 036-r4 version, but not in the 037-r4:

 90crypt.conf
 90lvm.conf
 90mdraid.conf
 base.conf

 Te contents of those files are (90crypt.conf is empty):

 90lvm.conf
rd.lvm.lv=vg/vol1
rd.lvm.lv=vg/vol4
rd.lvm.lv=vg/vol3

 90mdraid.conf
rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

 base.conf
ro

 So I just changed my /etc/default/grub file:

 GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
 rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
 rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

 I regenerated my GRUB2 config, and now again my LVM test system works
 perfectly with the latest dracut version.

 The thing is, I *ALWAYS* use the -H (host only) option, so it was my
 understanding that the command line should be automatically generated,
 and it was on 036, but now it doesn't in 037. I think that's a bug.

 John, with respect to your case: did you used dracut --print-cmdline
 to get the command line? Also, have you tried to use -H to generate
 your initramfs?

There are two new options, --hostonly-cmdline (store kernel command
line arguments needed in the initramfs) and --no-hostonly-cmdline
(Do not store kernel command line arguments needed in the initramfs).



Re: [gentoo-user] Having Trouble with Wireless Interface

2014-05-15 Thread Stroller

On Thu, 15 May 2014, at 10:29 am, Alan McKinnon alan.mckin...@gmail.com wrote:
 … 
 However, I'm pretty sure that loadable kernel modules behave the same 
 whether your kernel is built by hand or by genkernel - if you have modules 
 listed in /etc/conf.d/modules then I have to wonder if you really need them 
 there.
 
 I haven't used that file for years, and I prefer to compile everything as a 
 module, too.
 
 Some modules don't autoload, usually because there's no hardware they
 drive and so nothing to probe.
 
 netfilter modules come to mind, as well as VirtualBox. … 

Many thanks, that's very informative.

Stroller.





Re: [gentoo-user] boot problems

2014-05-15 Thread Canek Peláez Valdés
On Thu, May 15, 2014 at 4:14 AM, Stefan G. Weichinger li...@xunil.at wrote:
 Am 15.05.2014 09:08, schrieb Stefan G. Weichinger:
 Am 15.05.2014 08:49, schrieb Canek Peláez Valdés:
 On Thu, May 15, 2014 at 1:21 AM, Canek Peláez Valdés can...@gmail.com 
 wrote:
 On Mon, May 5, 2014 at 1:40 AM, Canek Peláez Valdés can...@gmail.com 
 wrote:

 [ It's been more than a week since I last participated in the thread,
 so I'm just replying to my last participation. ]

 Stefan, have you tried to run dracut --print-cmdline and add that to
 your kernel command line?

 By the last thread related to systemd+dracut, that solved my problems
 when using dracut 037. Could you try to see if it solves your issues?

 Also, I just noticed the --hostonly-cmdline option. Have you tried that?

 Nope.

 I am away from LVM  RAID now as mentioned in the other thread ... btrfs
 everywhere ;-)

 Aside from that: I always use your tool kerninst so I have -H set as
 well.

That's the issue; since version 037, --hostonly and --hostonly-cmdline
are *separated*. You need to specify both.

With -H, you don't get the kernel cmdline, and therefore your kernel
cannot load your LVM volumes since it doesn't know their... names? I
don't knot the terminology.

In any case, you need to set --hostonly-cmdline (or
hostonly_cmdline=yes in the config file), *besides* -H.

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México



Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread Canek Peláez Valdés
On Thu, May 15, 2014 at 4:48 AM,  cov...@ccs.covici.com wrote:
 Canek Peláez Valdés can...@gmail.com wrote:

 On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés can...@gmail.com 
 wrote:
  On Wed, May 14, 2014 at 5:26 PM,  cov...@ccs.covici.com wrote:
  [snip]
 
  Well, the workaround sort of worked -- it went through the initrd -- I
  had debug in the kernel command line, but it did not stop for nothing!
  When it went to the real root, however it did not activate any of the
  lvm volumes I had except for what I specified in the kernel command
  line, causing things not to work well.  Also, I noticed that if insisted
  on using the predictable network names, even though I have
  /etc/udev/rules.d/70-persistent-net.rules and
  /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
  me back my eth* names.  So all in all, it was a mess and took me to an
  emergency shell and that was the end of that.  I did eventually activate
  some volumes by lvchange -aay, but obviously that would not work well.
 
  OK, I was a little mystified about why dracut-036 worked on my system
  and 037 didn't. Before I tried any workaround, I wanted to know what
  changed from the previous version to the current one.
 
  So I generated an initramfs with dracut-036-r4 and another one with
  dracut-037-r1, and I tried to see what changed from one to the other.
  The answer is surprisingly easy: in /etc/cmdline.d/, the following
  files where in the 036-r4 version, but not in the 037-r4:
 
  90crypt.conf
  90lvm.conf
  90mdraid.conf
  base.conf
 
  Te contents of those files are (90crypt.conf is empty):
 
  90lvm.conf
 rd.lvm.lv=vg/vol1
 rd.lvm.lv=vg/vol4
 rd.lvm.lv=vg/vol3
 
  90mdraid.conf
 rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
  base.conf
 ro
 
  So I just changed my /etc/default/grub file:
 
  GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
  rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
  rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
  I regenerated my GRUB2 config, and now again my LVM test system works
  perfectly with the latest dracut version.

 I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
 BTW Jc, you used host_cmdline, I think the former is the correct one.

 So, to resume: there is no bug, is just that before hostonly_cmdline
 was yes by default, and now is no by default. This change was
 documented, but I failed to notice it (and I think the ebuild in
 Gentoo should print an einfo message).

 Anyway, I think that explains all my problems; John, I don't know if
 it will solve yours. Again: did you used dracut --print-cmdline to
 get the command line? Also, have you tried to use -H to generate your
 initramfs? And finally, have you tried with --hostonly-cmdline?

 I did not use --hostonly-cmdline because I have other parameters and
 wanted to keep everyting together -- should that make a difference?

I think so.

  If
 I did use that then would I have append= in lilo.conf  or the grub
 equivalemt?

Nothing; dracut would take care of everything (in theory).

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México



Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread Canek Peláez Valdés
On Thu, May 15, 2014 at 4:39 AM,  cov...@ccs.covici.com wrote:
 Canek Peláez Valdés can...@gmail.com wrote:

 On Wed, May 14, 2014 at 5:26 PM,  cov...@ccs.covici.com wrote:
 [snip]
 
  Well, the workaround sort of worked -- it went through the initrd -- I
  had debug in the kernel command line, but it did not stop for nothing!
  When it went to the real root, however it did not activate any of the
  lvm volumes I had except for what I specified in the kernel command
  line, causing things not to work well.  Also, I noticed that if insisted
  on using the predictable network names, even though I have
  /etc/udev/rules.d/70-persistent-net.rules and
  /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
  me back my eth* names.  So all in all, it was a mess and took me to an
  emergency shell and that was the end of that.  I did eventually activate
  some volumes by lvchange -aay, but obviously that would not work well.

 OK, I was a little mystified about why dracut-036 worked on my system
 and 037 didn't. Before I tried any workaround, I wanted to know what
 changed from the previous version to the current one.

 So I generated an initramfs with dracut-036-r4 and another one with
 dracut-037-r1, and I tried to see what changed from one to the other.
 The answer is surprisingly easy: in /etc/cmdline.d/, the following
 files where in the 036-r4 version, but not in the 037-r4:

 90crypt.conf
 90lvm.conf
 90mdraid.conf
 base.conf

 Te contents of those files are (90crypt.conf is empty):

 90lvm.conf
rd.lvm.lv=vg/vol1
rd.lvm.lv=vg/vol4
rd.lvm.lv=vg/vol3

 90mdraid.conf
rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

 base.conf
ro

 So I just changed my /etc/default/grub file:

 GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
 rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
 rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

 I regenerated my GRUB2 config, and now again my LVM test system works
 perfectly with the latest dracut version.

 The thing is, I *ALWAYS* use the -H (host only) option, so it was my
 understanding that the command line should be automatically generated,
 and it was on 036, but now it doesn't in 037. I think that's a bug.

 John, with respect to your case: did you used dracut --print-cmdline
 to get the command line? Also, have you tried to use -H to generate
 your initramfs?

 I did not try the -H, I may test with that later.


 I did look at the --print-cmdline and copied the volumes they mentioned,
 but I have other lvm volumes in my fstab and none of them were activated,
 only the ones I specified in the command line!  This is where I have run
 into problems.  I have quite a few lvms, I want them all activated!

I just have /, /boot, /usr and /home (encrypted) as lvms, but all are activated.

 Also, since I wrote the last message, I have been looking at the
 journalctl output and discovered a couple of things which I would like
 some help on, but getting the lvms to work is more important.

 First, whatever happened to DefaultControllers -- I want to disable
 those cpu hierarchies, but that option seems to have disappeared without
 a trace, although you can google and see it in some documentation.

That went away with the new cgroup handling that is being coordinated
between systemd and the kernel:

http://cgit.freedesktop.org/systemd/systemd/commit/?id=7ac807320a7416463d7ff3ef6ede574863a601c5

 The keyword also was not accepted in an install section I have, what is
 the matter with that?  I want to use my sysklogd for my syslog, how can
 I use that with systemd?

I think you can do that with systemd.log_target=kmsg in the kernel command line.

 Thanks so much for all your help on these things.

John, could you please include here the output of lsblk, your fstab,
your dracut.conf, and your lilo.conf?

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México



Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread Stefan G. Weichinger
Am 15.05.2014 20:23, schrieb Canek Peláez Valdés:

 John, could you please include here the output of lsblk, your fstab,
 your dracut.conf, and your lilo.conf?

.. I agree! it's hard to keep track and overview in here :-)




Re: [gentoo-user] boot problems

2014-05-15 Thread Stefan G. Weichinger
Am 15.05.2014 20:05, schrieb Canek Peláez Valdés:

 With -H, you don't get the kernel cmdline, and therefore your kernel
 cannot load your LVM volumes since it doesn't know their... names? I
 don't knot the terminology.
 
 In any case, you need to set --hostonly-cmdline (or
 hostonly_cmdline=yes in the config file), *besides* -H.

ok ... I pulled your changes (kerninst) from github ... on the web I see
it, but it doesn't get into my copy here ... strange.

As I don't need it right now, I will (a) wait or (b) edit manually.

No problem.




Re: [gentoo-user] boot problems

2014-05-15 Thread Stefan G. Weichinger
Am 15.05.2014 20:27, schrieb Stefan G. Weichinger:
 Am 15.05.2014 20:05, schrieb Canek Peláez Valdés:
 
 With -H, you don't get the kernel cmdline, and therefore your kernel
 cannot load your LVM volumes since it doesn't know their... names? I
 don't knot the terminology.

 In any case, you need to set --hostonly-cmdline (or
 hostonly_cmdline=yes in the config file), *besides* -H.
 
 ok ... I pulled your changes (kerninst) from github ... on the web I see
 it, but it doesn't get into my copy here ... strange.
 
 As I don't need it right now, I will (a) wait or (b) edit manually.

forget that. I had local changes ... git pull works.




Re: [gentoo-user] Re: [OT]: Is that (filesystem-)logic vald?

2014-05-15 Thread meino . cramer
walt w41...@gmail.com [14-05-13 03:00]:
 On 05/11/2014 08:25 PM, meino.cra...@gmx.de wrote:
  Hi,
  
  I have an embedded system with internal flash memory. 
  The internal flash memory contains some static files,
  which are only be read and others, which get written
  from time to time.
  
  The internal flash has a FAT32-formatted filesystem
  and no real partiton (the device is directly fomratted
  as so often with this kind of lash memories.
  
  From time to time the software crashes while updateing
  some files (writing to them) leaving a unclean filesystem
  behind.
  
  Often -- after fscking the filesystem -- files named
  FSCKnumber.REC are left in the root of the filesystem.
  
  Is it correct to assume, that only those files are
  affected by correcting the filesysten which were written/updated
  before or is there any chance, that other, only read files
  are also affected?
 
 I don't know the answer so I'll ask a question instead :)
 
 How long was the embedded system working correctly before
 the crashes started?  Did it ever work correctly?
 
 
 
 

Yes, it works fine...as long it does not touch files, which
may be involved with those filesystem problems...

Best regards,
mcc






Re: [gentoo-user] boot problems

2014-05-15 Thread Canek Peláez Valdés
On Thu, May 15, 2014 at 1:27 PM, Stefan G. Weichinger li...@xunil.at wrote:
 Am 15.05.2014 20:05, schrieb Canek Peláez Valdés:

 With -H, you don't get the kernel cmdline, and therefore your kernel
 cannot load your LVM volumes since it doesn't know their... names? I
 don't knot the terminology.

 In any case, you need to set --hostonly-cmdline (or
 hostonly_cmdline=yes in the config file), *besides* -H.

 ok ... I pulled your changes (kerninst) from github ... on the web I see
 it, but it doesn't get into my copy here ... strange.

 As I don't need it right now, I will (a) wait or (b) edit manually.

 No problem.

I actually *removed* -H from kerninst. That should be configured in
the user's dracut.conf; now I have:

hostonly=yes
hostonly_cmdline=yes

in my dracut.conf.

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México



Re: [gentoo-user] Re: [OT]: Is that (filesystem-)logic vald?

2014-05-15 Thread meino . cramer
James wirel...@tampabay.rr.com [14-05-13 05:12]:
  meino.cramer at gmx.de writes:
 
 
  I have an embedded system with internal flash memory. 
  The internal flash memory contains some static files,
  which are only be read and others, which get written
  from time to time.
 
 
 Embedded systems vary wildly. If you can you need to be
 as specific as possilble on which embedded system, processor
 model, vendor, version etc.
 
  The internal flash has a FAT32-formatted filesystem
  and no real partiton (the device is directly fomratted
  as so often with this kind of lash memories.
  From time to time the software crashes while updateing
  some files (writing to them) leaving a unclean filesystem
  behind.
 
 
  Often -- after fscking the filesystem -- files named
  FSCKnumber.REC are left in the root of the filesystem.
 
 Have you sought out help from the vendor/manufacture?
 
 Can the embedded OS be updated and maintained?
 
 Can you install another, better supported embedded OS
 like openWRT
 
 https://openwrt.org/
 
  Is it correct to assume, that only those files are
  affected by correcting the filesysten which were written/updated
  before or is there any chance, that other, only read files
  are also affected?
 
 You've got to get really specific on the details of the embedded OS
 and such details.
 
 
 hth,
 James
 


Hi,

The embedded system is a Sansa Clip ZIP mp3 player. The OS is 
rockbox (www.rockbox.org). 

I think I cannot expect help from the manufacturer as the manufacturer
will not support another OS as his own firmware...which is more
limited in compare to rockbox.

In the meanwhile it looks like that there are two sources of trouble:
The sdcard, which acts as addtional flash memory extension. I changed
the sdcard I used to use with a another one, which work much better --
with rockbox. The original firmware does not have a problem with
either card. 

Since such firmware - neither the original one nor rockbox - has the
abilities of a fully fledged OS like linux for example I am looking
for a simple method to revert a somehow corrupted filesystem on either
flash memory back to a valid one. I think it is better to loose some
files (which can be regenerated) for the benefit of a sane filesystem 
than to insist of using a invalid one (and screw it up beyond repair
with each new write to it).

Rockbox supports the execution of lua scripts (somehow limited...no 
floating point, limited OS lib etc...). So, when the player needs
to be hard resetted which lead to a not-so-valid state of the
filesystem it would be nice, if a lua script would be able to revert
the filesystem back to a valid state.

If (see initial question) this would be possible by simply delete
all files which were altered since last execution of the script and 
rebbot the play than...that would be nice.

But: I dont know, whether the logic behind my initial question
is valid and reasonable...or simply as corrupted as the filesystem
i want to repair...

Any further idea is heartly appreciated!
Best regards,
mcc







[gentoo-user] Firefox and Adobe's DRM plugin

2014-05-15 Thread Mick
Does anyone know if Gentoo will provide a USE flag to enable this if desired?

https://hacks.mozilla.org/2014/05/reconciling-mozillas-mission-and-w3c-eme/

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Firefox and Adobe's DRM plugin

2014-05-15 Thread the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 05/15/14 23:31, Mick wrote:
 Does anyone know if Gentoo will provide a USE flag to enable this
 if desired?
 
 https://hacks.mozilla.org/2014/05/reconciling-mozillas-mission-and-w3c-eme/

 
Yes, I received a very disturbing letter from FSF today.
It's never late to switch to another broswer (I thought to myself
pretending midori merge).
I guess it must be configurable in the browser.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJTdReHAAoJEK64IL1uI2haVD0H/RflDZc44/1gQbmFC9FY0Wuu
k1haC3+j3N870bVjWKVOCqFOkaVJhhsOFDXpIDYKhVCJXk0Y9etvLCXUribzygs8
tQH0mYz+9WXfBGxzNxSyhcN5T9eVFnDd4i1NG0PORKUj2fGl337nWDVFWrrpfcNj
jZQochvP9cJ6KOSHeNbYP32WHF/ffJfCbl16MHCyb8sW/CG3y/V3GBJOykFsk5gU
RjPa+UCAVh+01qSDX53H//Iivd2MWwJP5Gvg7xI5WuIs3foZV+vwBw8eM2/f6rWh
KYKGA6yEF2qFu/cDFRNtshZ8Psm4lkYHgP2oYWvF3WTtrb91hQBS8/038wx8hdQ=
=Kshj
-END PGP SIGNATURE-



Re: [gentoo-user] Having Trouble with Wireless Interface

2014-05-15 Thread Mick
On Thursday 15 May 2014 14:24:57 Alexander Kapshuk wrote:
 On 05/15/2014 11:39 AM, Stroller wrote:
  On Wed, 14 May 2014, at 12:36 pm, Alexander Kapshuk 
alexander.kaps...@gmail.com wrote:
  …
  If you like to check if RTL8192CE is enabled in  your kernel's .config
  file. If it isn't, you probably want to compile it as a module, and
  then add rtl8192ce to /etc/conf.d/modules as well.
  
  Am pretty sure there's no need to add this one to /etc/conf.d/modules -
  IME it'll just be found and loaded automagically by the kernel.
  
  Thanks for pointing that out. I wasn't aware of that. As I mentioned in
  my previous post, I do not use genkernel myself.
  
  Neither do I - for this reason I found it a little frustrating trying to
  help in a recent thread, myself.
  
  However, I'm pretty sure that loadable kernel modules behave the same
  whether your kernel is built by hand or by genkernel - if you have
  modules listed in /etc/conf.d/modules then I have to wonder if you
  really need them there.
  
  I haven't used that file for years, and I prefer to compile everything as
  a module, too.
  
  Stroller.
 
 That's interesting. I wasn't aware of that either.
 
 So far, I've just been following the instructions given in the handbook,
 section 7.d, which do recommend explicitly specifying the kernel modules
 to be loaded at boot time in /etc/conf.d/modules.
 
 How does the kernel know then what modules to load at boot time, if it
 doesn't rely on /etc/conf.d/modules to supply the list of modules to be
 loaded?
 
 Does it use udev, or some other mechanism for that?
 
 Thanks.

I understand it is udev magic which probes the hardware and it fetches the 
corresponding module from the kernel, as long as it has been compiled.  
Incidentally, I noticed that I now have this running on my system:

/lib/systemd/systemd-udevd --daemon

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread covici
Canek Peláez Valdés can...@gmail.com wrote:

 On Thu, May 15, 2014 at 4:39 AM,  cov...@ccs.covici.com wrote:
  Canek Peláez Valdés can...@gmail.com wrote:
 
  On Wed, May 14, 2014 at 5:26 PM,  cov...@ccs.covici.com wrote:
  [snip]
  
   Well, the workaround sort of worked -- it went through the initrd -- I
   had debug in the kernel command line, but it did not stop for nothing!
   When it went to the real root, however it did not activate any of the
   lvm volumes I had except for what I specified in the kernel command
   line, causing things not to work well.  Also, I noticed that if insisted
   on using the predictable network names, even though I have
   /etc/udev/rules.d/70-persistent-net.rules and
   /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
   me back my eth* names.  So all in all, it was a mess and took me to an
   emergency shell and that was the end of that.  I did eventually activate
   some volumes by lvchange -aay, but obviously that would not work well.
 
  OK, I was a little mystified about why dracut-036 worked on my system
  and 037 didn't. Before I tried any workaround, I wanted to know what
  changed from the previous version to the current one.
 
  So I generated an initramfs with dracut-036-r4 and another one with
  dracut-037-r1, and I tried to see what changed from one to the other.
  The answer is surprisingly easy: in /etc/cmdline.d/, the following
  files where in the 036-r4 version, but not in the 037-r4:
 
  90crypt.conf
  90lvm.conf
  90mdraid.conf
  base.conf
 
  Te contents of those files are (90crypt.conf is empty):
 
  90lvm.conf
 rd.lvm.lv=vg/vol1
 rd.lvm.lv=vg/vol4
 rd.lvm.lv=vg/vol3
 
  90mdraid.conf
 rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
  base.conf
 ro
 
  So I just changed my /etc/default/grub file:
 
  GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
  rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
  rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
 
  I regenerated my GRUB2 config, and now again my LVM test system works
  perfectly with the latest dracut version.
 
  The thing is, I *ALWAYS* use the -H (host only) option, so it was my
  understanding that the command line should be automatically generated,
  and it was on 036, but now it doesn't in 037. I think that's a bug.
 
  John, with respect to your case: did you used dracut --print-cmdline
  to get the command line? Also, have you tried to use -H to generate
  your initramfs?
 
  I did not try the -H, I may test with that later.
 
 
  I did look at the --print-cmdline and copied the volumes they mentioned,
  but I have other lvm volumes in my fstab and none of them were activated,
  only the ones I specified in the command line!  This is where I have run
  into problems.  I have quite a few lvms, I want them all activated!
 
 I just have /, /boot, /usr and /home (encrypted) as lvms, but all are 
 activated.
 
  Also, since I wrote the last message, I have been looking at the
  journalctl output and discovered a couple of things which I would like
  some help on, but getting the lvms to work is more important.
 
  First, whatever happened to DefaultControllers -- I want to disable
  those cpu hierarchies, but that option seems to have disappeared without
  a trace, although you can google and see it in some documentation.
 
 That went away with the new cgroup handling that is being coordinated
 between systemd and the kernel:
 
 http://cgit.freedesktop.org/systemd/systemd/commit/?id=7ac807320a7416463d7ff3ef6ede574863a601c5
 
  The keyword also was not accepted in an install section I have, what is
  the matter with that?  I want to use my sysklogd for my syslog, how can
  I use that with systemd?
 
 I think you can do that with systemd.log_target=kmsg in the kernel command 
 line.
 
  Thanks so much for all your help on these things.
 
 John, could you please include here the output of lsblk, your fstab,
 your dracut.conf, and your lilo.conf?

output of lsblk:
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda  8:00 931.5G  0 disk 
├─sda1   8:10 3G  0 part /boot
├─sda2   8:20  1000M  0 part /mnt/oldgentoo
└─sda3   8:30 927.6G  0 part 
  ├─linux--files-64--root  253:00 3G  0 lvm  /
  ├─linux--files-swap  253:10 2G  0 lvm  [SWAP]
  ├─linux--files-64--usr   253:2065G  0 lvm  /usr
  ├─linux--files-usr--src  253:3035G  0 lvm  /usr/src
  ├─linux--files-tmp   253:4010G  0 lvm  /tmp
  ├─linux--files-64--var   253:5020G  0 lvm  /var
  ├─linux--files-home  253:6030G  0 lvm  /home
  ├─linux--files-audio 253:70   990G  0 lvm  /audio
  ├─linux--files-usr--bbs  253:80   256M  0 lvm  /usr/bbs
  ├─linux--files-hard2 253:90   704M  0 lvm  /hard2
  ├─linux--files-scratch   253:10  

[gentoo-user] Re: Firefox and Adobe's DRM plugin

2014-05-15 Thread »Q«
On Thu, 15 May 2014 20:31:14 +0100
Mick michaelkintz...@gmail.com wrote:

 Does anyone know if Gentoo will provide a USE flag to enable this if
 desired?
 
 https://hacks.mozilla.org/2014/05/reconciling-mozillas-mission-and-w3c-eme/

It may not even be possible to enable it in Gentoo builds or it may be
possible only in firefox-bin builds.  From that article (which is by
Mozilla's CTO, by the way),

  Mozilla will distribute the sandbox alongside Firefox, and we are
  working on deterministic builds that will allow developers to use a
  sandbox compiled on their own machine with the CDM as an alternative.

IMO they *must* make that possible.  Otherwise the sandbox itself has
to be a binary blob, which would negate much of reason for having a
sandbox in the first place -- it would only be an alleged sandbox.

He also says,

  As plugins today, the CDM itself will be distributed by Adobe and
  will not be included in Firefox.

So if/when Gentoo gets around to making the CDM available, ISTM it will
almost certainly be a package separate from Firefox.  If so, maybe
there will be a USE flag for Firefox which pulls the CDM in as a
dependency, but that flag should be off by default (again IMO).






Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread Stefan G. Weichinger
Am 15.05.2014 22:38, schrieb cov...@ccs.covici.com:

 image=/boot/vmlinuz-3.6.2-gentoo

phew. 3.6.2 is from October 2012 ...
Did you recompile it with the suggested options for systemd?

Maybe it doesn't matter, but just a thought ... that kernel is quite old.

Stefan



Re: [gentoo-user] problems getting systemd to work

2014-05-15 Thread covici
Stefan G. Weichinger li...@xunil.at wrote:

 Am 15.05.2014 22:38, schrieb cov...@ccs.covici.com:
 
  image=/boot/vmlinuz-3.6.2-gentoo
 
 phew. 3.6.2 is from October 2012 ...
 Did you recompile it with the suggested options for systemd?
 
 Maybe it doesn't matter, but just a thought ... that kernel is quite old.

I did recompile a number of times, but for now I have to stick with this
one.

-- 
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] udev or Gentoo issue?

2014-05-15 Thread Mike Gilbert
On Thu, May 15, 2014 at 8:18 AM, Grant emailgr...@gmail.com wrote:
 I have this:

 # dmesg | grep enp
 [4.297862] systemd-udevd[659]: renamed network interface eth0 to 
 enp0s20u2u1
 [4.778289] systemd-udevd[660]: renamed network interface eth0 to 
 enp0s20u2u2
 [6.496193] ax88179_178a 3-2.1:1.0 enp0s20u2u1: ax88179 - Link status is: 1
 [7.905393] ax88179_178a 3-2.2:1.0 enp0s20u2u2: ax88179 - Link status is: 1
 #

 That doesn't tell us when the network initscripts tried and failed to
 start but this from /var/log/messages/everything/current shows the
 first time in the boot sequence that a dependent service failed to
 start because of the networking failure so it should be before this:

 [kernel] [0.787433] serio: i8042 AUX port at 0x60,0x64 irq 12
 [/etc/init.d/unbound] ERROR: cannot start unbound as net.enp0s20u2u1
 would not start
 [kernel] [0.792081] rtc_cmos 00:04: alarms up to one month, y3k,
 242 bytes nvram, hpet irqs


Yeah, so I think the kernel is detecting your network card after udev
has already started.

One interesting experiment would be to delay the boot process to allow
the kernel additional time to detect devices. Adding rootdelay=10 to
your kernel command line should do the trick, unless you are using
some broken initramfs.