Skip to main content

creating a bootable USB centOS from a Fedora

ISO to USB tool

I started from a minimal ISO taken from the centOS website (or mirror).

Then I used the livecd-iso-to-disk tool from the livecd-tools package this way:

 sudo livecd-iso-to-disk /media/500G/ISO/Fedora-16/Fedora-16-i686-Live-LXDE.iso /dev/sdb1 

Did not work out of the box

I mainly had 2 problems, but I think only 1 is related to the ISO building. The other one is more about something I did not investigate further.

First problem

The USB booted and wet through the Anaconda installer but:

When the installer looked for the existing disks: "The installation source given by device [''] could not be found. Please check your parameters and try again".

I checked the USB filesytem created with the livecd-iso-to-disk, and in the syslinux.cfg file, I only have:

append initrd=initrd.img stage2=hd:UUID=5E46-DFC2:/images/install.img repo=hd::/

According to this forum post, I modified my append line to be:

 append initrd=initrd.img stage2=hd:UUID=5E46-DFC2:/images/install.img repo=hd::/ method=hd:UUID=5E46-DFC2:/ 

Then I ran into the second problem...

Second problem

The installer did not find the iso file on the USB medium: I just had to copy the minimal iso on the USB and it worked.


Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl= " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme. I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create. Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard: "Create with shared configuration" will allow me to select the project I want the new one to share configuration with. The new created project will use the same configuration as the project I select There will be no creation of Workflow and Issue Scheme that