Hacker Newsnew | past | comments | ask | show | jobs | submit | moviuro's commentslogin

Search forums local to your country and write documentation on how to use Linux or BSD as a modem.

For OpenBSD on Orange France FTTH: https://lafibre.info/remplacer-livebox/remplacer-sa-livebox-... or https://try.popho.be/securing-home2.html


That link forever hangs for me :-(

The last time I searched for open hardware, even the implementations running Linux on a desktop PC with a caux adapter were not DOCSIS 3.X compatible.

The companies that multiplex the signal down the cables keep updating their standards, both a blessing (for speed) and a curse for maintained code




It's a very rare race condition, odds are very low that you were impacted. If you were, you would have noticed (heavy builds with files being moved around where suddenly files are zero).

[0] https://bugs.gentoo.org/917224

[1] https://github.com/openzfs/zfs/issues/15526 (referenced in the article)


See the explanation on the blog itself [0]

[0] https://joshcsimmons.com/post/H4sIAAAAAAAA%2F3xV227cRgx911cQ...


Wow... that is pretty janky.


> The signals required a lot of patience to learn and I'm not entirely sure I still understand them.

Chain signals before an intersection; regular signals after those, and on the track to split the track for multiple trains simultaneously.

See: https://wiki.factorio.com/Tutorial:Train_signals if you haven't already.


Another major stumbling block for train signals once you get the basics down is segment length. Signals indicate whether the next segment is occupied, not whether any given train will fit in there (and potentially block a segment or intersection behind it.)

I frequently set up tracks with segments as large as my longest train, but then end up having to add an intersection here or there, breaking up segments into smaller sizes. This is the root of most of my train woes (aside from LTN issues, which are a whole other issue!)


> Signals indicate whether the next segment is occupied, not whether any given train will fit in there (and potentially block a segment or intersection behind it.)

That's what chain signals are for. If a train waiting at a signal causes issues, replace the previous signal with a chain signal to prevent the train from problematically waiting at the signal.


> they lose the master password

The threat model for every lambda user having a password manager does not cover breaking and entering[0]: they should write down their master password and keep it at home in their bedroom drawer.

Use biometrics where possible (e.g. bitwarden on Android has that option)

[0] maybe it does for you, working on some DoD-confidential docs, but your computer-illiterate aunt doesn't.


I did that for my mother.

She lost it anyway. TWICE.

As for bio-metrics they are not possible on all devices, and some software will require you to enter the master password once in a while even if it's activated.

But even if it was not the case, if you loose your device, you need to setup the new one, and for that, you need the master password or have backups.

Back to square one.


It's only now added as an interactive step in the install script. It has ~always been possible to create a crypto device with the install medium by dropping to a shell: https://www.openbsd.org/faq/faq14.html#softraidFDE


> You can stack storage to your heart's content

Unless you actually hit the maximum your building can sustain (heat, volume). Building datacenters is incredibly expensive, so reusing existing infrastructure and packing it with more is actually important.


As specified when activating MFA, did you download (and print) your backup codes? If so, use them to re-enroll a new device into MFA.

If not, you can try reaching out to customer service after you get a new SIM card.

For banking and everything else IRL, you can just walk up to the teller with your ID.


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

Search: