Hacker Newsnew | past | comments | ask | show | jobs | submit | dev-il's commentslogin

Not really. Tizen wouldn't work on a small low-power and low-RAM bluetooth SoC like the NRF52 this watch has. Tizen requires iirc a minimum of 512MB or 256 MB for "Tizen light". So: different focus, much bigger SoC and RAM, much shorter battery time.


I do that too. For the latter, I use the redirector addon https://addons.mozilla.org/de/firefox/addon/redirector/


Actually, packs of 10 eggs are more common in continental Europe (e.g. Germany, France) than packs of 12 eggs these days.


the librem isn't more open than the PinePhone at all. The only difference is that they put the modem on a separate card… but that doesn't make it any more open at all. What matters, given the fact that there just isn't any open modem out there, is the fact that the modem is kept isolated from the SoC in a way that doesn't allow the modem to access anything the SoC doesn't explicitly give it.


> The only problem remaining, on this particular device, is direct connection of physical sensors (microphone, GPS, etc) directly to the modem

is that even the case of the microphone? My understanding was that - independently of the possibility to turn the microphone and modem off with kill switches - all audio data to the modem comes via I2S from the SoC anyways, i.e. that the microphone is NOT directly connected to the modem but to the SoC (possibly via a separate audio codec Chip) and that the SoC serves the modem via I2S whatever audio data the user pleases (whether that be from the microphone or whatever else).


Yes, the modem can't talk to anything, it's only connected to the SoC with the i2s audio bus and the usb bus, the SoC controls what gets sent to the modem. for a voice call the SoC proxies audio between the mic/speaker and the modem.


"Chromebook" should be renamed to "Chromebrick"


quotes From the "Hardware Requirements" page on that linked FreeNAS site:

• "64-bit hardware is required for current FreeNAS releases. Intel processors are strongly recommended."

• "8 GB of RAM is the absolute minimum requirement. 1 GB per terabyte of storage is a standard starting point for calculating additional RAM needs, although actual needs vary. ECC RAM is strongly recommended."

The example configuration for a "Home Media Server or Small Office File Share" even suggests "16 GB RAM".

I've heard that ZFS is quite RAM hungry, but c'mon, 16GB for a home media server?


I've run ZFS on OpenSolaris, Illumos, and then Linux, continuously since 2009. (However, I have no experience of using it on FreeBSD.) I've always regarded FreeNAS's RAM recommendations as being weirdly high. The "1GB per terabyte" thing dates from when ZFS systems were being pushed as enterprise workgroup file servers (i.e. maybe hundreds of users), with all storage on spinning rust. I wager that a great many FreeNAS systems are seeing approximately one user, primarily accessing large media files which mostly don't benefit that much from caching. Though of course, if you really are using FreeNAS in a more demanding role, then the hardware should reflect that.

I believe it did used to be the case that the FreeBSD port of ZFS had an issue where ZFS wouldn't always back off its RAM use fast enough, if the system came under memory presure, so it was at the time prudent to ensure that FreeBSD ZFS machines never got into low-memory situations, but I haven't heard anybody complain about that in practice in some years, so presumably it's fixed now, but FreeNAS's RAM recommendations have not been relaxed.


FreeNAS is famous for recommending the upper tier of ZFS requirements.

You can, and many people often do, run ZFS on a fraction of what FreeNAS recommends. In fact I’ve had ZFS running on a 32bot processor with 4GB RAM before. I’ve also had it running on 64bit with 2GB available RAM and it ran just fine for personal use.

However in fairness to FreeNAS, they are following best practices as defined by Sun/Oracle. It’s just those bear practices are defined with enterprise in mind.


I ran a ZFS file server and VM host for years with 6GB of RAM. It'll work fine, just don't use dedup.


With drive capacities topping 10TB and dedup being what it is, it's not too far of a stretch?


Those specs would be without dedup enabled (which generally isn’t in ZFS because it’s quite an expensive feature).


Yeah 8GB seems excessive. My Synology has 2GB of RAM and does just fine. I run multiple docker containers on it aswell.


That’s likely because Synology doesn’t offer ZFS or anything near the same capabilities.


synology uses btrfs which provides almost the same capabilities, but ZFS usually eats all the RAM it gets as some sort of cache to speed up disk operations.


You are thinking of the ARC. By default, ZFS will allocate what is available but you can constrain it as you like.


on the other hand, the big cost factor that would restrict home delivery to people who have money is… human labor costs. Once robot-based delivery is the standard, home delivery may be quite affordable. Maybe even less costly on the whole than operating supermarkets.


The latter doesn't contradict the former. What the market will bear results from all the individual subjective value assessments of every individual.

Indeed the market is made of all people, each with their personal and subjective assessment of value based on their own personal/subjective needs, criteria etc. What a product is worth TO YOU is your decision alone… and totally subjective, and… statistically irrelevant to the market at large.

The objective value measure though that matters to the market at large is: for what price can you be certain to find a buyer (in other words: "what the market will bear").



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: