5 ms·

Beginning with FreeBSD on exotic devices like these is going to ensure a poor first impression. Had she started on a standard x86_64 PC desktop or supported lap

by slacka 6y ago

Beginning with FreeBSD on exotic devices like these is going to ensure a poor first impression. Had she started on a standard x86_64 PC desktop or supported laptop like the thinkpads, she would have had much better results.

drewg123 6y ago
Yes and no.. She was using qemu/KVM on amd64 and had sendmail hang doing a DNS looking, blocking boot. I wish sendmail was not enabled by default. She could have just ^C'ed it, but coming from Linux, how was she supposed to know that?
- toast0 6y ago
  ^C on Linux used to work; that it doesn't under systemd (or at least Debian's default configuration of systemd) is on my list of grudges.
  - flatiron 6y ago
    my guess is because of the parallel startup that systemd does, what would the ctrl-c be stopping if there are multiple services coming up?
    - toast0 6y ago
      Whatever has been running without daemonizing for longest? Or just all the things currently running interactively. Or maybe just everything that hasn't started yet. Any option is better than having to chose between waiting indefinitely or hitting ctrl-alt-del and starting in single user mode and hoping to be able to disable it there.
  - naikrovek 6y ago
    SYSTEMD ITSELF is on my list of grudges.
- Lammy 6y ago
  > I wish sendmail was not enabled by default. Agreed that it's a poor default these days, but for what it's worth the option is available in the post-install setup interface alongside some other security tuning knobs.
- yjftsjthsd-h 6y ago
  The weird thing is that my FreeBSD laptop hangs at boot at that spot but it eventually continues, I assume after some timeout. Not sure why it didn't work for OP.
- xena 6y ago
  Wait you can control C it? I'm used to the boot process not accepting input.
  - Lammy 6y ago
    Yep, I use this all the time if I'm setting up a machine/network and am waiting on a `ifconfig_whatever="SYNCDHCP"` or a network drive mount that I know will never succeed.
  - bikenaga 6y ago
    I tried to bring up FreeBSD in a (amd64) qemu/kvm VM a couple of weeks ago, and the same sendmail/DNS lookup thing happened to me. I think I just waited (how long I don't recall) and the installer just went on - I don't think I did anything because I wouldn't have had any great ideas about what to do, anyway. So the install completed, and everything was fine as long as I stuck to command line stuff. But under xfce, mate, and even plain X Windows, the mouse had a jerky/laggy movement that I didn't know how to fix. I tried enabling/disabling moused but it didn't seem to have any effect. Maybe it was something about running in a VM, but I have no such problem running linux distros in a VM. Anyway, it was such a pain that I finally gave up.
amatecha 6y ago
Yeah, alternatively I'd imagine OpenBSD would have booted problem-free on RPi 4, which is mentioned specifically in the installation instructions at https://ftp.openbsd.org/pub/OpenBSD/6.8/arm64/INSTALL.arm64 https://ftp.openbsd.org/pub/OpenBSD/6.8/arm64/INSTALL.arm64 That said, I haven't tried OpenBSD on Pi nor have I yet tried FreeBSD -- just going by the official docs. :)
- xena 6y ago
  I will have to take a look at that! OpenBSD has been on my list for a while but I've never gotten around to using it successfully before.
justin66 6y ago
> exotic devices They’re on the Tier 2 support tier, not the Tier you’re foolish to even try to use this support tier. > Had she started on a standard x86_64 PC desktop or supported laptop like the thinkpads, she would have had much better results. On the other hand, if she owned the wrong laptop the entirety of the text might have been about making her touchpad work or something.

by slacka 6y ago

drewg123 6y ago

Yes and no.. She was using qemu/KVM on amd64 and had sendmail hang doing a DNS looking, blocking boot. I wish sendmail was not enabled by default. She could have just ^C'ed it, but coming from Linux, how was she supposed to know that?

toast0 6y ago
^C on Linux used to work; that it doesn't under systemd (or at least Debian's default configuration of systemd) is on my list of grudges.
- flatiron 6y ago
  my guess is because of the parallel startup that systemd does, what would the ctrl-c be stopping if there are multiple services coming up?
  - toast0 6y ago
    Whatever has been running without daemonizing for longest? Or just all the things currently running interactively. Or maybe just everything that hasn't started yet. Any option is better than having to chose between waiting indefinitely or hitting ctrl-alt-del and starting in single user mode and hoping to be able to disable it there.
- naikrovek 6y ago
  SYSTEMD ITSELF is on my list of grudges.
Lammy 6y ago
> I wish sendmail was not enabled by default. Agreed that it's a poor default these days, but for what it's worth the option is available in the post-install setup interface alongside some other security tuning knobs.
yjftsjthsd-h 6y ago
The weird thing is that my FreeBSD laptop hangs at boot at that spot but it eventually continues, I assume after some timeout. Not sure why it didn't work for OP.
xena 6y ago
Wait you can control C it? I'm used to the boot process not accepting input.
- Lammy 6y ago
  Yep, I use this all the time if I'm setting up a machine/network and am waiting on a `ifconfig_whatever="SYNCDHCP"` or a network drive mount that I know will never succeed.
- bikenaga 6y ago
  I tried to bring up FreeBSD in a (amd64) qemu/kvm VM a couple of weeks ago, and the same sendmail/DNS lookup thing happened to me. I think I just waited (how long I don't recall) and the installer just went on - I don't think I did anything because I wouldn't have had any great ideas about what to do, anyway. So the install completed, and everything was fine as long as I stuck to command line stuff. But under xfce, mate, and even plain X Windows, the mouse had a jerky/laggy movement that I didn't know how to fix. I tried enabling/disabling moused but it didn't seem to have any effect. Maybe it was something about running in a VM, but I have no such problem running linux distros in a VM. Anyway, it was such a pain that I finally gave up.

amatecha 6y ago

Yeah, alternatively I'd imagine OpenBSD would have booted problem-free on RPi 4, which is mentioned specifically in the installation instructions at https://ftp.openbsd.org/pub/OpenBSD/6.8/arm64/INSTALL.arm64 https://ftp.openbsd.org/pub/OpenBSD/6.8/arm64/INSTALL.arm64 That said, I haven't tried OpenBSD on Pi nor have I yet tried FreeBSD -- just going by the official docs. :)

xena 6y ago
I will have to take a look at that! OpenBSD has been on my list for a while but I've never gotten around to using it successfully before.

justin66 6y ago

> exotic devices They’re on the Tier 2 support tier, not the Tier you’re foolish to even try to use this support tier. > Had she started on a standard x86_64 PC desktop or supported laptop like the thinkpads, she would have had much better results. On the other hand, if she owned the wrong laptop the entirety of the text might have been about making her touchpad work or something.