Hi all,
OK, thanks to all the tips and tricks from yesterday in my previous thread, I got F20 Beta-5 up and running on a microSD on the BBB, completely headless, with only a network cable. Some comments:
- All the boot troubles were probably related to my attempts to push the boot button and expecting LEDs to turn on, not waiting long enough, etc. I see the instructions are adapted in the meantime.
- The lines in the FAQ about deleting systemd service links can be removed, as they do not apply anymore for the F20 Beta-5 image and are confusing.
- Just as a side note: I did not do the last 3 commands in the FAQ, but editted /etc/shadow on the image and copied an encrypted password that I know into the root entry. This might be easier for others too.
- After booting, I resized mmcblk0p3 with fdisk, rebooted, and used resize2fs to resize the fs.
Now one remaining question: is there a repository I can use for adding packages now or should I wait till F20 final is released? I want to do some experiments for applications I have in mind, for which I need to add several packages (and their dependencies.
Thanks again for all help. I'll contnue experimenting with it.
-- -- Jos Vos jos@xos.nl -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204
On Fri, Nov 29, 2013 at 2:04 PM, Jos Vos jos@xos.nl wrote:
Hi all,
OK, thanks to all the tips and tricks from yesterday in my previous thread, I got F20 Beta-5 up and running on a microSD on the BBB, completely headless, with only a network cable. Some comments:
All the boot troubles were probably related to my attempts to push the boot button and expecting LEDs to turn on, not waiting long enough, etc. I see the instructions are adapted in the meantime.
The lines in the FAQ about deleting systemd service links can be removed, as they do not apply anymore for the F20 Beta-5 image and are confusing.
Just as a side note: I did not do the last 3 commands in the FAQ, but editted /etc/shadow on the image and copied an encrypted password that I know into the root entry. This might be easier for others too.
After booting, I resized mmcblk0p3 with fdisk, rebooted, and used resize2fs to resize the fs.
Now one remaining question: is there a repository I can use for adding packages now or should I wait till F20 final is released? I want to do some experiments for applications I have in mind, for which I need to add several packages (and their dependencies.
The standard Fedora yum repo and package set is available by default. Check the date is correct before you run yum.
Peter
On Fri, Nov 29, 2013 at 02:43:18PM +0000, Peter Robinson wrote:
The standard Fedora yum repo and package set is available by default. Check the date is correct before you run yum.
Hmm.. ok, thanks, yum works now. I didn't immediately relate the error I got with yum to a date issue, but that was indeed the problem.
But "yum update" does not seem to be a good idea. First, I get tons of messages like:
/sbin/ldconfig: libraries libgcc_s-4.8.1-20130814.so.1 and libgcc_s-4.8.2-20131017.so.1 in directory /lib have same soname but different type. /sbin/ldconfig: libraries libkmod.so.2.2.4 and libkmod.so.2.2.5 in directory /lib have same soname but different type.
Then, in the cleanup fase, the system crashes, just after:
Cleanup : initial-setup-0.3.7-1.fc20.noarch 196/354
And the rpm stuff is a mess now, so I think I'll reflash the image.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El Fri, 29 Nov 2013 16:38:54 +0100 Jos Vos jos@xos.nl escribió:
On Fri, Nov 29, 2013 at 02:43:18PM +0000, Peter Robinson wrote:
The standard Fedora yum repo and package set is available by default. Check the date is correct before you run yum.
Hmm.. ok, thanks, yum works now. I didn't immediately relate the error I got with yum to a date issue, but that was indeed the problem.
But "yum update" does not seem to be a good idea. First, I get tons of messages like:
/sbin/ldconfig: libraries libgcc_s-4.8.1-20130814.so.1 and libgcc_s-4.8.2-20131017.so.1 in directory /lib have same soname but different type. /sbin/ldconfig: libraries libkmod.so.2.2.4 and libkmod.so.2.2.5 in directory /lib have same soname but different type.
This is expected, its a side effect of an old bug, and is just noise.
Then, in the cleanup fase, the system crashes, just after:
Cleanup : initial-setup-0.3.7-1.fc20.noarch 196/354
And the rpm stuff is a mess now, so I think I'll reflash the image.
odd, you can run "package-cleanup --cleandupes"
Dennis
-
Dennis Gilmore -
Jos Vos -
Peter Robinson