I run Fedora 12 on a IGEPv2.
If I set fstab correctly, whenever I power-cycle the board, fsck complains:
Checking all file systems.
[/sbin/fsck.ext2 (1) -- /] fsck.ext2 -a /dev/mmcblk0p2
/dev/mmcblk0p2: Superblock last mount time (Thu Mar 11 18:17:21 2010,
now = Sat Jan 1 01:00:04 2000) is in the future.
/dev/mmcblk0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
this is fixed in newest e2fsprog:
- Add new e2fsck.conf configuration option, default/broken_system_clock to
support systems with broken CMOS hardware clocks.
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
what do you think about creating a kernel-rpm for fedora-arm, I think
should be useful to have a kernel for my sheevaplug with nfs, ipv6,
and other interestings things.
Itamar Reis Peixoto
e-mail/msn/google talk/sip: itamar(a)ispbrasil.com.br
+55 11 4063 5033
+55 34 3221 8599
I'm a new member. I am working on a program that intends to use a rugged PDA and it has to use SELinux. All the PDAs that I have found use an X-scale processor; the Marvell PXA270 seems to be the one most commonly used. I have a few questions that maybe someone can answer or point me in the right direction:
Can Fedora run on an X-scale processor with SELinux enabled? Are there special patches required? Do you know of a software house that has experience porting Fedora or RHEL to PDA type devices? (We need to do this fairly quickly -within 5 months or so - and I think our software engineers would take too long to do this successfully.) Thanks for any information.
I've been running Fedora ARM for a short while, and am really impressed
by the work that's been done. It seems that this will become even more
important as new ARM-based devices -- tablets, home automation,
netbooks, XO 1.75 -- hit the market.
I'd like to help with this initiative. I'm at Seneca College, and we're
willing to host ARM builders and a Koji instance, with a goal of
tracking kernels, packages, and updates as close to the primary archs as
possible. I've got a small group working on this infrastructure, and we
should have it fully up and running in March (next week is our study
I have a couple of questions:
(1) What's a good representative sample of systems to test on, in
addition to a SheevaPlug, OpenRD, BeagleBoard, and HawkBoard?
(2) Since most ARM systems are initially booted with a prebuilt rootFS,
Anaconda has little value. However, it seems that building the rootFS
for ARM is not really any different from building a Live CD for
i386/x86_64 except for the final output format (obviously, this would
have to be done on an ARM system or in emulation so package scriptlets
could run). I'm wondering if we can adapt the livecdcreator to have
selectable output for various ARM devices, building images for SD cards
(and so forth, as appropriate to each target device) that have the root
FS plus the kernel with the right naming/file sequencing in the image.
This would make it easier to build a rootFS with a particular package
set. Any feedback on this idea?
-Chris (ctyler on freenode)