Reaction score: 560
You can't stop mocking me?
You can't stop mocking me?
It maybe OK for people who really used a console, but for people has never used a console like me it's very difficult, counter-intuitive to use and too limited. I learned to use the cli on modern virtual terminals like xfce4-terminal, mate-terminal... Asking me to deal with this old console, sorry, I will abandon Bhyve, only because that console. Luckily, we could use tmux as the console for Bhyve. It's really revived my interest for Bhyve and I tested many OSes on Bhyve. If you want to drag a younger audience, then this console is unacceptable. Nowadays we have too many choices, in no way we would limit ourselves by forcing us using that terrible console. No way!Can you please expand on this.
How can a console be shite? Does it crash or what exactly does not work?
If you want to drag a younger audience,
Don't project you incompetency or lack of experience on young people. Many of them are writing system programs, working on device drivers and programming microcontrollers.Us, the youngsters, grew up on modern virtual terminals, at least xterm-256, that old console is unacceptable.
It maybe OK for people who really used a console, but for people has never used a console like me it's very difficult, counter-intuitive to use.
You may not know this but FreeBSD's terminal is actually newer and "more modern" than them (https://www.freebsd.org/cgi/man.cgi?query=vt&sektion=4)modern virtual terminals like xfce4-terminal, mate-terminal...
This is one of the wonderful things that has happened recently with the rise of Raspberri Pi, Arduino, etc. More and more people are bit-banging on the hardware like it's 1988. I love it.Don't project you incompetency or lack of experience on young people. Many of them are writing system programs, working on device drivers and programming microcontrollers.
This is one of the wonderful things that has happened recently with the rise of Raspberri Pi, Arduino, etc. More and more people are bit-banging on the hardware like it's 1988. I love it.
Telling people is incompetence doesn't make you look cooler. The fact is your nmdm console sucks
I have already ditched your Bhyve for a long time.
Another bad thing about Bhyve is firmware support. It doesn't support legacy BIOS firmware. Yeah, there is uefi-csm, but it's just not work. The only way to install your guest as BIOS with a MSDOS partition table and boot it is using grub2-bhyve. This is the only way you could continue installing legacy BIOS based OSes without going the EFI route. Yes, only grub2-bhyve works. And that port is unmaintained
Anyone let me know if we could just grab the SeaBIOS firmware from VirtualBox and use it with Bhyve? And if it just works, why people don't do that from the beginning? Sorry but I don't see the point of using EFI for guest OS. Because most EFI firmwares of virtualization software out there sucks, including VirtualBox's own
p/s: it seemed KVM also uses SeaBIOS, too.
Reaction score: 1,263
“nmdm” is an abbreviation for null-modem. And you can think of it as exactly that: a software representation of a null-modem cable, no more and no less. People who are a little older probably remember that you used these kind of cables to connect serial terminals (like a DEC VT100 or VT220) to serial ports on your PC.
I learned a lot of what I know about Novell networking so I could play Doom 1 head-to-head against my buddy. A couple of garbage-picked 3com 3C501s; some thinnet, t-connectors, and terminators, and we're off to the races in what would've been called a LAN party in the naughts. I think LAN parties are old school now too.Not only that. Those things also enabled one of the earliest forms of online gaming. In the the most literal sense. You just had to grab your tower and take it to your buddy (very convenient!) and the both of you could then duke it out. All of this while sitting like maybe 2m apart because your PCs were physically on-a-line and the cable wouldn't reach any further. Null modem cables were very much ahead of their times!
Since it's a off-topic thread and it was from the beginning (wrong section, but things happens!) let me tell you my story. I was a Duke Nukem 3D fan, and at the time I thought I was a master in it! Then there was a Duke Nukem 3D competition. I was confident that I'm going to win the cup. PCs was connected to each other with Dialup MODEMs. Race started and in my first match I lost 0 to 50. I can't remember the exact score, but mine definitely was zero! At that very moment I realized that there's a very important concept in playing FPS, namely Mouse!I learned a lot of what I know about Novell networking so I could play Doom 1 head-to-head against my buddy
Reaction score: 71
What the OP needs to ask himself is- What does NVMM do that Bhyve does not?
That is what I would ask myself if I was a developer.
We have Bhyve and Xen.
Why do we need more options? We have two perfectly functioning tools for Virtualization.
Why would a developer want to add a third?
Is this a numbers game? The OS with the most choices win?
We have limited manpower and need to focus on refining the choices we have.