HN user

dveeden2

381 karma
Posts18
Comments85
View on HN

Things that I noticed are not yet there in this version: /proc, uptime, uname

Things that are working: `cal 2026`, coredumps

Things that might be broken or aren't working as expected: ps (only returns "No mem")

And utmp is in /tmp?

And no /usr/sbin or /sbin? And nothing in /usr/local?

The messages from `write root` are only in uppercase.

Other databases written in Go:

- TiDB by PingCAP

- Vitess by PlanetScale

Both are basically only the SQL part as TiDB uses TiKV (written in Rust) and Vitess uses MySQL.

For those who want to implement a database in Go but without having to implement a network protocol there is go-mysql, which allows you to do this: https://github.com/go-mysql-org/go-mysql/blob/master/cmd/go-... As demonstration I created a networked SQLite: https://github.com/dveeden/go-mysql-examples/blob/main/go-my...

Both TiDB and Vitess have parsers that can be used outside standalone. So if you only want to implement your own on disk format, this can help.

Note that I'm working for PingCAP on TiDB and I'm also a co-maintainer for go-mysql.

The uname output looks more like the content of /etc/os-release on modern Linux distros and FreeBSD than the output of uname on Linux or FreeBSD.

What 32-bit systems are being used today? Is this on ARM or x86? or is it just running 32-bit software on x86-64/AMD64?

I think slightly more elaborate answers would benefit the person asking for this info. Maybe include the PostgreSQL version, system memory and a short description of your application.

[dead] 2 years ago

Any PDF, screenshot or otherwise accessible version of this?

Back in the the day it was possible to boot Sun Solaris over HTTP. This was called wanboot. This article reminded me of that.

This was basically an option of the OpenBoot PROM firmware of the SPARC machines.

It looked like this (ok is the forth prompt of the firmware):

    ok setenv network-boot-arguments dhcp,hostname=myclient,file=https://192.168.1.1/cgi-bin/wanboot-cgi
    ok boot net
This doesn't only load the initramfs over the (inter)network but also the kernel.

https://docs.oracle.com/cd/E26505_01/html/E28037/wanboottask...

https://docs.oracle.com/cd/E19253-01/821-0439/wanboottasks2-...

Where is POSIX actually useful today?

Is it mostly for shell scripts? Aren't people targetting bash or basic bourne shell features intead of posix? Is shellcheck checking for best practices instead of POSIX compliance?

And for other applications (GUI, servers, etc) strict POSIX compliance might be too restrictive?

And with many things being Linux (or Linux-like like WSL) the need for this might be less?

Are Android and/or iOS fully POSIX compliant?

Any good blog or presentation describing the current state of POSIX?

The generated files libntlm-1.8.tar.gz and libntlm-1.8.tar.gz.sig are published

Shouldn't we make browsers and (lib)curl understand this and automatically verify signatures? Maybe with some PKI or TOFU?