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='https://ngx.rktmb.org/foo' 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='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 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='https://ngx.rktmb.org/foo&
Read more

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM
Read more

Emacs Pulumi LSP

Install Pulumi Emacs Mode The source code is on https://github.com/pulumi/pulumi-lsp. At the very bottom of the page are the instructions on how to install. You Need to have make installed. $ make install emacs-client mkdir -p ./bin go build -ldflags "-X github.com/pulumi/pulumi-lsp/sdk/version.Version=v0.2.3-6-gec49054" -o ./bin -p 10 ./cmd/... go: downloading github.com/pulumi/pulumi/sdk/v3 v3.53.1 ... ... ... go install -ldflags "-X github.com/pulumi/pulumi-lsp/sdk/version.Version=v0.2.3-6-gec49054" ./cmd/... mkdir -p editors/emacs/bin cd editors/emacs && emacs -Q --batch --eval "(progn (setq package-user-dir \"$(pwd)/bin\" \ package-archives '((\"melpa\" . \"https://melpa.org/packages/\") \
Read more