On Thu, Aug 16, 2012 at 04:11:11PM -0400, erik quanstrom wrote:
> > I think you missed the point. What I have given is an example, what
> > indeed made me wonder, initially, about a way to simply store
> > definitions as a text file, the relationships between the notions
> > being described by a di
the 9front kernels use a new rc based bootstrap system. the
kernel itself uses a compressed ram filesystem image (paqfs)
that will be mounted by /boot/boot containing the required
programs like rc, srv, ifconfig and file fileservers like
9660srv and cwfs to mount the real root filesystem.
there is
Hello cinap,
There are no 9pc and 9pccpu in 9front package.
Is there any reason?
It seems 9bootpxe of 9front does better jobs than 9pxeload.
However 9bootpxe does not support menu.
Is there any reason?
On 2012/07/31, at 5:45, cinap_len...@gmx.de wrote:
> or use 9front with *acpi=1
>
> --
> c
> I think you missed the point. What I have given is an example, what
> indeed made me wonder, initially, about a way to simply store
> definitions as a text file, the relationships between the notions
> being described by a directory structure. It was obvious rapidly
> that this won't do in a clas
On Thu, Aug 16, 2012 at 08:02:52PM +0300, Eugene Gorodinsky wrote:
> >
> > First one, related to what I was wandering about, is mathematical
> > definitions and relationships. Take the picture of the first volume of
> > van der Waerden's Albebra (I have the german edition and will keep the
> > germ
>
> First one, related to what I was wandering about, is mathematical
> definitions and relationships. Take the picture of the first volume of
> van der Waerden's Albebra (I have the german edition and will keep the
> german words). We speak about links between notions presented in a
> linear order
> It pretty much has to. Consider what happens when you do something like
>
> % x=`{pwd}
> % bind /sys/src tmp
> % cd tmp
> % cd ..
>
> This gets you back to $x. If you leave ".." upto the fileserver, you'd get
> back to /sys not $x. The server can't know the right context.
I thought this probl
On Thu, Aug 16, 2012 at 08:59:01AM -0700, Bakul Shah wrote:
> On Thu, 16 Aug 2012 09:40:22 EDT erik quanstrom
> wrote:
> > > What is more bizarre, with my scheme, is how to implement the meaning
> > > of ".."? If classical clients have to be able to be used, the server
> > > must create a fake n
On Thu, Aug 16, 2012 at 12:06:40PM -0400, erik quanstrom wrote:
>
> >
> > Except by allowing a new syntax .../{a,b,c,d}/foo meaning that foo has
> > a, b, c and d as parents, the only way I see things working with the
> > utilities and the ".." treatment is to insert a special name ensuring
> > t
On Thu Aug 16 11:44:01 EDT 2012, tlaro...@polynum.com wrote:
> On Thu, Aug 16, 2012 at 09:40:22AM -0400, erik quanstrom wrote:
> > > What is more bizarre, with my scheme, is how to implement the meaning
> > > of ".."? If classical clients have to be able to be used, the server
> > > must create a f
On Thu, 16 Aug 2012 09:40:22 EDT erik quanstrom wrote:
> > What is more bizarre, with my scheme, is how to implement the meaning
> > of ".."? If classical clients have to be able to be used, the server
> > must create a fake name (as the penultimate component of the
> > dirpath), that triggers th
On Thu, Aug 16, 2012 at 09:40:22AM -0400, erik quanstrom wrote:
> > What is more bizarre, with my scheme, is how to implement the meaning
> > of ".."? If classical clients have to be able to be used, the server
> > must create a fake name (as the penultimate component of the
> > dirpath), that trig
> > and as such, i was thinking of a server that simply distributed requests
> > among a set of servers. so that
> >
> > > > > echo "date" > /net/my-nodes/foo
> > > > > chmod +x /net/my-nodes/foo
> >
> > would work with the normal tools on a normal kernel. all the distribution
> > would
> What is more bizarre, with my scheme, is how to implement the meaning
> of ".."? If classical clients have to be able to be used, the server
> must create a fake name (as the penultimate component of the
> dirpath), that triggers the correct answer from the server.
see defmnt.c:/^fixdotdotname f
14 matches
Mail list logo
