Fernando de Oliveira wrote:
On 10-09-2014 15:12, Bruce Dubbs wrote:
Ken Moffat wrote:
Also, for LFS the UUID stuff in grub.cfg is not needed, and will
cause pain if you ever have to restore backups to a new disk.
You can specify a partition uuid. No initrd required. For example:
linux /bzImage root=PARTUUID=666c2eee-193d-42db-a490-4c444342bd4e ro
The partition UUID is not the same as a filesystem UUID and the
partition table must be of type GPT (another advantage of GPT). To find
it, type something like:
$ blkid /dev/sdb1
/dev/sdb1: UUID="e337b2bd-3899-4307-b374-e1c4cb1b5b8e" TYPE="ext4"
PARTLABEL="Linux filesystem"
PARTUUID="4a1bdb85-2937-4c44-96bc-c9387c43779a"
There are advantages and disadvantages. A disadvantage is, as stated
above, when restoring a backup. An advantage is more consistency on
large hard drives where partitions may be created and deleted more
frequently.
While we are here, my technical problem was trying to use for the first
time gpt. Before formatting, I searched a lot, including in (B)LFS,
because I remembered something about a first partition, Couldn't find,
divided the dis in partion ' (ext4) and 2 (swap). After LFS ready, I
decided to make a backup of the new virtual HD with LFS-7.6-rc1, and
this was my lucky.
I use always gparted even to set boot_flag (cannot remember exact name).
Obviously, lost the system, and, don't know how, lost the sources
directory, but had the backup.
Two questions.
My question is: How large does partition 1 (boot_gpt) needs to be?
Only 1 MiB.
Now I have:
$ sudo /sbin/gdisk -l /dev/sdc
GPT fdisk (gdisk) version 0.8.10
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 44040192 sectors, 21.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): D4581B4F-4EBB-4290-9067-29B688B9CABE
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 44040158
Partitions will be aligned on 1-sector boundaries
Total free space is 5994 sectors (2.9 MiB)
Number Start (sector) End (sector) Size Code Name
1 34 2104514 1.0 GiB EF02
WAY too big -- By a factor of 1000. I suggest that you boot from a
livecd iso with gdisk and manually partition before installing. That
should get the start location at 2048.
2 2104515 37752749 17.0 GiB 0700
Microsoft basic data? Should be type 8300, Linux filesystem.
3 37752750 44034164 3.0 GiB 8200
Also have the second disk, with home, opt and two small test partitions,
used for BLFS tests of package updates:
Number Start (sector) End (sector) Size Code Name
1 34 27262304 13.0 GiB 8300
2 27262305 41945714 7.0 GiB 8300
3 41945715 44050229 1.0 GiB 8300
4 44050230 46137310 1019.1 MiB 8300
Question 2: why Code 0700 in sdc2, if I formatted as ext4, so it should
be Code 8300?
That works, but it is set by the partition tool.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
