Hacker Timesnew | past | comments | ask | show | jobs | submit | andrewf's commentslogin

They may not be confident in its reliability over the fall gamut of cheap consumer drives.

Did he write down everything he learned? That way the next person only needs to cover the intervening time period.

Conceivably LLMs might be good at answering questions from an unorganized mass of timestamped documents/tickets/chat logs. All the stuff that exists anyway without any extra continuous effort required to curate it - I think that's key.


https://github.com/arobenko/embxx_on_rpi/blob/master/src/asm...

Their stuff isn't running on top of Linux on the Pi.


My original assessment wasn't concerned with bare-metal vs sw vs fw at all.


I worked for a company that published a PalmOS app. Palmgear.com was a very important distribution channel, but so was our own website, I forget the exact ratios.


You could do "network shares" as in mount the filesystem from Linux and export over Samba/NFS/etc; it would probably also be possible to export the drive as an iSCSI device and mount HFS(+) filesystems directly from the Mac.


> I assume we are using a lot more energy

What I've learned from visiting my own parents is, you can alleviate the energy concern, if you (1) get solar panels and (2) ban your spouse from running the dishwasher at night :P


or (3) get a battery


https://devblogs.microsoft.com/oldnewthing/20130108-00/?p=56...

Sounds like this is about making .OBJs that fit in the conventions set by Win32 and the Microsoft linker. If you were using Microsoft's LINK.EXE I'd look at https://learn.microsoft.com/en-us/cpp/build/reference/nodefa... (and /Zi for the Microsoft compiler)

More generally, a lot of compiler generated code (including from LLVM IR -> native) will rely on compiler-specific runtime library functions, which aren't necessarily considered part of the "C runtime". https://wiki.osdev.org/Libgcc occupies this role for GCC-compiled code. See https://godbolt.org/z/fb75PPobz for an example (64-bit division on 32-bit x86 generates a call to ___divdi3)


Swap the parameters around for C++ and similar langs where `assert(a, b)` evaluates the same as `(void) a; assert(b)`.


https://j00ru.vexillium.org/syscalls/nt/64/

(One example: hit "Show" on the table header for Win11, then use the form at the top of the page to highlight syscall 8c)


Changes in syscall numbers aren't necessarily breaking changes as you're supposed to use ntdll.dll to call kernel, not direct syscalls.


That was his point exactly.



Starting with FreeBSD might be easier than starting with Debian then removing all the GNUisms. But perhaps not as much Type II fun.


Using Linux gets you much more hardware compatibility especially for the consumer desktop and laptop systems this is targeted towards.


True


I think Linux is the better choice for replacing the entire userland. From what I've seen, the BSDs don't have such an accessible userspace/kernelspace split. With some effort, on Linux you could probably just run an exe as your init.


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

Search: