Revision history for LiveUSB


Revision [33691]

Last edited on 2024-07-27 14:52:47 by coolpup
Additions:
~~-[[https://mxlinux.org/wiki/help-files/help-mx-live-usb-maker/ MX Live USB Maker]] ([[https://github.com/MX-Linux/lum-qt-appimage/releases AppImage]])
Deletions:
~~-[[https://mxlinux.org/wiki/help-files/help-mx-live-usb-maker/ MX Live USB Maker]] [[https://github.com/MX-Linux/lum-qt-appimage/releases AppImage]]

Revision [33690]

Edited on 2024-07-27 14:50:58 by coolpup
Additions:
~~~-[[https://rufus.ie Rufus]] (the latest version of Rufus requires Windows 8 or later; last supported version for Windows 7 is [[https://github.com/pbatard/rufus/releases/download/v3.22/rufus-3.22p.exe version 3.22]])
~~~-[[https://gitlab.com/bztsrc/usbimager/-/releases USBImager]] ([[https://gitlab.com/bztsrc/usbimager/raw/master/usbimager-manual.pdf User's Manual]])
Deletions:
~~~-[[https://rufus.ie Rufus]] (advanced) (the latest version of Rufus requires Windows 8 or later; last supported version for Windows 7 is [[https://github.com/pbatard/rufus/releases/download/v3.22/rufus-3.22p.exe version 3.22]])
~~~-[[https://gitlab.com/bztsrc/usbimager/-/releases USBImager]] (simple) ([[https://gitlab.com/bztsrc/usbimager/raw/master/usbimager-manual.pdf User's Manual]])

Revision [33689]

Edited on 2024-07-27 14:49:47 by coolpup
Additions:
~~~-[[https://github.com/FedoraQt/MediaWriter/releases Fedora Media Writer]]

Revision [33688]

Edited on 2024-07-27 14:32:56 by coolpup
Additions:
- acquire the disk image file (with file extension //.img// or //.iso//) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- then, write the disk image file (with file extension //.img// or //.iso//) to an external device
~~~-then, write (burn) the disk image file (with file extension //.img// or //.iso//) to external device, via the command-line interface
Deletions:
- acquire the disk image file (with file extension //.img//, //.iso// or //.zip//) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- then, write the disk image file (with file extension //.img//, //.iso// or //.zip//) to an external device
~~~-then, write (burn) the disk image file (with file extension //.img//, //.iso// or //.zip//) to external device, via the command-line interface

Revision [33687]

Edited on 2024-07-27 14:30:55 by coolpup
Additions:
~~-[[https://gitlab.com/bztsrc/usbimager/-/releases USBImager]]
Deletions:
~~-[[https://gitlab.com/bztsrc/usbimager/ USBImager]]

Revision [33686]

Edited on 2024-07-27 14:29:25 by coolpup
Additions:
~~-[[https://mxlinux.org/wiki/help-files/help-mx-live-usb-maker/ MX Live USB Maker]] [[https://github.com/MX-Linux/lum-qt-appimage/releases AppImage]]

Revision [33656]

Edited on 2024-06-27 15:20:57 by coolpup
Additions:
{{nocomments}}

Revision [33592]

Edited on 2024-02-29 11:20:51 by coolpup
Additions:
~~-[[https://gitlab.com/systemrescue/systemrescue-usbwriter SystemRescue USB Writer]]
~~-[[https://gitlab.com/bztsrc/usbimager/ USBImager]]
~~-[[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]]
~~-//dd// command
Deletions:
~~-(i) [[https://gitlab.com/systemrescue/systemrescue-usbwriter SystemRescue USB Writer]]
~~-(ii) [[https://gitlab.com/bztsrc/usbimager/ USBImager]]
~~-(iii) [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]]
~~-(iv) //dd// command

Revision [33591]

Edited on 2024-02-23 08:09:20 by coolpup
Additions:
~~-(iii) [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]]
Deletions:
~~-(iii) [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] (G.U.I. & command-line interface modes available)

Revision [33590]

Edited on 2024-02-23 08:06:14 by coolpup
Additions:
~~-(i) [[https://gitlab.com/systemrescue/systemrescue-usbwriter SystemRescue USB Writer]]
~~-(ii) [[https://gitlab.com/bztsrc/usbimager/ USBImager]]
~~-(iii) [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] (G.U.I. & command-line interface modes available)
~~-(iv) //dd// command
Deletions:
~~-[[https://gitlab.com/systemrescue/systemrescue-usbwriter SystemRescue USB Writer]]
~~-[[https://gitlab.com/bztsrc/usbimager/ USBImager]]
~~-the //dd// command indirectly via [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] (G.U.I. & command-line interface modes available)
~~-the //dd// command directly

Revision [33589]

Edited on 2024-02-23 08:03:02 by coolpup
Additions:
~-From within GNU/Linux (select one of the following)
Deletions:
~-From within GNU/Linux
-Select one of the following:

Revision [33588]

Edited on 2024-02-23 08:00:20 by coolpup
Additions:
-Select one of the following:
Deletions:
Select one of the following:

Revision [33587]

Edited on 2024-02-23 07:57:47 by coolpup
Additions:
Select one of the following:
Deletions:
Select one of the following:

Revision [33586]

Edited on 2024-02-23 07:55:25 by coolpup
Additions:
~-From within GNU/Linux
Select one of the following:
~~-[[https://gitlab.com/systemrescue/systemrescue-usbwriter SystemRescue USB Writer]]
~~-[[https://gitlab.com/bztsrc/usbimager/ USBImager]]
~~-the //dd// command indirectly via [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] (G.U.I. & command-line interface modes available)
~~-the //dd// command directly
Deletions:
~-From within GNU/Linux:
~~-Either, use the //dd// command indirectly via [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] script (G.U.I. & command-line interface modes available)
~~-Or, use the //dd// command directly via the command-line interface

Revision [33585]

Edited on 2024-02-23 03:04:09 by coolpup
Additions:
~~~-next, list all known disk devices connected to the computer, via the command-line interface: %%lsblk -al%%
~~~-next, **{{color text="determine the correct device name (sdX) of the target device" c="red"}}** by invoking the //lsblk// command again, and comparing both outputs: %%lsblk -al%%
~~~~-**{{color text="WARNING" c="red"}}** the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK: %%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<DISK IMAGE FILE> of=/dev/sdX%%
~~~-[[https://gitlab.com/bztsrc/usbimager/-/releases USBImager]] (simple) ([[https://gitlab.com/bztsrc/usbimager/raw/master/usbimager-manual.pdf User's Manual]])
Deletions:
~~~-next, list all known disk devices connected to the computer, via the command-line interface: **%%lsblk -al%%**
~~~-next, **{{color text="determine the correct device name (sdX) of the target device" c="red"}}** by invoking the //lsblk// command again, and comparing both outputs: **%%lsblk -al%%**
~~~~-**{{color text="WARNING" c="red"}}** the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK: **%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<DISK IMAGE FILE> of=/dev/sdX%%**
~~~-[[https://gitlab.com/bztsrc/usbimager/-/releases USBImager]] (simple)

Revision [33584]

Edited on 2024-02-20 07:52:40 by coolpup
Additions:
https://www.system-rescue.org/Installing-SystemRescue-on-a-USB-memory-stick/

Revision [33582]

Edited on 2024-02-20 07:19:56 by coolpup
Additions:
~-//bypassing// the existing, internal operating system on one's computer
~-//without// altering the configuration of the existing, internal operating system on one's computer (//unless// one deliberately chooses to do so in order to fix a broken system configuration)
~~~-[[https://gitlab.com/bztsrc/usbimager/-/releases USBImager]] (simple)
Deletions:
~-//bypassing// the existing, internal operating system on ones computer
~-//without// altering the configuration of the existing, internal operating system on ones computer (//unless// one deliberately chooses to do so in order to fix a broken system configuration)
~~~-[[https://bztsrc.gitlab.io/usbimager/ USBImager]] (simple)

Revision [33572]

Edited on 2024-02-10 12:33:49 by coolpup
Additions:
~-next, ensure that the U.E.F.I./B.I.O.S. firmware (low-level software that starts just prior to the operating system doing so) settings is configured to follow the __desired boot sequence__ (read [[https://wikka.puppylinux.com/LiveDVD Appendix 3]])
Deletions:
~-next, ensure that the U.E.F.I./B.I.O.S. firmware (low-level software that starts just prior to the operating system doing so) is configured to follow the __desired boot sequence__ (read [[https://wikka.puppylinux.com/LiveDVD Appendix 3]])

Revision [33570]

Edited on 2024-02-10 11:57:40 by coolpup
Additions:
~~-Either, use the //dd// command indirectly via [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] script (G.U.I. & command-line interface modes available)
~~-Or, use the //dd// command directly via the command-line interface
Deletions:
~~-Using the //dd// command indirectly via [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] script (G.U.I. & command-line interface modes available)
~~-Using the //dd// command directly via the command-line interface

Revision [33569]

Edited on 2024-02-10 11:56:01 by coolpup
Additions:
~~-Using the //dd// command directly via the command-line interface
Deletions:
~~-Using the //dd// command directly

Revision [33568]

Edited on 2024-02-10 11:41:16 by coolpup
Additions:
~~-Using the //dd// command indirectly via [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] script (G.U.I. & command-line interface modes available)
Deletions:
~~-Using the //dd// command indirectly via [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] script (G.U.I. or command-line interface available)

Revision [33567]

Edited on 2024-02-10 11:29:47 by coolpup
Additions:
~~-Using the //dd// command indirectly via [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] script (G.U.I. or command-line interface available)
Deletions:
~~-Using the //dd// command indirectly via [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] (G.U.I. or command-line interface available)

Revision [33566]

Edited on 2024-02-10 11:28:51 by coolpup
Deletions:
[[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd]]

Revision [33565]

Edited on 2024-02-10 11:27:13 by coolpup
Additions:
~~-Using the //dd// command indirectly via [[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]] (G.U.I. or command-line interface available)
~~-Using the //dd// command directly
~~~-ensure the target device is disconnected, or remove all removable USB devices, from the computer
~~~-next, list all known disk devices connected to the computer, via the command-line interface: **%%lsblk -al%%**
~~~-next, connect the target device to the computer via an USB port
~~~-next, **{{color text="determine the correct device name (sdX) of the target device" c="red"}}** by invoking the //lsblk// command again, and comparing both outputs: **%%lsblk -al%%**
~~~-then, write (burn) the disk image file (with file extension //.img//, //.iso// or //.zip//) to external device, via the command-line interface
~~~~-**{{color text="WARNING" c="red"}}** the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK: **%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<DISK IMAGE FILE> of=/dev/sdX%%**
Deletions:
~~-ensure the target device is disconnected, or remove all removable USB devices, from the computer
~~-next, list all known disk devices connected to the computer, via the command-line interface: **%%lsblk -al%%**
~~-next, connect the target device to the computer via an USB port
~~-next, **{{color text="determine the correct device name (sdX) of the target device" c="red"}}** by invoking the //lsblk// command again, and comparing both outputs: **%%lsblk -al%%**
~~-then, write (burn) the disk image file (with file extension //.img//, //.iso// or //.zip//) to external device, via the command-line interface
~~~-**{{color text="WARNING" c="red"}}** the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK: **%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<DISK IMAGE FILE> of=/dev/sdX%%**

Revision [33564]

Edited on 2024-02-10 11:17:16 by coolpup
Additions:
~~-ensure an external device is connected to the smartphone/tablet, via the USB port
~~-then, use the following free software program:
~~~-[[https://etchdroid.app/ EtchDroid]]
Deletions:
~~-use [[https://etchdroid.app/ EtchDroid]]

Revision [33563]

Edited on 2024-02-10 11:11:11 by coolpup
Additions:
~-From within Android:
~~-use [[https://etchdroid.app/ EtchDroid]]

Revision [33562]

Edited on 2024-02-09 15:31:59 by coolpup
Additions:
~~-ensure the target device is disconnected, or remove all removable USB devices, from the computer
~~-next, list all known disk devices connected to the computer, via the command-line interface: **%%lsblk -al%%**
~~-next, **{{color text="determine the correct device name (sdX) of the target device" c="red"}}** by invoking the //lsblk// command again, and comparing both outputs: **%%lsblk -al%%**
Deletions:
~~-ensure the target device is disconnected from the computer
~~-next, list all USB external devices connected to the computer, via the command-line interface: **%%lsblk%%**
~~-next, **{{color text="determine the correct device name (sdX) of the target device" c="red"}}** by invoking the //lsblk// command again, and comparing both outputs: **%%lsblk%%**

Revision [33538]

Edited on 2024-02-08 06:27:44 by coolpup
Additions:
~-next, ensure that the computer is put in a __power-off state__
[[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd]]
Deletions:
~-next, ensure that the computer is in a __power-off state__
https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd

Revision [33529]

Edited on 2024-02-01 15:41:03 by coolpup
Additions:
==2a. How to write (burn) a disk image file to external device (except optical disc drive)==
==2b. How to write (burn) a disk image file to external device (optical disc drive only)==
~-go to [[LiveDVD]]
Deletions:
==2. How to write (burn) a disk image file to external device==

Revision [33528]

Edited on 2024-02-01 15:20:31 by coolpup
Additions:
~~-next, **{{color text="determine the correct device name (sdX) of the target device" c="red"}}** by invoking the //lsblk// command again, and comparing both outputs: **%%lsblk%%**
~~-then, write (burn) the disk image file (with file extension //.img//, //.iso// or //.zip//) to external device, via the command-line interface
~~-then, use either one of the following free software programs:
Deletions:
~~-**IMPORTANT** **{{color text="determine the correct device name (sdX) of the target device" c="red"}}** by invoking the //lsblk// command again, and comparing both outputs: **%%lsblk%%**
~~-next, write (burn) the disk image file (with file extension //.img//, //.iso// or //.zip//) to external device, via the command-line interface
~~-next, use either one of the following free software programs:

Revision [33527]

Edited on 2024-02-01 15:13:01 by coolpup
Additions:
~-optical disc drive (see [[LiveDVD]])
Deletions:
~-optical disk drive (see [[LiveDVD]])

Revision [33526]

Edited on 2024-02-01 15:12:16 by coolpup
Additions:
~-optical disk drive (see [[LiveDVD]])

Revision [33525]

Edited on 2024-02-01 15:08:31 by coolpup
Additions:
With a **live installation** of an operating system, it can be run directly from an external device:
With a **live installation** of an operating system, it can be run directly from an external device such as:
~-SD flash memory card
~-USB flash memory drive
~-solid-state drive (SSD)
~-hard disk drive (HDD)
Deletions:
With a **live installation** of an operating system, it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD):

Revision [33524]

Edited on 2024-02-01 14:56:52 by coolpup
Additions:
- then, write the disk image file (with file extension //.img//, //.iso// or //.zip//) to an external device
~~-next, list all USB external devices connected to the computer, via the command-line interface: **%%lsblk%%**
~~-next, connect the target device to the computer via an USB port
~~-next, write (burn) the disk image file (with file extension //.img//, //.iso// or //.zip//) to external device, via the command-line interface
~~-next, use either one of the following free software programs:
~-next, __power-on__ the computer
Deletions:
- write the disk image file (with file extension //.img//, //.iso// or //.zip//) to an external device
~~-list all USB external devices connected to the computer, via the command-line interface: **%%lsblk%%**
~~-connect the target device to the computer via an USB port
~~-write (burn) the disk image file (with file extension //.img//, //.iso// or //.zip//) to external device, via the command-line interface
~~-use either one of the following free software:
~-__power-on__ the computer

Revision [33523]

Edited on 2024-02-01 14:54:22 by coolpup
Additions:
==Appendix==
Deletions:
==4. Appendix==

Revision [33522]

Edited on 2024-02-01 13:15:22 by coolpup
Additions:
With a **live installation** of an operating system, it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD):
==1. How to create a live installation to external device==
==2. How to write (burn) a disk image file to external device==
==3. How to run GNU/Linux from the external device==
==4. Appendix==
Deletions:
With a **live installation** of an operating system, this means that it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD):
==How to create a live installation to external device==
==How to write (burn) a disk image file to external device==
==How to run GNU/Linux from the external device==
==Appendix==

Revision [33521]

Edited on 2024-02-01 13:04:30 by coolpup
Additions:
~-//bypassing// the existing, internal operating system on ones computer
~-//without// altering the configuration of the existing, internal operating system on ones computer (//unless// one deliberately chooses to do so in order to fix a broken system configuration)
- acquire the disk image file (with file extension //.img//, //.iso// or //.zip//) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- write the disk image file (with file extension //.img//, //.iso// or //.zip//) to an external device
~~-ensure the target device is disconnected from the computer
~~-write (burn) the disk image file (with file extension //.img//, //.iso// or //.zip//) to external device, via the command-line interface
~-ensure the external device is connected to the computer, usually via a USB port
~-next, ensure that the U.E.F.I./B.I.O.S. firmware (low-level software that starts just prior to the operating system doing so) is configured to follow the __desired boot sequence__ (read [[https://wikka.puppylinux.com/LiveDVD Appendix 3]])
~-next, ensure that the computer is in a __power-off state__
Deletions:
~-//bypassing// the existing operating system on your computer
~-//without// altering the configuration of the existing operating system on your computer (//unless// one deliberately chooses to do so in order to fix a broken system configuration)
- acquire the disk image file (with file extension //.img// or //.iso//) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- write the disk image file (with file extension //.img// or //.iso//) to an external device
~~-ensure the target device is __disconnected__ from the computer
~~-write (burn) the disk image file (with file extension //.img// or //.iso//) to external device, via the command-line interface
~-ensure the external device is __connected__ to the computer, usually via a USB port
~-ensure that the U.E.F.I./B.I.O.S. firmware (low-level software that starts just prior to the operating system doing so) is configured to follow the __desired boot sequence__ (read [[https://wikka.puppylinux.com/LiveDVD Appendix 3]])
~-next ensure that the computer is in a __power-off state__

Revision [33520]

Edited on 2024-02-01 12:03:42 by coolpup
Additions:
~~-use either one of the following free software:
~~~-[[https://rufus.ie Rufus]] (advanced) (the latest version of Rufus requires Windows 8 or later; last supported version for Windows 7 is [[https://github.com/pbatard/rufus/releases/download/v3.22/rufus-3.22p.exe version 3.22]])
~~~-[[https://bztsrc.gitlab.io/usbimager/ USBImager]] (simple)
Deletions:
~~-use the free software [[https://rufus.ie Rufus]] (the latest version of Rufus requires Windows 8 or later; last supported version for Windows 7 is [[https://github.com/pbatard/rufus/releases/download/v3.22/rufus-3.22p.exe version 3.22]])

Revision [33519]

Edited on 2024-01-30 07:36:42 by coolpup
Additions:
https://easyos.org/install/how-to-install-easyos-on-a-new-ssd.html
https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd
Deletions:
[[https://easyos.org/install/how-to-install-easyos-on-a-new-ssd.html https://easyos.org/install/how-to-install-easyos-on-a-new-ssd.html]]
[[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd]]

Revision [33518]

Edited on 2024-01-30 07:34:04 by coolpup
Additions:
https://www.happyassassin.net/posts/2014/01/25/uefi-boot-how-does-that-actually-work-then/
https://uefi.org/faq
Deletions:
[[https://www.happyassassin.net/posts/2014/01/25/uefi-boot-how-does-that-actually-work-then/ https://www.happyassassin.net/posts/2014/01/25/uefi-boot-how-does-that-actually-work-then/]]]]
[[https://uefi.org/faq https://uefi.org/faq]]

Revision [33514]

Edited on 2024-01-29 08:22:32 by coolpup
Additions:
~-next ensure that the computer is in a __power-off state__
[[https://www.happyassassin.net/posts/2014/01/25/uefi-boot-how-does-that-actually-work-then/ https://www.happyassassin.net/posts/2014/01/25/uefi-boot-how-does-that-actually-work-then/]]]]
[[https://uefi.org/faq https://uefi.org/faq]]
Deletions:
~-shutdown the computer and ensure that it is in a __power-off state__

Revision [33513]

Edited on 2024-01-29 08:09:34 by coolpup
Additions:
~-__power-on__ the computer
Deletions:
~---power-on-- the computer

Revision [33512]

Edited on 2024-01-29 08:08:05 by coolpup
Additions:
~-ensure the external device is __connected__ to the computer, usually via a USB port
~-ensure that the U.E.F.I./B.I.O.S. firmware (low-level software that starts just prior to the operating system doing so) is configured to follow the __desired boot sequence__ (read [[https://wikka.puppylinux.com/LiveDVD Appendix 3]])
~-shutdown the computer and ensure that it is in a __power-off state__
~---power-on-- the computer
Deletions:
~-ensure the external device is connected to the computer, usually via a USB port
~-ensure that the B.I.O.S./U.E.F.I. is configured to follow the correct boot sequence (read [[https://wikka.puppylinux.com/LiveDVD Appendix 3]])
~-shutdown the computer and ensure that the computer is switched off
~-switch on the computer

Revision [33511]

Edited on 2024-01-29 07:38:14 by coolpup
Additions:
~-ensure that the B.I.O.S./U.E.F.I. is configured to follow the correct boot sequence (read [[https://wikka.puppylinux.com/LiveDVD Appendix 3]])
Deletions:
~-ensure that the B.I.O.S. is configured to follow the correct boot sequence (read [[https://wikka.puppylinux.com/LiveDVD Appendix 3]])

Revision [33508]

Edited on 2024-01-27 12:52:08 by coolpup
Additions:
- acquire the disk image file (with file extension //.img// or //.iso//) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- write the disk image file (with file extension //.img// or //.iso//) to an external device
Deletions:
- acquire the **disk image** file (with file extension //.img// or //.iso//) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- write (burn) the disk image file (with file extension //.img// or //.iso//) to an external device

Revision [33501]

Edited on 2024-01-27 12:16:43 by coolpup
Additions:
==Appendix==
[[https://easyos.org/install/how-to-install-easyos-on-a-new-ssd.html https://easyos.org/install/how-to-install-easyos-on-a-new-ssd.html]]
Deletions:
==Appendix 1==

Revision [33475]

Edited on 2024-01-23 07:07:06 by coolpup
Additions:
[[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd]]
Deletions:
[[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]]

Revision [33474]

Edited on 2024-01-23 07:00:28 by coolpup
Additions:
With a **live installation** of an operating system, this means that it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD):
~-//bypassing// the existing operating system on your computer
~-//without// altering the configuration of the existing operating system on your computer (//unless// one deliberately chooses to do so in order to fix a broken system configuration)
Deletions:
With a **live installation** of an operating system means that:
~-it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD), //bypassing// the existing operating system on your computer
~-it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD), //without// altering the configuration of the existing operating system on your computer (//unless// one deliberately chooses to do so in order to fix a broken system configuration)

Revision [33473]

Edited on 2024-01-23 06:56:28 by coolpup
Additions:
With a **live installation** of an operating system means that:
~-it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD), //bypassing// the existing operating system on your computer
~-it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD), //without// altering the configuration of the existing operating system on your computer (//unless// one deliberately chooses to do so in order to fix a broken system configuration)
Deletions:
With a **live installation** of an operating system means that it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD), //without// altering the configuration of the existing operating system on your computer (//unless// one deliberately chooses to do so in order to fix a broken system confiiguration)

Revision [33472]

Edited on 2024-01-23 06:47:58 by coolpup
Additions:
[[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd EasyDD]]
Deletions:
[[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd]]
CategoryArchiving

Revision [33471]

Edited on 2024-01-23 06:44:18 by coolpup
Additions:
With a **live installation** of an operating system means that it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD), //without// altering the configuration of the existing operating system on your computer (//unless// one deliberately chooses to do so in order to fix a broken system confiiguration)
~-From within GNU/Linux:
~-From within Microsoft Windows:
Deletions:
With a **live installation** of an operating system means that it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD), //without// altering the configuration of the existing operating system on your computer.
~-__From within GNU/Linux__
~-__From within Microsoft Windows__
With a live installation one can do almost anything one can from a normal installation:
~-Safely browse the Internet without storing any history or cookie data
~-Access files and edit files stored on one's computer or external device
~-Create new office suite documents and save them remotely
~-Fix broken system configurations to get a computer running again
==Appendix 2==

Revision [33470]

Edited on 2024-01-23 06:33:47 by coolpup
Additions:
With a **live installation** of an operating system means that it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD), //without// altering the configuration of the existing operating system on your computer.
Deletions:
With a live installation of an operating system means that it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD), //without// altering the configuration of the existing operating system on your computer.

Revision [33469]

Edited on 2024-01-23 06:20:52 by coolpup
Additions:
==Appendix 1==
~-Safely browse the Internet without storing any history or cookie data
~-Access files and edit files stored on one's computer or external device
~-Fix broken system configurations to get a computer running again
==Appendix 2==
Deletions:
~-Safely browse the internet without storing any history or cookie data
~-Access files and edit files stored on your computer or external device
~-Fix broken configurations to get a computer running again
==Appendix==

Revision [33468]

Edited on 2024-01-23 06:16:00 by coolpup
Additions:
With a live installation of an operating system means that it can be run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD), //without// altering the configuration of the existing operating system on your computer.
With a live installation one can do almost anything one can from a normal installation:
~-Safely browse the internet without storing any history or cookie data
~-Access files and edit files stored on your computer or external device
~-Create new office suite documents and save them remotely
~-Fix broken configurations to get a computer running again
- acquire the **disk image** file (with file extension //.img// or //.iso//) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- write (burn) the disk image file (with file extension //.img// or //.iso//) to an external device
==How to write (burn) a disk image file to external device==
~~-write (burn) the disk image file (with file extension //.img// or //.iso//) to external device, via the command-line interface
~~~-**{{color text="WARNING" c="red"}}** the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK: **%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<DISK IMAGE FILE> of=/dev/sdX%%**
Deletions:
Puppy Linux can run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD).
- acquire the **image file** (with file extension //.img// or //.iso//) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- write (burn) the image file (with file extension //.img// or //.iso//) to an external device
==How to write (burn) an image file to external device==
~~-write (burn) the image file (with file extension //.img// or //.iso//) to external device, via the command-line interface
~~~-**{{color text="WARNING" c="red"}}** the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK: **%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX%%**

Revision [33464]

Edited on 2024-01-22 07:56:17 by coolpup
Additions:
[[https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd]]
Deletions:
https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd

Revision [33463]

Edited on 2024-01-22 07:55:22 by coolpup
Additions:
==Appendix==
https://easyos.org/install/how-to-write-easyos-to-a-flash-drive.html#EasyDD_frontend_for_dd

Revision [33460]

Edited on 2024-01-22 07:37:18 by coolpup
Additions:
~~-**IMPORTANT** **{{color text="determine the correct device name (sdX) of the target device" c="red"}}** by invoking the //lsblk// command again, and comparing both outputs: **%%lsblk%%**
Deletions:
~~-**IMPORTANT** **{{color text="determine the correct device name (sdX) of the target device" c="red"}}** by invoking the //lsblk// command again, and compare both outputs: **%%lsblk%%**

Revision [33457]

Edited on 2024-01-22 07:21:52 by coolpup
Additions:
Puppy Linux can run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state disk drive (SSD).
Deletions:
Puppy Linux can run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state drive (SSD).

Revision [33456]

Edited on 2024-01-22 07:20:54 by coolpup
Additions:
~~-use the free software [[https://rufus.ie Rufus]] (the latest version of Rufus requires Windows 8 or later; last supported version for Windows 7 is [[https://github.com/pbatard/rufus/releases/download/v3.22/rufus-3.22p.exe version 3.22]])
Deletions:
~~-use this free software [[https://rufus.ie Rufus]] (the latest version of Rufus requires Windows 8 or later; last supported version for Windows 7 is [[https://github.com/pbatard/rufus/releases/download/v3.22/rufus-3.22p.exe version 3.22]])

Revision [33455]

Edited on 2024-01-22 07:18:30 by coolpup
Additions:
~~-**IMPORTANT** **{{color text="determine the correct device name (sdX) of the target device" c="red"}}** by invoking the //lsblk// command again, and compare both outputs: **%%lsblk%%**
Deletions:
~~-**IMPORTANT** **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, by invoking the //lsblk// command again, and compare both outputs: **%%lsblk%%**

Revision [33454]

Edited on 2024-01-22 07:15:41 by coolpup
Additions:
~~-**IMPORTANT** **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, by invoking the //lsblk// command again, and compare both outputs: **%%lsblk%%**
Deletions:
~~-**IMPORTANT** **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**

Revision [33452]

Edited on 2024-01-22 07:00:30 by coolpup
Additions:
~-__From within GNU/Linux__
~~-**IMPORTANT** **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**
~-__From within Microsoft Windows__
Deletions:
~-__From Within GNU/Linux__
~~~-**IMPORTANT** **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**
~-__From Within Microsoft Windows__

Revision [33451]

Edited on 2024-01-22 06:59:02 by coolpup
Additions:
~~-ensure the target device is __disconnected__ from the computer
~~-list all USB external devices connected to the computer, via the command-line interface: **%%lsblk%%**
~~-connect the target device to the computer via an USB port

Revision [33450]

Edited on 2024-01-22 06:49:38 by coolpup
Additions:
~~~-**{{color text="WARNING" c="red"}}** the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK: **%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX%%**
Deletions:
~~~-({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX%%**

Revision [33449]

Edited on 2024-01-22 06:46:42 by coolpup
Additions:
~~-write (burn) the image file (with file extension //.img// or //.iso//) to external device, via the command-line interface
~~~-**IMPORTANT** **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**
~~~-({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX%%**
Deletions:
~~-write (burn) the image file (with file extension //.img// or //.iso//) to external device, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK):
~~~-**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**
~~~-**%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX%%**

Revision [33448]

Edited on 2024-01-22 06:18:10 by coolpup
Additions:
~~~-**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**
Deletions:
~~~-<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**<<

Revision [33445]

Edited on 2024-01-22 06:08:57 by coolpup

No Differences

Revision [33444]

Edited on 2024-01-22 06:08:02 by coolpup
Additions:
~~~-**%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX%%**
~~~-<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**<<
Deletions:
~~**%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX%%**
~~<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**<<

Revision [33443]

Edited on 2024-01-22 06:07:20 by coolpup
Additions:
~~-write (burn) the image file (with file extension //.img// or //.iso//) to external device, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK):
~~**%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX%%**
~~<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**<<
Deletions:
~~-write (burn) the image file (with file extension //.img// or //.iso//) to external device, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX%%**
~~-<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**<<

Revision [33442]

Edited on 2024-01-22 05:58:53 by coolpup
Additions:
~~-<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: **%%lsblk%%**<<
Deletions:
~~-<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: %%**lsblk**%%<<

Revision [33441]

Edited on 2024-01-22 05:57:30 by coolpup
Additions:
~~-<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: %%**lsblk**%%<<
Deletions:
~~-<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: %%lsblk%%<<

Revision [33440]

Edited on 2024-01-22 05:54:49 by coolpup
Additions:
~~-<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: %%lsblk%%<<
Deletions:
<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: %%lsblk%%<<

Revision [33439]

Edited on 2024-01-22 05:53:30 by coolpup
Additions:
<<**IMPORTANT**: **{{color text="determine the correct device name (sdX) of the target device" c="red"}}**, via the command-line interface: %%lsblk%%<<

Revision [33436]

Edited on 2024-01-22 05:11:33 by coolpup
Additions:
Puppy Linux can run directly from an external device such as an USB flash memory drive, SD flash memory card, hard disk drive (HDD) or solid state drive (SSD).
- write (burn) the image file (with file extension //.img// or //.iso//) to an external device
~-__From Within GNU/Linux__
~~-ensure an external device is connected to the computer, usually via a USB port
~~-write (burn) the image file (with file extension //.img// or //.iso//) to external device, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for your target device - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fdatasync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX%%**
~-__From Within Microsoft Windows__
~~-ensure an external device is connected to the computer, usually via a USB port
Deletions:
~Puppy Linux can run directly from a USB flash memory drive, SD flash memory card or solid state drive (SSD).
- write (burn) the image file (with file extension //.img// or //.iso//) to external device
~-__Within GNU/Linux__
~~-ensure the external device is connected to the computer, usually via a USB port
~~-write (burn) the image file (with file extension //.img// or //.iso//) to external device, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for the target device - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**
~-__ Within Microsoft Windows__
~~-ensure the external device is connected to the computer, usually via a USB port

Revision [33425]

Edited on 2024-01-21 14:00:53 by coolpup
Additions:
- acquire the **image file** (with file extension //.img// or //.iso//) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- write (burn) the image file (with file extension //.img// or //.iso//) to external device
~~-write (burn) the image file (with file extension //.img// or //.iso//) to external device, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for the target device - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**
Deletions:
- acquire the **image file** (//.img// or //.iso//) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- write (burn) the image file (//.img// or //.iso//) to external device
~~-write (burn) the image file (//.img// or //.iso//) to external device, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for the target device - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**

Revision [33424]

Edited on 2024-01-21 13:58:45 by coolpup
Additions:
- acquire the **image file** (//.img// or //.iso//) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- write (burn) the image file (//.img// or //.iso//) to external device
~~-write (burn) the image file (//.img// or //.iso//) to external device, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for the target device - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**
Deletions:
- acquire the **image file** (IMG or ISO) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
- write (burn) the image file (IMG or ISO) to external device
~~-write (burn) the image file (IMG or ISO) to external device, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for the target device - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**

Revision [33419]

Edited on 2024-01-21 05:27:49 by coolpup
Additions:
- acquire the **image file** (IMG or ISO) of the desired operating system, such as a recent Puppy Linux release (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
Deletions:
- acquire the **image file** (IMG or ISO) of the desired operating system, such as a recent Puppy Linux release, listed above (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])

Revision [33403]

Edited on 2024-01-21 02:11:39 by coolpup
Additions:
- acquire the **image file** (IMG or ISO) of the desired operating system, such as a recent Puppy Linux release, listed above (read [[https://wikka.puppylinux.com/LiveDVD Appendix 2]])
Deletions:
- acquire the **image file** (IMG or ISO) of the desired operating system, such as a recent Puppy Linux release, listed above (read //Appendix 2// below)

Revision [33402]

Edited on 2024-01-21 02:09:18 by coolpup
Additions:
~-ensure that the B.I.O.S. is configured to follow the correct boot sequence (read [[https://wikka.puppylinux.com/LiveDVD Appendix 3]])
Deletions:
~-ensure that the B.I.O.S. is configured to follow the correct boot sequence (read [[https://wikka.puppylinux.com/LiveDVD //Appendix 3//]])

Revision [33401]

Edited on 2024-01-21 02:08:37 by coolpup
Additions:
~-ensure that the B.I.O.S. is configured to follow the correct boot sequence (read [[https://wikka.puppylinux.com/LiveDVD //Appendix 3//]])
Deletions:
~-ensure that the B.I.O.S. is configured to follow the correct boot sequence (read [[LiveDVD //Appendix 3//]])

Revision [33400]

Edited on 2024-01-21 02:07:17 by coolpup
Additions:
==How to run GNU/Linux from the external device==
~-ensure the external device is connected to the computer, usually via a USB port
~-ensure that the B.I.O.S. is configured to follow the correct boot sequence (read [[LiveDVD //Appendix 3//]])
Deletions:
==How to run GNU/Linux from the external drive==
~-ensure the external drive is connected to the computer, usually via a USB port
~-ensure that the B.I.O.S. is configured to follow the correct boot sequence (read //Appendix 3// below)

Revision [33399]

Edited on 2024-01-21 02:05:47 by coolpup
Additions:
===Live Installation to External Device===
==How to create a live installation to external device==
- write (burn) the image file (IMG or ISO) to external device
==How to write (burn) an image file to external device==
~~-ensure the external device is connected to the computer, usually via a USB port
~~-write (burn) the image file (IMG or ISO) to external device, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target device X, where X represents the device letter for the target device - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**
~~-ensure the external device is connected to the computer, usually via a USB port
Deletions:
===Live Installation to External Drive===
==How to create a live installation to external drive==
- write (burn) the image file (IMG or ISO) to external drive
==How to write (burn) an image file to external drive==
~~-ensure the external drive is connected to the computer, usually via a USB port
~~-write (burn) the image file (IMG or ISO) to external drive, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target drive X, where X represents the device letter for the target drive - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**
~~-ensure the external drive is connected to the computer, usually via a USB port

Revision [33398]

Edited on 2024-01-21 01:55:43 by coolpup
Additions:
==How to create a live installation to external drive==
Deletions:
==How to create a live installation to external drive or partition==

Revision [33397]

Edited on 2024-01-21 01:55:00 by coolpup
Additions:
==How to create a live installation to external drive or partition==
~~-write (burn) the image file (IMG or ISO) to external drive, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target drive X, where X represents the device letter for the target drive - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**
Deletions:
==How to create a live installation to external drive==
~~-write (burn) the image file (IMG or ISO) to external drive, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target drive X, where X represents the device name of the target external drive - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**

Revision [33396]

Edited on 2024-01-21 01:50:01 by coolpup
Additions:
~~-write (burn) the image file (IMG or ISO) to external drive, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target drive X, where X represents the device name of the target external drive - USE ENTIRELY AT YOUR OWN RISK): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**
Deletions:
~~-write (burn) the image file (IMG or ISO) to external drive, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target drive X, where X represents the device name of the target external drive): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**

Revision [33395]

Edited on 2024-01-21 01:48:52 by coolpup
Additions:
~~-write (burn) the image file (IMG or ISO) to external drive, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite all existing data on the target drive X, where X represents the device name of the target external drive): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**
Deletions:
~~-write (burn) the image file (IMG or ISO) to external drive, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite the target drive X, where X represents the location of the target external drive): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**

Revision [33394]

Edited on 2024-01-21 01:46:54 by coolpup
Additions:
~~-write (burn) the image file (IMG or ISO) to external drive, via the command-line interface ({{color text="WARNING" c="red"}} the //dd// command will overwrite the target drive X, where X represents the location of the target external drive): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**
Deletions:
~~-write (burn) the image file (IMG or ISO) to external drive, via the command-line interface ({{color text="WARNING" c="red"}} the dd command will overwrite the target drive X, where X represents the location of the target external drive): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**

Revision [33392]

Edited on 2024-01-21 01:41:23 by coolpup
Additions:
---
----
==Categories==
CategoryArchiving
CategoryInstallation

Revision [33388]

Edited on 2024-01-21 01:24:18 by coolpup
Additions:
===Live Installation to External Drive===
~Puppy Linux can run directly from a USB flash memory drive, SD flash memory card or solid state drive (SSD).

==How to create a live installation to external drive==
- acquire the **image file** (IMG or ISO) of the desired operating system, such as a recent Puppy Linux release, listed above (read //Appendix 2// below)
- write (burn) the image file (IMG or ISO) to external drive

==How to write (burn) an image file to external drive==
~-__Within GNU/Linux__
~~-ensure the external drive is connected to the computer, usually via a USB port
~~-write (burn) the image file (IMG or ISO) to external drive, via the command-line interface ({{color text="WARNING" c="red"}} the dd command will overwrite the target drive X, where X represents the location of the target external drive): **%%time sudo dd bs=4M conv=notrunc,fsync oflag=direct status=progress if=<IMAGE FILE> of=/dev/sdX && sync%%**

~-__ Within Microsoft Windows__
~~-ensure the external drive is connected to the computer, usually via a USB port
~~-use this free software [[https://rufus.ie Rufus]] (the latest version of Rufus requires Windows 8 or later; last supported version for Windows 7 is [[https://github.com/pbatard/rufus/releases/download/v3.22/rufus-3.22p.exe version 3.22]])

==How to run GNU/Linux from the external drive==
~-ensure the external drive is connected to the computer, usually via a USB port
~-ensure that the B.I.O.S. is configured to follow the correct boot sequence (read //Appendix 3// below)
~-shutdown the computer and ensure that the computer is switched off
~-switch on the computer

Deletions:
http://puppylinux.org/wikka/InstallationFrugal

Revision [12108]

The oldest known version of this page was created on 2011-01-16 08:04:21 by coolpup
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki