I've wanted to go back to a BSD for a more old-school desktop OS, been
tempted to look at NetBSD.
If you do, I am interested to hear of it. I wonder if they still support 386 CPUs. I think linux quit those.
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
Re: Re: Cobol/gnucobolI used to run NetBSD a long time ago. A friend of mine was a developer
By: poindexter FORTRAN to Dumas Walker on Wed Jun 25 2025 08:11 am
I've wanted to go back to a BSD for a more old-school desktop OS,
been tempted to look at NetBSD.
If you do, I am interested to hear of it. I wonder if they still
support 386 CPUs. I think linux quit those.
---
â– Synchronet â– Vertrauen â– Home of Synchronet â– [vert/cvs/bbs].synchro.net
If you do, I am interested to hear of it. I wonder if they still support 386 CPUs. I think linux quit those.
I Know Debian and OpenSUSE still support 32 bit processors.
On Thu, 26 Jun 2025 09:38:49 -0700
I used to run NetBSD a long time ago. A friend of mine was a developer
and kept nagging me to use it. I think I tried to go bleeding edge and always ended up with some library incompatibilities. I'm sure things
are better these days. I actually quite liked it but ended with going
back to Linux with it being more the mainstream.
Re: Re: NetBSD
By: nelgin to All on Fri Jun 27 2025 09:21 am
On Thu, 26 Jun 2025 09:38:49 -0700
I used to run NetBSD a long time ago. A friend of mine was a
developer and kept nagging me to use it. I think I tried to go
bleeding edge and always ended up with some library
incompatibilities. I'm sure things are better these days. I
actually quite liked it but ended with going back to Linux with it
being more the mainstream.
NetBSD runs on more architectures. That's no easy trick. Pulling it
off is impressive. Using NetBSD takes time. It's another world to
learn.
NetBSD runs on more architectures. That's no easy trick. Pulling it
off is impressive. Using NetBSD takes time. It's another world to
learn.
Why are you telling me what I already know? Didn't I say I ran NetBSD?
I have a pretty good grasp on what it will run on. I find this post pointless.
If you do, I am interested to hear of it. I wonder if they still support
386 CPUs. I think linux quit those.
I Know Debian and OpenSUSE still support 32 bit processors.
But which ones. I think the kernel quit 386s.
NetBSD runs on more architectures. That's no easy trick. Pulling it
off is impressive. Using NetBSD takes time. It's another world to
learn.
Why are you telling me what I already know? Didn't I say I ran NetBSD?
I have a pretty good grasp on what it will run on. I find this post pointless.
If you don't like my style or content, you're not required to read it.
I read it as him paying you a compliment for "pulling it off" and learning it.
NetBSD runs on more architectures. That's no easy trick. Pulling it
off is impressive. Using NetBSD takes time. It's another world to
learn.
Why are you telling me what I already know? Didn't I say I ran NetBSD?
I have a pretty good grasp on what it will run on. I find this post pointless.
I read it as him paying you a compliment for "pulling it off" and learning it.
I used to run NetBSD a long time ago. A friend of mine was a developer and
kept nagging me to use it. I think I tried to go bleeding edge and always
ended up with some library incompatibilities.
NetBSD runs on more architectures. That's no easy trick. Pulling it off is
impressive. Using NetBSD takes time. It's another world to learn.
Why are you telling me what I already know? Didn't I say I ran NetBSD? I have a pretty good grasp on what it will run on. I find this post pointless.
NetBSD runs on more architectures. That's no easy trick. Pulling it
off is impressive. Using NetBSD takes time. It's another world to
learn.
Why are you telling me what I already know? Didn't I say I ran NetBSD?
I have a pretty good grasp on what it will run on. I find this post pointless.
Why are you telling me what I already know?...
I read it as him paying you a compliment for "pulling it off" and learning it.
I read it as him complimenting NetBSD on running on many architectures and goo
for them. *shrug*
Eh? Sounds to me like he was paying you a compliment ("That's no easy trick. Pulling it off is impressive").
Installing NetBSD on a PC is like installing Linux on a PC.
Re: Re: NetBSD
By: nelgin to All on Sat Jun 28 2025 01:47:34
Why are you telling me what I already know?...
Whoa, dude. Go have a Snickers. ;)
Installing NetBSD on a PC is like installing Linux on a PC.
NetBSD package management takes time to learn. It's not the same as
linux. And you need to compile a custom kernel. The default kernel is bloated with features many users don't need. Editing the kernel config often results in a failed build because you removed some essential dependency. It takes time, trial, and error to get it right.
i didnt need to edit the kernel config ... like years ago
Jcurtis wrote to MRO <=-
i didnt need to edit the kernel config ... like years ago
I did, to make it fit in a small memory system. Do you know what your kernel memory size is?
On modern, "normal" hardware, who gives a shit what the "kernel
memory size" is?
---i didnt need to edit the kernel config ... like years ago
I did, to make it fit in a small memory system. Do you know what your kernel memory size is?
Re: Re: NetBSD
By: Jcurtis to MRO on Mon Jun 30 2025 04:42 am
i didnt need to edit the kernel config ... like years ago
I did, to make it fit in a small memory system. Do you know what
your kernel memory size is?
did you intentionally edit my quote to make it say something else?
NetBSD package management takes time to learn. It's not the same as
linux. And you need to compile a custom kernel. The default kernel is bloated with features many users don't need. Editing the kernel config
often results in a failed build because you removed some essential dependency. It takes time, trial, and error to get it right.
It's not as easy as linux, if you want to do much work with it. Saying otherwise won't make it so.
Re: Re: NetBSD
By: MRO to Jcurtis on Mon Jun 30 2025 11:39 am
did you intentionally edit my quote to make it say something else?
No. I didn't add or change any words. I cut unneeded words. That's trimming, not editing.
---i didnt need to edit the kernel config ... like years ago
No. I didn't add or change any words. I cut unneeded words. That's trimming, not editing.
yeah but you entirely changed my sentence to make it say something else.
why even do that?
you changed it to:
i didnt need to edit the kernel config ... like years ago
Jcurtis wrote to MRO <=-
Re: Re: NetBSD
By: MRO to Jcurtis on Mon Jun 30 2025 08:34 pm
No. I didn't add or change any words. I cut unneeded words. That's trimming, not editing.
yeah but you entirely changed my sentence to make it say something else.
why even do that?
you changed it to:
i didnt need to edit the kernel config ... like years ago
It seemed harmless to me. Sorry for any offense.
you changed it to:
i didnt need to edit the kernel config ... like years ago
It seemed harmless to me. Sorry for any offense.
you're editing people's text to make it something else.
just stay out of it or dont quote it at all.
Sysop: | Bagwaa |
---|---|
Location: | Nottingham, UK |
Users: | 5 |
Nodes: | 10 (0 / 10) |
Uptime: | 215:03:31 |
Calls: | 14 |
Files: | 1 |
D/L today: |
1 files (3,430K bytes) |
Messages: | 78,664 |