emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#33389: closed (parted not recognizing partitions i


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#33389: closed (parted not recognizing partitions in "non-standard" MBRs with valid partition tables)
Date: Thu, 27 Dec 2018 20:59:01 +0000

Your message dated Thu, 27 Dec 2018 12:58:30 -0800
with message-id <address@hidden>
and subject line 26.1.90; Emacs occasionally fails to receive asynchronous 
subprocess output in batch mode
has caused the debbugs.gnu.org bug report #33389,
regarding parted not recognizing partitions in "non-standard" MBRs with valid 
partition tables
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
33389: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=33389
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: parted not recognizing partitions in "non-standard" MBRs with valid partition tables Date: Thu, 15 Nov 2018 00:27:02 +0200 User-agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
Hello,

While parted 2.3 had no issues with whatever was in the first 446 bytes of the MBR and only looked at the partition table, newer versions such as 3.2 seem to be thrown by unusual boot code (e.g. Grub4DOS) and either show the entire disk as unallocated space or as one big volume/partition with the file system of the first volume. This is despite the partition table being fully compliant and happily read by fdisk and sfdisk.

This may be a "feature" rather than a bug.   Please pardon my ignorance, perhaps newer partition table schemes require the first 446 bits to be parsed.  However it could save someone many hours of frustration if this was noted prominently in the documentation.

In my case It was fixed with a simple:
  dd if=/usr/lib/syslinux/mbr/mbr.bin of=/dev/sdb bs=446 count=1
after taking the requisite backups and a deep breath.

Thanks and regards,
Marc



--- End Message ---
--- Begin Message --- Subject: 26.1.90; Emacs occasionally fails to receive asynchronous subprocess output in batch mode Date: Thu, 27 Dec 2018 12:58:30 -0800 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
I don't think the manual states that output can
arrive after the process has finished, but if that's the case, then it
should do so.

Good point, and I installed the attached patch into emacs-26 to try to do that.

As this bug report seems to stem from a misunderstanding of accept-process-output (quite understandable, as its functionality is obscure) I'm taking the liberty of closing the report. If I'm wrong please feel free to reopen it.

Attachment: 0001-Improve-accept-process-process-doc.patch
Description: Text Data


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]