9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Lucas Francesco <lucas.francesco93@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Equivalent of Unix uname
Date: Sat, 9 Mar 2024 15:07:37 -0300	[thread overview]
Message-ID: <CAF=5iUVuzebd+xPGQ+0utj9kMjiShvM5AwOv+5BGtmejmcYwDw@mail.gmail.com> (raw)
In-Reply-To: <8769d936-b761-4dc6-950c-a9b2e8226c20@tcp80.org>

fwiw if you do need for sh shell scripts, ape/psh does mount an `uname
` command into your PATH, AFAIK there's no need for a uname command
elsewhere since we dont have a (updated) ssh server for you to connect
remotely and maybe get confused on where are you running things, and
even if we had, you can notice it due to lacking tty
emulation/interaction

On Sat, 9 Mar 2024 at 14:45, B. Atticus Grobe <grobe0ba@tcp80.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
>
> kernels aren't versioned. the os name isn't reported; you're expected to
> know you're on a plan 9 system. `echo $sysname' will tell you the system
> name. `echo $cputype' will tell you the arch.
>
> 9 doesn't need a uname command. $sysname matters depending on context,
> but $cputype really doesn't; the 9 compilers are natively cross-arch.
>

  reply	other threads:[~2024-03-09 18:11 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 [this message]
2024-03-09 17:42 ` Jacob Moody
2024-03-09 18:07   ` hiro
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='CAF=5iUVuzebd+xPGQ+0utj9kMjiShvM5AwOv+5BGtmejmcYwDw@mail.gmail.com' \
    --to=lucas.francesco93@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).