RE: Create bootable ISO that can be copied to a USB key
Thanks Bill Askew PCS Technical Lead (832) 224-7074 BAB 3E209 -Original Message- From: Konstantin Olchanski [mailto:olcha...@triumf.ca] Sent: Friday, July 20, 2018 7:38 PM To: EXT-Askew, R W Cc: scientific-linux-us...@listserv.fnal.gov Subject: Re: Create bootable ISO that can be copied to a USB key On Thu, May 24, 2018 at 01:17:35PM -0500, Bill wrote: > > I am creating a custom installation ISO using kickstart. This install ISO is > based on SL 7.2. > Here is my recipe for doing what you are doing: https://urldefense.proofpoint.com/v2/url?u=https-3A__daqshare.triumf.ca_-7Eolchansk_linux_CentOS7_AAA-2DREADME-2DUSBBOOT.txt&d=DwIFAw&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=4ptmKZ4Ekfhxz8D8GRd9TzkLQxVH7j2H0j0TTzqUG-c&s=0QKisuAkqOezv6rjbP-lgO7ehBNbaSepYjPtfKNzBDc&e= -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: urldefence?!? Re: Create bootable ISO that can be copied to a USB key
Urldefense gets prepended to URLs in e-mail as it passes through a solution called ProofPoint. One would assume that an organization like Boeing would be using a solution such as what ProofPoint offers. —- A Get Outlook for iOS<https://urldefense.proofpoint.com/v2/url?u=https-3A__aka.ms_o0ukef&d=DwIF-g&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=MQr0X7DMMAqNR-2zlVAzIcpuYDa0vmT-AlTaI_-JCuc&s=cWY5Dl6Tl78s0R0_nhmPiprGxEnQLQnIKWPsjtZPy2w&e=> From: 30101714000n behalf of Sent: Saturday, July 21, 2018 10:13 AM To: scientific-linux-us...@listserv.fnal.gov Subject: Re: urldefence?!? Re: Create bootable ISO that can be copied to a USB key On Fri, Jul 20, 2018 at 07:04:52PM -0700, Konstantin Olchanski wrote: > On Fri, Jul 20, 2018 at 05:37:34PM -0700, Konstantin Olchanski wrote: > > Here is my recipe for doing what you are doing: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__daqshare.triumf.ca_-7Eolchansk_linux_CentOS7_AAA-2DREADME-2DUSBBOOT.txt&d=DwIBAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=fk0JY3BhmGxCfN3pBlvgoU0w4oeNX-YtFJkujmomPYY&s=O0aGOYpKPfw848g7KU-jZW8EGsRnZL7EQomfx6fHYXo&e= > WTF, urldefence, really?!? On second thoughts, never mind. It's just the Departement of Privacy (the new sibling of Dept of Love and Dept of Peace) going about their business. Same as after using the sslabs https test tool I see my newly setup web server getting probed by everybody and their dog; now posting a URL to a public mailing list attracts the same kind of attention. (maybe it's not "urldefence" leaking the data to 3rd parties, maybe it's the mailing list "archive service" or they just scrape the mailing list archives directly). I hope this is not wildly off-topic, but I am certainly surprised and I will be more careful about what I post to this mailing list. "The walls have ears", as they say, but these specific ears seem to have hands, as well. Here is the hits on my AAA-README file from the web server logs. No hits before my message to the mailing list. Afterwards, at at least some of the repeated GETs from repeated IP addresses look like robots. And too many hits altogether. I wish everybody would read my README file and become enlightened, but I think not. K.O. [root@daqshare httpd]# grep AAA ssl_access_log | sort 108.233.44.194 - - [20/Jul/2018:19:08:25 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 130.180.57.94 - - [21/Jul/2018:04:46:51 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 159.93.44.107 - - [21/Jul/2018:00:49:55 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 170.231.7.54 - - [20/Jul/2018:18:04:59 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.185.86.122 - - [20/Jul/2018:20:06:34 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.204.44.205 - - [21/Jul/2018:06:43:40 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.206.90.46 - - [21/Jul/2018:00:09:28 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.207.100.116 - - [21/Jul/2018:05:30:35 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.207.183.231 - - [21/Jul/2018:00:50:16 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.208.195.101 - - [21/Jul/2018:04:47:13 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.209.212.163 - - [20/Jul/2018:20:43:59 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 184.66.246.4 - - [20/Jul/2018:22:44:07 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 185.180.48.209 - - [20/Jul/2018:20:43:34 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 204.141.38.224 - - [21/Jul/2018:06:43:12 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 210.14.99.3 - - [20/Jul/2018:18:12:07 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.200.240.227 - - [20/Jul/2018:19:09:00 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.201.205.73 - - [20/Jul/2018:18:20:05 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.201.56.50 - - [20/Jul/2018:22:12:07 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.231.157.157 - - [20/Jul/2018:19:08:25 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1&qu
Re: urldefence?!? Re: Create bootable ISO that can be copied to a USB key
On 20180721 07:13, Konstantin Olchanski wrote:
On Fri, Jul 20, 2018 at 07:04:52PM -0700, Konstantin Olchanski wrote:
On Fri, Jul 20, 2018 at 05:37:34PM -0700, Konstantin Olchanski wrote:
Here is my recipe for doing what you are doing:
https://urldefense.proofpoint.com/v2/url?u=https-3A__daqshare.triumf.ca_-7Eolchansk_linux_CentOS7_AAA-2DREADME-2DUSBBOOT.txt&d=DwIBAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=fk0JY3BhmGxCfN3pBlvgoU0w4oeNX-YtFJkujmomPYY&s=O0aGOYpKPfw848g7KU-jZW8EGsRnZL7EQomfx6fHYXo&e=
WTF, urldefence, really?!?
On second thoughts, never mind. It's just the Departement of Privacy (the new
sibling of Dept of Love and Dept of Peace) going about their business.
Same as after using the sslabs https test tool I see my newly setup web server
getting probed by everybody and their dog; now posting a URL to a public
mailing list
attracts the same kind of attention.
(maybe it's not "urldefence" leaking the data to 3rd parties, maybe it's the
mailing
list "archive service" or they just scrape the mailing list archives directly).
I hope this is not wildly off-topic, but I am certainly surprised and I will be
more
careful about what I post to this mailing list. "The walls have ears", as they
say,
but these specific ears seem to have hands, as well.
Here is the hits on my AAA-README file from the web server logs. No hits before
my message
to the mailing list. Afterwards, at at least some of the repeated GETs from
repeated IP addresses
look like robots. And too many hits altogether. I wish everybody would
read my README file and become enlightened, but I think not.
K.O.
[root@daqshare httpd]# grep AAA ssl_access_log | sort
108.233.44.194 - - [20/Jul/2018:19:08:25 -0700] "GET
/~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102
130.180.57.94 - - [21/Jul/2018:04:46:51 -0700] "GET
/~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102
...
Don't forget that more than just a few people are reading this list. Many will
check your page out of curiosity as well as need.
{o.o}
Re: urldefence?!? Re: Create bootable ISO that can be copied to a USB key
On Fri, Jul 20, 2018 at 07:04:52PM -0700, Konstantin Olchanski wrote: > On Fri, Jul 20, 2018 at 05:37:34PM -0700, Konstantin Olchanski wrote: > > Here is my recipe for doing what you are doing: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__daqshare.triumf.ca_-7Eolchansk_linux_CentOS7_AAA-2DREADME-2DUSBBOOT.txt&d=DwIBAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=fk0JY3BhmGxCfN3pBlvgoU0w4oeNX-YtFJkujmomPYY&s=O0aGOYpKPfw848g7KU-jZW8EGsRnZL7EQomfx6fHYXo&e= > WTF, urldefence, really?!? On second thoughts, never mind. It's just the Departement of Privacy (the new sibling of Dept of Love and Dept of Peace) going about their business. Same as after using the sslabs https test tool I see my newly setup web server getting probed by everybody and their dog; now posting a URL to a public mailing list attracts the same kind of attention. (maybe it's not "urldefence" leaking the data to 3rd parties, maybe it's the mailing list "archive service" or they just scrape the mailing list archives directly). I hope this is not wildly off-topic, but I am certainly surprised and I will be more careful about what I post to this mailing list. "The walls have ears", as they say, but these specific ears seem to have hands, as well. Here is the hits on my AAA-README file from the web server logs. No hits before my message to the mailing list. Afterwards, at at least some of the repeated GETs from repeated IP addresses look like robots. And too many hits altogether. I wish everybody would read my README file and become enlightened, but I think not. K.O. [root@daqshare httpd]# grep AAA ssl_access_log | sort 108.233.44.194 - - [20/Jul/2018:19:08:25 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 130.180.57.94 - - [21/Jul/2018:04:46:51 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 159.93.44.107 - - [21/Jul/2018:00:49:55 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 170.231.7.54 - - [20/Jul/2018:18:04:59 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.185.86.122 - - [20/Jul/2018:20:06:34 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.204.44.205 - - [21/Jul/2018:06:43:40 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.206.90.46 - - [21/Jul/2018:00:09:28 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.207.100.116 - - [21/Jul/2018:05:30:35 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.207.183.231 - - [21/Jul/2018:00:50:16 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.208.195.101 - - [21/Jul/2018:04:47:13 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 18.209.212.163 - - [20/Jul/2018:20:43:59 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 184.66.246.4 - - [20/Jul/2018:22:44:07 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 185.180.48.209 - - [20/Jul/2018:20:43:34 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 204.141.38.224 - - [21/Jul/2018:06:43:12 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 210.14.99.3 - - [20/Jul/2018:18:12:07 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.200.240.227 - - [20/Jul/2018:19:09:00 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.201.205.73 - - [20/Jul/2018:18:20:05 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.201.56.50 - - [20/Jul/2018:22:12:07 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.231.157.157 - - [20/Jul/2018:19:08:25 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.232.127.140 - - [20/Jul/2018:18:19:47 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.232.127.140 - - [20/Jul/2018:20:43:35 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.232.127.140 - - [21/Jul/2018:00:09:09 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 34.232.127.140 - - [21/Jul/2018:00:49:57 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 35.170.198.113 - - [20/Jul/2018:17:45:11 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 52.44.93.197 - - [20/Jul/2018:17:44:50 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 52.44.93.197 - - [20/Jul/2018:20:06:14 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 52.44.93.197 - - [20/Jul/2018:22:11:42 -0700] "GET /~olchansk/linux/CentOS7/AAA-README-USBBOOT.txt HTTP/1.1" 200 2102 52.44.93.197 - - [20/Jul/2018:22:44:11 -0700] "GET /~olchansk/linux/CentO
urldefence?!? Re: Create bootable ISO that can be copied to a USB key
On Fri, Jul 20, 2018 at 05:37:34PM -0700, Konstantin Olchanski wrote: > > Here is my recipe for doing what you are doing: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__daqshare.triumf.ca_-7Eolchansk_linux_CentOS7_AAA-2DREADME-2DUSBBOOT.txt&d=DwIBAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=fk0JY3BhmGxCfN3pBlvgoU0w4oeNX-YtFJkujmomPYY&s=O0aGOYpKPfw848g7KU-jZW8EGsRnZL7EQomfx6fHYXo&e= > WTF, urldefence, really?!? -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: Create bootable ISO that can be copied to a USB key
On Thu, May 24, 2018 at 01:17:35PM -0500, Bill wrote: > > I am creating a custom installation ISO using kickstart. This install ISO is > based on SL 7.2. > Here is my recipe for doing what you are doing: https://urldefense.proofpoint.com/v2/url?u=https-3A__daqshare.triumf.ca_-7Eolchansk_linux_CentOS7_AAA-2DREADME-2DUSBBOOT.txt&d=DwIBAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=fk0JY3BhmGxCfN3pBlvgoU0w4oeNX-YtFJkujmomPYY&s=O0aGOYpKPfw848g7KU-jZW8EGsRnZL7EQomfx6fHYXo&e= -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: Create bootable ISO that can be copied to a USB key
Thanks everyone for the responses. Using isohybrid on the ISO did the trick. Now when I use dd to create the install on the USB key the system boots from the USB key and I see the installation menu. Bill
Re: Create bootable ISO that can be copied to a USB key
> On May 24, 2018, at 2:17 PM, Bill wrote: > > I am creating a custom installation ISO using kickstart. This install ISO is > based on SL 7.2. > > When I burn a DVD from this ISO I can boot from the DVD and the install menu > come up as expected. > > When I use dd to copy the ISO to a USB key and try to boot from the USB key > the install menu does not appear and the system boots from the hard drive. > > I tried using dd to copy the SL7.2 ISO to a USB key. When I try to boot from > this USB key the install menu comes up as expected. > > What files on the SL7.2 have to do with booting from the USB key? “Any if them”, especially the boot loader, which is normally written *before* the partition information and superblicks for the filesystem. That was what “dd” copies first which file copies would not copy. > > Is there a mkisofs option I should be using to make booting USB key work? “dd” is your friend. There are many guidelines for building bootable cd’s you could review, but you can probably save a lot of work not using that.
Re: Create bootable ISO that can be copied to a USB key
Hey Bill,
This is not an uncommon thing to be doing, and there are
definitely challenges in terms of MBR/EFI, and media in doing
this.
I've culled some of my key resources as a short list of URLs here:
http://www.tuxfixer.com/mount-modify-edit-repack-create-uefi-iso-including-kickstart-file/
https://access.redhat.com/solutions/60959
http://ideanist.com/2017/03/09/unattended-kickstart-installation-centos-7/
http://www.frankreimer.de/?p=522
http://www.smorgasbork.com/2012/01/04/building-a-custom-centos-7-kickstart-disc-part-3/
https://gist.github.com/vkanevska/fd624f708cde7d7c172a576b10bc6966
# This is where I learned you have to mount -o loop the efi
image
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/anaconda_customization_guide/
I'd pay very close attention to that github gist that points out
that efi image that you'll need to mount and modify (there are
actually three locations you need to edit/modify for the bootable
media: EFI/BOOT/grub.cfg, isolinux.cfg, and within
images/efiboot.img).
The mkisofs command that we're using at ${EMPLOYER} is:
mkisofs -o
"${BASE_DIR}"/"${ENV}"/custom_${today}.iso \
-b isolinux/isolinux.bin -c
isolinux/boot.cat \
--no-emul-boot --boot-load-size
4 --boot-info-table \
-eltorito-alt-boot -e
images/efiboot.img -no-emul-boot \
-graft-points -m .git* -f -J -R
-V "CentOS 7 x86_64" -A \
"CentOS 7 x86_64" -volset
"CentOS 7 x86_64" /custom/
We're clearly working on/with CentOS, but you should be close with
the above.
Regards,
Steven M. Miano
(727)244-9990
http://stevenmiano.com
2AFF 44FC 5CC6 B712 00C7 79EF 1811 C2CB 8219 4F52
On 5/24/18 14:17, Bill wrote:
I am creating a custom installation ISO using kickstart. This install ISO is based on SL 7.2.
When I burn a DVD from this ISO I can boot from the DVD and the install menu come up as expected.
When I use dd to copy the ISO to a USB key and try to boot from the USB key the install menu does not appear and the system boots from the hard drive.
I tried using dd to copy the SL7.2 ISO to a USB key. When I try to boot from this USB key the install menu comes up as expected.
What files on the SL7.2 have to do with booting from the USB key?
Is there a mkisofs option I should be using to make booting USB key work?
signature.asc
Description: OpenPGP digital signature
