From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6491607282099421184 X-Received: by 10.223.170.141 with SMTP id h13mr2320050wrc.19.1511445101842; Thu, 23 Nov 2017 05:51:41 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.223.185.105 with SMTP id b38ls1704018wrg.1.gmail; Thu, 23 Nov 2017 05:51:41 -0800 (PST) X-Google-Smtp-Source: AGs4zMaMN4iGEvUi02OKq3Z6lkU6m2qs9f072OaD78ScJubyNNL0wLqAlkg/14TufJRWs8ER7cqW X-Received: by 10.28.178.68 with SMTP id b65mr806456wmf.17.1511445101427; Thu, 23 Nov 2017 05:51:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1511445101; cv=none; d=google.com; s=arc-20160816; b=aPoXPDEYo1dWPY4QXEp8uGG/WsQGk7SpU3HbY3JduGaQRZZK+iRWpw6c0pzGjQ81jz ok5lZO/X3OOMjn4XAhyqw55R+qq921v55qDLHl7OKL5eW6L5KhS9pYlyVGp5gczAU7Uk pMIVs+wPMJnT6+f+o1Q7coThGGzJyJQzde/zjUIjG4r8cOsq7JNq3CEuZGVFdw4zbO1r dJipsMCfn+DYT8CqN5do+saDjcx4HXDOOtei7fu72hDqB+2y3DhOALLB65DFqWBdjF/H JW4IUAOhjdG4n+a5i+J922cGpGz6HinCCy0U09NEFWeG4VT51eUaDRFVQsv/Li/S+Bv8 mzjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=to:subject:message-id:date:from:mime-version:dkim-signature :arc-authentication-results; bh=J01hfDUNk16SrnOIGUMbNCRszkPMRlfPAiHL+yxcFMA=; b=X+fCpnf5yNVeYHsUX3u2M+kZuIDPUupwimDoCyJcxEgB+pveRnZpM2qfhVVN1w76vb vW029BQi8r+ifspKlFFJolhYS8n8xdHcGVn5Z4G0H8mPLgDZeSWnuGxDGyHvQvXqe02R nDLj6ptp5IPNq6Gf4pQBrOJcrmSoxVgV6Dh406s1+oPvNbc5QUXukY+tVuEDIeImrlQu Ei7NTc5CuhdNAay++hCtSREToI/6kHSrXUZAsU2BgmTGZQxeanUiNgX8g8rOPKwxA+aS kgV7SEkjEKOQT7xtZIOVEKJQvTNfM1RYH9heiSX9LraLSCmZVsbHEg1hoJ2JWxwk2R3g GIoA== ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=qKGAna3b; spf=pass (google.com: domain of wm.a.mills@gmail.com designates 2a00:1450:400c:c0c::22b as permitted sender) smtp.mailfrom=wm.a.mills@gmail.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com. [2a00:1450:400c:c0c::22b]) by gmr-mx.google.com with ESMTPS id c51si1209319wrc.1.2017.11.23.05.51.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Nov 2017 05:51:41 -0800 (PST) Received-SPF: pass (google.com: domain of wm.a.mills@gmail.com designates 2a00:1450:400c:c0c::22b as permitted sender) client-ip=2a00:1450:400c:c0c::22b; Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=qKGAna3b; spf=pass (google.com: domain of wm.a.mills@gmail.com designates 2a00:1450:400c:c0c::22b as permitted sender) smtp.mailfrom=wm.a.mills@gmail.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: by mail-wr0-x22b.google.com with SMTP id k61so17678295wrc.4 for ; Thu, 23 Nov 2017 05:51:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=J01hfDUNk16SrnOIGUMbNCRszkPMRlfPAiHL+yxcFMA=; b=qKGAna3b59w1WzyHtuBgkHKAuz6TWnEjeAOVFkqVrhQM+HR37foRHbaBWOwBStMnw2 NAXoV7M0UZSiYnBbNSzY99Z0VMJR5RuxMjMAznPQDcl4fi/YP0kxQTysWY4b+eJmvz3x RQ5uVMKMiiOyiM8JRx8HdwJpDtJMMGj/X6GRy5DZqoyBTw140Ui5xd9MRL+bz4yLLDyb h7io6rGDfj9430/LYYAcwDokuNgEhT/cm6rtGisKu9RojjMJi0WjoVDoOhxEKD+IulSF fpRqYsFknC4d4BjtcLB3uuVNCEMcBMjQ6uPOYkdSBdAW+tHb6+tbLzFkCw2oOSSngnqf aPyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=J01hfDUNk16SrnOIGUMbNCRszkPMRlfPAiHL+yxcFMA=; b=fOJtC+EG/bC+9kvGJWao36BzAXd98UhfjC55PqrPvwltmv9audYyVDPZJUxM2sDD9N bFCQXEhknz6eaXc+WjMetsrR9suZ116p4AFCVJE4HGVdVAyhHIy0v0l2cf4JQitXs+3T iMCbGd6pIbdmUnJ77El2kraC/FCBXsdAP6HezYz5tkBpfV0qIArAtLOU+8sXbKze4qop MAAgm7U9SeCGnhhh+Hak4bdvmNtkhHxOEE2XNl6v0xJ2g5ls/dj0AcuVVo8hx+y4bR8u 62JmayotSC74tJ0gK1VRk9vUW7LuBUHSaXhItv387KYmgK+8M2denETwcESoRz6Z1ITL Yb+A== X-Gm-Message-State: AJaThX42BJ6DZedPEMswvfAAN9iOtsA98US7oGjRp5XQcdyl6PBlSepz WV3P9GPXvWRgySD0072StZ2Abe59S/di75MpnPZ7Uw== X-Received: by 10.223.171.6 with SMTP id q6mr15245760wrc.76.1511445100768; Thu, 23 Nov 2017 05:51:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.129.200 with HTTP; Thu, 23 Nov 2017 05:51:40 -0800 (PST) From: "William A. Mills" Date: Thu, 23 Nov 2017 08:51:40 -0500 Message-ID: Subject: New user feedback To: isar-users@googlegroups.com Content-Type: multipart/alternative; boundary="94eb2c1cb82c543348055ea6bc20" X-TUID: JXYRYXndZNXI --94eb2c1cb82c543348055ea6bc20 Content-Type: text/plain; charset="UTF-8" Hi, I am Bill Mills from TI. I can't use my @ti.com e-mail address on this forum or github project so I will be using this gmail one at least for now. Getting hands on with ISAR has been on my TODO list since DebConf in Montreal. I finally got around to this last Wednesday (11/15). I have been using OE since 2008 and Yocto Project since its inception. I am a log time Ubuntu user so I consider myself a decently knowledgeable power user for Debian style distros. The above is to give you some context. It is also to show that I have more experience than many of your potential users. The good news: In a fresh Debian Jessie VM I had no problem following your directions and getting builds for QEMU armhf, i386, and amd64. A good number of the problem I found and worked around were fixed in the push to master on Nov 17: rerepro & python package dependences, misplaced proc mount, clean up of dev and proc mounts on failure, The improvements I think you could make for new users: 1) The user documentation should say what host distros are supported. It is clear from the user doc that it was written for Debian jessie but it does not say that explicitly. It also does not say if others could work. I think you should state which distros you are testing on and warn users away from any others. Of course centos, opensuse etc will not work and you should be clear about this. Which distros _should_ be test? IMHO it should be: Debian: stable, oldstable Ubuntu: LTS, LTS-1 If that is not possible then documenting the one that does work is even more important. Ubuntu 16.04 does not work, I tried, I even used the multistrap from jessie-backports and it still fails with the same error: W: Failed to fetch http://ftp.debian.org/debian/dists/jessie/main/binary-armhf/Packages 404 Not Found [IP: 130.89.148.12 80] 2) The user documentation should guide the user to setup a new VM (or container) to do the work in. I think you should guide new users to do the work in a clean VM and say that containers don't work. For users that don't have a preferred way to setup a VM you should pick one and guide them. Since you run parts as root and require passwordless sudo, the user should really be doing this work with a safety net even if they are running on a supported host distro. If your day job is ISAR then perhaps you are running native but this won't be the case for most people trying this out. I first thought I would try a container. I tried docker a bit and failed. (I am not an experienced docker user). I next tried lxd which I have used a decent bit. Even with a privileged container I could not get ISAR to run. It would fail when trying to mount /dev into the buildroot. I did see discussion of docker debian/jessie-slim etc in one of the github issues. Is someone running ISAR in docker? If so I would like to know how to make this work. After failing containers I tried a fresh VM. I tried it two ways and both worked. While travelling last weekend I used Virtualbox on Windows to run the Debian Jessie netinstall CD. When I got back home I used vagrant with libvirt provider on Ubuntu. (Vagrant w/ Virtualbox on Windows and Linux should work also but I did not try these). Of course spinning up a machine in a cloud provider should work as well but I did not try. 3) Provide extra host configuration guidance I know how to enable jessie-backports but I am not sure everyone will. Some methods of getting a clean VM leaves the locales unconfigured which causes a problem with bitbake. I use: sudo dpkg-reconfigure locales and then pick en_US.UTF-8 UTF8 from the text menu. I think there are better ways also. 4) Provide a build dir delete script or task Since some of the files in the build dir are owned by root, the normal user can't delete them. The user will be tempted to do sudo -rf build but that is very dangerous if there are stray mounts in the tree. I know you have added more cleanup of the dev and proc mounts but I worry that it may not cover every situation. sudo rm -rf /dev is a rather nasty thing to do. I know you are looking to add support for psuedo but that may not be enough and may take some time to get there. I think you should put a ./delete-build-dir scipt into the base of the build dir when you create it. This script could iterate sudo umount commands, run a user level rm -rf and then check that what is left is truly expected before doing sudo rm -rf on it. Of course if the user is in a VM the damage is contained and a reboot of the VM should fix things but this would still be good practice IMHO. ------- Should I create issues for these 4 items? This is my feedback so far. I did read over the recipes, classes and main scripts and have a decent understanding of the basics. Thanks for your attention. Bill --94eb2c1cb82c543348055ea6bc20 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I am Bill Mills from TI.=C2=A0 I can't use my @ti.com e-mail address on this forum or github project so I will b= e using this gmail one at least for now.

