Ubuntu Core 16 Final!
xiaoguo.liu at canonical.com
Fri Nov 4 08:06:40 UTC 2016
Thanks. I have found the root cause of it. I need to replace USER with my
own account "liu-xiao-guo". I think USER is different from my account name
in the Ubuntu One.
On Fri, Nov 4, 2016 at 3:10 PM, XiaoGuo Liu <xiaoguo.liu at canonical.com>
> Hi Michael,
> First, thanks for your detailed instructions. I just followed your steps
> to install the QEMU to test the Ubuntu Core. However, I have to problems in
> logging into the Ubuntu Core. The captured screen is like
> http://imgur.com/a/Qyfc9. May I know what the correct password for
> logging into the Ubuntu core. Is it the one for Ubuntu One? or the one for
> the ssh?
> Thanks & best regards,
> On Thu, Nov 3, 2016 at 11:47 PM, Michael Vogt <michael.vogt at canonical.com>
>> The Snappy team is happy to announce the release of Ubuntu Core 16.
>> Ubuntu Core is an operating system entirely based on snaps, including
>> its foundation. Applications, kernel, core operating system, and
>> gadget components are all managed as snaps and are installed and
>> refreshed by snapd, the daemon and tooling responsible for making it
>> all dance.
>> The images are available currently for PC (amd64, i386) and
>> for Pi2/Pi3 and Dragonboard. These images can be downloaded from:
>> Once unpacked, the images are bootable, the PC image can be booted
>> directly in qemu-kvm, virtualbox or on real hardware. When running the
>> images in qemu-kvm it is helpful to use the "-redir" feature of
>> qemu-kvm. e.g.:
>> $ kvm -smp 2 -m 1500 -redir tcp:10022::22 ubuntu-core-16-amd64.img
>> The message from console-conf is a bit misleading in this setup. It
>> will say "ssh USER at 10.0.2.15". However due to the way that the
>> qemu-kvm user networking behaves, you will actually have to run the
>> following to ssh into the images:
>> $ ssh -p 10022 USER at localhost
>> or if you have the following snippet in ~/.ssh/config
>> Host kvm.snappy
>> Hostname localhost
>> Port 10022
>> User USER
>> UserKnownHostsFile /dev/null
>> StrictHostKeyChecking no
>> then you can just
>> $ ssh kvm.snappy
>> into it.
>> The Pi2/Pi3/Dragonboard image can be written to a sdcard via dd. An
>> alternative way to write the image is to use "go-dd", e.g. on Ubuntu
>> $ sudo snap install --devmode --beta godd
>> $ sudo /snap/bin/godd ubuntu-core-16-pi2.img.xz
>> [this will print a message showing what devices are removable]
>> $ xzcat ubuntu-core-16-pi2-rc2.img.xz | sudo /snap/bin/godd -
>> After booting the image you can enter your Ubuntu One email and it
>> will automatically create a matching user with the right ssh keys. If
>> you do not have an Ubuntu SSO account yet please create one at:
>> (don't forget to add your public ssh keys to that account).
>> Known issues:
>> - pi3 wlan can not be initially configured, wired network needs to be
>> used for the initial setup (you can re-run "sudo console-conf" at
>> any later point to re-configure the device for wlan only
>> Bug references for the pi3 known issues:
>> - http://pad.lv/1637153
>> plugging in network cable during configuration can cause a traceback
>> on pi3
>> - http://pav.lv/1624322
>> no wlan0 device at all on first boot on pi3
>> - http://pad.lv/1632387
>> wifi setup times out on pi3 devices on first boot
>> These images follow the "stable" channel. If you find any issues,
>> please let us know via:
>> Ubuntu Core 16 follows a rolling release model, security updates and
>> bug fixes will come to you via regular over the air updates for the
>> lifetime of the release.
>> Enjoy this release!
>> Michael Vogt (on behalf of the Snappy team)
>> Devices mailing list
>> Devices at lists.snapcraft.io
>> Modify settings or unsubscribe at: https://lists.snapcraft.io/mai
> XiaoGuo, Liu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Snapcraft