mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samuel Maftoul <maftoul@esrf.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: Ieee1394
Date: Wed, 28 Nov 2001 16:29:06 +0100	[thread overview]
Message-ID: <20011128162906.A29500@pcmaftoul.esrf.fr> (raw)
In-Reply-To: <20011128103256.A28083@pcmaftoul.esrf.fr> <20011128090928.I23907@visi.net>
In-Reply-To: <20011128090928.I23907@visi.net>; from bcollins@debian.org on Wed, Nov 28, 2001 at 09:09:28AM -0500

On Wed, Nov 28, 2001 at 09:09:28AM -0500, Ben Collins wrote:
> On Wed, Nov 28, 2001 at 10:32:56AM +0100, Samuel Maftoul wrote:
> > Hello everyone,
> >         Still me with my ieee1394 problems :)
> > 
> > Workaround: My goal is to make ieee1394 HardDisk  work in a production 
> > environment:
> > 	User come on a machine, plug his disk, store his (experience 
> > 	results) datas on it, unplugs it and go away with it in his home
> > 	institute where he processes his datas.
> 
> I don't see any mention of the kernel version you are using, nor about
> the specific ohci chipset, or the hardware (ppc, i386?).
> 
> Give me some details. I don't see this issue right now, but I'm using
> linux1394 CVS.
i386, AFW-4300, 2.4.16, ieee1394 from kernel (not CVS , but soon CVS :)
)
Most problems resolved.
Now I'm working on a script to automount and autoumount the HD.
This is so fucking hard 'cause we are not aware of what user wants to
use the disk (for mount -o user to let the user accessing his datas in
rw mode). Another problem is the umount: if the directory s busy, my
script isn't able to du "cd .." for the user ...
so crazy
        Sam
> 
> 
> Ben
> 
> -- 
>  .----------=======-=-======-=========-----------=====------------=-=-----.
> /                   Ben Collins    --    Debian GNU/Linux                  \
> `  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
>  `---=========------=======-------------=-=-----=-===-======-------=--=---'
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2001-11-28 15:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28  9:32 Ieee1394 Samuel Maftoul
2001-11-28 12:19 ` Ieee1394 Kristian Hogsberg
2001-11-28 14:09 ` Ieee1394 Ben Collins
2001-11-28 15:29   ` Samuel Maftoul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-27 13:49 Ieee1394 Samuel Maftoul
2001-11-27 15:04 ` Ieee1394 Keith Owens
2001-11-27 18:50 ` Ieee1394 Greg KH

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=20011128162906.A29500@pcmaftoul.esrf.fr \
    --to=maftoul@esrf.fr \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®