Getting hands on with= ISAR has been on my TODO list since DebConf in Montreal.=C2=A0 I finally g= ot around to this last Wednesday (11/15).

I have been using OE= since 2008 and Yocto Project since its inception.=C2=A0 I am a log time Ub= untu user so I consider myself a decently knowledgeable power user for Debi= an style distros.

The above is to give you some context.=C2=A0= It is also to show that I have more experience than many of your potential= users.

The good news:

In a fresh Debian Jessie V= M I had no problem following your directions and getting builds for QEMU ar= mhf, i386, and amd64.

A good number of the problem= I found and worked around were fixed in the push to master on Nov 17:=C2= =A0 rerepro & python package dependences, misplaced proc mount, clean u= p of dev and proc mounts on failure,

The improveme= nts I think you could make for new users:

1) The user document= ation should say what host distros are supported.

= It is clear from the user doc that it was written for Debian jessie but it = does not say that explicitly.=C2=A0 It also does not say if others could wo= rk.

I think you should state which distros you are= testing on and warn users away from any others.
Of course centos= , opensuse etc will not work and you should be clear about this.
=
Which distros _should_ be test?=C2=A0 IMHO it should be:
Debian: stable, oldstable
Ubuntu: LTS, LTS-1
If that is not possible then documenting the one that does work= is even more important.

