home.social

Search

689 results for “RL_Dane”

  1. @rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.

  2. @rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.

  3. @rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.

  4. @rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.

  5. @rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.

  6. @rl_dane

    The alternative is to make the shell handle the un-escaping:

    echo hello,there |sed 's/,/'"\n"'/g'

    It's undocumented in several ksh flavours, but nonetheless works. However, those flavours also (trying a quick few tests) support the better way, which is also undocumented though:

    echo hello,there |sed $'s/,/\n/g'

    #sed #UnixShells #KornShell #OpenBSD #ksh

  7. @rl_dane correction, for giggles on OpenBSD:

    echo hello,earth |sed 's/,/\n/g'

    #OpenBSD #peaceonearth

  8. @rl_dane

    Unless the "meme language" is #awk or Forth, in which case I might consider it 😆

  9. @rl_dane

    Unless the "meme language" is #awk or Forth, in which case I might consider it 😆

  10. @rl_dane

    Unless the "meme language" is #awk or Forth, in which case I might consider it 😆

  11. @rl_dane

    Unless the "meme language" is #awk or Forth, in which case I might consider it 😆

  12. @rl_dane

    Unless the "meme language" is #awk or Forth, in which case I might consider it 😆

  13. @rl_dane It handled it OK, actually. Definitely slowed down :D

    I was wondering if it would give me 's warning about opening too many programs at once, when I once accidentally did the thing I did on purpose here but on Windows XP.

  14. @rl_dane @EF

    Yes. The #OpenBSD version does not work as-is anywhere else. Basically: either one modifies the code to conditionally-compile out the OpenBSDisms and loses functionality, or one takes the OpenBSDisms out completely and replaces them with sudoisms.

    news.ycombinator.com/item?id=3

    news.ycombinator.com/item?id=3

    #FreeBSD, #NetBSD, and #Arch Linux have both Smith's and Overbruck's versions; #Debian Linux only the latter; #SmartOS only the former.

    @ianthetechie @tubsta @dexter
    #doas #sudo

  15. @rl_dane @EF

    Yes. The #OpenBSD version does not work as-is anywhere else. Basically: either one modifies the code to conditionally-compile out the OpenBSDisms and loses functionality, or one takes the OpenBSDisms out completely and replaces them with sudoisms.

    news.ycombinator.com/item?id=3

    news.ycombinator.com/item?id=3

    #FreeBSD, #NetBSD, and #Arch Linux have both Smith's and Overbruck's versions; #Debian Linux only the latter; #SmartOS only the former.

    @ianthetechie @tubsta @dexter
    #doas #sudo

  16. @rl_dane @EF

    Yes. The #OpenBSD version does not work as-is anywhere else. Basically: either one modifies the code to conditionally-compile out the OpenBSDisms and loses functionality, or one takes the OpenBSDisms out completely and replaces them with sudoisms.

    news.ycombinator.com/item?id=3

    news.ycombinator.com/item?id=3

    #FreeBSD, #NetBSD, and #Arch Linux have both Smith's and Overbruck's versions; #Debian Linux only the latter; #SmartOS only the former.

    @ianthetechie @tubsta @dexter
    #doas #sudo

  17. @rl_dane @EF

    Yes. The #OpenBSD version does not work as-is anywhere else. Basically: either one modifies the code to conditionally-compile out the OpenBSDisms and loses functionality, or one takes the OpenBSDisms out completely and replaces them with sudoisms.

    news.ycombinator.com/item?id=3

    news.ycombinator.com/item?id=3

    #FreeBSD, #NetBSD, and #Arch Linux have both Smith's and Overbruck's versions; #Debian Linux only the latter; #SmartOS only the former.

    @ianthetechie @tubsta @dexter
    #doas #sudo

  18. @rl_dane @EF

    Yes. The #OpenBSD version does not work as-is anywhere else. Basically: either one modifies the code to conditionally-compile out the OpenBSDisms and loses functionality, or one takes the OpenBSDisms out completely and replaces them with sudoisms.

    news.ycombinator.com/item?id=3

    news.ycombinator.com/item?id=3

    #FreeBSD, #NetBSD, and #Arch Linux have both Smith's and Overbruck's versions; #Debian Linux only the latter; #SmartOS only the former.

    @ianthetechie @tubsta @dexter
    #doas #sudo

  19. @rl_dane @dexter

    One would have to touch the #FreeBSD kernel to get the full #OpenBSD functionality.

    OpenBSD provides doas with a way to persist, by storing data in the session structure associated with the controlling terminal. FreeBSD would need to have that added.

    The OpenDOAS fork (in FreeBSD ports) uses the more problematic flag files, per sudo, that OpenBSD was trying to get away from. So one must avoid starting from that instead of the original, moreover.

    #doas #OpenDOAS

  20. @rl_dane @dexter

    One would have to touch the #FreeBSD kernel to get the full #OpenBSD functionality.

    OpenBSD provides doas with a way to persist, by storing data in the session structure associated with the controlling terminal. FreeBSD would need to have that added.

    The OpenDOAS fork (in FreeBSD ports) uses the more problematic flag files, per sudo, that OpenBSD was trying to get away from. So one must avoid starting from that instead of the original, moreover.

    #doas #OpenDOAS

  21. @rl_dane @dexter

    One would have to touch the #FreeBSD kernel to get the full #OpenBSD functionality.

    OpenBSD provides doas with a way to persist, by storing data in the session structure associated with the controlling terminal. FreeBSD would need to have that added.

    The OpenDOAS fork (in FreeBSD ports) uses the more problematic flag files, per sudo, that OpenBSD was trying to get away from. So one must avoid starting from that instead of the original, moreover.

    #doas #OpenDOAS

  22. @rl_dane @dexter

    One would have to touch the #FreeBSD kernel to get the full #OpenBSD functionality.

    OpenBSD provides doas with a way to persist, by storing data in the session structure associated with the controlling terminal. FreeBSD would need to have that added.

    The OpenDOAS fork (in FreeBSD ports) uses the more problematic flag files, per sudo, that OpenBSD was trying to get away from. So one must avoid starting from that instead of the original, moreover.

    #doas #OpenDOAS

  23. @rl_dane @dexter

    One would have to touch the #FreeBSD kernel to get the full #OpenBSD functionality.

    OpenBSD provides doas with a way to persist, by storing data in the session structure associated with the controlling terminal. FreeBSD would need to have that added.

    The OpenDOAS fork (in FreeBSD ports) uses the more problematic flag files, per sudo, that OpenBSD was trying to get away from. So one must avoid starting from that instead of the original, moreover.

    #doas #OpenDOAS

  24. @rl_dane

    curl log with transfer succes

    wttr.in/nieuw_amsterdam_suriname

    $ curl --verbose wttr.in/nieuw_amsterdam_suriname|lolcat
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 5.9.243.187:80...
    * Connected to wttr.in (5.9.243.187) port 80 (#0)
    > GET /nieuw_amsterdam_suriname HTTP/1.1
    > Host: wttr.in
    > User-Agent: curl/7.88.1
    > Accept: */*
    >
    0 0 0 0 0 0 0 0 --:--:-- 0:00:06 --:--:-- 0< HTTP/1.1 200 OK
    < Access-Control-Allow-Origin: *
    < Content-Length: 9015
    < Content-Type: text/plain; charset=utf-8
    < Date: Sun, 15 Feb 2026 20:29:33 GMT
    <
    { [1209 bytes data]
    100 9015 100 9015 0 0 1393 0 0:00:06 0:00:06 --:--:-- 2197
    * Connection #0 to host wttr.in left intact

    ^Z

    the screen cap is also included

    syntax:

    `xfce4-screenshooter -S -d 2 --window -s "$HOME/Pictures/$(date +%Y-%m-%d_%H-%M-%S)_Screenshot2.png"`

    #weather #curl #libcurl #programming #technology #networking #protocols #ftp #http #https #ports #OpenSource #POSIX #Physics #Chemistry #Lineair #Algebra #Mathematics #Logic

  25. @rl_dane

    It does. In the log you'll see how the handshake goes. The server checks the port then checks the user agent before it continues. At this point in time curl talks to a server park which is loaded heavily so I'm not getting more than the current log output. It's enough to respond to your question

    Log

    $ curl wttr.in/nieuw_amsterdam_suriname|lolcat
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- 0:01:49 --:--:-- 0^C

    slow response atm

    $ curl --verbose wttr.in/nieuw_amsterdam_suriname|lolcat
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 5.9.243.187:80...
    0 0 0 0 0 0 0 0 --:--:-- 0:00:11 --:--:-- 0* Connected to wttr.in (5.9.243.187) port 80 (#0)
    0 0 0 0 0 0 0 0 --:--:-- 0:00:11 --:--:-- 0> GET /nieuw_amsterdam_suriname HTTP/1.1
    > Host: wttr.in
    > User-Agent: curl/7.88.1
    > Accept: */*
    >
    0 0 0 0 0 0 0 0 --:--:-- 0:00:23 --:--:-- 0* Recv failure: Connection reset by peer
    0 0 0 0 0 0 0 0 --:--:-- 0:00:24 --:--:-- 0
    * Closing connection 0
    curl: (56) Recv failure: Connection reset by peer

    ^Z

    #Weather #wttr #meteorology #technology #curl #Physics #Chemistry #Mathematics #lineair #algebra #technology #OpenSource #programming #POSIX #energy

  26. @rl_dane

    So true
    The bandwidth limit I was referring to is that of wttr in
    The owner has put up an amount per day that is allowed to be used. People who come in on Port 443 via browser get much much lower priority than people who come in through curl. The browser response uses more bandwidth from the server, which makes the decision logical

    #Weather #wttr #meteorology #Physics #Chemistry #Mathematics #lineair #algebra #technology #OpenSource #programming #POSIX #technology

  27. @rl_dane
    I have to state that there are still multi button gaming mice available, where you can assign different functions to them, including scroll wheels, in both Open Source Operating Systems and Closed Source.
    In your case you would disable the scroll wheel. However I have the feeling that's not what you're looking for.

    You don't want a scroll wheel at all.

    That means that it is an ergonomic preference

    Are my assumptions true?

    #Mouse #gaming #scroll #wheel #five #buttons #technology #ball

  28. @rl_dane the combination of True three button mouse without scroll wheel is special

    I always need the scroll wheel even if there's an actual seperate third button just like the Logitech gaming mouse that I've had 30 years ago. That mouse had five buttons

    #Mouse #gaming #scroll #wheel #five #buttons #technology #ball

  29. @rl_dane

    When I have the bandwidth I will download the set and play with it, including archivers.
    However I'm certain it's available in zip format
    Check the torrents

    #Programming #Pile #program #OpenSource #LLM #slop #AI #technology #dataset