On 2015-06-18 04:51 AM, [email protected] wrote: > Send snappy-devel mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ubuntu.com/mailman/listinfo/snappy-devel > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of snappy-devel digest..." > > > Today's Topics: > > 1. Re: Usb compact Wifi - BBB (G?bor Paller) > 2. Re: Usb compact Wifi - BBB (Oliver Grawert) > 3. Re: RFC: Snappy shell (Mark Shuttleworth) > 4. Re: RFC: Snappy shell (Mark Shuttleworth) > 5. Re: RFC: Snappy shell (Nathan Haines) > 6. Re: RFC: Snappy shell (Mark Shuttleworth) > 7. Re: RFC: Snappy shell (Oliver Grawert) > 8. Re: Snappy RPi2 stable image #3 now available > (Ricardo Salveti de Araujo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 18 Jun 2015 08:23:05 +0200 > From: G?bor Paller <[email protected]> > To: Joseph Liau <[email protected]> > Cc: Snappy Devel <[email protected]> > Subject: Re: Usb compact Wifi - BBB > Message-ID: > <camif05jt3ez_yj3ceknfzzxxmnu4odudxfx2abgl3m1hhc9...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > The last time I checked (2 months ago) the WiFi subsystem was not > preinstalled on Snappy. > This tutorial worked for me: > http://www.marinus.nu/2015/02/enabling-wifi-on-snappy-ubuntu-core.html Thanks. I have tried this tutorial before. I was able to get a different dongle to be recognized and get an ip address, but it also did not actually connect to the network. No ssh access or ping-ability.
- Should also note as Oli said below: wpasupplicant comes with the image. If you follow the tutorial, it will replace that with an older version. However, it still does not aid with drivers/installation of the compact wifi dongle. > > > On Thu, Jun 18, 2015 at 2:55 AM, Joseph Liau <[email protected]> wrote: > >> Hello, >> >> I am trying to get wifi working on the beaglebone black with a compact >> usb wifi dongle. The dongle is the same as described in this tutorial: >> >> https://docs.google.com/document/d/1-CIGQYdk8ZhU3D3UCNn70jc7C9HdXvEZAsiNW71fGIE/edit?pli=1 >> >> I have followed the "quick installation" but the adapter is not showing >> up in the ifconfig. >> >> Thanks >> Joe >> >> >> >> >> -- >> snappy-devel mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/snappy-devel >> >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <https://lists.ubuntu.com/archives/snappy-devel/attachments/20150618/974ec429/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Thu, 18 Jun 2015 10:45:42 +0200 > From: Oliver Grawert <[email protected]> > To: [email protected] > Subject: Re: Usb compact Wifi - BBB > Message-ID: <1434617142.21572.10.camel@anubis> > Content-Type: text/plain; charset="UTF-8" > > hi, > Am Donnerstag, den 18.06.2015, 08:23 +0200 schrieb G?bor Paller: >> The last time I checked (2 months ago) the WiFi subsystem was not >> preinstalled on Snappy. > it was added the last stable image (15.04.1) > > ciao > oli Yes, I have noticed the wpasupplicant package in the image. Is that all that's required? > > > > > > > ------------------------------ > > Message: 3 > Date: Thu, 18 Jun 2015 11:06:10 +0100 > From: Mark Shuttleworth <[email protected]> > To: Jamie Strandboge <[email protected]>, > [email protected] > Subject: Re: RFC: Snappy shell > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > > I think this experience can be achieved with OpenSSH, there is no hard > requirement to link SSH into snappy to enable this. > > On 15/06/15 17:15, Jamie Strandboge wrote: >> Seems like we set up the snappy user's shell to this and have >> snappy-cli as an available option in /etc/shells so that in the future >> new users can use this shell? > Imagine that every snap can provide a terminal shell command. The > mythical "comfy" framework snap could thus provide a traditional shell, > other snaps can provide CLI environments suitable for them. So if I > install an ICOS snap, I can say something like: > > > % shell icos > > ...and find myself at the ICOS command prompt. > > Mark > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 181 bytes > Desc: OpenPGP digital signature > URL: > <https://lists.ubuntu.com/archives/snappy-devel/attachments/20150618/f464f9ac/attachment-0001.pgp> > > ------------------------------ > > Message: 4 > Date: Thu, 18 Jun 2015 11:17:25 +0100 > From: Mark Shuttleworth <[email protected]> > To: Lo?c Minier <[email protected]>, Gustavo Niemeyer > <[email protected]> > Cc: Snappy Devel <[email protected]> > Subject: Re: RFC: Snappy shell > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > On 16/06/15 09:44, Lo?c Minier wrote: >> First, consider that the networking industry is proposing this today: in >> all products, for all major brands, you end up in a custom CLI experience. >> I certainly agree it's painful to learn a new one each time, much like it's >> a pain to learn how to use/configure a new piece of software of any kind. >> But at least we get to define this one and offer it as a base for others to >> derive from. Perhaps frameworks/snaps could extent the command set with >> additional commands, e.g. to manage the ASIC, or provide hardware >> diagnostics etc. >> >> I'm not convinced that this shell approach is inherently good or bad for >> these network vendors, but it's a fact that they all do this, and snappy >> shell gives a path towards this kind of user experience. > If we think that the functionality of all those firmwares transition to > their snaps in an Ubuntu Core world, then it's very useful to have a way > for those snaps to say "here's how you get my CLI" in a standard way, > and to have a standard way to jump from the snappy shall to the shell of > a particular snap. > > If we think that the "snap for human usage of a snappy system" is comfy, > then the equivalent of "give me a bash shell" is the comfy shell. > > For example: > > snappy % list > comfy > network-os > > snappy % shell comfy > > bash $ ls -a > . .. .bashrc > bash $ exit > > snappy % > >> Snappy shell needs not be required for all snappy based images and/or needs >> not be on port 22, it is rather an optional interface to snappy, much like >> webdm is an useful tool and default web user experience. > Here I disagree; if it's worth doing, it's worth doing universally. > > Personally, I think: > > * it's worth doing by default on all snappy systems > * the jump to a "normal Linux shell" needs to be crisp and obvious and easy > * interaction with SSH needs to be straightforward and well thought through > for cloud and device instances of snappy > > Mark > > > > > > ------------------------------ > > Message: 5 > Date: Thu, 18 Jun 2015 03:19:51 -0700 > From: Nathan Haines <[email protected]> > To: [email protected] > Subject: Re: RFC: Snappy shell > Message-ID: <[email protected]> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On 06/18/2015 03:06 AM, Mark Shuttleworth wrote: >> Imagine that every snap can provide a terminal shell command. The >> mythical "comfy" framework snap could thus provide a traditional shell, >> other snaps can provide CLI environments suitable for them. So if I >> install an ICOS snap, I can say something like: > I was pondering much the same basic idea. I'd sort of like a bash shell > by default, but it does seem like a per-snap CLI would be really nifty. > > That way I get my comfy Linux shell that I've been using for two > decades, but an Ubuntu Core router could have an IOS style shell, or a > home automation unit could have some really easy to use shell for > turning on the kitchen lights or displaying the interior temperature. > All the better if it's the default experience but optional. > > And that's one of the really compelling strengths of having modular > snaps that fit into Ubuntu Core after all: task and application > independence. >
signature.asc
Description: OpenPGP digital signature
-- snappy-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snappy-devel