<TLDR>
Ubuntu 16.04 does not work, I tried,=C2=A0 I even used the multistrap fro= m jessie-backports and it still fails with the same error:
W= : Failed to fetch http://ftp.debian.org/debian/dists/jessie/main/bina= ry-armhf/Packages=C2=A0 404=C2=A0 Not Found [IP: 130.89.148.12 80]
</TLDR>

2) The user documentation shoul= d guide the user to setup a new VM (or container) to do the work in.

I think you should= guide new users to do the work in a clean VM and say that containers don't work.=C2=A0 For users that don't have a = preferred=20 way to setup a VM you should pick one and guide them.

<= div><TLDR>
Since you run parts as root and require passwordl= ess sudo, the user should really be doing this work with a safety net even = if they are running on a supported host distro.

If= your day job is ISAR then perhaps you are running native but this won'= t be the case for most people trying this out.

I first th= ought I would try a container.

I tried docker a bi= t and failed.=C2=A0 (I am not an experienced docker user).=C2=A0
=

I next tried lxd which I have used a decent bit.=C2=A0 = Even with a privileged container I could not get ISAR to run.=C2=A0 It woul= d fail when trying to mount /dev into the buildroot.

I did see discussion of docker debian/jessie-slim etc in one of the gith= ub issues.=C2=A0 Is someone running ISAR in docker?=C2=A0 If so I would lik= e to know how to make this work.

After failing con= tainers I tried a fresh VM.=C2=A0 I tried it two ways and both worked.

While travelling last weekend I used Virtualbox on Win= dows to run the Debian Jessie netinstall CD.=C2=A0 When I got back home I u= sed vagrant with libvirt provider on Ubuntu. (Vagrant w/ Virtualbox on Wind= ows and Linux should work also but I did not try these).=C2=A0 Of course sp= inning up a machine in a cloud provider should work as well but I did not t= ry.
</TLDR>

3) Provide extra h= ost configuration guidance

I know how to enable je= ssie-backports but I am not sure everyone will.

So= me methods of getting a clean VM leaves the locales unconfigured which caus= es a problem with bitbake.=C2=A0 I use:
sudo dpkg-reconfigure loc= ales

and then pick en_US.UTF-8 UTF8 from the text = menu.
I think there are better ways also.

4) Provide a build dir delete script or task

Since some of the files in the build dir are owned by root, the normal use= r can't delete them.=C2=A0 The user will be tempted to do sudo -rf buil= d but that is very dangerous if there are stray mounts in the tree.

I know you have added more cleanup of the dev and proc mo= unts but I worry that it may not cover every situation.=C2=A0 sudo rm -rf /= dev is a rather nasty thing to do.

I know you are = looking to add support for psuedo but that may not be enough and may take s= ome time to get there.

I think you should put = a ./delete-build-dir scipt into the base of the build dir when you create i= t.
This script could iterate sudo umount commands, run a user lev= el rm -rf and then check that what is left is truly expected before doing s= udo rm -rf on it.

Of course if the user is in= a VM the damage is contained and a reboot of the VM should fix things but = this would still be good practice IMHO.

------= -

Should I create issues for these 4 items?
<= div>
This is my feedback so far.
I did read over th= e recipes, classes and main scripts and have a decent understanding of the = basics.

Thanks for your attention.
Bill<= br>


= --94eb2c1cb82c543348055ea6bc20--