On Mon, Jan 14, 2008 at 02:34:00PM -0500, Gene Heskett wrote:
> Do we have a utility that can force the kernel to re-read, and re-initialize
> itself to a given drives partition tables without having to reboot if one is
> working with a drive that is not part of the required kernel directory
On Jan 14 2008 15:53, Robert P. J. Day wrote:
>>
>> fdisk or similar should have issued an ioctl to reread the partition
>> table after writing the new one, but you can do it manually with
>> 'blockdev --rereadpt '.
>
>i remember bringing up this very issue quite some time ago and, IIRC,
>the
On Jan 14 2008 15:53, Robert P. J. Day wrote:
fdisk or similar should have issued an ioctl to reread the partition
table after writing the new one, but you can do it manually with
'blockdev --rereadpt device'.
i remember bringing up this very issue quite some time ago and, IIRC,
the
On Mon, Jan 14, 2008 at 02:34:00PM -0500, Gene Heskett wrote:
Do we have a utility that can force the kernel to re-read, and re-initialize
itself to a given drives partition tables without having to reboot if one is
working with a drive that is not part of the required kernel directory tree?
On Jan 14 2008 22:29, Olaf Titz wrote:
>> 200Mb had been filled when it had been umounted from /mnt/bootf8
>> repartitioned, mke2fs'd, a journal added and a new label written and then
>> mounted to /amandatapes.
>>
>> Something it seems to me, should have forced the re-init, but didn't. So is
>
> 200Mb had been filled when it had been umounted from /mnt/bootf8
> repartitioned, mke2fs'd, a journal added and a new label written and then
> mounted to /amandatapes.
>
> Something it seems to me, should have forced the re-init, but didn't. So is
Something I stumbled across just a few days
On Mon, 14 Jan 2008, Dagfinn Ilmari Mannsåker wrote:
> Gene Heskett <[EMAIL PROTECTED]> writes:
>
> > Greetings;
> >
> > Do we have a utility that can force the kernel to re-read, and re-initialize
> > itself to a given drives partition tables without having to reboot if one is
> > working with a
Gene Heskett <[EMAIL PROTECTED]> writes:
> Greetings;
>
> Do we have a utility that can force the kernel to re-read, and re-initialize
> itself to a given drives partition tables without having to reboot if one is
> working with a drive that is not part of the required kernel directory tree?
On Mon, 14 Jan 2008, Robert P. J. Day wrote:
> On Mon, 14 Jan 2008, Gene Heskett wrote:
>
> > Greetings;
> >
> > Do we have a utility that can force the kernel to re-read, and
> > re-initialize itself to a given drives partition tables without
> > having to reboot if one is working with a drive
Hi,
On 14 Jan 2008, at 19:34, Gene Heskett wrote:
Do we have a utility that can force the kernel to re-read, and re-
initialize
itself to a given drives partition tables without having to reboot
if one is
working with a drive that is not part of the required kernel
directory tree?
Yes,
On Jan 14 2008 14:34, Gene Heskett wrote:
>
>Do we have a utility that can force the kernel to re-read, and re-initialize
>itself to a given drives partition tables without having to reboot if one is
>working with a drive that is not part of the required kernel directory tree?
fdisk issues an
On Mon, 14 Jan 2008, Gene Heskett wrote:
> Greetings;
>
> Do we have a utility that can force the kernel to re-read, and
> re-initialize itself to a given drives partition tables without
> having to reboot if one is working with a drive that is not part of
> the required kernel directory tree?
i
Greetings;
Do we have a utility that can force the kernel to re-read, and re-initialize
itself to a given drives partition tables without having to reboot if one is
working with a drive that is not part of the required kernel directory tree?
The reason I ask, is that I've just spent about 20
Greetings;
Do we have a utility that can force the kernel to re-read, and re-initialize
itself to a given drives partition tables without having to reboot if one is
working with a drive that is not part of the required kernel directory tree?
The reason I ask, is that I've just spent about 20
On Mon, 14 Jan 2008, Gene Heskett wrote:
Greetings;
Do we have a utility that can force the kernel to re-read, and
re-initialize itself to a given drives partition tables without
having to reboot if one is working with a drive that is not part of
the required kernel directory tree?
i would
Hi,
On 14 Jan 2008, at 19:34, Gene Heskett wrote:
Do we have a utility that can force the kernel to re-read, and re-
initialize
itself to a given drives partition tables without having to reboot
if one is
working with a drive that is not part of the required kernel
directory tree?
Yes,
On Jan 14 2008 14:34, Gene Heskett wrote:
Do we have a utility that can force the kernel to re-read, and re-initialize
itself to a given drives partition tables without having to reboot if one is
working with a drive that is not part of the required kernel directory tree?
fdisk issues an
Gene Heskett [EMAIL PROTECTED] writes:
Greetings;
Do we have a utility that can force the kernel to re-read, and re-initialize
itself to a given drives partition tables without having to reboot if one is
working with a drive that is not part of the required kernel directory tree?
[…]
On Mon, 14 Jan 2008, Robert P. J. Day wrote:
On Mon, 14 Jan 2008, Gene Heskett wrote:
Greetings;
Do we have a utility that can force the kernel to re-read, and
re-initialize itself to a given drives partition tables without
having to reboot if one is working with a drive that is not
On Mon, 14 Jan 2008, Dagfinn Ilmari Mannsåker wrote:
Gene Heskett [EMAIL PROTECTED] writes:
Greetings;
Do we have a utility that can force the kernel to re-read, and re-initialize
itself to a given drives partition tables without having to reboot if one is
working with a drive that is
200Mb had been filled when it had been umounted from /mnt/bootf8
repartitioned, mke2fs'd, a journal added and a new label written and then
mounted to /amandatapes.
Something it seems to me, should have forced the re-init, but didn't. So is
Something I stumbled across just a few days ago:
On Jan 14 2008 22:29, Olaf Titz wrote:
200Mb had been filled when it had been umounted from /mnt/bootf8
repartitioned, mke2fs'd, a journal added and a new label written and then
mounted to /amandatapes.
Something it seems to me, should have forced the re-init, but didn't. So is
Something I
22 matches
Mail list logo
