public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] eject and util-linux blocker
Date: Tue, 17 Mar 2015 16:07:29 -0500	[thread overview]
Message-ID: <55089791.5080603@gmail.com> (raw)
In-Reply-To: <55088F2D.5080708@gmail.com>

Alan McKinnon wrote:
> On 17/03/2015 22:16, Dale wrote:
>> Mike Gilbert wrote:
>>> On Tue, Mar 17, 2015 at 2:10 PM, Dale <rdalek1967@gmail.com> wrote:
>>>> Alan McKinnon wrote:
>>>>> Your basic problem is that you have static and static-libs in USE. When
>>>>> applied to lvm, a whole bunch of blockers kick in and you get what you
>>>>> got. So take them out of USE.
>>>>>
>>>>> USE="static static-libs" has it's uses, it's great for building rescue
>>>>> disks, busybox and maybe some disk repair utils, but makes very little
>>>>> sense on a regular workstation. If you break your workstation, you'll
>>>>> boot off a rescue disk and use the tools on it to fix your install, so
>>>>> you don't need it on the main system.
>>>>>
>>>>> There is nothing wrong with your eudev.
>>>>> lvm2 is bitching about blockers between lvm2 built with "USE=static" and
>>>>> udev - there's some incompatibility there and the ebuild knows about them
>>>>>
>>>>>
>>>> I went through the package.use file and commented out the static and
>>>> static-libs stuff.  It seems happy but thing is, when I put them there,
>>>> they were needed for some reason.  Actually, all the parts I found had
>>>> the output of where emerge said those were needed.  Maybe the reason
>>>> they were needed then has changed and they are no longer needed.  I hope
>>>> anyway.  ;-)
>>> I know there were some guides for doing LVM root that used to advise
>>> building stuff statically, probably because of some problem with
>>> genkernel.
>>>
>>> With a modern initramfs (dracut, and possible recent genkernel),
>>> shared libs work just as well, so there should be no need.
>>>
>>>
>> Well, in package.use, it has some output of emerge that said it needed. 
>> Here is a snippet:
>>
>> # required by sys-fs/lvm2-2.02.109[static]
>> # required by @selected
>> # required by @world (argument)
>> #=sys-apps/util-linux-2.24.1-r3 static-libs
>
> You are reading it wrong. That means:
> util-linux needs to be built with USE="static-libs"
> because
> lvm2 is already built with USE="static"
>
> None of which explains why you originally built lvm2 that way.


It was because emerge told me it needed it for some reason.  It is very
rare that I just put something in package.use on my own.  On the rare
times I have done it, it is on a package that I use and I need to enable
something but don't want to enable it globally or only that one package
has that USE flag.  A couple examples, gimp, nut, gtkam is a few that I
have in there because of some option I need to enable/disable. 


>> # required by virtual/udev-208-r2
>> # required by @selected
>> # required by @world (argument)
>> #virtual/libudev static-libs
>>
>> # required by virtual/udev-208-r2[gudev]
>> # required by @selected
>> # required by @world (argument)
>> #virtual/libgudev static-libs
>>
>> There's a couple more but you get the idea.  I don't use genkernel,
>> tried it but never got a working kernel from it so I do them by hand. 
>> Everything built OK with no more complaining so I guess whatever it is
>> has changed.  Still weird tho. 
>
> This has nothing to do with genkernel.
> More than likely, you followed some daft advice on teh intarwebz saying
> you need a static lvm to be able to boot / on lvm.
>
>

I don't have / on lvm.  /boot and / are on regular partitions. 
Everything else, /usr, /var and /home, are on lvm.  Keep in mind, I was
trying to avoid that init thingy. 

I mentioned genkernel because Mike mentioned it.  I tried it ages ago
and never got a kernel that would boot.  I don't even have it installed
here.  I started doing them by hand and have been pretty good at it ever
since.  Odd I know. 

Dale

:-)  :-) 



  reply	other threads:[~2015-03-17 21:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 14:08 [gentoo-user] eject and util-linux blocker Dale
2015-03-16 15:34 ` Walter Dnes
2015-03-17  1:43   ` Dale
2015-03-17  8:14     ` Alan McKinnon
2015-03-17 17:01       ` Dale
2015-03-17 17:30         ` Alan McKinnon
2015-03-17 18:10           ` Dale
2015-03-17 18:40             ` Mike Gilbert
2015-03-17 20:16               ` Dale
2015-03-17 20:31                 ` Alan McKinnon
2015-03-17 21:07                   ` Dale [this message]
2015-03-18  8:54                     ` Peter Humphrey
2015-03-18  9:08                       ` Neil Bothwick
2015-03-18  9:33                       ` Dale
2015-03-18 10:21                         ` Peter Humphrey
2015-03-18 16:14                           ` Dale
2015-03-18 17:03                             ` Peter Humphrey
2015-03-18 16:37                     ` Rich Freeman
2015-03-18 17:56                       ` Poncho
2015-03-18 18:12                         ` Dale
2015-03-18 21:55                           ` Rich Freeman
2015-03-18 23:12                           ` Peter Humphrey
2015-03-19  4:14                             ` Dale
2015-03-19  9:34                               ` Peter Humphrey
2015-03-19 15:29                                 ` Dale
2015-03-17 18:50             ` Alan McKinnon
2015-03-17 20:20               ` Dale
2015-03-17 20:46                 ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55089791.5080603@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox