Re: [9fans] gar nix!
the trouble with the zeroing pages scheme, which has been done before (eg, having the process with least priority top up the memory), is that it was great when the system wasn't under load, just fine under increased load, but eventually, when you most want your cycles, you're back in the original situation. if you were able to hold usage below that level, it still worked against keeping more useful data cached in that memory. (in effect, you had a cache of zeroes.) in a similar way, there might be more useful things to do with your DMA cycles, which cost something too, and there are implications for power. the maths behind Working Set hasn't gone away just because the parameters got bigger. otherwise, it would never have been true.
Re: [9fans] gar nix!
sure but we are talking about x86_64, which has a limited number of possible page sizes no, it doesn't.
Re: [9fans] Announcing Inferno for Android phones
Any idea how much work it would be to adapt that for the nokia n900? No need for the android version on maemo - standard hosted inferno just works on the n900. I've been running it for quite a while (or was until my pocket was picked in Paris last week ☹). I'll have to go back to my n800 (=n900 without the phone part) which also runs standard inferno happily, after a small mod to win-x11a (in contrib/miller/inferno/n800). N900 is a nice device, but android phones can be a lot cheaper.
Re: [9fans] Announcing Inferno for Android phones
Good to know, thanks! On Sat, Sep 17, 2011 at 12:58 PM, Richard Miller 9f...@hamnavoe.com wrote: Any idea how much work it would be to adapt that for the nokia n900? No need for the android version on maemo - standard hosted inferno just works on the n900. I've been running it for quite a while (or was until my pocket was picked in Paris last week ☹). I'll have to go back to my n800 (=n900 without the phone part) which also runs standard inferno happily, after a small mod to win-x11a (in contrib/miller/inferno/n800). N900 is a nice device, but android phones can be a lot cheaper.
Re: [9fans] Announcing Inferno for Android phones
On Fri, 16 Sep 2011 15:23:01 -0700 John Floren j...@jfloren.net wrote: We would like to announce the availability of Inferno for Android phones. Because our slogan is If it ain't broke, break it, we decided to replace the Java stack on Android phones with Inferno. We've dubbed it the Hellaphone--it was originally Hellphone, to keep with the Inferno theme, but then we realized we're in Northern California and the change was obvious. Excelent! Now where can I steal an Android phone from... There's a tablet I might be able to get my hands on but it's got some funky CPU; not ARM, something else. My memory is saying Dragonball but I've got a feeling it's lying.
Re: [9fans] Announcing Inferno for Android phones
OK, more data this morning. Since the cyanogen upgrade, no linux vm I have on OSX/VMWare can enumerate the phone over USB. This is a very common problem as revealed by any search. On the one linux box I have, the phone is enumerated as a USB storage. There may be some setting I need to reset ... but that box, having been turned off since april, seems to have decided it can't do wifi more ... so, that's not an option at present! I did try downloading the android sdk on a clean vmware-based linux platform. No fastboot in there. So far the only fastboot I have is the one I built from source during android bootcamp. You can NOT install inferno from anything but Linux. There are a few linux tool dependencies in th scripts that can not be satisfied (yet) on a mac. I am going to see what is possible. I continue to be amused that all these Java write once run everywhere environments always come with a huge stack of this CPU, this OS, this version programs without which they can not function. Hmm. All I need with inferno is emu. Maybe inferno can teach them some things :-) Finally, it's a linux phone: I keep thinking I ought to be able to do the install scripts on the phone, not on some other box and download them. If I can figure out where to plug in an SD card -- it claims to have one! -- I might just give that a go. ron
Re: [9fans] Announcing Inferno for Android phones
On Sat, 2011-09-17 at 09:29 -0700, ron minnich wrote: If I can figure out where to plug in an SD card -- it claims to have one! -- I might just give that a go. The MicroSD slot in my Droid X is hidden under the battery fwiw.
Re: [9fans] Announcing Inferno for Android phones
On Sat, Sep 17, 2011 at 10:46 AM, Wes Kussmaul w...@authentrus.com wrote: On Sat, 2011-09-17 at 09:29 -0700, ron minnich wrote: If I can figure out where to plug in an SD card -- it claims to have one! -- I might just give that a go. The MicroSD slot in my Droid X is hidden under the battery fwiw. There's not actually an SD card in the Nexus S, it's apparently just onboard flash made to look like one. John
Re: [9fans] Announcing Inferno for Android phones
On Fri, Sep 16, 2011 at 3:46 PM, andrey mirtchovski mirtchov...@gmail.com wrote: John, turn a camera on and film the phone while using it, please! Terrible video: http://www.youtube.com/watch?v=dF_-jQc53jw Some screenshots are available at https://bitbucket.org/floren/inferno/wiki/Home John
Re: [9fans] Announcing Inferno for Android phones
On Sat, Sep 17, 2011 at 9:29 AM, ron minnich rminn...@gmail.com wrote: OK, more data this morning. Since the cyanogen upgrade, no linux vm I have on OSX/VMWare can enumerate the phone over USB. This is a very common problem as revealed by any search. On the one linux box I have, the phone is enumerated as a USB storage. There may be some setting I need to reset ... but that box, having been turned off since april, seems to have decided it can't do wifi more ... so, that's not an option at present! I did try downloading the android sdk on a clean vmware-based linux platform. No fastboot in there. So far the only fastboot I have is the one I built from source during android bootcamp. You can NOT install inferno from anything but Linux. There are a few linux tool dependencies in th scripts that can not be satisfied (yet) on a mac. I am going to see what is possible. I continue to be amused that all these Java write once run everywhere environments always come with a huge stack of this CPU, this OS, this version programs without which they can not function. Hmm. All I need with inferno is emu. Maybe inferno can teach them some things :-) Finally, it's a linux phone: I keep thinking I ought to be able to do the install scripts on the phone, not on some other box and download them. If I can figure out where to plug in an SD card -- it claims to have one! -- I might just give that a go. If I'm understanding right, you have adb but not fastboot on Mac, right? As long as your phone is unlocked, you can still install inferno on the Nexus with just adb by manually flashing the boot partition. Once you've pushed everything over to /data/inferno, run the Reflash-Nexus-S.sh script. It should fail at the fastboot step, but that's fine. Reboot the phone into Cyanogen. Then, from the same folder as the Reflash-Nexus-S.sh script: $ adb shell mount -o remount,rw / $ adb push boot-inferno.img $ adb shell Now you'll be in an Android shell. android$ cat /proc/mtd This will hopefully give you a list of mtd devices and their names. We only care about the one called boot. android$ cat /dev/zero /dev/mtd/boot device from above The zeroing step may not be necessary, but I've never tried flashing the boot manually without it. android$ flash_image boot /boot-inferno.img Then reboot and it should work. If it's broken, the good news is it's nearly impossible to screw up the recovery partition. Boot into the bootloader by holding the power and volume up buttons, then enter the recovery mode and reinstall Cyanogen.
Re: [9fans] Announcing Inferno for Android phones
On Sat, Sep 17, 2011 at 11:02 AM, John Floren j...@jfloren.net wrote: Terrible video: http://www.youtube.com/watch?v=dF_-jQc53jw Pretty good for being shot with a laptop webcam! I think incoming calls should be working, though, unless I screwed something up between last week and now (which is likely). The phone won't beep or anything when a call comes in, but if you open up the dialer application the status should say incoming (155) and the dial button should change to an answer button, etc. Side note: I'm attempting to port to my HTC Inspire and by far the biggest difficulty seems to be just getting the Android source to compile, especially since you have to rely on mirrors since the kernel.org attacks. I'm running into the USB enumeration errors as well.
Re: [9fans] gar nix!
hey noah, what's the mailing list? - erik
Re: [9fans] gar nix!
nix-...@googlegroups.com Noah On Sat, Sep 17, 2011 at 9:41 PM, erik quanstrom quans...@quanstro.net wrote: hey noah, what's the mailing list? - erik
Re: [9fans] Announcing Inferno for Android phones
joel, on osx, some scripts are not there. I was more concerned about this than the flash failures because I'm not sure what they do. sh: mkbootimg: command not found Where did your version of this one come from? It's nowhere on my machine. ron
Re: [9fans] NIX 64-bit kernel is available
hee hee Brantley On Sep 14, 2011, at 6:10 PM, Dan Cross wrote: On Wed, Sep 14, 2011 at 5:48 PM, John Floren j...@jfloren.net wrote: I don't want to drag out the discussion, but: 1. Nixie is pretty much generic these days. Wikipedia even calls it a genericised trademark. 2. Nixies are also Germanic water spirits. I think we're good :) (I don't want to contribute to the noise, but PIX would be a pretty cool name, all things considered.) - Dan C.
Re: [9fans] Announcing Inferno for Android phones
On Sat, Sep 17, 2011 at 1:26 PM, ron minnich rminn...@gmail.com wrote: joel, on osx, some scripts are not there. I was more concerned about this than the flash failures because I'm not sure what they do. sh: mkbootimg: command not found Where did your version of this one come from? It's nowhere on my machine. It comes from the full Android source. I guess it doesn't make sense for it to be in the SDK. The android git server is dead right now, but you can fetch a mirror of this specific sub-project at https://github.com/CyanogenMod/android_system_core/android_system_core. It's in system/core if you already have an Android source tree. The Android build system is a pain in general, but especially if you just want to build a specific executable, so from the cloned system_core tree: cd libmincrypt gcc -I../include/ -o sha.o -c sha.c mv sha.o ../mkbootimg/ gcc -I../include/ -o mkbootimg -c mkbootimg.c gcc -o mkbootimg mkbootimg.o sha.o should do it. Fastboot is in that tree too if you need a mac version.
Re: [9fans] Announcing Inferno for Android phones
It comes from the full Android source. I guess it doesn't make sense for it to be in the SDK. The android git server is dead right now, but you can fetch a mirror of this specific sub-project at https://github.com/CyanogenMod/android_system_core/android_system_core. URL correction: it's https://github.com/CyanogenMod/android_system_core.
Re: [9fans] Announcing Inferno for Android phones
Slight correction: git clone https://github.com/CyanogenMod/android_system_core cd android_system_core/ cd libmincrypt/ gcc -I../include/ -o sha.o -c sha.c mv sha.o ../mkbootimg/ cd ../mkbootimg/ gcc -I../include/ -c mkbootimg.c gcc -o mkbootimg mkbootimg.o sha.o Although most of you will get that. ron
Re: [9fans] Announcing Inferno for Android phones
A few corrections. $ adb shell mount -o remount,rw / $ adb push boot-inferno.img adb push work/boot-inferno.img /boot-inferno.img $ adb shell Now you'll be in an Android shell. android$ cat /proc/mtd This will hopefully give you a list of mtd devices and their names. We only care about the one called boot. android$ cat /dev/zero /dev/mtd/boot device from above The zeroing step may not be necessary, but I've never tried flashing the boot manually without it. It is hard to believe it is needed. The reason is the erase state of flash is all 1s, not all zeros. Cat'ing zeros onto the flash is probably not what you want: it corresponds to an all-bits-burned state, not an all-bits-cleared state. In this case when you the next step: android$ flash_image boot /boot-inferno.img The mtd driver will likely erase the flash (to all 1s!) and then burn it :-) Then reboot and it should work. android continues to work. But no inferno at present. I get the nice white screen, but if I touch it, well, it's blank after a bit. The parallel_push script did not work that well for me, I had to push dis/ by hand. I think it would be better to copy the tar file over and untar it -- would avoid mac silliness with case in the names, as well. Anyway, I'm booted. I've taken notes and will post them later. I think I'm still missing lots of stuff so I may just push the tar file and untar it. ron
Re: [9fans] Announcing Inferno for Android phones
OK, I just adb pushed the tar file over and untar'ed and things were more complete. So it's up on my nexus-s too. John, would recommend putting OSX and linux versions of fastboot and mkbootimg into the tar file or on the web page. I can tell it's inferno because I hit a button and get instant response. This is somewhat unlike the java-based experience, although of course I'm not about to stop using android for good ... just for most of the time :-) What would truly be interesting, since we don't need to reboot to switch modes, would be a button to do just that ... All right folks, it's there. Now it's time to contribute! You can see the limitations, and this is a very hackable system. Somebody want to write a gps device so I can cat my GPS coords and see if that creates a number I can dial :-) ron
[9fans] inferno on android on slashdot
hot grits! - erik
Re: [9fans] inferno on android on slashdot
hot grits! you're dating yourself :) slashdot was better back then. now it's all whiny kids who like bells and whistles: Seems to me Android has more interesting visuals in its robotic fingernail than Inferno on mobile has
Re: [9fans] inferno on android on slashdot
Hey Erik, I thought you'd said you didn't read Slashdot! On 9/17/11, erik quanstrom quans...@quanstro.net wrote: hot grits! - erik
Re: [9fans] Announcing Inferno for Android phones
the video shows the OS to be pretty snappy, John. thanks!
Re: [9fans] inferno on android on slashdot
of course, being well-tuned to the needs of the younger generation I have prepared some tools that should allow them to, if not stay off our lawn then at least be quiet while trampling it. i don't have an android phone, but those should run on it, i think: http://mirtchovski.com/code/code_files/sokoban.tgz http://mirtchovski.com/code/code_files/decay.b http://mirtchovski.com/code/code_files/lens.b http://mirtchovski.com/code/code_files/zoom.b http://mirtchovski.com/code/code_files/rotzoom.b
Re: [9fans] inferno on android on slashdot
It comes free with the usual high level of slashdot cluelessness. But that's what one should expect :-) ron
[9fans] gs on amd64
does anyone have a ghostscript that works with amd64? i can get gs to display man pages and the stuff in /sys/doc, but not, e.g., the intel arch pdfs. chula; page docs/intel/v3b.pdf reading through pdf... Ghostscript Error: Error: /undefined in --setcolor-- Operand stack: --dict:8/8(L)-- (In) 0.031373 0.37647 0.65882 --nostringval-- --nostringval-- cs_prepare_color --dict:13/20(G)-- --nostringval-- Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- %arfatal: readimage error screen id in use ray_continue --nostringval-- false 1 %stopped_push --nostringval-- %loop_continue --nostringval-- --nostringval-- --nostringval-- %array_continue --nostringval-- --nostringval-- 6 8 %oparray_pop Dictionary stack: --dict:1127/1686(ro)(G)-- --dict:2/20(G)-- --dict:78/200(L)-- --dict:105/127(ro)(G)-- --dict:258/347(ro)(G)-- --dict:22/24(L)-- --dict:4/6(L)-- --dict:27/32(L)-- Current allocation mode is local Last OS error: 20 - erik
Re: [9fans] gs on amd64
I would give ratrace a go. ron
Re: [9fans] gs on amd64
On Sat Sep 17 21:53:06 EDT 2011, rminn...@gmail.com wrote: I would give ratrace a go. ratrace on amd64 produces no output. - erik
Re: [9fans] gs on amd64
On Sat, Sep 17, 2011 at 6:57 PM, erik quanstrom quans...@quanstro.net wrote: On Sat Sep 17 21:53:06 EDT 2011, rminn...@gmail.com wrote: I would give ratrace a go. ratrace on amd64 produces no output. I know. geoff fixed it on 9 and I need to get his fix into nix. I just keep forgetting to figure out how he fixed it :-) ron
Re: [9fans] my kingdom for a web browser :-P
Things are becoming very complex. Chromium even process C++ in the client-side, civilization is dying. On 9/16/11, tlaro...@polynum.com tlaro...@polynum.com wrote: On Fri, Sep 16, 2011 at 03:56:18PM +0100, Ethan Grammatikidis wrote: On Fri, 16 Sep 2011 13:11:00 +0300 Aram H?v?rneanu ara...@mgk.ro wrote: And I don't believe in full linux environments in lguest, in general, a kernel plus a single static binary, like a browser would be enough. I don't think a browser can even be a static binary any more. I'm not going to try to recall exactly which bits won't statically linked; I suspect I'd get very depressed if I remembered. Last time I tried, I had to give up due to the dependencies of dependencies of dependencies... of the X11 and above dynamically shared libraries. If simplicity is the shortest path to the truth, I'm afraid I'm not convinced some people are on the right track to the truth... -- Thierry Laronde tlaronde +AT+ polynum +dot+ com http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C -- S.
[9fans] toff fonts
trying to render special unicode character 0x2019 in troff. but pr2post fails with: /386/bin/aux/tr2post: stdin:31 :WARNING: cannot find glyph, rune=0x2019 stoken=’ troff font R now looking in: /sys/lib/postscript/troff/R 0x2000 0x20ff LucidaSansUnicode20 but in: /sys/lib/troff/font/devutf/R there is no reference to 0x2019 at all, only in /sys/lib/troff/font/devutf/LucidaSans:12: ' 32 2 8217 2019 setting to front to LucidaSans in the troff source works. so whats the relation between /sys/lib/postscript/troff/* and /sys/lib/troff/font/dev*/*? should the stuff in /sys/lib/troff/font/dev*/* be autogeneated somehow? -- cinap
