GitLab

Created by: mmlb

When viewing a file from the Files view the file is rendered effectively like garbage. The file is an asciidoc.

The raw file follows

DSR Imaging Procedure
=====================
Manuel Mendez <mmendez@srtrl.com>
version 1, 09/06/2012

Imaging
-------
{empty}1. Insert the Clonezilla CD into the CD drive and plug the USB stick containing the image(s)
into one of the front USB ports.

{empty}2. Reboot the Dell server.

{empty}3. The server is configured to automatically boot from CD when available.
Clonezilla's boot screen should show up, as seen below.

image::00-boot.png[align="center",height="50%"]

<<<

{empty}4. Clonezilla will ask the preferred language, accept the default of English.

image::01-lang.png[align="center",height="50%"]

{empty}5. Select `Don't touch keymap`

image::02-keymap.png[align="center",height="50%"]

<<<

{empty}6. Start Clonezilla

image::03-start.png[align="center",height="50%"]

{empty}7. Select `device-image`

image::04-device-image.png[align="center",height="50%"]

<<<

{empty}8. Select `local_dev`

image::05-local_dev.png[align="center",height="50%"]

{empty}9. Clonezilla will then ask to insert the USB and wait 5 seconds. If the USB was not inserted before boot
insert it now and wait the 5 seconds. If the USB was already inserted, just press `Enter`.

image::06-usb.png[align="center",height="50%"]

<<<

{empty}10. Clonezilla will then show a list of the devices it found; select the USB device, which is usually `sdb1`.

image::07-sdb.png[align="center",height="50%"]

{empty}11. Select `/      Top_directory_in_the_local_device`

image::08-top_dir.png[align="center",height="50%"]

<<<

{empty}12. A list of all the filesystem usage will then be shown, continue by pressing `Enter`.

image::09-disk_usage.png[align="center",height="50%"]

{empty}13. The imaging process is about to begin. Select Beinner mode.

image::10-beginner.png[align="center",height="50%"]

<<<

{empty}14. Select the `restoredisk` option.

image::12-restore.png[align="center",height="50%"]

{empty}15. Select `dsr-2012-09-07-18-img` or the most recent image available.

image::13-image-file.png[align="center",height="50%"]

<<<

{empty}16. `sda` should be the only disk available for imaging onto.

image::14-dest-target.png[align="center",height="50%"]

{empty}17. Clonezilla print out the command it will execute. Press `Enter`.

image::14b-next-time-command.png[align="center",height="50%"]

<<<

{empty}17. Clonezilla will ask to verify the operation. Type `y` and `Enter`.

image::15-continue.png[align="center",height="50%"]

{empty}18. Type `y` and `Enter` again to confirm.

image::16-confirm.png[align="center",height="50%"]

<<<

{empty}19. Clonezilla will start the operation by restoring `/dev/sda1`.

image::17-sda1.png[align="center",height="50%"]

{empty}20. Clonezilla will proceed by restoring `/dev/sda3`.

image::18-sda3.png[align="center",height="50%"]

<<<

{empty}21. Once the restoration press `Enter` to get to the last step.

image::19-done.png[align="center",height="50%"]

{empty}22. Press `(1) Reboot` and `Enter` to reboot out of Clonezilla and into the new image.

image::20-reboot.png[align="center",height="50%"]

{empty}23. Proceed to configure the dsr as a specific DSR.

Configuration
-------------

{empty}1. Log in to the DSR using `root` as the username, and `thuraya` as the password.

{empty}2. Open a terminal by clicking the black terminal icon on the top panel.

{empty}3. Run the `set-dsr` command to set the ip address and other settings for this DSR to the appropriate values.

TIP: The DSR number can be verified from the LCD on the front of the Dell Server, or from the back RF-Panel tag.

image::21-set-dsr.png[align="center",height="50%"]

<<<

{empty}4. Once the settings have all been configured, the DSR will need to be
joined to the Windows AD domain. Using the command printed on the screen,
substitue `$USER` for a AD user with Admin rights.

image::22-set-dsr-done.png[align="center",height="50%"]

{empty}5. Reboot the DSR after it has been added to the domain.

Created by: RainFlying

Add "asciidoctor" to your Gemfile, then run bundle install again. GitHub::Markup.render will try Asciidoctor::Document.new(content).render first.

diff --git a/Gemfile b/Gemfile index e1e5bba..379178e 100644 --- a/Gemfile +++ b/Gemfile @@ -73,6 +73,7 @@ gem "seed-fu"

Markdown to HTML

gem "redcarpet", "~> 2.2.2" gem "github-markup", "~> 0.7.4", require: 'github/markup' +gem "asciidoctor"

Servers

gem "unicorn"

By Administrator on 2013-05-02T07:26:19 (imported from GitLab project)

Created by: mmlb

Awesome that worked great. I guess I expected GitHub::Markup.render to go out to asciidoc for the rendering.

By Administrator on 2013-05-02T13:20:35 (imported from GitLab project)

Created by: bbodenmiller

Is this still an issue in 5.2? Thanks for the issue report. Please reformat your issue to conform to the issue tracker guidelines found in our contributing guidelines.

By Administrator on 2013-06-11T23:35:13 (imported from GitLab project)