Makeiso

This is an overview of the Makeiso project.

The goal of Makeios is to create an easy to use method of duplicating an existing Arch install for installation on new hardware. Makeiso will create a live iso containing all the info to recreate your Arch install, within a GUI environment.

This will be accomplished via downloading the Makeiso scripts and following the instructions.

I'll run through the process starting at downloading the scripts.

1) Downloaded the Makeiso archive from here: https://drive.google.com/open?id=0B1fY6LMsdRuOUjZaeTNIRGlHQUE

2) Create a ~/makeiso directory to place the archive in and extract it.

3) Open a terminal in the releng directory and su to root.

4) Run:  ./makeiso

5) It will take a while to run the script. When it's done, the ~/makeiso/releng/iso/ directory will contain your new iso.


Here's the makeiso script running to copy info and create the iso.


6) You can either burn the image to DVD or use the dd command to copy it to a usb thumb drive. Now boot the iso on the computer you want to install on.


You can "Boot Makeiso" or "Select Console Resolution" mode as shown.
Notice in blue, the instructions for logging in.


7) If you used the "Selectable Console Resolution" mode, you'll see this next. If you select "Boot Makeiso", skip ahead to step number 9.




This one is pretty self explanatory. Not much to say here...


8) Now you can select a resolution from the list.




9) Booting...




10) As instructed earlier, login as root. No password required.




11) Here, you can choose to proceed in either the console or  GUI mode. If you run GUI mode, skip ahead to step number 14.




12) Running the  # ig   command starts the lynx web browser with the arch installation guide.


This is the official installation guide from the Arch wiki.




13)  # man archlinux   




14) Running   # s   will startx into a basic tiling WM.




15) Pressing super key [left windows key], then F12 will bring up the info menu.




16)




17)




18)




19)









===================================================================================================

I wanted to source the images for this blog from my google drive, so I wouldn't have a messy collection below. For some reason, Google does not want to allow this.  If I use a direct link to the image, after a few minutes, the link gets blocked with a "403, you don't have permission to use this link".


Lets try again using gdurl: http://gdurl.com/   http://gdurl.com/qM4d  This website links directly to the image on your google drive.
During the process of setting this up, I learned that the ability to host an image on Google Drive has been discontinued by Google.



EDIT: Months later, the images in this page above, started disappearing. I gave in and did it how google wants, which results in the big fu##ing mess below!



google215b8b15eb5589eb.html

ą
1.png
(44k)
Jeff Story,
Jan 24, 2017, 12:02 AM
ą
10.png
(45k)
Jeff Story,
Jan 23, 2017, 11:40 PM
ą
100.png
(71k)
Jeff Story,
Jan 23, 2017, 11:16 PM
ą
101.png
(26k)
Jeff Story,
Jan 23, 2017, 11:41 PM
ą
102.png
(33k)
Jeff Story,
Jan 23, 2017, 11:41 PM
ą
103a.png
(2211k)
Jeff Story,
Jan 23, 2017, 11:41 PM
ą
104.png
(2263k)
Jeff Story,
Jan 23, 2017, 11:42 PM
ą
105(1).png
(2538k)
Jeff Story,
Jan 23, 2017, 11:43 PM
ą
105.png
(2538k)
Jeff Story,
Jan 23, 2017, 11:43 PM
ą
106.png
(521k)
Jeff Story,
Jan 24, 2017, 12:47 AM
ą
107.png
(681k)
Jeff Story,
Jan 24, 2017, 12:48 AM
ą
108.png
(2421k)
Jeff Story,
Jan 24, 2017, 12:49 AM
ą
109.png
(713k)
Jeff Story,
Jan 24, 2017, 12:49 AM
ą
11.png
(45k)
Jeff Story,
Jan 23, 2017, 11:40 PM
ą
2.png
(4k)
Jeff Story,
Jan 24, 2017, 12:02 AM
ą
3.png
(38k)
Jeff Story,
Jan 23, 2017, 11:12 PM
ą
4.png
(55k)
Jeff Story,
Jan 23, 2017, 11:12 PM
ą
5.png
(29k)
Jeff Story,
Jan 23, 2017, 11:12 PM
ą
6.png
(43k)
Jeff Story,
Jan 23, 2017, 11:12 PM
ą
7.png
(48k)
Jeff Story,
Jan 23, 2017, 11:40 PM
ą
8.png
(50k)
Jeff Story,
Jan 23, 2017, 11:40 PM
ą
9.png
(46k)
Jeff Story,
Jan 23, 2017, 11:40 PM
ċ
google215b8b15eb5589eb.html
(0k)
Jeff Story,
Oct 16, 2016, 10:16 AM
Comments