Re: [fedora-arm] F17 snapshot images
On Sat, Mar 31, 2012 at 2:20 AM, Brendan Conoboy wrote: > On 03/30/2012 05:35 PM, "Andy Green (林安廸)" wrote: >> >> It's great that you're doing this, but I don't think dding partition + >> filesystems is a good idea. > > > It's definitely tricky to get right. The number of possible configurations > makes it tricky to do an efficient selection of images. I may end up doing a > combination tegra+omap+etc image to cut down the waste. > > >> We found that various "8GB" SD cards have different absolute numbers of >> available sectors, it can lead to eventual filesystem corruption if your >> image is slightly large than someone else's card. > > > Well, the image is being created out of a sparse file with 8000 1048576 byte > sectors. If that proves too many it would be little trouble to drop it down > to 7900 or something. We'll see how it goes in practice. > > >> If someone's going to try this they're probably OK running fdisk and >> using tarballs. > > > Yeah, the uboot enabled kernel tarball will probably be the most universally > useful. I personally had plenty of trouble marking working uboot files so > leveraging David Marlin's work on grubby will hopefully spare others that > trouble. Meanwhile, a number of people have asked for images they can dd, > so I'm trying to fulfill both needs. > > >> I've been using Peter's F17 alpha1 image and following progress with >> updates, it's been very good. It's stuck as of last week with >> gnome-shell problems though. But generally package completeness has >> been increasing really well last few weeks, great job. > > > What are the gnome-shell problems? Perhaps they're well known but I'm not > acquainted with them. If we're missing a package that will help things out > let me know and I'll put it in the next snapshot. It'll be dep issues, I'm awaiting the reopening of mainline so we'll get updates. Peter ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F17 snapshot images
On 03/31/2012 09:20 AM, Somebody in the thread at some point said: > On 03/30/2012 05:35 PM, "Andy Green (林安廸)" wrote: >> It's great that you're doing this, but I don't think dding partition + >> filesystems is a good idea. > > It's definitely tricky to get right. The number of possible > configurations makes it tricky to do an efficient selection of images. I > may end up doing a combination tegra+omap+etc image to cut down the waste. > >> We found that various "8GB" SD cards have different absolute numbers of >> available sectors, it can lead to eventual filesystem corruption if your >> image is slightly large than someone else's card. > > Well, the image is being created out of a sparse file with 8000 1048576 > byte sectors. If that proves too many it would be little trouble to > drop it down to 7900 or something. We'll see how it goes in practice. Just saying if the filesystem in there at the end doesn't all make it on the device, it will work for a while and die corrupted. It won't hurt to pare it back 100MB. >> If someone's going to try this they're probably OK running fdisk and >> using tarballs. > > Yeah, the uboot enabled kernel tarball will probably be the most > universally useful. I personally had plenty of trouble marking working > uboot files so leveraging David Marlin's work on grubby will hopefully > spare others that trouble. Meanwhile, a number of people have asked for > images they can dd, so I'm trying to fulfill both needs. Yes working with U-Boot isn't pretty. >> I've been using Peter's F17 alpha1 image and following progress with >> updates, it's been very good. It's stuck as of last week with >> gnome-shell problems though. But generally package completeness has >> been increasing really well last few weeks, great job. > > What are the gnome-shell problems? Perhaps they're well known but I'm > not acquainted with them. If we're missing a package that will help > things out let me know and I'll put it in the next snapshot. It's not deps afaict, a couple of weeks ago pieces were missing, but there now is enough to yum install @gnome-desktop sanely with --skip-broken; abrt, elfutils, gdb, libreport and xmlrpc-c are skipped. Here anyway the resulting gdm / gnome ends up showing "Oh no! Something has gone wrong." before gdm login. Poking around in gdm logs shows a segfault after not being able to find org.gnome.SessionManager |not provided by any .service files". I had to mess with a javascript file in gnome to get that info, it was otherwise complaining that there were too many args sent to the logging api. -Andy ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F17 snapshot images
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 30 Mar 2012 18:20:17 -0700 Brendan Conoboy wrote: > On 03/30/2012 05:35 PM, "Andy Green (林安廸)" wrote: > > It's great that you're doing this, but I don't think dding > > partition + filesystems is a good idea. > > It's definitely tricky to get right. The number of possible > configurations makes it tricky to do an efficient selection of > images. I may end up doing a combination tegra+omap+etc image to cut > down the waste. > > > We found that various "8GB" SD cards have different absolute > > numbers of available sectors, it can lead to eventual filesystem > > corruption if your image is slightly large than someone else's card. > > Well, the image is being created out of a sparse file with 8000 > 1048576 byte sectors. If that proves too many it would be little > trouble to drop it down to 7900 or something. We'll see how it goes > in practice. i think we should only make the image 2 gb using domething like "dd if=/dev/zero of/raw/disk bs=1M count=2048" cound could be 2000 also then it should work everywhere. > > If someone's going to try this they're probably OK running fdisk and > > using tarballs. the idea is to get to a point where its simple to deploy lower the barrier of entry. > Yeah, the uboot enabled kernel tarball will probably be the most > universally useful. I personally had plenty of trouble marking > working uboot files so leveraging David Marlin's work on grubby will > hopefully spare others that trouble. Meanwhile, a number of people > have asked for images they can dd, so I'm trying to fulfill both > needs. > > > I've been using Peter's F17 alpha1 image and following progress with > > updates, it's been very good. It's stuck as of last week with > > gnome-shell problems though. But generally package completeness has > > been increasing really well last few weeks, great job. > > What are the gnome-shell problems? Perhaps they're well known but > I'm not acquainted with them. If we're missing a package that will > help things out let me know and I'll put it in the next snapshot. > there is gnome 3.4.0 in testing on primary now there is a change it will get pushed to stable for beta on monday if not its probably 2 weeks away. What we need to do is come up with a set of F17 beta deliverables and work really hard in the next 2 weeks to deliver a F17 Beta. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk93GjwACgkQkSxm47BaWffvhwCgg3VtFwVUF2FVBWPL0tMMA6Ik yJ4AoJEKuHTrJCBlyv7JZgGf5LAqYxWE =MCFP -END PGP SIGNATURE- ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F17 snapshot images
On Sat, 2012-03-31 at 09:52 -0500, Dennis Gilmore wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Fri, 30 Mar 2012 18:20:17 -0700 > Brendan Conoboy wrote: > > > On 03/30/2012 05:35 PM, "Andy Green (林安廸)" wrote: > > > It's great that you're doing this, but I don't think dding > > > partition + filesystems is a good idea. > > > > It's definitely tricky to get right. The number of possible > > configurations makes it tricky to do an efficient selection of > > images. I may end up doing a combination tegra+omap+etc image to cut > > down the waste. > > > > > We found that various "8GB" SD cards have different absolute > > > numbers of available sectors, it can lead to eventual filesystem > > > corruption if your image is slightly large than someone else's card. > > > > Well, the image is being created out of a sparse file with 8000 > > 1048576 byte sectors. If that proves too many it would be little > > trouble to drop it down to 7900 or something. We'll see how it goes > > in practice. > i think we should only make the image 2 gb using domething like "dd > if=/dev/zero of/raw/disk bs=1M count=2048" cound could be 2000 also > then it should work everywhere. On the Raspberry Pi Fedora Remix I'm shrinking the image as much as possible by shortening the last (root) partition. The partition is resized to fill the SD card on first boot (fdisk, reboot, resize2fs). This results in a small image size, minimizes unnecessary writes to the SD card, works on any card size, and lets you take full advantage of the space on the card. Perhaps we should adopt that approach for the images? -Chris ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F17 snapshot images
On 03/31/2012 08:10 AM, Chris Tyler wrote: On the Raspberry Pi Fedora Remix I'm shrinking the image as much as possible by shortening the last (root) partition. The partition is resized to fill the SD card on first boot (fdisk, reboot, resize2fs). This results in a small image size, minimizes unnecessary writes to the SD card, works on any card size, and lets you take full advantage of the space on the card. Perhaps we should adopt that approach for the images? Would be happy to add this- with that sort of functionality I'd have no reservation about creating a 1.990GB image. Send me a pointer to how you're doing this during the first boot and I'll integrate it into the rootfs image generator. -- Brendan Conoboy / Red Hat, Inc. / b...@redhat.com ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
