There is a howto regarding booting off of zfs floating around...

On 5/9/07, Michelle Olson <Michelle.Olson at sun.com> wrote:
> Hi Blake,
>
> Nice work on the list of future HowTos, thanks all for getting this
> rolling! I assume that you've sent the issue you're having to the
> osol-help or ZFS aliases? Just want to be sure the rigth folks know so
> they can help you out.
>
> -Michelle
>
> Blake wrote On 05/08/07 17:42,:
>
> > There should be links to in-depth coverage of associated tools in each
> > of these HOWTO documents.  The vi resources would be a perfect start.
> > Man pages should be linked as well.
> >
> > A sidebar or side-note each time a specific tool (like vi) is first
> > mentioned would be a nice way to let the reader fork off into deeper
> > material at their whim.
> >
> >
> >
> > I should add that I'm going to have to take a break from documentation
> > until I get the issues with my Syba 4-channel SATA controller worked
> > out - it's a Silicon Image 3114 chipset, but I can't get the included
> > Solaris 10 (11/06) drivers to attach to it.  Any help would be greatly
> > appreciated.
> >
> > Blake
> >
> >
> >
> > On 5/8/07, *Brian Gupta* <brian.gupta at gmail.com
> > <mailto:brian.gupta at gmail.com>> wrote:
> >
> >     http://www.oreilly.com/catalog/vi6/chapter/ch08.html
> >
> >     On 5/8/07, Rainer Heilke <rheilke at dragonhearth.com
> >     <mailto:rheilke at dragonhearth.com>> wrote:
> >     > Really? Wow, I've never heard of this before. I've never really
> >     been a
> >     > vi guru by any stretch, but this is a real surprise. Sorry,
> >     everyone,
> >     > and thanks for correcting me, Eric. I never bought the O'Reilly
> >     book, as
> >     > I never pushed vi hard enough to need it. Between that, and some
> >     of the
> >     > extensions being undocumented otherwise, it would explain my
> >     complete
> >     > obliviousness to this.
> >     >
> >     > I'll have to look into this some.
> >     >
> >     > Rainer
> >     >
> >     > Eric Lowe wrote:
> >     >
> >     > >Solaris vi does have some non-standard extensions, such as a
> >     tag stack. Some of them are undocumented. The O'Reilly vi book (
> >     http://www.oreilly.com/catalog/vi6/index.html) has a nice
> >     comparison and a description of the Solaris-specific features.
> >     > >
> >     > >- Eric
> >     > >
> >     > >----- Original Message ----
> >     > >From: Rainer Heilke < rheilke at dragonhearth.com
> >     <mailto:rheilke at dragonhearth.com>>
> >     > >To: Blake <blake.irvin at gmail.com <mailto:blake.irvin at 
> > gmail.com>>
> >     > >Cc: Richard L. Hamilton < rlhamil at smart.net
> >     <mailto:rlhamil at smart.net>>; docs-discuss at opensolaris.org
> >     <mailto:docs-discuss at opensolaris.org>
> >     > >Sent: Sunday, May 6, 2007 10:45:56 PM
> >     > >Subject: Re: [docs-discuss] Re: 'cheat sheets' for common
> >     administrative tasks
> >     > >
> >     > >The vi that comes with Solaris 10 is the standard, generic vi
> >     from Bill
> >     > >Joy (the author, I believe). There is nothing Solaris-specific
> >     that I
> >     > >know of, and that's comparing it to the vi from FreeBSD as well.
> >     > >
> >     > >You are correct about Linux; the distros/versions I've looked
> >     at all
> >     > >linked the vi command to vim. It was actually a source of
> >     frustration to
> >     > >me, as vim does not behave like vi.
> >     > >
> >     > >Rainer
> >     > >
> >     > >
> >     > >
> >     >
> >     > _______________________________________________
> >     > docs-discuss mailing list
> >     > docs-discuss at opensolaris.org <mailto:docs-discuss at 
> > opensolaris.org>
> >     >
> >     _______________________________________________
> >     docs-discuss mailing list
> >     docs-discuss at opensolaris.org <mailto:docs-discuss at opensolaris.org>
> >
> >
> >
> >
> > --
> >
> > blake/
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >docs-discuss mailing list
> >docs-discuss at opensolaris.org
> >
>

Reply via email to