On Fri, 28 Aug 2015 22:23:07 +0200, Per Jessen wrote:
Jim Henderson wrote:
On Fri, 28 Aug 2015 20:38:12 +0200, Per Jessen wrote:
That said, though, if there's a group of users who want to continue to build a 32-bit version, that's cool. Let it be like the Pi versions, or the other non-official builds like Evergreen or the education version. That's what open source is all about.
Where do I/we start? It seems to be slightly different to both Evergreen and the education version as they are based on existing versions. (to my knowledge).
If it were me, I'd start by learning how to build the packages and build a release. That seems like a logical first step.
I agree, sounds good. I tried joining the release engineering team back in June, but my attempts were so far ignored. Is there documentation available anywhere? I know how to build packages, now how about an entire release?
Richard? Can you hook Per up?
I got rid of my last 32-bit system many years ago. When I was laid off, I had to scrape together enough money to buy a laptop, and I bought a 64-bit system for a pretty good price. I wouldn't say I was in poverty, but I certainly had to watch every penny I spent.
Apologies, I may be stepping on somebodys toes, but it's really not so much about running on real 32-bit hardware. The 32-bit-only hardware _is_ dying, but it doesn't mean the software has to die too. For the purpose of this discussion, perhaps we ought to focus on running 32-bit systems on 64-bit hardware. (that's my current focus any way).
To what end? Why would you install a 32-bit OS on 64-bit hardware?
Jim, people (and myself) have pointed that out earlier in this thread:
running 32bit apps running 32bit virtual guests.
Both use less memory in 32bit.
Ah, "scarcity". Not a really good argument IMHO. I've got one system here with 8 GB of RAM, one with 16 GB of RAM, and one with 32 GB of RAM. I run 64-bit SLE in VMs on the latter, typically about 8 at a time.
If it's to deal with some deficiency in the 64-bit version, fix the deficiency rather than maintain an entire infrastructure to build a 32- bit release.
The deficiency is that a 64bit app uses more memory than a 32bit ditto.
How much? 2x? 1.5x? 16 bytes more because of double-byte pointers? It can't be *that* significant, certainly not significant enough to justify the resources to build *an entire 32-bit distribution* to deal with a handful of people who still treat memory is a scarce resource. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org