What software to run on a SBC "Rpi" for the upcoming Duet-3
-
@calvinx said in What software to run on a SBC "Rpi" for the upcoming Duet-3:
And you might call it jumping the gun, I call it being prepared for any eventuality.
Prepared would have lead you to know that dc42 posted a link to the setup guide they send out with their prototypes and it clearly states raspbian, as have been the topic of more than on thread lately. I seem to recall the same link posted more than once in the last few weeks as well.
-
@bearer
Never saw it...
I followed the information at : https://forum.duet3d.com/topic/11540/duet-3-mainboard-6hc-initial-production-run/71
But I must thank you for bringing this to my attention, as this only confirms what I have been saying and highlights even more so the possible problems that might be encountered in the future.
Trying to be prepared led me to following the information provided by the vendor, and as you have quite rightly pointed out there is more than one set of instructions and/or information which is scattered all over the place only further highlights and provides credence to my statement that people are going to have issues.
This shows the importance of proper document control and how confusion can occur when documentation on the same subject is scattered all over the place instead of in one simple single point.
-
@calvinx What you leave out of the equation all of the time are also various statements about the documentation not being ready yet and that they will have it once the product is available.
-
Please show me where I said contrary to that? You can’t because I didn’t...
And that is not the point the point is (which from my rabbit hole point of view) This actually all came about because of a statement YOU made which led me down this particular avenue for my own interest.
One that led me to conclude:
That unless a fully compiled SD card image is available there could be issues, unless the image has everything already set up to allow the user avoid having to use the terminal then I stand by the assertion that there is going to be issues.
For example, take a look at the following link:
Now looking at that from a non-Linux users point of view the amount of input via the terminal is daunting for some imagine what it’s going to be like for those who even struggle with windows!!
You are preaching to the converted here, no one want to see the DUET-3 be a success more than I, but I want to play devil’s advocate here, unless it’s almost plug and play there is going to be a huge amount of problems.
And if the off the cuff comment you made about arch Linux is anything to go by It managed to lead me down this particular rabbit hole, what’s to say it couldn’t have lead someone else down that rabbit hole too. We all need to take ownership of our actions.
So if I can highlight my experience and a possible issue and that makes sure that it’s been noted so that action can be take so problems can be avoided then that’s really good and if it means that the Duet team takes a look at and decides "we need to get this area right first time with minimal input from the user" then that’s a good thing too.
If a one stop SD image is made available then Excellent, just be prepared for the unexpected.
-
@wilriker said in What software to run on a SBC "Rpi" for the upcoming Duet-3:
@calvinx What you leave out of the equation all of the time are also various statements about the documentation not being ready yet and that they will have it once the product is available.
Also on that point I would direct you to read the following and tell me how far away that point is.......... remembering that TODAY is the 15th of August!!
@t3p3tony said in Duet 3 Mainboard 6HC - initial production run.:
We will begin delivery the first week of September, in the order we receive your purchases.
-
@calvinx said in What software to run on a SBC "Rpi" for the upcoming Duet-3:
Please show me where I said contrary to that? You can’t because I didn’t...
@calvinx said in What software to run on a SBC "Rpi" for the upcoming Duet-3:
Trying to be prepared led me to following the information provided by the vendor, and as you have quite rightly pointed out there is more than one set of instructions and/or information which is scattered all over the place only further highlights and provides credence to my statement that people are going to have issues.
Here you said that people "are going to have issues". That is stated as a fact that sounds like the current state of documentation is supposed to be what the user will get once the product is available. At least that is my interpretation of this paragraph.
And that is not the point the point is (which from my rabbit hole point of view) This actually all came about because of a statement YOU made which led me down this particular avenue for my own interest.
I never said though that you should use Arch Linux. I even pointed out that this is mainly personal preference and what I like about it.
One that led me to conclude:
That unless a fully compiled SD card image is available there could be issues, unless the image has everything already set up to allow the user avoid having to use the terminal then I stand by the assertion that there is going to be issues.
For example, take a look at the following link:
Now looking at that from a non-Linux users point of view the amount of input via the terminal is daunting for some imagine what it’s going to be like for those who even struggle with windows!!
You are citing the page that was intended for prototype testers/OEMs. Do you also read development guides for the software you use if it is not yet fully released? (Playing devil's advocate here myself)
You are preaching to the converted here, no one want to see the DUET-3 be a success more than I, but I want to play devil’s advocate here, unless it’s almost plug and play there is going to be a huge amount of problems.
But to me at least it seems that you are playing devil's advocate on the usability of Arch Linux ARM based on comment of me that I like it. But that's not even what is being prepared for Duet 3 so IMHO there is no point at all here.
And if the off the cuff comment you made about arch Linux is anything to go by It managed to lead me down this particular rabbit hole, what’s to say it couldn’t have lead someone else down that rabbit hole too. We all need to take ownership of our actions.
Then please take the ownership of you going down a road you were not prepared to because of comment of a stranger. All I said was I like Arch Linux and I have prepared packages for DSF to be installed in Arch Linux.
I will stop participating in this discussion from now.
-
@wilriker said in What software to run on a SBC "Rpi" for the upcoming Duet-3:
I will stop participating in this discussion from now.
A bit late in the day now isnt it...
-
@calvinx said in What software to run on a SBC "Rpi" for the upcoming Duet-3:
But I must thank you for bringing this to my attention, as this only confirms what I have been saying and highlights even more so the possible problems that might be encountered in the future.
No need to go down a rabbit hole not intended for you and scream bloddy murder because you don't like the contents. Duet3d had also said they would provide official images which we haven't seen, but there is every reason to think it'll be on par with the current Duet2 SD cards provided.
If you want to live on the bleeding edge and provide feedback I'm sure that's great, but I don't think "this is too complex" is a valid feedback when it comes to non-release versions, be it firmware, hardware or documentation - then you're better of waiting for actual releases and maybe even let the releases mature a bit.
-
@bearer
And still you can't see the wood for the trees... And are missing the point entirely. Oh well you can take a horse to the water but you can't make it drink even with a kick in the nuts...
-
I am locking this thread before it degenerates any further.