=) etsh-5.2.0 - https://etsh.io/src/ - is now available (= .. signed with my #OpenBSD #signify key it is .. yay ! #v6shell #etsh #ancient #opensource #UNIX #cli ( 2 ports of the original V6 Thompson shell )
#etsh: shells/etsh: #OpenBSD #Ports, brillante (shiny)!! - https://blog.v6shell.org/etsh-shells-etsh-openbsd-ports/ | #v6shell #opensource #UNIX #cli or #commandlineinterface: #OpenBSDPorts =^)
@vetelko Thanks for the follow
@v6shell also
"Commentary on the Sixth Edition UNIX Operating System"
https://www.openbsdfoundation.org/campaign2018.html
If your company uses #OpenBSD or its products (pf, openssh, libressl) bring up donations to keep this software project running that provides code that basically the entire internet runs on. It takes more than just good will to run this!
IMO individual users should consider monthly donations e.g. via PayPal.
Oh, ma manca poco più di una settimana a #HackIT e già c'è (quasi) un programma !?!?!
💣 👾
#HackIT18 #hm0x15
6-8 luglio a #Genova #falene
Just a week to go before #HackIT and we ALREADY have a (kind of) schedule?!!? 💣 👾
#moth #HackIT18 #hm0x15 6-8 july #Genova
Se manca una semana a #HackIT y ja tenemos (algo como) un programa? 💣 👾
#polillas #HackIT18 #hm0x15 6-8 julio #Genova
Regular reminder that if you use #OpenBSD, a great help to developers is to send your machines' dmesg outputs to dmesg <AT> openbsd.org.
If you'd like to help other *BSD users, regardless of what *BSD you use, submit your machines' dmesg outputs to http://dmesgd.nycbug.org/
It's free to do, and works best when we all chip in!
@v6shell Congrats!
Once I got over the initial stress and fear about moving my repos back to cvs ( from fossil and git ), and (re)learning how to do it without losing everything in the process... It's actually been fun and relaxing to sit down and move my projects that used to be on #GitHub to my own little self-hosted #cvs repository.
Almost ready to roll with cvsweb and anoncvs access as well .. Good fun all around it's turned out to be ! =^]
So... Sometime recently I looked in the mirror and thought.. Hmmm, no eres demasiado feo, tal vez guapo de hecho! 🤔😉😀 ( Jajajaj .. Divertido 🌞 )
So, I disabled HyperThreading (== proprietary Intel #smt implementation) on my Dell Inspiron 5567 laptop. So, I'll be ready when I see about up(dat|grad)ing tomorrow (or this weekend).
@lerk
Greetings lerk. Thanks for the follow. I'm a vegan too ( mostly. meaning, I rarely eat meat, as animals are friends. I do like eggs though. )
=)
% echo 'VSZ RSS COMMAND';\
ps mOvsz,rss ^ grep '[t]sh'
VSZ RSS COMMAND
416 1540 -etsh (etsh)
412 1528 etsh -l
320 1344 tsh
Statically though (to compare apples & apples)... etsh & tsh still use less memory (VSZ RSS) than ksh it seems...
720 884 -ksh (ksh)
428 568 ./etsh
236 368 ./tsh
and it makes me happy to know my babies aren't sucking up to much RAM =D
@mikeburns
Hello .. Thanks for the follow, if I may say so !
New #OpenBSD errata for 6.3, backporting the Intel FPU security fix. syspatch(8) now! (amd64) https://www.mail-archive.com/announce@openbsd.org/msg00213.html
=) etsh-5.2.0 - https://etsh.io/src/ - is now available (= .. signed with my #OpenBSD #signify key it is .. yay ! #v6shell #etsh #ancient #opensource #UNIX #cli ( 2 ports of the original V6 Thompson shell )
#EuroBSDCon presentation deadline is coming up on Sunday! Do you do cool stuff with #OpenBSD, #FreeBSD, #NetBSD (or any #BSD)? PS, yes you do. You should submit an abstract for a 45 minute presentation, and give a talk.
Travel, hotel, and entry will be covered for selected speakers!
The Clash of NGC 3256
Image Credit & License: NASA, ESA, Hubble Space Telescope
Colin Percival tweeted a short thread on the “Lazy FPU” vulnerability that was just disclosed (CVE-2018-3665).
Colin credits his learning about it to Theo de Raadt. Took him ~5 hours to come up with working exploit code.
https://twitter.com/cperciva/status/1007010583244230656?s=21
More info on seclists.org and discussion on lobste.rs.
http://seclists.org/oss-sec/2018/q2/189
https://lobste.rs/s/qotnxq/confirmed_speculative_register_leakage
#OpenBSD intuition regarding a new side-channel caused by the speculative execution on systems with lazy FPU context switching wasn't unsubstantiated. Intel has just published an avdisory: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00145.html