-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Using OSTree Examining Your System #73
base: master
Are you sure you want to change the base?
Conversation
Hold on to this, we kind of messed up the repo directory structure. Will merge once we fix it. |
<< History beyond this commit not fetched >> | ||
.... | ||
|
||
This ref has one commit in its history. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you interested in adding some information on how to download history that is not currently fetched?
Something like this: https://github.com/dustymabe/dustymabe.com/blob/33a300f3b31c7126b69a6d56487d251b776522ef/content/post/2017-09-01/post.md#browsing-histroy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, I'm happy to do that when I next get some spare time :)
To check which ref is currently checked out, run `ostree admin status`: | ||
|
||
.... | ||
$ ostree admin status |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we also show the output of rpm-ostree status
here and show the user that they essentially show the same output?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as their isn't an rpm-ostree
section, it makes sense to add that in here
closes #72