From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Each grub-mkrescue run leaves a file in /tmp/
Date: Tue, 29 Dec 2015 21:04:41 +0300 [thread overview]
Message-ID: <5682CB39.5050402@gmail.com> (raw)
In-Reply-To: <5682B9F4.3040700@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
29.12.2015 19:51, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
> On 28.12.2015 04:40, Andrei Borzenkov wrote:
>> 27.12.2015 23:48, Thomas Schmitt пишет:
>>> Hi,
>>>
>>> when running grub-mkrescue from Debian Sid, i get a
>>> growing collection of files in /tmp. One per run.
>>>
>>> Names are like:
>>> /tmp/grub.00529W
>>>
>>> Content is always the same:
>>> insmod part_acorn
>>> insmod part_amiga
>>> insmod part_apple
>>> insmod part_bsd
>>> insmod part_dfly
>>> insmod part_dvh
>>> insmod part_gpt
>>> insmod part_msdos
>>> insmod part_plan
>>> insmod part_sun
>>> insmod part_sunpc
>>>
>>
>> That's load.cfg used to build image. I'm surprised this is the only one
>> left, there should be more.
>>
>>> grub-mkrescue -V
>>> grub-mkrescue (GRUB) 2.02~beta2-33
>>>
>>> Where to report ? Upstream or distro ?
>>>
>>
>> Yes, I have this hanging around. Not because of garbage in /tmp, but to
>> better documentation of generated image (load.cfg is stored by
>> grub-install as well).
>>
>> Vladimir?
>>
> Fixed. It was just omission of delete. We leave load.cfg in our
> directory (boot/grub)
No, we do not.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-12-29 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <21871572876213560699@scdbackup.webframe.org>
2015-12-28 3:40 ` Each grub-mkrescue run leaves a file in /tmp/ Andrei Borzenkov
2015-12-29 16:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-12-29 18:04 ` Andrei Borzenkov [this message]
2015-12-29 18:13 ` Vladimir 'phcoder' Serbinenko
2015-12-29 18:31 ` Andrei Borzenkov
2015-12-29 18:55 ` Vladimir 'phcoder' Serbinenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5682CB39.5050402@gmail.com \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.