It's in relation to using a UUID instead of /dev/sdx. I've never had good luck using UUID's, probably because I do not really know much in way of using them properly.
Also I used the drive object directly when I probably should have targeted the partition instead. On Wed, Feb 17, 2016 at 4:17 PM, William Hermans <[email protected]> wrote: > OK so further checking, the listing in fstab does not seem to work. I'll > have to look into it when I get some free time. > > On Wed, Feb 17, 2016 at 2:42 PM, William Hermans <[email protected]> > wrote: > >> quick worklog, but do note that I used a 4GB USB thumb drive to make >> things easier( so as not to have to format an existing USB hard drive ). >> http://pastebin.com/1zEFAYM3 >> >> Do note that the only thing you need to fstab is: >> >> >> >> *UUID=1808bf31-3313-44e6-b063-2d4d81f02e9e none swap sw,pri=5 0 0* >> But do keep in mind your UUID will be different. >> >> Anyway, I'll probably write up a blog on this to have a link for >> additional queries. But It'll probably at minimum take me a few hours to >> get around to it. >> >> On Tue, Feb 16, 2016 at 5:14 PM, William Hermans <[email protected]> >> wrote: >> >>> *The OP said he has algorithms already written in Python so I was >>>> pointing out that if he need to improve performance, it is easy to do. >>>> Anyway, you know that most build systems like Openembedded, yocto, etc, all >>>> use Python? If it was so slow, they wouldn’t be using it. Now I’m wondering >>>> why they just don’t write the whole thing in C ;-)* >>>> *Regards,* >>>> >>> *John* >>> >>> I kind of like the idea behind interfaces in C for Python . . . I just >>> don't like Python. So John, if you read my posts above you'd know that I >>> know that Python is a requirement for building Linux systems. Python Perl, >>> and C are all required. I said "Ruby" above, but meant Perl. In my mind >>> they're both equivalent( garbage, but useful I guess ), hence my mistake >>> Anyway . . . >>> >>> There are machine learning libraries for C . . . No idea if a specific >>> one out there would fit the bill for the OP though. Not my job to look into >>> all that. >>> >>> >>> On Tue, Feb 16, 2016 at 4:45 PM, John Syne <[email protected]> wrote: >>> >>>> The OP said he has algorithms already written in Python so I was >>>> pointing out that if he need to improve performance, it is easy to do. >>>> Anyway, you know that most build systems like Openembedded, yocto, etc, all >>>> use Python? If it was so slow, they wouldn’t be using it. Now I’m wondering >>>> why they just don’t write the whole thing in C ;-) >>>> >>>> Regards, >>>> John >>>> >>>> >>>> >>>> >>>> On Feb 16, 2016, at 3:21 PM, William Hermans <[email protected]> wrote: >>>> >>>> First, "the interface" is slow: meaning the run time. But if you have >>>> to "reinvent" a Python API / BCL because it is slow - And do that in C. Why >>>> not just use C to begin with ? >>>> >>>> Aside from Python forcing coding guidelines on it users, it's a fine >>>> language. What it is not though, is a good language when you need pure all >>>> out performance. But not all code needs to be fast. Sometimes, fast enough >>>> works. Probably even most of the time. >>>> >>>> On Tue, Feb 16, 2016 at 3:36 PM, John Syne <[email protected]> wrote: >>>> >>>>> The benefit of Python is the easy interface to C code, which means >>>>> that when your algorithm is slow, you can reimplement that code in C but >>>>> keep the benefit of writing in a more feature rich language like Python. >>>>> >>>>> Regards, >>>>> John >>>>> >>>>> >>>>> >>>>> >>>>> On Feb 16, 2016, at 1:47 PM, [email protected] wrote: >>>>> >>>>> @William, I love to work with C. >>>>> But, the thing is I want to implement machine learning algorithms in >>>>> BeagleBone. >>>>> So, it is quite easier to implement them with Python or R, as their >>>>> are some >>>>> dedicated packages to analyze the data. >>>>> >>>>> -- >>>>> 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 [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> >>>>> >>>>> -- >>>>> 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 [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> -- >>>> 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 [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> >>>> -- >>>> 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 [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
