It's easy but you're complicated.
--
Aram Hăvărneanu
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T000c7f7d66260ba3-M4820b11cc08bf4aa0d58cc4d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
gt;
Perhaps you should fork 9legacy and rename $objtype to aarch64.
--
Aram Hăvărneanu
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T7409a8df6326c959-M69a58820b3814d2e4fbf1be1
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
s fine if you do not agree with these decisions.
--
Aram Hăvărneanu
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T000c7f7d66260ba3-Mebd6b59cb5583e354a55a3d8
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Since Charles wrote the arm64 compiler, he can call it whatever he wants.
--
Aram Hăvărneanu
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T000c7f7d66260ba3-M4e50b3b8d6464665cbeb69f0
Delivery options: https://9fans.topicbox.com
retailers that lied about having stock
stock. I got three. With these three, I have in total about ten
spares, which I hope will last me for a while.
--
Aram Hăvărneanu
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T49f3cceea70d2b61
So what's the plan?
--
Aram Hăvărneanu
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T72dd761e0f95baf7-Ma68691f11b8174583c457e13
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
My e-mail client decided to mark this thread as read. I am glad it did.
--
Aram Hăvărneanu
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T9ef6430f3025e731-M19d5cd1a3c6215f93b235b39
Delivery options: https://9fans.topicbox.com/groups
Research Unix and a liberated Plan 9. Never thought I'd see the
day. Amazing.
--
Aram Hăvărneanu
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tf20bce89ef96d4b6-Mf5070050ea6955fd06f25044
Delivery options: https://9fans.topicbo
Steve and Richard,
You are a bunch of hypocrites. Bitter old men.
--
Aram Hăvărneanu
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tf27e6479d8812712-M08bfe720c68d2b835d25e368
Delivery options: https://9fans.topicbox.com/groups/9fans
https://www.contourdesign.com/product/contour-mouse/
--
Aram Hăvărneanu
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Teef4e32e6f6c10de-Mb656c0b0c50d1ac47b9c9d5a
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Test.
--
Aram Hăvărneanu
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T73a7388a716e3644-M4477ede150279a780653725c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
> Posted August 15th, 2013:
> https://9p.io/sources/contrib/stallion/src/sdmpt2.c Corresponding
> announcement:
> https://groups.google.com/forum/#!topic/comp.os.plan9/134-YyYnfbQ
This is not a NVMe driver.
--
Aram Hăvărneanu
> given the attitudes that seem so prevalent these days.
You are mistaken, it has always been like this.
--
Aram Hăvărneanu
OH MY GOD, I installed plan9port so hard right now.
--
Aram Hăvărneanu
On Thu, Oct 4, 2018 at 5:49 AM, wrote:
> what is the point of this exercise?
>
To appear stupid, apparently,
--
Aram Hăvărneanu
> since it's not the original rio in plan9port, how about renaming
> it to rioc (rio clone)?
How about no.
--
Aram Hăvărneanu
It's easy but you're complicated.
--
Aram Hăvărneanu
> i had been trying to work with a collaborator to develop a complete,
> installable system for plan9port.
Plan9port is already installable.
--
Aram Hăvărneanu
Looks pretty portable, the only Linux-specific things seem to be
non-essential sandboxing stuff, e.g. seccomp, and the only
Unix-specific dependency is on ptrace. Should not be too hard to make
it into linuxemu on Plan 9.
--
Aram Hăvărneanu
> I don't think anyone is running it anymore.
> At least, I'm not running it.
> Sorry.
What do you run?
--
Aram Hăvărneanu
Hardly.
--
Aram Hăvărneanu
understanding if the usual, desired mode of
operation is through the file system or through the protocols
directly, via libraries and commands.
--
Aram Hăvărneanu
iagnostic
> "Installation directory must be on a local hard drive", which is slightly
> ironic in the circumstances.
Upspin does not currently work on Windows, but if you need Go on
Windows you don't need to use the Go installer, unzipping the zip file
will suffice (and works in any directory)
--
Aram Hăvărneanu
There are cheaper ways of disposing of 10TB of data.
--
Aram Hăvărneanu
One day I will write a samterm that works like acme. I mostly use
acme, but sometimes on Unix I have to use sam because only sam can do
"sam -r".
--
Aram Hăvărneanu
You're asking the wrong questions.
--
Aram Hăvărneanu
he Plan 9 calling convention.
Doing a rump port with gcc, cross-compiling on Unix and running on
Plan 9, should be easy though.
--
Aram Hăvărneanu
What problem would this solve, it's not like netsurf can display any
useful web page that mothra can't display.
--
Aram Hăvărneanu
it done twice (actually three times), I'd say it's about 7x-10x
more work to re-target the Go toolchain than it is to re-target the
Plan 9 toolchain.
Mind you, compared to gcc and clang, 7x-10x more work is still
pretty good...
--
Aram Hăvărneanu
To add some more on my previous post, yes, there are inconsistencies,
but the common syntax still help tremendously, so much that
translating between power and arm64 assembly has been mostly achieved
through sam(1).
--
Aram Hăvărneanu
c instructions
on ARM64 come to mind. Note that printing is still in "from, reg,
from3, to" order, so printing these instructions (7a -S) will print
something different than the input. This has been fixed in Go.
--
Aram Hăvărneanu
between architectures.
--
Aram Hăvărneanu
Yes, on Plan 9, on amd64, only one register is used (as explained by
Charles). Go doesn't use any registers for argument passing (even on
Plan 9).
You can just run 6c -S to see these things yourself.
--
Aram Hăvărneanu
than that?).
Only one single person noticed, and that was months later after the
fact. That serves as a useful test to gauge interest (and quality) in
Go on Plan 9.
--
Aram Hăvărneanu
Mercurial works.
--
Aram Hăvărneanu
On Fri, Oct 2, 2015 at 10:32 AM, hiro <23h...@gmail.com> wrote:
> Is the git protocol really so huge that a native implementation
> wouldn't be feasible?
The git protocol and file format is very simple. I'm sure it's easier
to write something from scratch than port git.
--
Aram Hăvărneanu
https://swtch.com/lsr.c
https://github.com/4ad/mgk.ro/blob/master/cmd/lsr/lsr.go
--
Aram Hăvărneanu
On Wed, Sep 9, 2015 at 9:52 AM, Jeremy Jackins wrote:
> This repo is not a part of the Go project, though.
It uses the same procedure, though.
See plan9port's codereview(1).
--
Aram Hăvărneanu
On Thu, Sep 3, 2015 at 3:11 PM, erik quanstrom wrote:
> because the keyboard doesn't pass modal presses to user space
There has been solved in 9front in 2011: http://man.cat-v.org/9front/8/kbdfs
--
Aram Hăvărneanu
t GCC compiling Plan 9 at a speed reasonably comparable to kencc.
I will refrain making comments on how wise that is, however.
--
Aram Hăvărneanu
Maybe I am working on a port to X-Gene, or maybe I am not.
--
Aram Hăvărneanu
o copying one is an O(n) operation.
--
Aram Hăvărneanu
http://blog.golang.org/slices
http://blog.golang.org/go-slices-usage-and-internals
--
Aram Hăvărneanu
I have not been able to compile vx32 since 10.7 I think.
--
Aram Hăvărneanu
This happens to me sporadically on ThinkPad T400. I can fix it by rebooting.
--
Aram Hăvărneanu
It's pretty interesting that at least three people all got exactly
150kB/s on vastly different machines, both real and virtual. Maybe the
number comes from some tick frequency?
--
Aram Hăvărneanu
mance is not the
issue. The problem is that the mere presence of Plan 9 venti induces
this problem somewhere else (fossil or the kernel).
--
Aram Hăvărneanu
On Wed, Mar 11, 2015 at 10:04 PM, Ryan Gonzalez wrote:
> As you can see, Go actually had a working 64-bit compiler.
Plan 9 and Inferno have working 64-bit compilers. They are used for
the many Plan 9 amd64 kernels. Go's C compilers all came from Inferno,
including 6c.
--
Aram Hăvărneanu
u'd need *a lot* of work, much more work than by
starting with the Plan 9/Inferno/Ken-cc directly.
--
Aram Hăvărneanu
It doesn't come with a suitable libc that you expect.
--
Aram Hăvărneanu
The Plan 9 C compilers included with Go have been removed for some
time. Also they worked quite differently than the Plan 9 ones because
of liblink.
The Plan 9 linker also supports ELF, although it lacks DWARF and a
symbol table in the generated binaries.
--
Aram Hăvărneanu
On Fri, Mar 6, 2015 at 12:59 PM, wrote:
> I think it's fair for Google to devote help for softwares that do have
> huge problems
Correct. phpMyAdmin has huge problems.
--
Aram Hăvărneanu
On Wed, Mar 4, 2015 at 5:13 PM, Giacomo Tesio wrote:
>
> why the hell we still use troff for manual pages?
What do you propose we use instead?
--
Aram Hăvărneanu
On Thu, Feb 26, 2015 at 6:04 PM, Jeff Sickel wrote:
> That would be a good GSOC project.
I haven't realized OS X has a GSoC now.
--
Aram Hăvărneanu
use 9term you can even plumb normally.
--
Aram Hăvărneanu
I am not sure I understand the question. Programming in Go on Plan 9
is almost the same as programming in Go in Unix. The "setup" is the
same.
--
Aram Hăvărneanu
On Wed, Nov 19, 2014 at 3:36 PM, erik quanstrom wrote:
> by the way, at one point i had a hacked up kernel which allowed me to
> mount a file server over the cec protocol.
In what situation would this be useful?
--
Aram Hăvărneanu
If you must use a rpi, you should strive to use it as a terminal, and
like every other Plan 9 terminal it should use the central file server
without local storage.
--
Aram Hăvărneanu
The startup file is there exactly to teach you about these things, you
should read it.
--
Aram Hăvărneanu
You have to mmap an executable region of memory, but it is doable in
almost all cases (certainly for every desktop).
--
Aram Hăvărneanu
You can generate the PDFs from the troff sources. The printed manual
is very old, albeit very nice to have as a historical artifact.
--
Aram Hăvărneanu
On Sun, Jul 20, 2014 at 3:42 AM, wrote:
> removed the saving and restoring
> of DS/ES/FS/GS segment registers... they have no effect in long mode
Actually FS and GS do work in long mode. Since we don't need them for
TLS, maybe we can do something useful with them.
--
Aram Hăvărneanu
On Sat, Jul 19, 2014 at 9:20 PM, Christopher Nielsen wrote:
> Not to mention heartbleed has nothing to do with ssh... It was an
> implementation bug in openssl only; it wasn't even a protocol bug.
Yes, OpenSSH doesn't even use OpenSSL.
--
Aram Hăvărneanu
his for the plan9/386 Go port and made the plan9/amd64
Go port use the same mechanism.
--
Aram Hăvărneanu
9 is not Unix.
Combining the Plan 9 model with orthogonal Plan 9 primitives gives
you a much richer and cleaner environment that all falls naturally
from the design of the system, rather than having all features
backed in the vcs blob.
--
Aram Hăvărneanu
On Sat, Jul 19, 2014 at 2:42 PM, Charles Forsyth
wrote:
> _tos only works when every process has
> at least one stack always at the same fixed virtual address.
Isn't this always true?
--
Aram Hăvărneanu
I don't have any opinion on whether R14 and R15 should be saved, but
the justification posted in the top post seems weak.
The stack is already per-process data. One can use _tos for per-proc
data, just like privalloc(2) does.
--
Aram Hăvărneanu
t and
mercurial. What git does better (at least according to some people),
is patch management. The Labs and 9atom use some patch management
technology best described in their manuals rather than on the mailing
list. 9front uses mercurial for patch management.
--
Aram Hăvărneanu
On Wed, Jul 16, 2014 at 7:31 PM, Lee Fallat wrote:
> This has been done for 9front.
Only partially. The tag expands to multiple lines, but does not accept
newlines. Also, sl is right.
--
Aram Hăvărneanu
This works:
addpsfonts /sys/doc/backup.ps | lp -H -dlexmarkx203n
Thanks David.
--
Aram Hăvărneanu
onts. What to do in this
case?
Thanks,
--
Aram Hăvărneanu
test -f /lib/face/48x48x1/u/unknown.1
test -r /lib/face/48x48x2/u/unknown.1
cat
cat
cat
exit ''
exit
wait
rm -f /tmp/lp107693
exit
rm -f /tmp/lp107693
exit
exit 'lpdspool 107692: |lpdsend 107695: 1'
exit ''
There is no effect on the printer.
I can use this printer on Linux, BSD and OS X through LPR + generic
postscript driver (no special Lexmark drivers).
What to do?
Thanks,
--
Aram Hăvărneanu
What BIOS?
--
Aram Hăvărneanu
QEMU I am using has
a bug where it can't PXE-boot with more than one NIC. On my CPU
servers I just import /net from my primary fs/cpu/auth server, and
to access the CPU server directly I just use aux/trampoline.
--
Aram Hăvărneanu
> & if the acme tags show
> $foo/file1
> $foo/file2
> it would be much nicer.
Real paths are plumbable and copyable, variable names are not. p9p
acme (where this problem is more acute) has multiline tags.
--
Aram Hăvărneanu
On Sat, Jun 7, 2014 at 1:24 PM, Ramakrishnan Muthukrishnan
wrote:
> it hangs after printing:
> ...
> init: starting /bin/rc
Probably a problem with timesync(8), disable it in your cpurc/termrc.
--
Aram Hăvărneanu
ssh2 doesn't work with passwords (at least not without changing server
settings), you need to use keys.
--
Aram Hăvărneanu
scribed in the "key
management" section of ssh2(1). Use auth/rsagen to generate the key
and add it to factotum, copy the public key from factotum and use
rsa2ssh2 to convert it to the format Unix ssh understands, copy public
key to .ssh/authorized_keys on the Unix host.
I use secstore t
17
23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64 x86_64
: iridium:aram; logout
cpu%
I didn't do anything more special except adding keys to factotum.
--
Aram Hăvărneanu
I'm using it only as a client. I don't see the point in using it in
other capacity on Plan 9.
--
Aram Hăvărneanu
> I’ve never been able to get the ssh v2 version to work on Plan 9 for testing.
Never had any major problem[1] with ssh2 (using the one from labs, with
factotum, not nfactotum).
[1] a small problem is that I needed to patch srvssh like this:
http://okturing.com/src/2230/body
--
Aram Hăvărneanu
Plan 9 doesn't have virtio ethernet driver (except mischief's, which I
don't think is ready for public consumption yet).
--
Aram Hăvărneanu
's clear that
> you enjoy it. It's also clear that nobody else cares any more.
Hey, we're not coming to your Googleplex to insult you, but you come
here to insult us. We don't serve koolaid here, so go back and drink
your koolaid at Google.
Thank you for choosing 9fans OSX/Linux. Have a nice day.
--
Aram Hăvărneanu
On Thu, May 22, 2014 at 6:17 PM, ron minnich wrote:
> has anyone looked at camlistore as a starting point? Written in Go,
> which means it works on Plan 9.
No, it doesn't. I uses FUSE for God's sake. Camlistore is also 65kLOC
--
Aram Hăvărneanu
> Ah, ruby, yet another technology I have zero use for on my systems.
That technology is already installed on your system.
--
Aram Hăvărneanu
t). 1.6.1 is not ancient
and I didn't even need to compile it. Plan 9 runs just fine. 2.0 I
compiled because I needed the new arm64 support. It wasn't hard.
--
Aram Hăvărneanu
> because they're using osx, and don't want to shell out for vmware.
QEMU works on OS X.
--
Aram Hăvărneanu
Why do people insist on VirtualBox? How many times it has to be said.
VirtualBox is utter shite. QEMU and VMware work. QEMU is especially
interesting because it can work without a broken kernel driver
(although it can use kvm, a good kernel driver on Linux).
--
Aram Hăvărneanu
have to decide whether to share something or not.
--
Aram Hăvărneanu
7;s 8c are different programs. Different calling
conventions, different output. Right now Go's 8c uses liblink and
generates machine code. .8 files cannot be consumed by Plan 9's 8l.
Even before liblink there were serious incompatibilities in the object
files.
8c is going away soon anyway,
; // a useless comment
> .
> w
> q
> EOF
> % cat <<'EOF' >/n/hg/ctl
> tag "rev1beta1" # tag this version
> note "added a silly comment to main.c and tagged this version
> as beta1" # commit string?
Somebody would have to write the code, right now hgfs is read-only.
I don't know how hard it would be. Are you offering?
--
Aram Hăvărneanu
On Thu, May 22, 2014 at 9:36 AM, wrote:
> ...
It would be nice if you didn't hijack other people's threads.
--
Aram Hăvărneanu
What are you talking about?
--
Aram Hăvărneanu
is problem doesn't exist in the port of
Go to Plan 9 anymore (although the fix was different)...
In short, I can't justify this new system call. I'm happy to be
educated, however.
--
Aram Hăvărneanu
It's easy to make it use clang directly (instead of gcc wrapper) and
compile it in 32-bit mode, the larger issue is that it uses an
obsolete devdraw implementation that doesn't compile in Mavericks any
more...
--
Aram Hăvărneanu
question is not why does Plan 9 compile so quickly, is what
catastrophe happened in Unix making everything so slow and large.
--
Aram Hăvărneanu
I PXE-boot most of them, yes.
--
Aram Hăvărneanu
member this ever
being a problem.
--
Aram Hăvărneanu
chines that all use vesa, all widescreen. I have
never seen a vesa BIOS that didn't provide widescreen modes. I'm sure
they exist, but they certainly are not rare. I drive 1920x1200x32 with
vesa and Cinap's realemu just fine.
--
Aram Hăvărneanu
FWIW I've found osxfuse pretty unstable, YMMV.
--
Aram Hăvărneanu
1 - 100 of 230 matches
Mail list logo
