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

Re: [atomic-devel] "Hello World" - seems to be successful



OK, moving right along - seems to work fine.

[user1 pce02 ~]$ which -a postfix
/usr/bin/which: no postfix in (/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbi)

[user1 pce02 ~]$ rpm-ostree install postfix
==== AUTHENTICATING FOR org.projectatomic.rpmostree1.install-uninstall-packages=
Authentication is required to install and remove software
Authenticating as: Bob Gustafson (user1)
Password:
==== AUTHENTICATION COMPLETE ====
Checking out tree 89bfa70... done
Enabled rpm-md repositories: fedora updates
Updating metadata for 'fedora': [=============] 100%
rpm-md repo 'fedora'; generated: 2018-10-24T22:20:15Z
Updating metadata for 'updates': [=============] 100%
rpm-md repo 'updates'; generated: 2018-11-19T02:11:42Z
Importing metadata [=============] 100%
Resolving dependencies... done
Will download: 1 package (1.4 MB)
  Downloading from fedora: [=============] 100%
Importing (1/1) [=============] 100%
Checking out packages (1/1) [=============] 100%
Running pre scripts... [ 2376.346930] fuse init (API version 7.27)
1 done
Running post scripts... 8 done
Writing rpmdb... done
Writing OSTree commit... done
Staging deployment... done
Freed: 422.4 MB (pkgcache branches: 0)
Added:
postfix-2:3.3.1-5.fc29.x86_64
Run "systemctl reboot" to start a reboot
[user1 pce02 ~]$

I will try to install a few more packages before doing a reboot.

Thanks much - Bob G

On 11/19/18 3:19 PM, Bob Gustafson wrote:
OK, I was able to rebase to AH 29 using the following instructions:

# ostree remote gpg-import fedora-atomic -k /etc/pki/rpm-gpg/PM-GPG-KEY-fedora-29-x86_64
Imported 1 GPG key to remote "fedora-atomic"

# rpm-ostree rebase -b fedora/29/x86_64/atomic-host

# systemctl reboot

I was logged in from a different machine when I did the steps above and the reboot disconnected me.

I tried to ssh back in, but system seemed dead.

Needed to power cycle and boot using serial port..

Result is:

Fedora 29.20181113.0 (Atomic Host)
Kernel 4.18.17-300.fc29.x86_64 on an x86_64 (ttyS0)

pce02 login: user1
Password:
Last login: Mon Nov 19 13:21:58 from 192.168.50.60
[user1 pce02 ~]$
[user1 pce02 ~]$
[user1 pce02 ~]$ uname -a
Linux pce02.chidig.com 4.18.17-300.fc29.x86_64 #1 SMP Mon Nov 5 17:56:16 UTC 20x
[user1 pce02 ~]$

Now will try to add some 'packages'

Have fun - Bob G

On 11/19/18 11:13 AM, Bob Gustafson wrote:
I am using "atomic host upgrade" as my 'Hello World' test. It seems to be successful

The starting point was: Fedora-AtomicHost-ostree-x86_64-28-20180902.0.iso installed using a USB flash drive. (uncertainty - it might have been an earlier image on the flash drive).

The target system is a pcengines.ch APU4b4 with 4G ram, 4xGigEth, 4 core AMD Embedded G series GX-412TC, 60 GB SSD.

At idle it is using about 4 watts including power adapter inefficiencies (viewed on Kill A Watt meter). No fan needed.

It does not have video, so some screwing around necessary at initial boot to insert console=ttyS0,115200n8

After the original system was running:

Commands given:

atomic host upgrade

...

systemctl reboot

.....

Fedora 28.20181007.0 (Atomic Host)
Kernel 4.18.11-200.fc28.x86_64 on an x86_64 (ttyS0)

pce02 login: root
Password:
Last login: Sat May 12 11:40:40 on pts/1
[root pce02 ~]# date
Mon Nov 19 06:27:37 CST 2018
[root pce02 ~]# uname -a
Linux pce02.chidig.com 4.18.11-200.fc28.x86_64 #1 SMP Sun Sep 30 15:31:40 UTC 2x
[root pce02 ~]#


The date of the Last login may have been the build date of the board or coreboot bios. I was having some network config problems on my host Fedora 29 before the successful atomic host upgrade.

It seems that the version is 28. I'm not sure why it did not upgrade to 29.

Thanks for all the work getting Atomic to this point.

I wonder about its future under IBM..




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