On Thu, May 02, 2013 at 04:17:11PM -0400, 9p...@imu.li wrote:
if we're talking about xd, i'll suggest 'tcs -f 8859-1' again in which case:
My question was _not_ related to text, and _not_ related to french i.e.
8859-1. I know how to deal with this.
--
Thierry Laronde tlaronde +AT+
... or I may just be doing something inappropriate. But right now, I
get:
5c -FTVw runebase.c
f0 a4 8b
ae 20
f0 a2 a1
8a 20
f0 a2 a1
84 20
f0 a3 8f
95 20
f0 a5 89
89 20
runebase.c:1255
if we're talking about xd, i'll suggest 'tcs -f 8859-1' again in which case:
My question was _not_ related to text, and _not_ related to french i.e.
8859-1. I know how to deal with this.
tcs -f 8859-1
will take your _binary_ files, and replace the bytes 0x80-0xff with the
unicode points
2013/5/1 Steve Simon st...@quintile.net:
There has been a win32.c in the labs distribution of rc(1) for years
but it has never (to my knowledge) worked.
I did a major overhall of the win32 port and back ports of a few
plan9 tools to posix (I know, I know), and packaged the whole thing up.
The procedure is:
1. remove runebase from /sys/src/libc/port/mkfile
2. cd /sys/src/libc mk install mk clean
3. for(i in /sys/src/cmd/8?) {cd $i mk install mk clean}
4. add runebase in /sys/src/libc/port/mkfile
5. cd /sys/src/libc mk install mk clean
6. cd /sys/src mk install mk clean
--
On Fri May 3 09:31:11 EDT 2013, 0in...@gmail.com wrote:
The procedure is:
1. remove runebase from /sys/src/libc/port/mkfile
2. cd /sys/src/libc mk install mk clean
3. for(i in /sys/src/cmd/8?) {cd $i mk install mk clean}
4. add runebase in /sys/src/libc/port/mkfile
5. cd /sys/src/libc
On Fri May 3 08:56:58 EDT 2013, lu...@proxima.alt.za wrote:
... or I may just be doing something inappropriate. But right now, I
get:
5c -FTVw runebase.c
one thing not in the sources version of 21-bit runes is the
ability to regenerate the rune tables automaticly from the
official
Thinking of tackeling ghostscript again but failed at the first hurdle,
it needs autotools to build...
Anyone attempted this?
-Steve
what the subject says, anyone put their venti (those that use it)
on a solid state disk?
-Steve
On Fri May 3 10:19:43 EDT 2013, st...@quintile.net wrote:
Thinking of tackeling ghostscript again but failed at the first hurdle,
it needs autotools to build...
oh please do!
one question, though. are there better alternatives than ghostscript
for pdf? ghostscript usually fails for simple
I have not yet, but i've been meaning to play around some with
different arrangements for different parts. Please let us know if
you hear anything interesting.
Anthony
On Fri, May 03, 2013 at 10:22:13AM -0400, erik quanstrom wrote:
one question, though. are there better alternatives than ghostscript
evince is a poppler frontend; poppler's problematic dependencies include
glib and cmake. poppler is descended from xpdf, whose problematic
dependencies are
Thinking of tackeling ghostscript again but failed at the first hurdle,
it needs autotools to build...
Anyone attempted this?
Ghostscript 8.53 was already using autotools, but Russ Cox wrote a
mkfile for it when he ported it to Plan 9.
The current mkfile is already able to compile Ghostscript
On Fri, May 03, 2013 at 03:18:40PM +0100, Steve Simon wrote:
Thinking of tackeling ghostscript again but failed at the first hurdle,
it needs autotools to build...
Plan A, create a SmallScript borrowing the rasterizing routines of
METAFONT and not aiming to be a full PostScript interpreter.
...and how does that help me read a pre-existing PDF document?
---BeginMessage---
On Fri, May 03, 2013 at 03:18:40PM +0100, Steve Simon wrote:
Thinking of tackeling ghostscript again but failed at the first hurdle,
it needs autotools to build...
Plan A, create a SmallScript borrowing the
On Fri, May 03, 2013 at 09:15:27AM -0400, Tristan wrote:
tcs -f 8859-1
will take your _binary_ files, and replace the bytes 0x80-0xff with the
unicode points U0080-U00ff, so you can use the standard regexps and tools
on them. and just convert back afterwards.
OK, mea culpa... since I'm
Is a PS/PDF library something that might benefit from reconstruction in Go?
Or is it just a spaghetti mess?
What about mupdf? It has few dependecies [1]
http://mupdf.com/doc/
[1] http://git.ghostscript.com/?p=mupdf.git;a=tree;f=thirdparty;hb=HEAD
pmarin.
On Fri, May 3, 2013 at 7:16 PM, erik quanstrom quans...@quanstro.netwrote:
On Fri May 3 13:15:41 EDT 2013, knapj...@gmail.com wrote:
Is a
On May 3, 2013, at 12:16 PM, erik quanstrom quans...@quanstro.net wrote:
On Fri May 3 13:15:41 EDT 2013, knapj...@gmail.com wrote:
Is a PS/PDF library something that might benefit from reconstruction in Go?
Or is it just a spaghetti mess?
go or c, a fresh implementation might be an
On Fri, May 03, 2013 at 09:14:18AM -0800, Jack Johnson wrote:
Is a PS/PDF library something that might benefit from reconstruction in Go?
Or is it just a spaghetti mess?
Whatever the way (porting existing to Go or writing from scratch), a Go
version would be an improvement against a C++ one
But in this case, there are
probably online PDF viewers...
But no Plan 9 browsers.
--
Aram Hăvărneanu
On Fri, May 03, 2013 at 08:10:26PM +0200, Aram H?v?rneanu wrote:
But in this case, there are
probably online PDF viewers...
But no Plan 9 browsers.
Yes... But this is also why, concurrently, work has to be done to get
rid of some unnecessities: that documents produced on Plan9 be viewable
Hello!
I'm aware that it's rather late for this, and that I very nearly missed the
submission deadline, but well... real life had other plans for me. Still,
I'd just love to work on Plan9 over the summer, and here is my proposal:
Yes... But this is also why, concurrently, work has to be done to get
rid of some unnecessities: that documents produced on Plan9 be viewable
on Plan9 with only Plan9 means (external documents are another problem).
ghostscript already renders plan 9 produced pdf just fine.
so that problem is
On Tue, Apr 23, 2013 at 11:18:37AM -0400, erik quanstrom wrote:
i have seen that some ati cards are not happy with some modes.
you may wish to try cinap's realemu which is at
9fs atom # srv $nflag -q tcp!atom.9atom.org atom
# mount $nflag /srv/atom /n/atom atom
On Fri, May 3, 2013 at 10:38 AM, erik quanstrom quans...@labs.coraid.comwrote:
Yes... But this is also why, concurrently, work has to be done to get
rid of some unnecessities: that documents produced on Plan9 be viewable
on Plan9 with only Plan9 means (external documents are another
I have retrieved atom aux/realemu and I will have to test.
But before, I will have to read the aux/vga sources to understand what
it expects. Because aux/vga -p gives me all the informations about the
vesa supported modes of the card, and even the monitor settings (I
wonder that the problem
On Fri, May 03, 2013 at 02:57:12PM -0400, erik quanstrom wrote:
the problem is that the VBE calls that are used to set up
various video modes jump to vendor-provided real mode
code that is often buggy. the reason for emulation is
(a) to avoid problems associated with real-mode code
Russ Cox wrote a
mkfile for it when he ported it to Plan 9.
thanks,
yes I looked at ghostscript a year or two ago but they seem
to have changed their directory layout and modifying the mkfile
was not straightforward.
My need is for postscript to pcl6 for the printer we have, currently I
run
I tried putting our index on a single OCZ SSD and it died during buildindex.
The SSD was completely unresponsive thereafter, which is pretty
appalling behaviour for a storage device. Having since sworn off
OCZ, I would try again with a pair of Intel 330s in a RAID.
I tried putting venti on an ssd with similar results. Fossil, kenfs, and cwfs
all worked fine on that drive though. I think it was one of the earlier Intels.
On May 3, 2013, at 16:59, ge...@plan9.bell-labs.com wrote:
I tried putting our index on a single OCZ SSD and it died during buildindex.
i have 60GB intel ssd in my new fileserver holding the
cwfs worm cache. no problems so far. but the machine is
just up for two weeks.
its an experiment. if it breaks i have spare sata drive
that could replace it. the worm is on a mirror with
traditional mechanical harddrives.
cpu% cat
On 3 May 2013 21:59, ge...@plan9.bell-labs.com wrote:
I tried putting our index on a single OCZ SSD and it died during
buildindex.
The SSD was completely unresponsive thereafter, which is pretty
appalling behaviour for a storage device.
I had similar problems with OCZ. I was only copying
On 2013-05-03, at 1:59 PM, ge...@plan9.bell-labs.com wrote:
I tried putting our index on a single OCZ SSD and it died during buildindex.
The SSD was completely unresponsive thereafter, which is pretty
appalling behaviour for a storage device. Having since sworn off
OCZ, I would try again
We've had a lot of success with Intel SSDs, only problem is that they
seem to be in short supply right now. We're also looking at Samsung
SSDs, and they seem to be perhaps even better than the Intel SSDs.
OCZs break often in my experience.
2013/5/3 cinap_len...@gmx.de:
ocz seems to have a bad
I was running a really bastardized mix of old and new boot software,
so it's quite possible I screwed up installing the correct MBR and
boot loader. But it might also have been a problem with the BIOS or
SATA controller on the motherboard -- it's a slightly ancient
Supermicro Atom 1U, and it
On 2013-05-03, at 6:31 PM, cinap_len...@gmx.de wrote:
ocz seems to have a bad reputation. just googled intel ssd broken
and you get tons of results from people with broken/dead ocz ssd's.
Disk drive reliability comes and goes with the seasons. For years I only ran
Seagate disks, and
On 2013-05-03, at 6:43 PM, erik quanstrom wrote:
(i'm not absolving the drive. just saying that there are plan 9
issues affecting your machine.)
No doubt. But I got it to the point where it's working quite happily. And it
can maintain that steady state until it tips over and dies, at
Disk drive reliability comes and goes with the seasons. For years I
only ran Seagate disks, and wouldn't go near WD. Then, after a 30%
failure run on 1 year old Seagates, I switched back to WDs, which
have been flawless for me. So far. And Hitachi has drifted in and
out of the picture
On 2013-05-03, at 6:51 PM, erik quanstrom wrote:
imho, applying 50 years of experience with spinning hard drives with
the relatively new flash memory drive is a suspect comparison.
Is it? Cheap SSD seems to break as often as cheap spinny disks. According to
everyone's anecdotal stories, at
On Fri May 3 17:59:27 EDT 2013, cinap_len...@gmx.de wrote:
i have 60GB intel ssd in my new fileserver holding the
cwfs worm cache. no problems so far. but the machine is
just up for two weeks.
as long as we're straying from venti, i'll say that i've used ssds
in ken's file server as both
On 2013-05-03, at 7:00 PM, erik quanstrom wrote:
well clearly, we must lump everything
that breaks anecdotally as often
in the same catagory,
by manufacturer.
Exactly. That's where we started this conversation :-)
On Fri, May 03, 2013 at 10:00:41PM -0400, erik quanstrom wrote:
On 2013-05-03, at 6:51 PM, erik quanstrom wrote:
imho, applying 50 years of experience with spinning hard drives with
the relatively new flash memory drive is a suspect comparison.
Is it? Cheap SSD seems to break as
well clearly, we must lump everything
that breaks anecdotally as often
in the same catagory,
by manufacturer.
- erik
that was the worst haiku I've ever seen
oh, now.
you give me too much credit.
i wasn't even
trying.
- erik
I had originally used a Crucial 32GB SSD years ago and swapped to a 55GB
OCZ enterprise drive (using sdahci). More recently I've moved my venti
arenas over to plan9port and have switched over to using the entire SSD for
fossil. So far this has been faster than running venti natively - though I
cwfs copies the blocks from worm into the cache on read.
so the working set is served from the ssd and the ram
buffer cache. reading /n/dump would hit the mechanical
disk tho.
--
cinap
no cats in picture!
--
cinap
On 4 May 2013 00:59, Charles Forsyth charles.fors...@gmail.com wrote:
I had similar problems with OCZ.
I ought to have observed that I bought the drive from Fry's as refurbished,
which probably wasn't a good recommendation for a drive that was fairly new.
48 matches
Mail list logo
