On 2014-08-07 11:35, Robert Moskowitz wrote:
Well, as of my last post, I am stalled on building Redsleeve for my Cubieboard2. And I really want to do this. At least 4 of my Intel servers can switch to arm now if I can get Redsleeve working. The ROI based on energy savings is 1 year! And the heat savings in my 'data center' would not be anything to sneeze at either. So how to proceed?
See my reply to your other email. The remaining problems you have sound like they are pretty trivial to solve. The console issue exists on most hardware because the serial console ports vary. It is almost certainly as trivial as putting a puttying a this in /etc/init/ttyS0.conf: === start on stopped rc RUNLEVEL=[2345] stop on starting runlevel [016] respawn pre-start exec /sbin/securetty ttyS0 exec /sbin/agetty -L /dev/ttyS0 115200 vt102 === Change ttyS0 to whatever your serial console port is.
I COULD work with the F20 remix for 2 of the boxes for now. I don't like that I can't update the kernel with the remix; a security patch to the kernel would go right by me.
Kernels is an ongoing issue as far as ARM machines go. You wouldn't get kernel updates for your machine via the distro, either, you would likely have to build your own and rebuild your uboot partition each time. If you are not feeling up to this task on an ARM machine, and you want to keep up with kernel patches, you are well and truly out of luck.
And since I can't update the kernel, more and more packages have to be skipped because they need the updated kernel-headers. But this would 'just be' until F21 ships.
At which point you'd be expected to update the entire distro. It is insanity like this that made me build RedSleeve. I didn't find Fedora to be an even remotely usable proposition for any use other than bleeding edge cowboy hacking development.
Much better is to start with Redsleeve now and work on the Centos 7 port. So given that at least the boot setup is different (uboot partition), how to proceed? Please give me some approach for the next test. What do I copy from your /boot directory into the uboot directory, for example?
See above. The problem you have is nothing to do with the uboot partition, a suitable init serial console configuration file should fix your problem. Gordan _______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
