> On Mar 1, 2017, at 23:34 , William Hermans <yyrk...@gmail.com> wrote: > > Back on topic. > > I wonder if it wouldn't be simpler, and easier for everyone if someone where > to just write / create a setup script for both options. It's been a while, so > I do not recall the finer details with each process. But I can say while I do > not know everything, I'm also not a novice Linux user by far. And I was never > able to get remoteproc setup correctly and working. Also, having > documentation of the finer details for remoteproc is a must. Things like what > is a *.hex file, and which options are required, or optional. In addition to > what all these options mean. e.g. definitions are required.
+1 > > Setting up uio_pruss was also no cake walk, But in the end I was able to get > two of the examples working. > > I still think that remoteproc in concept a pretty cool feature.I'd like to > see a lot of people using it, and showing off really cool examples of it's > usage. Despite me thinking that remoteproc is better suited for systems with > multi core application processors. e.g. running Linux on one core, and having > the other cores running bare metal. Or some mixture in between that. But in > all honestly, when was the last time you saw something really cool done with > the PRU's ? ~2013, using uio_pruss, to create an all software( in PRU ) VGA > adapter ? That's the last really cool project I remember achieved through the > PRU's anyway . . . > > On Wed, Mar 1, 2017 at 11:52 PM, William Hermans <yyrk...@gmail.com> wrote: > > > On Wed, Mar 1, 2017 at 10:19 PM, Robert Nelson > <robertcnel...@beagleboard.org> wrote: > The above is disabled by default as of 2-3 weeks ago.. > > I'm still kind of on the fence. I can completely understand wanting to just > type ssh root@beaglebone and *bam* be right where I need to be to start > working on a problem. I get it. But at the same time, I sit behind 3 layers > of routers between any local system, and the internet. I also understand the > implications of having root wide open to the world. Free to anyone with a > port scanner to exploit. Assuming I had a hole punched in our routers for > outside access. Still,it's not impossible for someone to "hack" in to our > network, but it would not be very easier either. > > For those who still may not understand. Allowing root access to port 22( ssh > ) with no password is akin to allowing remote assistance access into a > Windows system with no admin password. Which just so happens to be a big > "player" in the reason why Windows is often seen as the most insecure > operating system in the wild. Because by default, and from the factory. > Windows does not setup an admin password, and default to allowing remote > access to anyone with the username, and password. IF the username is known > "admin" and no password . . . At this point, the operating systems software > architecture is irreverent, and is begging any, or all script kiddie with a > port scanner to take over your system. > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/CALHSORowq3jt9Sn3Odp_gZFfhxqW4pCEn5P%3Du%2BEbUXi-csr-Jw%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- Rick Mann rm...@latencyzero.com -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/EB7E6C05-C756-4B7B-8B16-5C69983C9EED%40latencyzero.com. For more options, visit https://groups.google.com/d/optout.
