Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 970
    • Issues 970
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #10831
Closed
Open
Issue created Dec 31, 2015 by intrigeri@intrigeriMaintainer

Update nopersistent boot parameter

Originally created by @intrigeri on #10831 (Redmine)

Apparently, since live-boot (3.0~a27-1) and this commit:

commit 4e54d60d7f69ae3441e519e5611bd7ea48a8be19
Author: Daniel Baumann <daniel@debian.org>
Date:   Sun Apr 8 18:29:45 2012 +0200

    Using 'persistence' (noun) rather than 'persistent' (adjective/adverb) everywhere.

… we should use nopersistence instead of nopersistent on the kernel command line.

Strangely, db4e9230 updates the design doc while the code is unchanged. Too bad we didn’t have an automated test for the way live-boot handles persistence in the initramfs.

This may has security implications, to be confirmed (the fact we’re passing live-media=removable might help quite a bit).

Feature Branch: bugfix/persistence-fixes-for-2.0-take1

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking