All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: re-reading the partition table on a "busy" drive
Date: Fri, 08 Sep 2006 16:56:19 +0200	[thread overview]
Message-ID: <45018493.9050207@flower.upol.cz> (raw)
In-Reply-To: <Pine.LNX.4.61.0609081546260.25316@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
>>>My anwser to this question: if it's so "pretty annoying", just let it be
>>>"yes, do as i said !", not more and not less, just most ;).
>>
>>Well, this whole question is already moot, as pointed out by Olaf.
>>Because kernel already supports add/delete single partition ioctls,
>>which is sufficient.  For my needs I already wrote a tiny hack which
>>compares /proc/partitions with the output of `sfdisk -d' and re-adds
>>anything which changed.  It should be possible to do the same with
>>parted instead of {sf,cf,f}disk without using that hack, but hell,
>>all those fdisks (parted included) sucks badly, each in its own way,
>>so all are being used for different parts of the task, including the
>>hack ;)
> 
> 
> So something should write the perfect utility. There are people on this 
> list capable of this, like we have seen with git :)

As far as i can see, most of such was actually started by Linus,
including linux.....

> Jan Engelhardt


-- 
-o--=O`C  /. .\   (+)
  #oo'L O      o    |
<___=E M    ^--    |  (you're barking up the wrong tree)


  reply	other threads:[~2006-09-08 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 16:21 re-reading the partition table on a "busy" drive Michael Tokarev
2006-09-08  5:55 ` Oleg Verych
2006-09-08  6:58   ` Jan Engelhardt
     [not found]     ` <20060908135858.GB14370@flower.upol.cz>
2006-09-08 13:34       ` Michael Tokarev
2006-09-08 13:47         ` Jan Engelhardt
2006-09-08 14:56           ` Oleg Verych [this message]
2006-09-08  8:27 ` Olaf Hering

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=45018493.9050207@flower.upol.cz \
    --to=olecom@flower.upol.cz \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.