Changeset 3f460da0
- Timestamp:
- 09/04/2016 08:51:37 PM (8 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 2a589b08
- Parents:
- b06ee8de
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
general/sysutils/weston.xml
rb06ee8de r3f460da0 40 40 </para> 41 41 42 &lfs7 9_checked;&gcc6_checked;42 &lfs7a_checked; 43 43 44 44 <bridgehead renderas="sect3">Package Information</bridgehead> -
kde/kf5/kf5-frameworks.xml
rb06ee8de r3f460da0 104 104 <para role="optional"> 105 105 <xref linkend="doxygen"/>, 106 <ulink url="https://pypi.python.org/packages/source/J/Jinja2/">Jinja2</ulink>, and 107 <ulink url="http://pyyaml.org/">PyYAML</ulink> 106 <phrase revision="sysv"><ulink url="https://pypi.python.org/pypi/Jinja2">Jinja2</ulink></phrase> 107 <phrase revision="systemd"><xref linkend="Jinja2"/></phrase>, and 108 <phrase revision="sysv"><ulink url="http://pyyaml.org/">PyYAML</ulink></phrase> 109 <phrase revision="systemd"><xref linkend="PyYAML"/></phrase> 108 110 </para> 109 111 -
kde/plasma5/plasma-all.xml
rb06ee8de r3f460da0 266 266 <title>Starting Plasma5</title> 267 267 268 <para >268 <para revision="sysv"> 269 269 You can start <application>Plasma5</application> from runlevel 3, using 270 270 <xref linkend="xinit"/>, or from runlevel 5, using a Display Manager, … … 272 272 </para> 273 273 274 <para revision="systemd"> 275 You can start <application>Plasma5</application> from a TTY, using 276 <xref linkend="xinit"/>, or from a graphical display manager, such as 277 <xref linkend="sddm"/>. 278 </para> 279 274 280 <para> 275 281 To start <application>Plasma 5</application> using <xref linkend="xinit"/>, … … 277 283 </para> 278 284 279 <screen ><userinput>cat > ~/.xinitrc << "EOF"285 <screen revision="sysv"><userinput>cat > ~/.xinitrc << "EOF" 280 286 <literal>ck-launch-session dbus-launch --exit-with-session $KF5_PREFIX/bin/startkde</literal> 287 EOF 288 289 startx</userinput></screen> 290 291 <screen revision="systemd"><userinput>cat > ~/.xinitrc << "EOF" 292 <literal>dbus-launch --exit-with-session $KF5_PREFIX/bin/startkde</literal> 281 293 EOF 282 294 … … 299 311 <screen><userinput>startx &> ~/x-session-errors</userinput></screen> 300 312 301 <note >313 <note revision="sysv"> 302 314 <para> 303 315 You may wish to drop consolekit and/or dbus-launch, e.g., just using -
lxqt/desktop/post-install.xml
rb06ee8de r3f460da0 89 89 <title>Starting LXQt</title> 90 90 91 <para >91 <para revision="sysv"> 92 92 You can start <application>LXQt</application> from runlevel 3, using 93 93 <xref linkend="xinit"/>, or from runlevel 5, using a Display Manager, … … 95 95 file needs to be fixed, or will not be listed in <xref linkend="sddm"/> 96 96 and <xref linkend="lxdm"/>: 97 </para> 98 99 <para revision="systemd"> 100 You can start <application>LXQt</application> from a TTY, using 101 <xref linkend="xinit"/>, or by using a graphical display manager such 102 as <xref linkend="sddm"/>. The <filename>lxqt.desktop</filename> 103 file needs to be fixed, or it will not be listed in <xref linkend="sddm"/> 104 and <xref linkend="lxdm"/> 97 105 </para> 98 106 … … 105 113 </para> 106 114 107 <screen ><userinput>cat > ~/.xinitrc << "EOF"115 <screen revision="sysv"><userinput>cat > ~/.xinitrc << "EOF" 108 116 <literal>ck-launch-session dbus-launch --exit-with-session startlxqt</literal> 117 EOF 118 119 startx</userinput></screen> 120 121 <screen revision="systemd"><userinput>cat > ~/.xinitrc << "EOF" 122 <literal>dbus-launch --exit-with-session startlxqt</literal> 109 123 EOF 110 124 … … 127 141 <screen><userinput>startx &> ~/.x-session-errors</userinput></screen> 128 142 129 <note >143 <note revision="sysv"> 130 144 <para> 131 145 You may wish to drop consolekit and/or dbus-launch, e.g., just using -
x/dm/lxdm.xml
rb06ee8de r3f460da0 132 132 </para> 133 133 134 <screen ><userinput>./configure --prefix=/usr \134 <screen revision="sysv"><userinput>./configure --prefix=/usr \ 135 135 --sysconfdir=/etc \ 136 136 --with-pam \ 137 137 --with-systemdsystemunitdir=no && 138 make</userinput></screen> 139 140 <screen revision="systemd"><userinput>./configure --prefix=/usr \ 141 --sysconfdir=/etc \ 142 --with-pam && 138 143 make</userinput></screen> 139 144 … … 185 190 </para> 186 191 187 <para >192 <para revision="sysv"> 188 193 <parameter>--with-systemdsystemunitdir=no</parameter>: BLFS does not 189 194 support systemd. … … 255 260 </sect3> 256 261 257 <sect3 >262 <sect3 revision="sysv"> 258 263 <title>Starting lxdm</title> 259 264 -
xfce/core/xfce4-session.xml
rb06ee8de r3f460da0 179 179 <title>Starting Xfce4</title> 180 180 181 <para >181 <para revision="sysv"> 182 182 You can start <application>Xfce4</application> from runlevel 3, using 183 183 <xref linkend="xinit"/>, or from runlevel 5, using a Display Manager, … … 185 185 </para> 186 186 187 <para revision="systemd"> 188 You can start <application>Xfce4</application> from a TTY using 189 <xref linkend="xinit"/>, or from a graphical display manager, such as 190 <xref linkend="sddm"/>. 191 </para> 192 187 193 <para> 188 194 To start <application>Xfce4</application> using <xref linkend="xinit"/>, … … 190 196 </para> 191 197 192 <screen ><userinput>cat > ~/.xinitrc << "EOF"198 <screen revision="sysv"><userinput>cat > ~/.xinitrc << "EOF" 193 199 <literal>ck-launch-session dbus-launch --exit-with-session startxfce4</literal> 200 EOF 201 202 startx</userinput></screen> 203 204 <screen revision="systemd"><userinput>cat > ~/.xinitrc << "EOF" 205 <literal>dbus-launch --exit-with-session startxfce4</literal> 194 206 EOF 195 207 … … 212 224 <screen><userinput>startx &> ~/.x-session-errors</userinput></screen> 213 225 214 <note >226 <note revision="sysv"> 215 227 <para> 216 228 You may wish to drop consolekit and/or dbus-launch, e.g., just using
Note:
See TracChangeset
for help on using the changeset viewer.