From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <a012fc580804031756u2f240207xb16a786315e7d7eb@mail.gmail.com>
Date: Thu,  3 Apr 2008 20:56:56 -0400
From: "devrin talen" <jackfrost13@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
In-Reply-To: <7aace973af1fa7bb1b2bcbcda19f3a0b@quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <a012fc580804031658t4e8d5b6gca8f612a3a1e4367@mail.gmail.com>
	<7aace973af1fa7bb1b2bcbcda19f3a0b@quanstro.net>
Subject: Re: [9fans] Unmount a USB stick?
Topicbox-Message-UUID: 88c2223e-ead3-11e9-9d60-3106f5b1d025

On Thu, Apr 3, 2008 at 8:41 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>  trick 'o the day: keep kernel messages from messing with rio:
>         window -hide rc -c 'label kmesg ; tail -f /dev/kprint'
>  as long as you have someone reading kernel messages, they won't
>  be written directly to the screen.

Thanks!

>  what happens when you do the following:
>
>         slay usbd|rc
>         slay disk|rc
>         usb/usbd; usb/disk -l

% usb/usbd; usb/disk -l
usb/disk: maxlun 0

But then I try

% usbfat:
mount: mount /n/usb: '/n/disk/0' i/o on hungup channel

Is that an effect of me killing the window earlier?