Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
L
lxc
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Chen Yisong
lxc
Commits
840295ff
Unverified
Commit
840295ff
authored
Aug 30, 2013
by
Stéphane Graber
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix some typos
Signed-off-by:
Dmitry Shachnev
<
mitya57@ubuntu.com
>
Reported-by: Vincent Ladeuil Acked-by:
Stéphane Graber
<
stgraber@ubuntu.com
>
parent
80507ee8
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
4 deletions
+4
-4
lxc.conf.sgml.in
doc/lxc.conf.sgml.in
+3
-3
lxc-ubuntu-cloud.in
templates/lxc-ubuntu-cloud.in
+1
-1
No files found.
doc/lxc.conf.sgml.in
View file @
840295ff
...
...
@@ -255,7 +255,7 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
bridge is set up as a reflective relay. Broadcast
frames coming in from the upper_dev get flooded to all
macvlan interfaces in VEPA mode, local frames are not
delivered locall
a
y, or <option>bridge</option>, it
delivered locally, or <option>bridge</option>, it
provides the behavior of a simple bridge between
different macvlan interfaces on the same port. Frames
from one interface to another one get delivered directly
...
...
@@ -570,7 +570,7 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
rootfs LXC will mount a fresh tmpfs under <filename>/dev</filename>
(limited to 100k) and fill in a minimal set of initial devices.
This is generally required when starting a container containing
a "systemd" based "init" but may be optional at other times. Addional
a "systemd" based "init" but may be optional at other times. Addi
ti
onal
devices in the containers /dev directory may be created through the
use of the <option>lxc.hook.autodev</option> hook.
</para>
...
...
@@ -1026,7 +1026,7 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Host relative path to the container configuration file. This
gives the container to reference the original, top level,
configuration file for the container in order to locate any
add
o
tional configuration information not otherwise made
add
i
tional configuration information not otherwise made
available. [<option>-f</option>]
</para>
</listitem>
...
...
templates/lxc-ubuntu-cloud.in
View file @
840295ff
...
...
@@ -148,7 +148,7 @@ LXC Container configuration for Ubuntu Cloud images.
Generic Options
[ -r | --release <release> ]: Release name of container, defaults to host
[ --rootfs <path> ]: Path in which rootfs will be placed
[ -a | --arch ]: Arhcitecture of container, defaults to host arcitecture
[ -a | --arch ]: Arhcitecture of container, defaults to host arc
h
itecture
[ -T | --tarball ]: Location of tarball
[ -d | --debug ]: Run with 'set -x' to debug errors
[ -s | --stream]: Use specified stream rather than 'released'
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment