On Mon, 2009-04-13 at 14:44 +0200, Alexander Boström wrote:
Maybe something is missing from the initrd. The process of creating it
is a bit of a mystery to me, but making sure /dev/root is set up right
before generating the initrd seems to work. Try this:
The initrd is missing the modules
Hi Martin,
What would it take to move the next XS Server release to either F10 or
F11 as F9 will be EOL as soon as F11 comes out in a month or so (one
month after F11 is out F9 will be EOL).
Peter
On Mon, Apr 13, 2009 at 11:29 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
On the mission
On Wed, Apr 15, 2009 at 11:08 AM, Peter Robinson pbrobin...@gmail.com wrote:
What would it take to move the next XS Server release to either F10 or
F11 as F9 will be EOL as soon as F11 comes out in a month or so (one
month after F11 is out F9 will be EOL).
It's a bit of a recurring question. I
What would it take to move the next XS Server release to either F10 or
F11 as F9 will be EOL as soon as F11 comes out in a month or so (one
month after F11 is out F9 will be EOL).
It's a bit of a recurring question. I am swamped with feature
development for a while. My hope is to port to F11
On Wed, Apr 15, 2009 at 2:41 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
On Wed, Apr 15, 2009 at 11:08 AM, Peter Robinson pbrobin...@gmail.com wrote:
What would it take to move the next XS Server release to either F10 or
F11 as F9 will be EOL as soon as F11 comes out in a month or so
On Wed, 15 Apr 2009, Sameer Verma wrote:
On Wed, Apr 15, 2009 at 2:41 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
On Wed, Apr 15, 2009 at 11:08 AM, Peter Robinson pbrobin...@gmail.com
wrote:
What would it take to move the next XS Server release to either F10 or
F11 as F9 will be
On Wed, Apr 15, 2009 at 6:01 PM, Greg Dekoenigsberg g...@redhat.com wrote:
Choose CentOS. The workflow for managing development atop Centos and Fedora
are essentially the same.
That's the plan for the XS (I'm sure gregdek knows it, but it's good
to broadcast the msg) :-)
In the meantime,
On Wed, 15 Apr 2009, Martin Langhoff wrote:
On Wed, Apr 15, 2009 at 6:01 PM, Greg Dekoenigsberg g...@redhat.com wrote:
Choose CentOS. The workflow for managing development atop Centos and Fedora
are essentially the same.
That's the plan for the XS (I'm sure gregdek knows it, but it's good
On Wed, Apr 15, 2009 at 6:47 PM, Greg Dekoenigsberg g...@redhat.com wrote:
Is there a bug I can herd people towards?
Not a bug as such, as I haven't narrowed down steps to repro, but
here's the start of the relevant threads:
http://lists.laptop.org/pipermail/server-devel/2009-April/003209.html
Choose CentOS. The workflow for managing development atop Centos and Fedora
are essentially the same.
I have no doubt about it, and I've read that going forward that is the
plan for XS. The reason I originally asked the question about what we
need to move it forward to F11 was so that we can
On Wed, 15 Apr 2009, Martin Langhoff wrote:
On Wed, Apr 15, 2009 at 6:01 PM, Greg Dekoenigsberg g...@redhat.com wrote:
Choose CentOS. The workflow for managing development atop Centos and Fedora
are essentially the same.
That's the plan for the XS (I'm sure gregdek knows it, but it's good
On Mon, Apr 13, 2009 at 5:01 PM, Jerry Vonau jvo...@shaw.ca wrote:
So far I have added to %post:
cat /etc/sysconfig/mkinitrd EOF
MODULES=sdhci mmc_block
EOF
I just tried a variation on that, and it didn't work. It does load
sdhci and mmc_block now, but it still fails. There's something
On Tue, Apr 14, 2009 at 9:26 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
I just tried a variation on that, and it didn't work. It does load
sdhci and mmc_block now, but it still fails. There's something else at
play...
If I replace the kernel with an OLPC kernel, at least it tries to
On Tue, Apr 14, 2009 at 2:24 PM, Martin Langhoff
martin.langh...@gmail.com wrote:
If I replace the kernel with an OLPC kernel, at least it tries to open
mmcblk0p1 -- and fails, because the drivers we need are built as
modules.
Have you had any success?
Using dsd's XO-alt-distro scripts we
On Tue, 2009-04-14 at 20:45 +0200, Martin Langhoff wrote:
On Tue, Apr 14, 2009 at 2:24 PM, Martin Langhoff
martin.langh...@gmail.com wrote:
If I replace the kernel with an OLPC kernel, at least it tries to open
mmcblk0p1 -- and fails, because the drivers we need are built as
modules.
On the mission of getting a XS image running on the XO, I have abused
imagecreator (part of livecdtools) to create an ext3 image based on
the XS ISO we distribute.
Now I am trying to make the image boot on the XO, and it is not
working. It fails in trying to mount (and then switchroot to)
Maybe something is missing from the initrd. The process of creating it
is a bit of a mystery to me, but making sure /dev/root is set up right
before generating the initrd seems to work. Try this:
Boot the XO into the regular Sugar system.
Insert SD card, open a root shell.
mount -o remount,dev
I can download the image, or at least the initrd.img, from where?
Jerry
On Mon, 2009-04-13 at 12:29 +0200, Martin Langhoff wrote:
On the mission of getting a XS image running on the XO, I have abused
imagecreator (part of livecdtools) to create an ext3 image based on
the XS ISO we
I can download the image, or at least the initrd.img, from where?
Jerry
On Mon, 2009-04-13 at 12:29 +0200, Martin Langhoff wrote:
On the mission of getting a XS image running on the XO, I have abused
imagecreator (part of livecdtools) to create an ext3 image based on
the XS ISO we
On Mon, 2009-04-13 at 08:26 -0500, Jerry Vonau wrote:
On Mon, 2009-04-13 at 14:44 +0200, Alexander Boström wrote:
Maybe something is missing from the initrd. The process of creating it
is a bit of a mystery to me, but making sure /dev/root is set up right
before generating the initrd
20 matches
Mail list logo
