Changeset 45174 in vbox
- Timestamp:
- Mar 25, 2013 2:05:19 PM (12 years ago)
- Location:
- trunk
- Files:
-
- 1 deleted
- 3 edited
-
doc/manual/en_US/user_AdvancedTopics.xml (modified) (2 diffs)
-
include/iprt/mem.h (modified) (1 diff)
-
src/VBox/Runtime/r3/os2/systemmem-os2.cpp (deleted)
-
src/VBox/Runtime/testcase/tstLog.cpp (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_AdvancedTopics.xml
r45173 r45174 252 252 guest logons on platforms which support this framework. Virtually all 253 253 modern Linux/Unix distributions rely on PAM.</para> 254 255 <para>For automated logons on Ubuntu (or Ubuntu-derived) distributions256 using LightDM as the display manager, please see257 <xref linkend="autologon_unix_lightdm" />.</para>258 254 259 255 <para>The <computeroutput>pam_vbox.so</computeroutput> module itself … … 410 406 <computeroutput>debug</computeroutput> option.</para> 411 407 </note></para> 412 413 <sect3 id="autologon_unix_lightdm">414 <title>VirtualBox Greeter for Ubuntu / LightDM</title>415 416 <para>Starting with version 4.2.6, VirtualBox comes with an own greeter417 module named vbox-greeter which can be used with LightDM 1.0.1 or later.418 LightDM is the default display manager since Ubuntu 10.11 and therefore419 also can be used for automated guest logons.</para>420 421 <para>vbox-greeter does not need the pam_vbox module described above422 in order to function -- it comes with its own authentication mechanism423 provided by LightDM. However, to provide maximum of flexibility both424 modules can be used together on the same guest.</para>425 426 <para>As for the pam_vbox module, vbox-greeter is shipped as part of427 the Guest Additions but it is not installed and/or activated on the428 guest OS by default For installing vbox-greeter automatically upon429 Guest Additions installation, use the430 <computeroutput>--with-autologon</computeroutput> switch when starting431 the VBoxLinuxAdditions.run file:<screen>432 # ./VBoxLinuxAdditions.run -- --with-autologon</screen></para>433 434 <para>For manual or postponed installation, the435 <computeroutput>vbox-greeter.desktop</computeroutput>436 file has to be copied from437 <computeroutput>/opt/VBoxGuestAdditions-<version>/shared/VBoxGuestAdditions/</computeroutput>438 to the <computeroutput>xgreeters</computeroutput> directory, usually439 <computeroutput>/usr/share/xgreeters/</computeroutput>.440 Please refer to your guest OS documentation for the correct LightDM441 greeter directory.</para>442 443 <para>The vbox-greeter module itself already was installed by the444 VirtualBox Guest Additions installer and resides in445 <computeroutput>/usr/sbin/</computeroutput>. To enable vbox-greeter as446 the standard greeter module, the file447 <computeroutput>/etc/lightdm/lightdm.conf</computeroutput> needs to be448 edited:</para>449 450 <para><screen>451 [SeatDefaults]452 greeter-session=vbox-greeter</screen></para>453 454 <note><para>The LightDM server needs to be fully restarted in order to455 get vbox-greeter used as the default greeter. As root, do a456 <computeroutput>service lightdm --full-restart</computeroutput> on457 Ubuntu, or simply restart the guest.</para></note>458 459 <note><para>vbox-greeter is independent of the graphical session chosen460 by the user (like Gnome, KDE, Unity etc). However it requires FLTK 1.3461 for representing its user interface.</para></note>462 463 <para>In addition to the guest property values of the464 pam_vbox module listed above, vbox-greeter has the following guest465 properties for further customizing its user interface, residing all in466 <computeroutput>/VirtualBox/GuestAdd/Greeter/</computeroutput>:</para>467 468 <orderedlist>469 <listitem>470 <para><computeroutput>HideRestart</computeroutput>: Set to "1" if471 vbox-greeter should hide the button to restart the guest. This472 property must be set read-only for the guest473 (<computeroutput>RDONLYGUEST</computeroutput>).</para>474 </listitem>475 476 <listitem>477 <para><computeroutput>HideShutdown</computeroutput>: Set to "1" if478 vbox-greeter should hide the button to shutdown the guest. This479 property must be set read-only for the guest480 (<computeroutput>RDONLYGUEST</computeroutput>).</para>481 </listitem>482 483 <listitem>484 <para><computeroutput>BannerPath</computeroutput>: Path to a .PNG485 file for using it as a banner on the top. The image size must be486 460 x 90 pixels, any bit depth. This property must be487 set read-only for the guest488 (<computeroutput>RDONLYGUEST</computeroutput>).</para>489 </listitem>490 491 <listitem>492 <para><computeroutput>UseTheming</computeroutput>: Set to "1" for493 turning on the following theming options. This property must be494 set read-only for the guest495 (<computeroutput>RDONLYGUEST</computeroutput>).</para>496 </listitem>497 498 <listitem>499 <para><computeroutput>Theme/BackgroundColor</computeroutput>:500 Hexadecimal RRGGBB color for the background. This property must be501 set read-only for the guest502 (<computeroutput>RDONLYGUEST</computeroutput>).</para>503 </listitem>504 505 <listitem>506 <para><computeroutput>Theme/LogonDialog/HeaderColor</computeroutput>:507 Hexadecimal RRGGBB foreground color for the header text. This508 property must be set read-only for the guest509 (<computeroutput>RDONLYGUEST</computeroutput>).</para>510 </listitem>511 512 <listitem>513 <para><computeroutput>Theme/LogonDialog/BackgroundColor</computeroutput>:514 Hexadecimal RRGGBB color for the logon dialog background. This515 property must be set read-only for the guest516 (<computeroutput>RDONLYGUEST</computeroutput>).</para>517 </listitem>518 519 <listitem>520 <para><computeroutput>Theme/LogonDialog/ButtonColor</computeroutput>:521 Hexadecimal RRGGBB background color for the logon dialog button. This522 property must be set read-only for the guest523 (<computeroutput>RDONLYGUEST</computeroutput>).</para>524 </listitem>525 </orderedlist>526 527 <note><para>The same restrictions for the guest properties above apply528 as for the ones specified in the pam_vbox section.</para></note>529 </sect3>530 408 </sect2> 531 409 </sect1> -
trunk/include/iprt/mem.h
r45173 r45174 66 66 */ 67 67 #ifndef RTMEM_TAG 68 # if 168 # if 0 69 69 # define RTMEM_TAG (__FILE__ ":" RT_XSTR(__LINE__)) 70 70 # else -
trunk/src/VBox/Runtime/testcase/tstLog.cpp
r45173 r45174 31 31 #include <iprt/initterm.h> 32 32 #include <iprt/err.h> 33 #include <iprt/stream.h>34 33 35 34 #include <stdio.h> … … 38 37 { 39 38 RTR3InitExeNoArguments(0); 40 uint32_t a = 0x80000000, b = 0x80000000, c = 0x80000000;41 RTPrintf("%d %d", 0x80000000, 0x80000000);42 39 printf("tstLog: Requires manual inspection of the log output!\n"); 43 40 RTLogPrintf("%%Rrc %d: %Rrc\n", VERR_INVALID_PARAMETER, VERR_INVALID_PARAMETER);
Note:
See TracChangeset
for help on using the changeset viewer.

