Matthew Kirkwood writes:
>
> On Tue, 16 Feb 1999, Simon Weijgers wrote:
>
> > The elkscmd package has been imported into the CVS tree. You can use
> > the same account used for the other elks modules (elks and elkspages).
> >
> > Name of the module: elkscmd.
>
> For those without CVS access, th
On Tue, 16 Feb 1999, Simon Weijgers wrote:
> The elkscmd package has been imported into the CVS tree. You can use
> the same account used for the other elks modules (elks and elkspages).
>
> Name of the module: elkscmd.
For those without CVS access, there are also nightly tarballs (of both CVS
m
Simon Weijgers writes:
>
> On Tue, 16 Feb 1999, Alistair Riddoch wrote:
>
> > elkscmd.tar.gz - Compressed user program source
>
> > The user command package elkscmd has been re-organised in preparation for
> > inclusion in the CVS system. The old sash/stand-alone directory is now
>
David Murn writes:
>
> On Tue, 16 Feb 1999, Alistair Riddoch wrote:
>
> > A single make command can now be used to build a complete filsystem image,
> > or a (nearly) bootable floppy image, including configuring and
> > building the kernel and bootblocks code.
>
> How was this different to befo
On Tue, 16 Feb 1999, Alistair Riddoch wrote:
> A single make command can now be used to build a complete filsystem image,
> or a (nearly) bootable floppy image, including configuring and
> building the kernel and bootblocks code.
How was this different to before? Make used to create that stuff
On Tue, 16 Feb 1999, Alistair Riddoch wrote:
> elkscmd.tar.gz - Compressed user program source
> The user command package elkscmd has been re-organised in preparation for
> inclusion in the CVS system. The old sash/stand-alone directory is now
The elkscmd package has been importe
