Créer un compteSe connecter

Recherches récentes

Aucune recherche récente

Options de recherche

Disponible uniquement lorsque vous êtes connecté.
mastouille.fr est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastouille est une instance Mastodon durable, ouverte, et hébergée en France.

Administré par :

Statistiques du serveur :

701
comptes actifs

mastouille.fr: À proposAnnuaire des profilsPolitique de confidentialité

Mastodon: À proposTélécharger l’applicationRaccourcis clavierVoir le code sourcev4.3.4

#netbsd

11 messages11 participants0 message aujourd’hui
Public
Raven

Today is orange flag day! I will experiment with NetBSD as I want to see how it compares to FreeBSD and OpenBSD and possibly use it as a new host operating system for my virtual machines

@stefano has made the best advertisement for NetBSD with the 10 year old server that's possibly still running as of today 😉

#netbsd
A répondu dans un fil de discussion
Public
R.L. Dane :Debian: :OpenBSD: 🍵

@MekahimeAkari

No idea, unless it's just another case of parallel evolution.

Gnu's manpage doesn't make mention of #POSIX. The info page might, but who's got time to faff with that? XD

#FreeBSD's manpage says,

STANDARDS
       The date utility is expected to be  compatible  with  IEEE  Std  1003.2
       ("POSIX.2").   With the exception of the -u option, all options are ex-
       tensions to the standard.

#OpenBSD's says,

STANDARDS

The date utility is compliant with the IEEE Std 1003.1-2008 (“POSIX.1”)
specification.

The flags [-afjrz], as well as the conversion specifiers ‘%F’, ‘%G’, ‘%g’, ‘%k’,
‘%l’, ‘%R’, ‘%s’, ‘%v’, and ‘%+’, are extensions to that specification.

This implementation requires the traditional BSD date format, [[[[[cc]yy]mm]dd]
HH]MM[.SS], which differs from the X/Open System Interfaces option of the IEEE
Std 1003.1-2008 (“POSIX.1”) specification.

#NetBSD:

STANDARDS

     The date utility is expected to be compatible with IEEE Std 1003.2
     (``POSIX.2'').  However, achieving true compatability requires running
     date with the environment variable POSIXLY_CORRECT set, in order to parse
     the time string in the archaic format POSIX demands, rather than the more
     rational version described above.
Public *
R.L. Dane :Debian: :OpenBSD: 🍵 
function dateFromEpoch() {
    case $(uname) in
        Linux|NetBSD)       date -d @$1 "$2";;
        FreeBSD|OpenBSD)    date -r $1 "$2";;
    esac
}

Ehhh, STANDARDS. Who really needs 'em?

🤣🤦‍♂️

P.S., to be fair, Linux is the only OS I've tried that refuses to recognize date -r. #NetBSD interestingly accepts both forms:

rldane@rosa.tilde.pink$ uname
NetBSD
rldane@rosa.tilde.pink$ date -r 1746797092
Fri May  9 13:24:52 UTC 2025
rldane@rosa.tilde.pink$ date -d @1746797092
Fri May  9 13:24:52 UTC 2025
rldane@rosa.tilde.pink$
A répondu dans un fil de discussion
Public
Kevin Karhan :verified:

@wolf480pl So yeah, I think that everything has compromises to some extent.

  • I'm shure #OpenBSD could even up their #security if they were willing to break #POSIX and #compatibility in general for their distro, but that'll only introduce more headaches and pain along the way.

I chose #Linux as basis for @OS1337 because it solves the #driver problem for me and I know it. I'm just complete shit with #NetBSD which may arguably be the better option targeting low-end systems, but that'll again result in more pain and frustration getting other #apps ported over when I can't just say: "Target linux-#i486 and statically compile in all your dependencies" to any 3rd party as starting point.

Public *
Paul Buetow

Wondering how well #NetBSD would work on my old #ThinkPad X240. I've read mixed successes but they were a bit older. I am thinking to set it up as a single-purpose machine. I want to use it only to help learning Bulgarian, e.g. dictionary, translator, etc, (I moved to Bulgaria recently and am still learning the language), without all the other distractions out there in the apps I usually have all the time running. Why #NetBSD? Because I haven't used it in a while. Will try it out.

Public
chesheer

I've been reading an interesting article by Liguo Yu et. al., "Maintainability of the kernels of open-source operating systems: A comparison of Linux with FreeBSD, NetBSD, and OpenBSD" (DOI: 10.1016/j.jss.2005.08.014). Keep in mind, the article is from 2005 (published in 2006), so it would be interesting to know how things have changed since then. We are talking here about #Linux 2,4,20, #FreeBSD 5.1, #NetBSD 1.6 and #OpenBSD 3.3.
The article basically explores maintainability of said OSes judging mainly by usage of global variables.
Here's some interesting takeouts.
"Unsafe definition" is in their terms a usage of global variables between kernel modules and non-kernel modules.

Two graphs showing number of global variables and unsafe definitions in Linux and three BSDs. Linux has significantly more of both.
A répondu dans un fil de discussion
Public
Bitslingers-R-Us

@jfparis @stefano A full ./build.sh -D ../dest-evbarm -O ../obj-evbarm -T ../tools -R ../sets -m evbarm -a earmv6hf -x tools distribution sets takes about 4 days and 22 hours at 1 GHz on a microSD card.

The same takes 12.25 minutes on a Ryzen 7900, less time than it takes to run install=/ on the Pi Zero (17.25 minutes) :P

I just had to know!

#NetBSD
ExplorerFlux en direct
À propos