[gentoo-catalyst] livecd stage1 kernel .config

[gentoo-catalyst] livecd stage1 kernel .config

[Greg Fitzgerald]

I went and created stages 1-3 and I am now working on my livecd stage1.

My spec file is as follows:

subarch: amd64
version_stamp: installer-2007.0
target: livecd-stage1
rel_type: default
profile: default-linux/amd64/2007.0/desktop
snapshot: 20080104 
source_subpath: default/stage3-amd64-20080104

livecd/use:
        branding
        livecd
        socks5

livecd/packages:
--- lots of packages here ---

It compiles around 400 packages then dies on gnome-menus which requires a 
.config file in my kernel sources directory. Wondering how to solve this 
issue. I am new to making a livecd with catalyst, but my understanding is
you set the .config file for your kernel in your livecd stage2. I tried
to copy it to the livecd cache directory under /usr/src/linux and starting
again with -a but it appears to get deleted when I start again. Can anyone
let me know how I should proceed from here?

Thanks,
Greg
-- 
gentoo-catalyst@lists.gentoo.org mailing list

[gentoo-catalyst] livecd stage1 kernel .config

[Greg Fitzgerald]

First off, sorry if this got double posted. Pretty sure I sent it
to the wrong address first time.

I went and created stages 1-3 and I am now working on my livecd stage1.

My spec file is as follows:

subarch: amd64
version_stamp: installer-2007.0
target: livecd-stage1
rel_type: default
profile: default-linux/amd64/2007.0/desktop
snapshot: 20080104
source_subpath: default/stage3-amd64-20080104

livecd/use:
        branding
        livecd
        socks5

livecd/packages:
--- lots of packages here ---

It compiles around 400 packages then dies on gnome-menus which requires a
.config file in my kernel sources directory. Wondering how to solve this
issue. I am new to making a livecd with catalyst, but my understanding is
you set the .config file for your kernel in your livecd stage2. I tried
to copy it to the livecd cache directory under /usr/src/linux and starting
again with -a but it appears to get deleted when I start again. Can anyone
let me know how I should proceed from here?

Thanks,
Greg
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] livecd stage1 kernel .config

[Andrew Gaffney]

Greg Fitzgerald wrote:
> I went and created stages 1-3 and I am now working on my livecd stage1.
> 
> My spec file is as follows:
> 
> subarch: amd64
> version_stamp: installer-2007.0
> target: livecd-stage1
> rel_type: default
> profile: default-linux/amd64/2007.0/desktop
> snapshot: 20080104 
> source_subpath: default/stage3-amd64-20080104
> 
> livecd/use:
>         branding
>         livecd
>         socks5
> 
> livecd/packages:
> --- lots of packages here ---
> 
> It compiles around 400 packages then dies on gnome-menus which requires a 
> .config file in my kernel sources directory. Wondering how to solve this 
> issue. I am new to making a livecd with catalyst, but my understanding is
> you set the .config file for your kernel in your livecd stage2. I tried
> to copy it to the livecd cache directory under /usr/src/linux and starting
> again with -a but it appears to get deleted when I start again. Can anyone
> let me know how I should proceed from here?

There are a couple of ways around this, but you probably won't like any of them.

1) switch to xfce4, which doesn't bring in gnome-menus (the way I'd go)
2) modify the ebuild in your snapshot to bypass the kernel feature check
3) modify linux-info.eclass in your snapshot to not fail like this
4) give up

-- 
Andrew Gaffney                                 http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer             Catalyst/Installer + x86 release coordinator
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] livecd stage1 kernel .config

[Greg Fitzgerald]

On  1:52 PM - Monday, January  7, Andrew Gaffney wrote:

