I see no difference between the 3b & the 3B+ regarding 32/64bit OS's and it's been discussed several times on these forums. There are 64bit OS's available for the Pi.
Like Raspbian they simply need to update their boot code and kernel, in a short while all other OS's will work. there is no reason why they cannot be updated for the PI 3B+.
That's an interesting 64-bit recommendation. I think there are 64-bit versions of Arch and Ubuntu that also run on the Pi 2 and 3. I wonder how the different distributions compare from reliability, security, support and performance points of view.
I would not get too hung up on the "sanctioned" idea. Certainly don't hold your breath waiting for a 64 bit Raspbian. Supporting both 32 and 64 bit is a lot of work for somebody and will cause a lot of confusion in user land. Especially since 64 bit is not needed for 99% of users and applications of a Pi.I too would like to see a 64 bit raspian. I have 64 bit 4.14 running but need 64 bit java and postgresql, essentially a sanctioned 64 bit package.
ejolson wrote: ↑Mon Mar 19, 2018 12:21 amThat's an interesting 64-bit recommendation. I think there are 64-bit versions of Arch and Ubuntu that also run on the Pi 2 and 3. I wonder how the different distributions compare from reliability, security, support and performance points of view.
Note that switching from Raspbian is a jump from ARMv6 compatible code all the way to ARMv8. Certain things will run much faster and if those are the things you are interested in, then the difference can be significant.
Still, as demonstrated by the popularity of the 32-bit Raspbian for x86 processors, there is quite a bit of computer science that can be learned using a 32-bit operating system.
I once worked on an IBM mainframe (S/360-30) that had 32KB. It really hurt when a new release caused the OS nucleus to grow from 6KB to 8KB. I spent several weeks recompiling programs to get rid of double-buffering of files so they would still fit and run (no virtual memory in those days...and, as an aside, almost no microcomputers, either).
I can't say that those acronyms ring any bells, but I did do a fair amount of ALC programming on IBM DOS systems, including one memorable program I didn't write, but had to do maintenance on. It was the main post program for a Demand Deposit Accounting system (think checking accounts) that ran to 11,000 lines of assembler. Somewhere around the house I have the listing of an ALC program I wrote for fun...it does a complete set of solutions to the Soma Cube. One night it took a S/360-50 4.5 hours to do the entire run. It might be fun to re-write it for the Pi (in any language) to see how long it would take...royhenderson wrote: ↑Mon Mar 19, 2018 6:18 pm@jamesh - my 4GB onboard is not a wish but just the point at which 64bit would start to offer benefit for me ... however, a 2GB now would be of interest - even at a price premium.
@W.H. H - sounds like you might even remember the joys of SDMOD and DTFSD ...
There is something odd about ARM addressing, or its memory mapped IO, that requires a 64-bit OS when moving to 2GB, not 4GB as you might think. Thats one reason why the Pine64 and the Odroid C2 both have 64-bit official OS's (they use the same Cortex-A53 as the Pi's and 2GB RAM).
I also find it amazing and sympathize with your point of view.I find it amazing how much RAM we 'need' nowadays, when we were doing very similar tasks in 32MB devices not that long ago. Just badly written code in my opinion.
In what way is the current ARMv7 Raspbian bottlenecked or limited compared to a theoretical ARMv8 Raspbian?
Ok, so "database engines that memory map inordinately huge database files" is one valid reason. Any more?Heater wrote: ↑Mon Mar 19, 2018 9:30 pmIt is not.
There are some odd things that need a 64 bit address space.
I believe MongoDB is one. If your database is bigger than 2GB.
CockroachDB can get by with 32 bits but needs tweaking to do so.
Of course nobody in their right mind is going to be using a Pi for huge databases. Except for experimentation.
I'm not sure who you are quoting there, certainly not me, but...Ok, so "database engines that memory map inordinately huge database files" is one valid reason. Any more?
Think of it this way:
ATM we don't need it (actually the Pi architecture right now doesn't) but it is a stepping stone toward the future and those that do feel they need it now do have options.