Hi , can anyone please guide me on how do i go about getting the CPU Usage and available free physical and virtual memories?
i know i can get it by using prstat, but i want to get an overall CPU Usage and not a breakdown of all same for the free physical and virtual memories ? (2 Replies)
Hello,
I am installing RX7640 and i have some issue with the memory modules. My system shows them as deconfigured.
Do you think I use the right memories? (2 Replies)
Hi guys and gals...
Who still plays with the AMIGA in any of its guises?
I have a classic A1200(HD) on 24/7 and still build and code for it...
Also _clones_ of the same machine using WinUAE and E-UAE...
It still has that one major beauty for this 62 year old - moi - it is FUN! ;o) (2 Replies)
Well I wrote this in 2005 and uploaded to AMINET.as a commemoration of a machine that is still in use today.
It is now 29 years since this machne came into being. Phenominal and it is still being supported- WOW!
My A1200 is on 24/7 and I use it to test code developed on AMIGA emulators...
... (0 Replies)
Hi guys...
For the AMIGA fans out there...
Not sure if this is the right forum but someone has done a successful working port of gcc for the classic AMIGA A1200.
It contains a very large subset of *NIX commands and now AMIGA fanatics like me can include another platform, within the... (0 Replies)
I don't know if anyone is interested but I have been meddling with FFT for the AMIGA.
(Sadly we AMIGAns don't have these luxuries through any scripting language.
Below is a Python snippet that uses the builtin 'cmath' module to work with the lowly
Python 2.0.1 for the AMIGA. It is part of a... (0 Replies)
Discussion started by: wisecracker
0 Replies
LEARN ABOUT PLAN9
attach
ATTACH(5) File Formats Manual ATTACH(5)NAME
attach, session, nop - messages to initiate activity
SYNOPSIS
Tnop tag[2]
Rnop tag[2]
Tsession tag[2] chal[8]
Rsession tag[2] chal[8] authid[28] authdom[48]
Tattach tag[2] fid[2] uid[28] aname[28] ticket[72] auth[13]
Rattach tag[2] fid[2] qid[8] rauth[13]
DESCRIPTION
The nop request does nothing overt but may be used to synchronize the channel between two service hosts initially.
The session request is used to initialize a connection between a client and a server. All outstanding I/O on the connection is aborted.
The set of messages between session requests is called a session. The host's user name (authid) and its authentication domain (authdom)
identify the key to be used when authenticating to this host. The exchanged challenges (chal) are used in the authentication algorithm.
If authid is a null string no authentication is performed in this session.
The tag should be NOTAG (value 0xFFFF) for a nop or session message.
The attach message serves as a fresh introduction from a user on the client machine to a server. The message identifies the user (uid) and
may select the file tree to access (aname). The ticket and auth arguments contains authorization data derived from the exchanged chal-
lenges of the session message; see auth(6).
As a result of the attach transaction, the client will have a connection to the root directory of the desired file tree, represented by
fid. An error is returned if fid is already in use. The server's idea of the root of the file tree is represented by the returned qid.
ENTRY POINTS
An attach transaction will be generated for kernel devices (see intro(3)) when a system call evaluates a file name beginning with Pipe(2)
generates an attach on the kernel device pipe(3). The mount system call (see bind(2)) generates an attach messages to the remote file
server. When the kernel boots, an attach is made to the root device, root(3), and then an attach is made to the requested file server
machine.
SEE ALSO auth(6)ATTACH(5)