> Greg Fitzgerald wrote:
>> I went and created stages 1-3 and I am now working on my livecd stage1.
>> My spec file is as follows:
>> subarch: amd64
>> version_stamp: installer-2007.0
>> target: livecd-stage1
>> rel_type: default
>> profile: default-linux/amd64/2007.0/desktop
>> snapshot: 20080104 source_subpath: default/stage3-amd64-20080104
>> livecd/use:
>>         branding
>>         livecd
>>         socks5
>> livecd/packages:
>> --- lots of packages here ---
>> It compiles around 400 packages then dies on gnome-menus which requires a 
>> .config file in my kernel sources directory. Wondering how to solve this 
>> issue. I am new to making a livecd with catalyst, but my understanding is
>> you set the .config file for your kernel in your livecd stage2. I tried
>> to copy it to the livecd cache directory under /usr/src/linux and starting
>> again with -a but it appears to get deleted when I start again. Can anyone
>> let me know how I should proceed from here?
>
> There are a couple of ways around this, but you probably won't like any of 
> them.
>
> 1) switch to xfce4, which doesn't bring in gnome-menus (the way I'd go)
> 2) modify the ebuild in your snapshot to bypass the kernel feature check
> 3) modify linux-info.eclass in your snapshot to not fail like this
> 4) give up
>
> -- 
> Andrew Gaffney                                 
> http://dev.gentoo.org/~agaffney/
> Gentoo Linux Developer             Catalyst/Installer + x86 release 
> coordinator
> -- 
> gentoo-catalyst@lists.gentoo.org mailing list
>

Well I actually don't even have xfce in my list period actually. Nor do
I have gnome. Trying to find out what actually wants to pull in gnome
menu right now. I am trying to build the cd so that It boots into
console and you could run startx and go into openbox if you wanted to.
That is my goal. Enclosing my package list maybe someone can tell me
what would even be trying to pull in gnome-menu. In the mean time I'll
probably modify the ebuild in my snapshot, hopefully next time I'm
working on this I can avoid doing that though.

Below is my package list. Anyone see something that would be pulling in gnome-menus
that I am missing? I tried to clean out items that would pull in to many
gnome items right from the start considering I just wanted to go with openbox,
and firefox, thunderbird, for now. Must have something though that still needs
gnome-menu or the default use flags are causing it to be brought in.

livecd/packages:
    app-admin/ide-smart
    app-admin/logrotate
    app-admin/passook
    app-admin/pwgen
    app-admin/sudo
    app-admin/syslog-ng
    app-arch/mt-st
    app-benchmarks/cpuburn
    app-cdr/cdrkit
    app-crypt/gnupg
    app-editors/vim
    app-misc/livecd-tools
    app-misc/screen
    app-misc/vlock
    app-portage/gentoolkit
    app-portage/mirrorselect
    app-portage/ufed
    dev-util/ccache
    x11-wm/openbox
    mail-client/mozilla-thunderbird
    media-gfx/fbgrab
    media-sound/audacious
    net-analyzer/netcat
    net-analyzer/nmap
    net-analyzer/traceroute
    net-dialup/mingetty
    net-dialup/minicom
    net-dialup/pptpclient
    net-dialup/rp-pppoe
    net-fs/nfs-utils
    net-im/pidgin
    net-irc/irssi
    net-irc/xchat
    net-misc/bridge-utils
    net-misc/dhcpcd
    net-misc/iputils
    net-misc/rdate
    net-misc/rdesktop
    net-misc/vconfig
    net-misc/whois
    net-p2p/bittorrent
    net-proxy/dante
    net-proxy/tsocks
    net-wireless/prism54-firmware
    net-wireless/wireless-tools
    net-wireless/wpa_supplicant
    net-wireless/zd1211-firmware
    sys-apps/eject
    sys-apps/ethtool
    sys-apps/fxload
    sys-apps/gli
    sys-apps/hdparm
    sys-apps/hwsetup
    sys-apps/iproute2
    sys-apps/memtester
    sys-apps/netplug
    sys-apps/parted
    sys-apps/sdparm
    sys-apps/slocate
    sys-block/aoetools
    sys-block/disktype
    sys-block/gparted
    sys-boot/grub
    sys-devel/distcc
    sys-fs/dosfstools
    sys-fs/e2fsprogs
    sys-fs/evms
    sys-fs/jfsutils
    sys-fs/lsscsi
    sys-fs/lvm2
    sys-fs/mdadm
    sys-fs/ntfsprogs
    sys-fs/reiserfsprogs
    sys-fs/xfsprogs
    sys-kernel/genkernel
    sys-libs/gpm
    sys-power/acpid
    sys-process/vixie-cron
    www-client/links
    www-client/mozilla-firefox
    x11-base/xorg-server
    x11-base/xorg-x11
    x11-drivers/synaptics

Best Regards,
Greg
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] livecd stage1 kernel .config

[Chris Traylor]

