9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] a few misc. questions...
Date: Wed, 22 Jul 2009 08:04:12 -0700	[thread overview]
Message-ID: <3e1162e60907220804u56c408ecw5aecc5d1ae40c5f5@mail.gmail.com> (raw)
In-Reply-To: <03c3b7ce9858735561e960331f367585@quanstro.net>

[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]

On Wed, Jul 22, 2009 at 6:13 AM, erik quanstrom <quanstro@quanstro.net>wrote:

> > ... but which would be considered the most logical place to deal with
> > things such as setting hd parameters for the machine on bootup like
> > the 'echo dma on > /dev/sdC0/ctl' example above?
>
> also see dmaon(8).  just as an obvious note, this only
> affects interfaces using ide or ide emulation.  you can
> tell which driver you're using by catting /dev/sdctl.  for
> example, the first drive is ide.  unfortunately, the driver
> calls itself "ata".
>
> ladd# cat /dev/sdctl
> sdC ata port 1F0 ctl 3F4 irq 14
> sdE ahci sb600 port 0xe0022800: 64a alp clo coal led mps ncq ntf pm pslum
> slum iss 2 ncs 31 np 4 ghc 80000002 isr 0 pi f 0-3 ver 10100
>
> > > Kfs is the older disk file system for standalone terminals and the
> like.
> > > For most purposes, fossil replaces it. Fossil is user-mode, while kfs
> > > is a "kernel file system." See in kfs(4).
> > >
> >
> > Ok, so I may simply generally disregard any mention of kfs in any docs or
> > scripts and config files I might happen upon? Since fossil has
> effectively
> > deprecated kfs?
>
> both (as noted) are user-level fses.  and while kfs is older and
> simpler, it is very robust.  there may be more kfs in operation
> than any other plan 9 fs.  fossil does snapshots, talks to venti
> and other things, but being more complicated, there are more
> ways for it to go sideways.
>
> so like anything else you don't use, feel free to ignore.  but
> that doesn't mean kfs is "deprecated".  i think it's just a different
> tool for a different task.
>

Yeah, I'm pretty sure that, in an emulated environment, I'd pick kfs over
Venti, most of the time, unless your goal is to learn about Venti and Fossil
:-).

You can do Fossil without Venti too, but it's not as fun :-)

Dave


>
> - erik
>
>

[-- Attachment #2: Type: text/html, Size: 2599 bytes --]

  reply	other threads:[~2009-07-22 15:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22  5:21 Corey
2009-07-22  5:59 ` Josh Wood
2009-07-22  6:08   ` Josh Wood
2009-07-22  7:31   ` Corey
2009-07-22  8:35     ` Josh Wood
2009-07-22  8:40     ` Richard Miller
2009-07-22 13:13     ` erik quanstrom
2009-07-22 15:04       ` David Leimbach [this message]
2009-07-22 17:57         ` hiro
2009-07-22 19:12           ` David Leimbach
2009-07-23  3:36 ` Corey
2009-07-23  4:33   ` Federico G. Benavento
2009-07-24 15:48     ` maht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e1162e60907220804u56c408ecw5aecc5d1ae40c5f5@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).