On 08/07/2014 08:19 PM, Robert Moskowitz wrote:

On 08/07/2014 02:52 PM, Gordan Bobic wrote:
On 08/07/2014 06:21 PM, Robert Moskowitz wrote:
So with some care, I have a card booted into Redsleeve, but access only
from the console.

Monitor is showing some startup messages, but no login prompt. Mouse is
active and input works, but nothing seems to be listening.

Network is up, but not sshd:

# service sshd status
sshd: unrecognized service

yum install openssh-server

# yum install openssh-server
rsel6                                                    | 3.8 kB     00:00
rsel6/primary_db                                         | 3.1 MB     00:43
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package openssh-server.armv5tel 0:5.3p1-52.el6.2 will be installed
--> Processing Dependency: openssh = 5.3p1-52.el6.2 for package:
openssh-server-5.3p1-52.el6.2.armv5tel
--> Finished Dependency Resolution
Error: Package: openssh-server-5.3p1-52.el6.2.armv5tel (rsel6)
            Requires: openssh = 5.3p1-52.el6.2
            Installed: openssh-5.3p1-84.1.el6.armv5tel (installed)
                openssh = 5.3p1-84.1.el6
            Available: openssh-5.3p1-52.el6.2.armv5tel (rsel6)
                openssh = 5.3p1-52.el6.2
  You could try using --skip-broken to work around the problem
  You could try running: rpm -Va --nofiles --nodigest

Did I get a wrong tar?  Not the armv7, but armv5?  Oops?

Try:

yum update redsleeve-release
yum update
yum install openssh-server

But not having sshd in minimal?   Strange, but then if I am mismatched
on armv then that might explain it.

The idea of the rootfs is that it is _really minimal_, and you yum install whatever else you need after you get it up and running.

Attached is the firstboot console capture:
[...]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: mount: special device
UUID=2cb94397-dc57-4276-bd81-0f30170f8cc1 does not exist
[FAILED]

Check your fstab and make sure the UUID specified there matches the
one on the relevant file system this is referring to.

ooh, most likely wrong.  Afterall, the fstab is from a F19 build and
this is a 'clean' separate build so of course it will have different UUIDs.

Indeed, it will almost certainly be mismatched.

dumpe2fs on your rootfs should tell you what your rootfs' UUID is, so put that in fstab.

Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users

Reply via email to