[-- Attachment #1: Type: text/plain, Size: 366 bytes --]

On Mon, 2008-01-07 at 15:28 -0500, Greg Fitzgerald wrote:

>     mail-client/mozilla-thunderbird
>     www-client/mozilla-firefox


Without knowing for sure, I would suspect one or both of these two.

Chris

--
Q: How many neocons does it take to change a lightbulb?
A: None. Neocons don't believe in light bulbs, they declare war on evil
and set the house on fire.

[-- Attachment #2: Type: text/html, Size: 809 bytes --]

Re: [gentoo-catalyst] livecd stage1 kernel .config

[Greg Fitzgerald]

On  3:38 PM - Monday, January  7, Chris Traylor wrote:

> On Mon, 2008-01-07 at 15:28 -0500, Greg Fitzgerald wrote:
> 
> >     mail-client/mozilla-thunderbird
> >     www-client/mozilla-firefox
> 
> 
> Without knowing for sure, I would suspect one or both of these two.
> 
> Chris
> 
> --
> Q: How many neocons does it take to change a lightbulb?
> A: None. Neocons don't believe in light bulbs, they declare war on evil
> and set the house on fire.

>From what I see in those two ebuilds, I doubt it is either of those
myself. Could be, I just don't see it from the depends listed. I did
however found out the profile I was using has the gnome use flag set
by default. So I changed that to -gnome modified my list of apps a
little and I am going to set it up to build again tonight. Let everyone
know how it goes sometime tomorrow. Sure I can figure this out on my own
now, I was just more curious if I was missing some super secret method or
option in my spec file. I'll make a post soon as I know something more.
Still open to opinions.

Thanks,
Greg
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] livecd stage1 kernel .config

[Daniel Ostrow]

[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]

On Mon, 2008-01-07 at 15:52 -0500, Greg Fitzgerald wrote:
> On  3:38 PM - Monday, January  7, Chris Traylor wrote:
> 
> > On Mon, 2008-01-07 at 15:28 -0500, Greg Fitzgerald wrote:
> > 
> > >     mail-client/mozilla-thunderbird
> > >     www-client/mozilla-firefox
> > 
> > 
> > Without knowing for sure, I would suspect one or both of these two.
> > 
> > Chris
> > 
> > --
> > Q: How many neocons does it take to change a lightbulb?
> > A: None. Neocons don't believe in light bulbs, they declare war on evil
> > and set the house on fire.
> 
> From what I see in those two ebuilds, I doubt it is either of those
> myself. Could be, I just don't see it from the depends listed. I did
> however found out the profile I was using has the gnome use flag set
> by default. So I changed that to -gnome modified my list of apps a
> little and I am going to set it up to build again tonight. Let everyone
> know how it goes sometime tomorrow. Sure I can figure this out on my own
> now, I was just more curious if I was missing some super secret method or
> option in my spec file. I'll make a post soon as I know something more.
> Still open to opinions.
> 
> Thanks,
> Greg

thunderbird, firefox and ntfsprogs all pull in gnome-vfs which pulls in
gnome-mount which pulls in gnome-menu. In all cases this is due to the
gnome USE flag.

--Dan

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] livecd stage1 kernel .config

[Greg Fitzgerald]

On  3:27 PM - Monday, January  7, Daniel Ostrow wrote:

> On Mon, 2008-01-07 at 15:52 -0500, Greg Fitzgerald wrote:
> > On  3:38 PM - Monday, January  7, Chris Traylor wrote:
> > 
> > > On Mon, 2008-01-07 at 15:28 -0500, Greg Fitzgerald wrote:
> > > 
> > > >     mail-client/mozilla-thunderbird
> > > >     www-client/mozilla-firefox
> > > 
> > > 
> > > Without knowing for sure, I would suspect one or both of these two.
> > > 
> > > Chris
> > > 
> > > --
> > > Q: How many neocons does it take to change a lightbulb?
> > > A: None. Neocons don't believe in light bulbs, they declare war on evil
> > > and set the house on fire.
> > 
> > From what I see in those two ebuilds, I doubt it is either of those
> > myself. Could be, I just don't see it from the depends listed. I did
> > however found out the profile I was using has the gnome use flag set
> > by default. So I changed that to -gnome modified my list of apps a
> > little and I am going to set it up to build again tonight. Let everyone
> > know how it goes sometime tomorrow. Sure I can figure this out on my own
> > now, I was just more curious if I was missing some super secret method or
> > option in my spec file. I'll make a post soon as I know something more.
> > Still open to opinions.
> > 
> > Thanks,
> > Greg
> 
> thunderbird, firefox and ntfsprogs all pull in gnome-vfs which pulls in
> gnome-mount which pulls in gnome-menu. In all cases this is due to the
> gnome USE flag.
> 
> --Dan

