9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Equivalent of Unix uname
Date: Sat, 9 Mar 2024 19:07:07 +0100	[thread overview]
Message-ID: <CAFSF3XNA+cUOTwk3-fVfuVfU=+Fw0SefG6YP9qMHXo1J+stwSg@mail.gmail.com> (raw)
In-Reply-To: <c1e9780d-33ce-4b84-948d-8257c204bd2b@posixcafe.org>

plan9 is distributed with binaries, but installations are kept
up-to-date via source updates from git, so in practice, before you run
sysupdate and mk install yourself you may check the current git
revision.

also keep in mind that in the canonical deployments you will have only
one central fileserver for all your cpu servers and terminals, so if
you know the version of one of your computers you should automatically
be able to imply the version of all other computers.

On 3/9/24, Jacob Moody <moody@posixcafe.org> wrote:
> On 3/9/24 11:31, rockyhotas@firemail.cc wrote:
>> Hello!
>> I'm trying to move the first steps into Plan9.
>> It is not Unix, the user is often warned about this. However, some tools
>> are available in both systems with almost the same usage, like uptime(1)
>> for example. Is there anything equivalent to `uname'? I couldn't find
>> such a tool nor in
>>
>>   <https://fqa.9front.org/fqa8.html>
>>
>> neither in
>>
>>   <https://wiki.9front.org/unix2plan9>
>>
>> If there is not a perfect equivalent tool, is it anyway possible to list
>> some basic information about the current system? For example the OS
>> name,
>> the kernel version, the architecture, the hostname.
>>
>> Bye!
>>
>> Rocky
>
> There is /dev/osversion but its not really particularly insightful.
> Uname is generally used to differentiate different Unixen from
> each other, so I don't see why it would be particularly useful
> on Plan 9.
>
> We also do not generally have version of the kernel per se,
> at least not in the same way something like Linux does.
> For architecture there is $cputype and for host name there
> is $sysname.
>
>
> Hope that helps,
> moody
>
>

  reply	other threads:[~2024-03-09 18:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09 17:31 rockyhotas
2024-03-09 17:42 ` B. Atticus Grobe
2024-03-09 18:07   ` Lucas Francesco
2024-03-09 17:42 ` Jacob Moody
2024-03-09 18:07   ` hiro [this message]
2024-03-10 16:28   ` Rocky Hotas
2024-03-09 19:32 ` Jon Sharp
2024-03-10 21:03 ` Eli Cohen
2024-03-10 21:07   ` Jacob Moody

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFSF3XNA+cUOTwk3-fVfuVfU=+Fw0SefG6YP9qMHXo1J+stwSg@mail.gmail.com' \
    --to=23hiro@gmail.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).