Re: F17 snapshot images

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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.

arm mailing list

[Index of Archives]     [Linux ARM (Vger)]     [Linux ARM]     [ARM Kernel]     [Fedora User Discussion]     [Older Fedora Users Discussion]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

Powered by Linux