ALT Linux kernel packages development
 help / color / mirror / Atom feed
From: Anton Farygin <rider@altlinux.com>
To: ALT Linux kernel packages development <devel-kernel@altlinux.ru>
Subject: Re: [d-kernel] Re: I: kernel-feat-core-supermount for 2.6
Date: Wed, 21 Jan 2004 11:25:36 +0300
Message-ID: <20040121082536.GI23904@master.altlinux.ru> (raw)
In-Reply-To: <20040121074119.GA4273@wrars-comp.wrarsdomain>

On Wed, Jan 21, 2004 at 12:41:19PM +0500, Andrey Rahmatullin wrote:
> On Wed, Jan 21, 2004 at 10:29:00AM +0300, Anton Farygin wrote:
> > On Wed, Jan 21, 2004 at 12:16:13PM +0500, Andrey Rahmatullin wrote:
> > > On Wed, Jan 21, 2004 at 10:01:15AM +0300, Anton Farygin wrote:
> > > > Тем, что глючит намного больше. Глюки наблюдаются в районе: "приложение
> > > > юзает примонтированное устройство, а пользователь его вынимает".
> > > 
> > > tray_lock=always
> > 
> > А смысл ?
> 
> * tray_lock={always,onwrite,never}     [default is "onwrite"]
>        Specify when supermount is to prevent media removal. `always' means
> on every access (it was default in earlier versions), `onwrite' means only
> for write access and `never' means never :) `onwrite' and `never' are the
> same for ro media like CD-ROM.
> 
> 
> Как вообще приведенная выше ситуация 
> 1. должна обрабатываться

Тут два варианта: 1) - отдать CDROM, размонтировав его с опцией -l 2)
Дождаться пока приложение отпустит CDROM и потом отдать
> 2. обрабатывается с autofs
Там все просто - CDROM не будет размонтирован, пока приложение его
использует.
> 3. обрабатывается с supermount

В теории - так же как с autofs. 
Хотя почему-то я не наблюдал глюков, если размонтировать используемое
устройство методом umount -l

Наверное это все-таки как то связано с самим supermount'ом (на supermount
глюки воспроизводились)

Rgds,
Rider


  reply	other threads:[~2004-01-21  8:25 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-17 19:55 [d-kernel] " Andrey Rahmatullin
2004-01-17 22:13 ` Albert R. Valiev
2004-01-20 18:13 ` [d-kernel] " Ed V. Bartosh
2004-01-21  7:01   ` Anton Farygin
2004-01-21  7:16     ` Andrey Rahmatullin
2004-01-21  7:29       ` Anton Farygin
2004-01-21  7:41         ` Andrey Rahmatullin
2004-01-21  8:25           ` Anton Farygin [this message]
2004-01-21  8:34             ` Michael Shigorin
2004-01-21  8:39               ` Anton Farygin
2004-01-21  8:52                 ` Michael Shigorin
2004-01-21  9:04                   ` Anton Farygin
2004-01-21 10:23                   ` Ed V. Bartosh
2004-01-21 10:31                     ` Michael Shigorin
2004-01-21 10:38                     ` Anton Farygin
2004-01-21 10:04             ` Albert R. Valiev
2004-01-21 10:02               ` Michael Shigorin
2004-01-21 10:03               ` Anton Farygin
2004-01-21 10:30                 ` Michael Shigorin
2004-01-21 10:40                   ` Anton Farygin
2004-01-21 13:32                     ` Michael Shigorin
2004-01-21 13:35                       ` Anton Farygin
2004-01-21 11:08                 ` Andrey Rahmatullin
2004-01-21 13:28                   ` Anton Farygin
2004-01-21  7:30       ` Вячеслав Диконов
2004-01-21  7:36         ` Anton Farygin
2004-01-21  8:34           ` Michael Shigorin
2004-01-21  8:41             ` Anton Farygin
2004-01-21 16:01               ` Vitaly Lipatov
2004-01-21 16:35                 ` Michael Shigorin
2004-01-21 16:56                   ` Sergey Vlasov
2004-01-22  6:34                 ` Anton Farygin
2004-01-22  9:53                   ` Vitaly Lipatov
2004-01-22 10:14                   ` Sergey Vlasov
2004-01-22 10:21                     ` Anton Farygin
2004-01-22 10:42                       ` Sergey Vlasov
2004-01-22 10:50                     ` Vitaly Lipatov
2004-01-21  8:30     ` Michael Shigorin
2004-01-22 12:30     ` Yury Aliaev
2004-01-21  7:40   ` Gleb Stiblo

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=20040121082536.GI23904@master.altlinux.ru \
    --to=rider@altlinux.com \
    --cc=devel-kernel@altlinux.ru \
    /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

ALT Linux kernel packages development

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel-kernel/0 devel-kernel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel-kernel devel-kernel/ http://lore.altlinux.org/devel-kernel \
		devel-kernel@altlinux.org devel-kernel@altlinux.ru devel-kernel@altlinux.com
	public-inbox-index devel-kernel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel-kernel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git