grub-devel
[Top][All Lists]
Advanced

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

Re: Each grub-mkrescue run leaves a file in /tmp/


From: Vladimir 'phcoder' Serbinenko
Subject: Re: Each grub-mkrescue run leaves a file in /tmp/
Date: Tue, 29 Dec 2015 19:13:41 +0100


Le 29 déc. 2015 7:05 PM, "Andrei Borzenkov" <address@hidden> a écrit :
>
> 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.
>
>
I meant in grub-install case. I don't think we need to waste space on ISO in mkrescue case. We shouldn't leave any files behind in temp for normal operation. We can have an option to leave them if it's useful
>
> _______________________________________________
> Grub-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/grub-devel
>


reply via email to

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