We've spent a lot of time thinking about file system front ends
for databases (mostly in the context of pq, but not entirely). I'm
unconvinced that this model of representation really adds much
for most databases.
The problem is that the application talking to the database
still has to know too mu
// I haven't used PQ either. In fact, has anyone used PQ in the
// last couple years?
Yes. In the past few years I've worked with teams building two
unrelated applications with it. One went through a technology
trial with a Tier 1 US telecom provider, but then floundered for
unrelated reasons. Th
in the news:
http://www.regdeveloper.co.uk/2008/03/27/google_summer_code_debian_losers/
On Thu, Mar 27, 2008 at 11:46:21AM -0400, [EMAIL PROTECTED] wrote:
> > On Wed, Mar 26, 2008 at 09:14:38PM -0400, Tom Lieber wrote:
> >> On Wed, Mar 26, 2008 at 8:04 PM, Enrico Weigelt <[EMAIL PROTECTED]> wrote:
> >> > I'm currently planning an little ezine about Plan9 and related stuff
> >> > (in
I had been thinking of adding a database to Plan 9 for a while.
Here's my design:
The DBMS is a 9P server. Upon mounting, it takes as arguments two files:
- the list of names of records and fields
- the data itself
It then parses the data into virtual files in the location given
> I haven't used PQ either. In fact, has anyone used PQ in the last
> couple years? I wouldn't trust OO to do my databases, but considering
> the Sinkhole of Support I'd be likely to experience with PQ (it's in
> sources/extra, it's old, it's unsupported), I'd be more inclined to
> write an inter
> Who needs OpenOffice.org Write when you have troff?
>
> Who needs OpenOffice.org Calc when you have CSV and awk?
>
> Who needs OpenOffice.org Impress (PowerPoint) when you have troff and
> either mv or Uriel's macros?
>
> Who needs OpenOffice.org Draw when you have 2nd edition draw in /n/
>
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> My concern with "ezines" is always that they don't have much to offer
> that you can't get through incremental updates to a blog. I like
> getting real magazines and newsletters because you have the
> anticipation of waiting and end up with a nice
* Harri Haataja <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 26, 2008 at 09:14:38PM -0400, Tom Lieber wrote:
> > On Wed, Mar 26, 2008 at 8:04 PM, Enrico Weigelt <[EMAIL PROTECTED]> wrote:
> > > I'm currently planning an little ezine about Plan9 and related stuff
> > > (incl. 9P+synthentic filesystems
it has been some time since i last used sam interactively,
but your description
sam appears to forget the state (in fact it's I that forget
it) and treat my input as plain text. In this case, no matter putting
a single dot or completing with a `/' could not save me. As a r
> On Wed, Mar 26, 2008 at 09:14:38PM -0400, Tom Lieber wrote:
>> On Wed, Mar 26, 2008 at 8:04 PM, Enrico Weigelt <[EMAIL PROTECTED]> wrote:
>> > I'm currently planning an little ezine about Plan9 and related stuff
>> > (incl. 9P+synthentic filesystems on other OS'es).
>> > Maybe anyone intereste
Hi,
The UNIX standard editor ed, which also exists in Plan 9, accepts the
interrupt signal. When it listens an interrupt signal, ed will print
a `?' and returns to its command level. Frankly, it is a very
convenient feature since the user could not loose himself, especially
for a line editor.
> Install a pbs on it and see if it gets loaded and run.
I have been running PBS off the USB stick the whole time. It's the
step from 9load to the kernel which isn't working. 9load isn't able
to find plan9.ini or the kernel I tell it on the USB stick - it
doesn't even seem to be able to see the U
>
> Either the BIOS is not exposing the USB stick as a disk, or the 9load
> BIOS device code isn't searching correctly. I'm going to give it a
> r
This is easy to see. Install a pbs on it and see if it gets loaded and run.
If it is not, the BIOS does not see it. Take a look at the configuratio
Hi,
trying to adapt the getcallerpc function - that
exists on Plan9 and p9p - to the arm7 using the arm-elf-gcc
compiler, I realized that this would not be easy, as
most function arguments are put into registers
(the return value into lr), and only pushed on the
stack on demand - so it seems one c
Here is the output after commenting out "|| !biosinited" in
/sys/src/boot/pc/devbios.c:137:
bios0: drive 0x80: 4001292288 bytes, type 3
biosinit: sorry, only one bios drive; can't read last one
(From reading the 9load code I don't understand how biosinited is ever
1 when biosinit() gets called. T
I am just playing with that right now. I have removed *nobiosload
from plan9.ini. But I think 9load isn't able to access my plan9.ini
on the USB stick.
> What were those options in plan9.ini for letting the bios do the disk access?
*nobiosload may need to be disabled?
Stefan
On Thu, Mar 27, 20
I don't think 9load can just boot off a usb yet.
Can the eee bios make the usb look like a disk? What were those
options in plan9.ini for letting the bios do the disk access?
Robby
Thank you all, sqweek and arvindh :-)
I think the most convenient method, for me, is still modifying the 9
script and call p9p programs through 9 when necessary. I said that is
due to my consideration: I hope I can stick with bash (I like its
readline support) and also play with p9p programs in a
I just played with an Eee PC for a few minutes. So the Eee PC's
southbridge is not supported by 9load or the kernel. See
/sys/src/boot/pc/pci.c and /sys/src/9/pc/pci.c for the southbridges
list.
I'm not sure how to boot Plan 9 without a CD-ROM drive, so I used dd
to copy the ISO's bootdisk.img o
20 matches
Mail list logo
