On Sun, Jun 4, 2017 at 12:59 AM, Pascal Hambourg wrote:
> Le 03/06/2017 à 17:48, Gene Heskett a écrit :
>>
>>
>> I don't believe that will work. dd runs on the raw device, not to an
>> artificially created "partition".
>
>
> dd runs on any type of device, including partitions.
>
But it copies th
(Google or something is screwing up the threading. My apologies if I
mess it up further.)
On Sun, Jun 4, 2017 at 7:30 AM, Fungi4All wrote:
>
>> From: deb...@lionunicorn.co.uk
>>
>>> Ι was waiting to see if anyone else found something like this significant
>> and willing to contribute some wisdom
From: deb...@lionunicorn.co.uk
> Ι was waiting to see if anyone else found something like this significant and
> willing to contribute some wisdom
No wisdom here, I'm afraid.
just evolution of the unix-dna
> I suspect the experiment would be simple.
> Let's say we make a new partition on a disk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jun 03, 2017 at 05:59:06PM +0200, Pascal Hambourg wrote:
> Le 03/06/2017 à 17:48, Gene Heskett a écrit :
> >
> >I don't believe that will work. dd runs on the raw device, not to an
> >artificially created "partition".
>
> dd runs on any type
Le 03/06/2017 à 18:04, David Wright a écrit :
AIUI there's a race condition here, perhaps even several. The correct
MBR should be read as normal by the BIOS, but grub then searches
by UUID for the kernel/ramdisk, and the kernel searches by UUID for
the root filesystem, and we don't know how it
On Sat 03 Jun 2017 at 11:02:54 (-0400), Fungi4All wrote:
> Ι was waiting to see if anyone else found something like this significant and
> willing to contribute some wisdom
No wisdom here, I'm afraid.
> I suspect the experiment would be simple.
> Let's say we make a new partition on a disk with
Le 03/06/2017 à 17:48, Gene Heskett a écrit :
I don't believe that will work. dd runs on the raw device, not to an
artificially created "partition".
dd runs on any type of device, including partitions.
On Saturday 03 June 2017 11:02:54 Fungi4All wrote:
> Original Message
> From: deb...@lionunicorn.co.uk
> To: debian-user@lists.debian.org
>
> On Thu 01 Jun 2017 at 12:24:28 (-0400), Fungi4All wrote:
> > Why don't just skip all this that we are in perfect agreement with
> > and go
Original Message
From: deb...@lionunicorn.co.uk
To: debian-user@lists.debian.org
On Thu 01 Jun 2017 at 12:24:28 (-0400), Fungi4All wrote:
> Why don't just skip all this that we are in perfect agreement with and go to
> the juicy part.
> After all uuids are unique and fstab are
On Thu 01 Jun 2017 at 12:24:28 (-0400), Fungi4All wrote:
> Why don't just skip all this that we are in perfect agreement with and go to
> the juicy part.
> After all uuids are unique and fstab are all correct, updating-grub would mix
> match uuids in writing
> its grub.cfg
> Two uuids on the sam
Original Message
Subject: drive names and UUIDs, was Re: Intresting dd fsck grub uuid fstab
action
From: joel.r...@gmail.com
To: Fungi4All
Fungi4All-san,
I'll try explaining what we don't know whether you understand or not.
I understand everything you have written
Fungi4All-san,
I'll try explaining what we don't know whether you understand or not.
First, about
/dev/sda
/dev/sdb
...
When you turn the machine on, these "names" do not exist. Well, at
least, the computer does not know which physical device is /dev/sda
and which is /dev/sdb, etc.
Whe
12 matches
Mail list logo
