From: swedebugia <swedebugia@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>,
Julien Lepiller <julien@lepiller.eu>
Cc: 34184@debbugs.gnu.org
Subject: bug#34184: Nitpick on reconfigure message: Installing for i386-pc platform.
Date: Thu, 24 Jan 2019 08:41:25 +0100 [thread overview]
Message-ID: <52EB70B3-A774-4BE7-9872-16503C2C1EC1@riseup.net> (raw)
In-Reply-To: <87imyf57sh.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
Ricardo Wurmus <rekado@elephly.net> skrev: (23 januari 2019 23:27:26 CET)
>
>Julien Lepiller <julien@lepiller.eu> writes:
>
>> Le 23 janvier 2019 22:12:58 GMT+01:00, swedebugia
><swedebugia@riseup.net> a écrit :
>>>"Installing for i386-pc platform.
>>>Installation finished. No error reported."
>>>
>>>After reboot:
>>> $ uname -a
>>>Linux komputilo 4.20.3-gnu #1 SMP 1 x86_64 GNU/Linux
>>>
>>>The i386 is technically incorrect according to
>>>https://en.wikipedia.org/wiki/Intel_80386 and
>>>https://en.wikipedia.org/wiki/X86-64
>>>
>>>I think we should drop the line and keep "Installation finished. No
>>>error reported."
>>
>> Hi, this message is actually from grub-install and is perfectly
>> correct: it means it's intalling in legacy (bios) mode. "No error
>> reported" is also from grub and is very confusing…
>
>Maybe we should
>
>1) prefix messages from other tools with the name of the tool, and
>2) hide these tool messages by default behind descriptive messages like
>“installing bootloader”
>
>What do you think?
>
>--
>Ricardo
+1 😃
--
Sent from my p≡p for Android.
[-- Attachment #2: Type: text/html, Size: 1780 bytes --]
next prev parent reply other threads:[~2019-01-24 7:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 21:12 bug#34184: Nitpick on reconfigure message: Installing for i386-pc platform swedebugia
2019-01-23 21:40 ` Leo Famulari
2019-01-23 22:14 ` Julien Lepiller
2019-01-23 22:27 ` Ricardo Wurmus
2019-01-24 7:41 ` swedebugia [this message]
2019-01-25 22:37 ` Ludovic Courtès
2019-02-12 17:46 ` Leo Famulari
2020-05-13 21:52 ` Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52EB70B3-A774-4BE7-9872-16503C2C1EC1@riseup.net \
--to=swedebugia@riseup.net \
--cc=34184@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).