© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I'll try to complete Patrick's answer here:
1°)
root@localhost:~# snap list
Name Version Rev Developer
canonical-pi2 3.2 6 canonical
canonical-pi2-linux 4.4.0-1011-
ubuntu-core 16.04+20160518.
<REBOOT>
ubuntu@localhost:~$ ls -lR /dev/ptmx /dev/pts
crw-rw-rw- 1 root tty 5, 2 May 24 09:12 /dev/ptmx
/dev/pts:
total 0
c--------- 1 root root 5, 2 Jan 1 1970 ptmx
2°)
root@localhost:~# snap install hello-world
Name Version Rev Developer
hello-world 6.0 25 canonical
root@localhost:~# hello-world.echo foo
unable to mount '/dev/pts/
root@localhost:~# ls -lR /dev/ptmx /dev/pts
crw-rw-rw- 1 root tty 5, 2 Feb 11 16:28 /dev/ptmx
/dev/pts:
total 0
c--------- 1 root root 5, 2 Jan 1 1970 ptmx
3°) I'm using the RPI2 kernel snap as a basis, I unsquashfs'ed it, replaced the kernel to an arm64 Tegra X1 one, replaced the kernel modules and the firmwares.
4°) I'm using the unmodified rpi2 gadget snap
5°) I'm targeting a custom Tegra X1 board (armv8), I'm using arm64 kernel and armhf (32 bits) userspace.
the snap list :
root@localhost:~# snap list
Name Version Rev Developer
canonical-pi2 3.2 6 canonical
canonical-pi2-linux 4.4.0-1011-
hello-world 6.0 25 canonical
ubuntu-core 16.04+20160518.
root@localhost:~# uname -a
Linux localhost.
To further explain how I produced the Snappy image :
I'm not able to generate a Snappy image right now using UDF due to this bug: https:/
So for now, I'm using a bit of a hackish technique to generate an image for my Tegra board.
I am using this script: https:/
This is basically generating an RPI2 image and then modifying the kernel snap to contain the correct kernel+
And same thing with the initramfs.