public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Tsoy <alexander@tsoy.me>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Anyone with access to genkernel repository? Or should genkernel be p.masked on amd64 profiles?
Date: Sat, 31 May 2014 00:23:49 +0400	[thread overview]
Message-ID: <1401481429.8057.2.camel@Nokia-N900> (raw)
In-Reply-To: <20140530183032.GA20205@gentoo.org>

On Fri May 30 22:30:32 2014 Sven Vermeulen <swift@gentoo.org> wrote:
> On Fri, May 30, 2014 at 04:34:09PM +0000, hasufell wrote:
> > Tom Wijsman:
> > > 
> > > Please no p.mask for a single line being wrong...
> > > 
> > 
> > That's nonsense. The amount of wrong lines doesn't matter. A single
> > wrong line in the kernel can break your whole system as well.
> > 
> > Please p.mask (or patch) immediately. There is no point in waiting.
> 
> I'd appreciate any patch on the Gentoo Handbook to use another tool for
> initramfs. I have some experience with dracut, but the last dracut
> generated initramfs failed on my system, whereas genkernel's still goes
> well.
> 

Hmm.. You are the second person in this thread who experienced problems with latest dracut. I suspect this is due to hostonly-cmdline option, which is disabled by default. If this is really the case, we should either enable it in gentoo.conf or revert corresponding changes like in fedora [1].

And where are bug reports? :)

Sorry for offtop.

[1] http://pkgs.fedoraproject.org/cgit/dracut.git/commit/?id=2fa76e2882883ea64be6c3210c257cff4e4b641a

> The last Dracut generated initramfs also failed on SELinux systems, but
> that isn't something that cannot be worked around...
> 
> Wkr,
>     Sven Vermeulen
> 

-- 
Alexander Tsoy


  parent reply	other threads:[~2014-05-30 20:19 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30 15:10 [gentoo-dev] Anyone with access to genkernel repository? Or should genkernel be p.masked on amd64 profiles? Samuli Suominen
2014-05-30 16:10 ` Tom Wijsman
2014-05-30 16:16   ` Samuli Suominen
2014-05-30 16:26     ` Samuli Suominen
2014-05-30 16:50       ` Tom Wijsman
2014-05-30 17:02         ` Ben Kohler
2014-05-30 17:32           ` Rich Freeman
2014-05-30 17:39             ` Fabio Erculiani
2014-05-30 17:58               ` Rick "Zero_Chaos" Farina
2014-05-30 17:59             ` Tom Wijsman
2014-05-30 18:08               ` Ben Kohler
2014-05-30 18:28                 ` Tom Wijsman
2014-05-30 17:22         ` Rich Freeman
2014-05-30 18:03           ` Tom Wijsman
2014-05-30 16:34   ` hasufell
2014-05-30 17:11     ` Tom Wijsman
2014-05-30 17:14       ` Ciaran McCreesh
2014-05-30 17:17         ` Tom Wijsman
2014-06-03 18:58           ` Jeroen Roovers
2014-06-03 22:18             ` Tom Wijsman
2014-06-03 22:35               ` hasufell
2014-06-03 23:13                 ` Tom Wijsman
2014-05-30 17:20         ` Ian Stakenvicius
2014-05-30 19:52         ` Andreas K. Huettel
2014-05-30 17:14       ` Alexander Berntsen
2014-05-30 17:18         ` Tom Wijsman
2014-05-30 17:21           ` Alexander Berntsen
2014-05-30 18:15             ` Tom Wijsman
2014-05-30 18:30     ` Sven Vermeulen
2014-05-30 19:20       ` hasufell
2014-05-30 20:23       ` Alexander Tsoy [this message]
2014-05-30 16:43   ` Alexander Berntsen
2014-05-30 17:12     ` Tom Wijsman
2014-05-30 16:50 ` Rick "Zero_Chaos" Farina
2014-05-31  2:39   ` [gentoo-dev] " Steven J. Long
2014-05-30 16:51 ` [gentoo-dev] " Alexander Tsoy
2014-05-30 17:15   ` Tom Wijsman
2014-05-31 19:41 ` Robin H. Johnson
2014-05-31 19:46   ` Samuli Suominen
2014-05-31 20:00     ` Robin H. Johnson
2014-05-31 20:16       ` Samuli Suominen
2014-05-31 22:53         ` Robin H. Johnson
2014-05-31 19:51   ` Fabio Erculiani
2014-05-31 20:06     ` Robin H. Johnson
2014-05-31 21:42       ` Fabio Erculiani
2014-05-31 22:20         ` Tom Wijsman
2014-05-31 23:01         ` Robin H. Johnson

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=1401481429.8057.2.camel@Nokia-N900 \
    --to=alexander@tsoy.me \
    --cc=gentoo-dev@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