Thanks for correcting me. I had already gone about setting -gnome though
and solved that. Moved onto the livecd-stage2.spec and that went fine.
Now when I boot the iso imagine I get the following error.

mount: Mounting /dev/loop0 on /mnt/newroot/livecd failed: invalid
argument

Started searching around for this error. Found a possible solution by
editing the squashfs imagine but I have no idea if that will work and
its very hackish. Wondering if someone might know what I did wrong.
Using the stable version of genkernel of course.

Two things I did read about was some people had luck with squashfs
compiled as a module others had better luck with it compiled into the
kernel. I have tried both ways now. 

Best Regards,
Greg
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] livecd stage1 kernel .config

[Andrew Gaffney]

Greg Fitzgerald wrote:
> Thanks for correcting me. I had already gone about setting -gnome though
> and solved that. Moved onto the livecd-stage2.spec and that went fine.
> Now when I boot the iso imagine I get the following error.
> 
> mount: Mounting /dev/loop0 on /mnt/newroot/livecd failed: invalid
> argument
> 
> Started searching around for this error. Found a possible solution by
> editing the squashfs imagine but I have no idea if that will work and
> its very hackish. Wondering if someone might know what I did wrong.
> Using the stable version of genkernel of course.
> 
> Two things I did read about was some people had luck with squashfs
> compiled as a module others had better luck with it compiled into the
> kernel. I have tried both ways now. 

Are you sure you have loop device and squashfs support enabled in your kernel?

-- 
Andrew Gaffney                                 http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer             Catalyst/Installer + x86 release coordinator
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] livecd stage1 kernel .config

[Greg Fitzgerald]

On 10:41 AM - Tuesday, January  8, Andrew Gaffney wrote:

> Greg Fitzgerald wrote:
>> Thanks for correcting me. I had already gone about setting -gnome though
>> and solved that. Moved onto the livecd-stage2.spec and that went fine.
>> Now when I boot the iso imagine I get the following error.
>> mount: Mounting /dev/loop0 on /mnt/newroot/livecd failed: invalid
>> argument
>> Started searching around for this error. Found a possible solution by
>> editing the squashfs imagine but I have no idea if that will work and
>> its very hackish. Wondering if someone might know what I did wrong.
>> Using the stable version of genkernel of course.
>> Two things I did read about was some people had luck with squashfs
>> compiled as a module others had better luck with it compiled into the
>> kernel. I have tried both ways now. 
>
> Are you sure you have loop device and squashfs support enabled in your 
> kernel?
>
> -- 
> Andrew Gaffney                                 
> http://dev.gentoo.org/~agaffney/
> Gentoo Linux Developer             Catalyst/Installer + x86 release 
> coordinator
> -- 
> gentoo-catalyst@lists.gentoo.org mailing list
>
Yep,

CONFIG_BLK_DEV_LOOP=y
CONFIG_SQUASHFS=y
CONFIG_SQUASHFS_EMBEDDED=y
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3


--Greg
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] livecd stage1 kernel .config

[Greg Fitzgerald]

On 10:41 AM - Tuesday, January  8, Andrew Gaffney wrote:

> Greg Fitzgerald wrote:
>> Thanks for correcting me. I had already gone about setting -gnome though
>> and solved that. Moved onto the livecd-stage2.spec and that went fine.
>> Now when I boot the iso imagine I get the following error.
>> mount: Mounting /dev/loop0 on /mnt/newroot/livecd failed: invalid
>> argument
>> Started searching around for this error. Found a possible solution by
>> editing the squashfs imagine but I have no idea if that will work and
>> its very hackish. Wondering if someone might know what I did wrong.
>> Using the stable version of genkernel of course.
>> Two things I did read about was some people had luck with squashfs
>> compiled as a module others had better luck with it compiled into the
>> kernel. I have tried both ways now. 
>
> Are you sure you have loop device and squashfs support enabled in your 
> kernel?
>
> -- 
> Andrew Gaffney                                 
> http://dev.gentoo.org/~agaffney/
> Gentoo Linux Developer             Catalyst/Installer + x86 release 
> coordinator
> -- 
> gentoo-catalyst@lists.gentoo.org mailing list
>

