Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
crest
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
56 ms
·
751.
▲
by
crest
9y ago
The disadvantage of enabling WAL is that your database just turned into two files and you have to recover the database to read it. Recovery is fast but it requires write access.
752.
▲
by
crest
9y ago
Because there is no scarcity that requires management by enforcing an monopoly. If I want to stop playing chess why should everyone else stop playing chess as well?
753.
▲
by
crest
9y ago
Because the alternatives are worse.
754.
▲
by
crest
9y ago
AES is slower for bulk encryption than Blowfish on old CPUs (at least those with enough data cache for the Blowfish tables).
755.
▲
by
crest
9y ago
Some Alpha AXP cores used a split register file and the register renaming logic took care of the synchronisation.
756.
▲
by
crest
9y ago
There have been CPUs with multiple datastacks e.g. https://bernd-paysan.de/4stack.html is a VLIW ISA with a very dense encoding and "just less ports" to the register file than a classic DSP.
757.
▲
by
crest
9y ago
In theory FreeBSD supports a sane aio_read/write/fsync() implementation by extending sigevent to include the generation of kqueue events, but there are no aio_open/close/fstat/rename() syscalls and if you need a thr
758.
▲
by
crest
9y ago
Afaik the problem is that XFS trusts the hardware to do the right thing during a power loss aka stop inflight requests before the brownout turns you disks and their controllers into heavily biased random number generators. Lots of x86(-64)
759.
▲
by
crest
9y ago
The bhyve hypervisor does support PCI-e passthrough.
760.
▲
by
crest
9y ago
When non-blocking socket I/O was implemented the disk was considered to be too fast to warrant the same kind of treatment. At the API level the different is that sockets, pipes and ttys are have an additional "ready for use"
761.
▲
by
crest
9y ago
In effect this is still Ethernet over TCP, but other than that it's a cool idea. Now if only NATS would support SCTP...
762.
▲
by
crest
9y ago
Use the (hash of the) source code to seed the CPRNG.
763.
▲
by
crest
9y ago
Use forward error correction.
764.
▲
by
crest
10y ago
Some language runtimes create threads before the application main() function is executed. Even if Linux has to retain bug-for-bug ABI compatibility there is valid reason to only provide fucked up the set id() syscalls. The problem is even w
765.
▲
by
crest
10y ago
How would your Neo ISA compare to the proposed RISC V Cray style vector extension for FFTs?
766.
▲
by
crest
10y ago
FreeBSD doesn't overcommit the available memory (RAM + swap) by default. Don't use swapfiles in FreeBSD because the file system write paths of UFS and ZFS potentially allocate memory. Both geom_mirror (software RAID-1) and geom_el
767.
▲
by
crest
10y ago
These days the primary use of swap is to get the efficiency of overcommitting RAM without compromising reliability.
768.
▲
by
crest
10y ago
In that case have a look at https://wiki.netbsd.org/guide/veriexec/ .
769.
▲
by
crest
10y ago
It's not just a performance problem. OpenSSH's VPN works by encapsulating either IP packets (tun) or Ethernet frames (tap) in TCP. Now you suffer from head of line blocking and nested congestion control. If you want an easy to use
770.
▲
by
crest
10y ago
Sudo and polkit are so complicated because they solve the wrong problem. The common problem is how do I execute code under a different effective user id. Instead they try to solve a much harder superset: how to securely implement a policy d
771.
▲
by
crest
10y ago
The x86 instruction set wasn't designed with hardware virtualisation in mind. Some of its instructions are defined to leak state from higher privileged levels into lower privileged levels. As hypervisor Xen must preserve these semantic
772.
▲
by
crest
10y ago
Have the APs limit the RSSI and let the client roam.
773.
▲
by
crest
10y ago
I didn't mean to imply that. I just explained why ezjail looks so convoluted to a new user. Ezjail still solves the same problems today as it did 10 years ago. On the other hand since not even bloatware did keep up with storage cost de
774.
▲
by
crest
10y ago
What issue? Root outside the jail is implicitly trusted by the jail so why would you hide resources (in this case jailed processes) from the "true" root? Jails can't see each others processes. The only case I can think of how
775.
▲
by
crest
10y ago
The firewall can match on the jail id for local sockets and apply traffic shaping based on these matches. Hierarchical resource limits on CPU/disk/memory/... can be configured per jail.
776.
▲
by
crest
10y ago
Docker moves fast and breaks things without stabilising them first this post explains the problem fairly well: https://thehftguy.wordpress.com/2016/11/01/docker-in-product... . There have been lots of bugs (so
777.
▲
by
crest
10y ago
UIDs and GIDs are just numbers to the kernel. Root inside a jail become any UID/GID and chmod/chown files just like root outside the jail, but even root inside a jail is locked down into the jail root directory. You can prevent ro
778.
▲
by
crest
10y ago
The bug I ran into was https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212649 which turned out to be an other symptom of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212576 .
779.
▲
by
crest
10y ago
Ezjail is fairly old. It works with the older less capable API to jails and is restricted to features supported by the old API. It was also designed for use with UFS on tiny disks. Lets say you are a webhoster around the year 2000 and your
780.
▲
by
crest
10y ago
I did and during my tests i found no more panics, but I ran into a bug in the IPFW tables logic. The fix hasn't been backported to FreeBSD 11.0 as an errata. Also the epair pseudo-interface used for connecting IP stacks tops out at abo
More ›