Bug 76706 - Optionally disable boot.log
Summary: Optionally disable boot.log
Status: RESOLVED FIXED
Alias: None
Product: plymouth
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-27 19:56 UTC by Cosimo Cecchi
Modified: 2014-03-27 20:16 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
0001-main-don-t-write-an-empty-file-when-no_boot_log-is-s.patch (1.48 KB, text/plain)
2014-03-27 19:59 UTC, Cosimo Cecchi 		Details
0002-main-add-a-no-boot-log-commandline-option.patch (2.75 KB, text/plain)
2014-03-27 19:59 UTC, Cosimo Cecchi 		Details
View All

Description Cosimo Cecchi 2014-03-27 19:56:42 UTC 
In order to minimize disk writes, one might want to disable plymouth's boot.log at startup, without changing the kernel command line.
Note that there's also a bug where boot.log will be created empty when the current kernel command line option is enabled.

The following patch adds support for a --no-boot-log command line option, that can be used e.g. from the systemd .service file.
Comment 1 Cosimo Cecchi 2014-03-27 19:59:12 UTC 
Created attachment 96481 [details]
0001-main-don-t-write-an-empty-file-when-no_boot_log-is-s.patch
Comment 2 Cosimo Cecchi 2014-03-27 19:59:28 UTC 
Created attachment 96482 [details]
0002-main-add-a-no-boot-log-commandline-option.patch
Comment 3 Ray Strode [halfline] 2014-03-27 20:16:05 UTC 
sure thanks, pushed!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.