We'll still stuck on that same error. Here is my kernel config that I
stole from the squash image so I was sure it was being used.

http://gregf.org/gentoo/kernel-config-x86_64-2.6.23-gentoo-r3

I also tried changing my livecd type to livecd/type: generic-livecd
based off of the comments from the default spec file. No luck there
either.

Both loop and squashfs are enabled. I have done some looking around and
I see a bunch of people complaining about the same issue on
gentoo-wiki.com. I know it's unsupported, just where I happened to find
others with the same issue.

When I hit up the forums one person was talking about doing some things
to get it working by modifying the squashfs image inside the iso.
/dev/loop0 does exist inside the image. There is no entry in the fstab
but I'm assuming everything is called with full paths so there is no
need.

First time doing this as I mentioned before so any help would be
appreciated. If I can provide any info to make it easier let me know.

Best Regards,
Greg
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] livecd stage1 kernel .config

[Philipp Riegger]

On Mon, 2008-01-07 at 14:33 -0500, Greg Fitzgerald wrote:
> It compiles around 400 packages then dies on gnome-menus which requires a
> .config file in my kernel sources directory. Wondering how to solve this
> issue. I am new to making a livecd with catalyst, but my understanding is
> you set the .config file for your kernel in your livecd stage2. I tried
> to copy it to the livecd cache directory under /usr/src/linux and starting
> again with -a but it appears to get deleted when I start again. Can anyone
> let me know how I should proceed from here?

I have the same problem when compiling gnome with tinderbox. What is the
right way to solve this one?

Philipp

-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] livecd stage1 kernel .config

["Andreas Rückert"]

Hi!

-------- Original-Nachricht --------
> Datum: Thu, 10 Jan 2008 12:19:31 +0100
> Von: Philipp Riegger <lists@anderedomain.de>
> An: gentoo-catalyst@lists.gentoo.org
> Betreff: Re: [gentoo-catalyst] livecd stage1 kernel .config

> 
> On Mon, 2008-01-07 at 14:33 -0500, Greg Fitzgerald wrote:
> > It compiles around 400 packages then dies on gnome-menus which requires
> a
> > .config file in my kernel sources directory. Wondering how to solve this
> > issue. I am new to making a livecd with catalyst, but my understanding
> is
> > you set the .config file for your kernel in your livecd stage2. I tried
> > to copy it to the livecd cache directory under /usr/src/linux and
> starting
> > again with -a but it appears to get deleted when I start again. Can
> anyone
> > let me know how I should proceed from here?
> 
> I have the same problem when compiling gnome with tinderbox. What is the
> right way to solve this one?

Packages, that require a kernel config are usually moved to livecd-stage2.

kdemultimedia-kioslaves
is in stage 2 here as an example...

HTH,
Andreas

-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] livecd stage1 kernel .config

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]

On Thu, 2008-01-10 at 12:19 +0100, Philipp Riegger wrote:
> On Mon, 2008-01-07 at 14:33 -0500, Greg Fitzgerald wrote:
> > It compiles around 400 packages then dies on gnome-menus which requires a
> > .config file in my kernel sources directory. Wondering how to solve this
> > issue. I am new to making a livecd with catalyst, but my understanding is
> > you set the .config file for your kernel in your livecd stage2. I tried
> > to copy it to the livecd cache directory under /usr/src/linux and starting
> > again with -a but it appears to get deleted when I start again. Can anyone
> > let me know how I should proceed from here?
> 
> I have the same problem when compiling gnome with tinderbox. What is the
> right way to solve this one?

Get the package updated to not need to do a stupid kernel configuration
check is the proper solution.

Quite honestly, the linux-info eclass needs to be completely rewritten.
The eclass should *not* fail by default, for any reason.  Any failures
should be optional and opt-in only.  The linux-mod eclass, on the other
hand, *should* fail.  Basically, not being able to get information about
the running/compiled kernel in a package which is not a kernel module
should never be a failure.  In the current code, it is a failure.

http://bugs.gentoo.org/show_bug.cgi?id=192556

Everybody who is getting this error, add yourself to CC on that bug.
That bug being fixed is what you need to resolve this issue.

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Games Developer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]