Well, provided that the Wi-Fi works, similar to a Raspberry, such a device could be a little server in the private home network serving as ftp, dlna, samba server or whatever, accessible and configurable through ssh from your PC. As those smartphones all have a slot for micro SD cards, I guess enough additional space for storage could be achieved. Just an idea.What would you do with those smartphones if you could install NetBSD? ??
Thanks for the info, but could someone answer the original question, please? Or has nobody ever tried to flash NetBSD to a smartphone, or can at least rule out it's not possible in the first place?Note: Battery-powered devices ready to catch fire if you keep them plugged in permanently.
Thanks for the info, but could someone answer the original question, please? Or has nobody ever tried to flash NetBSD to a smartphone, or can at least rule out it's not possible in the first place?
7. We will not allow technical/support questions about any operating system other than FreeBSD anywhere on this forum. That includes the Off-Topic forum. Always ask technical/support questions about other operating systems on the forums or mailing lists associated with those operating systems.
Bumping up this thread
Long time FreeBSD user here.
I am moving away from FreeBSD. Sort of.
I will be watching, but focussing more on NetBSD.
The thing is this.
FreeBSD nowadays works very well on desktop. Kudos to the FreeBSD team. If you have a mainstream hardware (HP/DELL/LENOVO) that is in the market for last 2-3 years, then FreeBSD will work wonderfully.
Now the reason for chipping in here.
My primary work is IoT applications and Edge computing.
There I find that NetBSD has better support for peripherals.
So, I made a trade off.
Desktop ? Windows is fine to get things done. Even Debian which I have in dual boot mode.
Since, I have to get my products out, I need a platform where junior firmware engineers can start off with quick prototyping.
FreeBSD is breeze to install and setup.
But for a widely used tinkering board like Raspberry Pi (lot of people have mentioned in the thread here), FreeBSD does not have support for Bluetooth, WiFi, DSI, CSI.
Even the SPI support is not there.
FWIW, FreeBSD Bluetooth is broken even of mainstream AMD64/x86-64 platform.
NetBSD is a pain to install.
But once that is done, I found most peripherals working except SPI.
If I were to prototype a outdoor sensing platform on Raspberry Pi or any such widely available ARM SoC, I really don't care about CSI and DSI.
So, here the deal breaker was lack of radio networking support.
Most smart sensors in the market work with Bluetooth Low Energy.
I'm getting down to writing a NetBSD SPI driver that can be accessed from user space daemons. I can live with that.
So, it will be a slightly outdated NetBSD desktop working with half a dozen ARM SoC running NetBSD.
I wish it were FreeBSD.
I don't know.
It doesn't make any sense to me why FreeBSD Foundation wants to lose the IoT market.
But as I mentioned FreeBSD will be on constant watchlist.
Do you get acceptable speeds
And when will that be? Do you have any concrete information on that, or is that mere speculation / wishful thinking? I could just test on my Raspberry Pi 3, that NetBSD 10 now finally supports the internal WiFi (that was not the case in 9.3 and 9.4) and sound. So would it not be possible to somehow copy those drivers from NetBSD and port them to FreeBSD?Some day internatl Wifi will work and Video Core IV GPU accelartion will be enabled.
10 years ago NetBSD was my favorite BSD by far. Nowadays I'm a Puffy believer though.For FreeBSD users, and those who've ever used FreeBSD, share your NetBSD experience. Including, if you've used NetBSD for complementary use with FreeBSD, such as needing hardware support for access.
Keep in mind: Thread why-is-freebsd-not-more-like.66591. For other discussion and technical help about NetBSD, use daemonforums.org, unitedbsd.com or NetBSD mailing lists.
Trying NetBSD
I've tried NetBSD before 2016, but had trouble with the network card, so couldn't continue. The network card had to be physically removed for it to boot up. I don't remember if that was the wireless card which didn't work with it, which I needed at that time.
NetBSD as a desktop
My first time using NetBSD successfully on the desktop was in February or March of 2018 until May or June of that year. It was likely the 7.1.2 release in mid March, or 7.1.1 of the end of the previous year.
NetBSD, by default, mounts the kernel and pty on their own filesystem.
NetBSD pkgsrc uses a file rather than an ncurses menu for configuring its ports. It has less ports, but they're sturdy and seemed less complicated or simpler. Their dependency choices were set from a file, rather than from an ncurses menu.
My desktop froze up a lot from Internet browser's runaway processes. This hasn't happened on FreeBSD, until more recently, as it became a frequent occurrence with Firefox: this was largely fixed by limiting the amount of RAM of the (login) user account which this program ran under.
Native audio only allowed 1 application to play at a time on NetBSD. It used EsounD (Enlightened Sound Daemon; ESD) or PulseAudio more often than oss or sndio. Former member Sensucht94 showed me a link which shows how to use ESD to take audio from multiple applications, and output it for the speaker.
At the time, I've heard that the 8 series (including while it was current) of NetBSD uses an improved native sound server which allows multiple sound sources to play at the same time.
Their ttys file was simple, as it usedxdm_enable="YES"
for turning on xdm. It has been reported that FreeBSD could also be configured with this, but I haven't gotten it to work like that.
The desktop of NetBSD was in very low resolution. If this was the default that could have been adjusted, I didn't know how to.
Since then, it has been said that the Video display and sound system on NetBSD have been improved.
The time I've used NetBSD for legacy and specialty hardware support
I used NetBSD, in an attempt to use legacy and specialty hardware in 2022, after my computer broke. The attempt was to get a 32bit PC with IDE cables with an old SATA card to access a SATA harddisk. It was a RAID card, which use was attempted in JBOD (Just a Bunch of Disks) mode.
The /dev/ directory was overwhelming to use, because it listed all possible devices, whether they were loaded or not, instead of autoloading drivers when needed.
In this, the people in the NetBSD IRC rooms were friendly and eager to help.
It turns out, that my RAID card was bad. Then, tried another solution of using a USB to SATA cable, for my laptop on FreeBSD, which the harddisks were damaged and important data couldn't be accessed.
Related:
According to https://freebsdfoundation.org/wp-co...nterface-Device-HID-Support-in-FreeBSD-13.pdf, NetBSD and OpenBSD have had the improved HID stack for a while, that is recently being implemented in FreeBSD.
Related threads: