Pointers to start new Express Disc development

northridgegrp
Posts: 134
Joined: Sun Mar 07, 2010 9:54 am

Re: Pointers to start new Express Disc development

Postby northridgegrp » Sun Jun 16, 2013 1:49 pm

Good progress!

We should probably not optimize for the size of the build until things are working well.
(I am using textual anaconda to configure, not doing X, so my process is somewhat different.)
I see you are doing the 64-bit build. I am going down the 32-bit path. ;)

northridgegrp
Posts: 134
Joined: Sun Mar 07, 2010 9:54 am

Amahi 7 Repository Information

Postby northridgegrp » Fri Jun 21, 2013 1:10 pm

What is the current http: repository information for getting the A7 rpms? Is this going to be the final production location and naming?

I am planning on integrating the A7 repos in to my build machine this weekend.

User avatar
cpg
Administrator
Posts: 2594
Joined: Wed Dec 03, 2008 7:40 am
Contact:

Re: Pointers to start new Express Disc development

Postby cpg » Fri Jun 21, 2013 1:15 pm

The location is the usual in our naming conventions:

Code: Select all

http://f18.amahi.org
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1

northridgegrp
Posts: 134
Joined: Sun Mar 07, 2010 9:54 am

Re: Pointers to start new Express Disc development

Postby northridgegrp » Fri Jun 21, 2013 1:27 pm

The location is the usual in our naming conventions:

Code: Select all

http://f18.amahi.org
Great thanx! I will provide a current status once I get this repo integrated in to my DVD build. I've been busy researching and tinkering a lot since we last chatted. I am currently waiting for some queries I posted to other reference sources in the last few days.

northridgegrp
Posts: 134
Joined: Sun Mar 07, 2010 9:54 am

Re: Amahi 7

Postby northridgegrp » Sat Jun 22, 2013 8:32 am

The location is the usual in our naming conventions:

Code: Select all

http://f18.amahi.org
Great thanx! I will provide a current status once I get this repo integrated in to my DVD build. I've been busy researching and tinkering a lot since we last chatted. I am currently waiting for some queries I posted to other reference sources in the last few days.
I am in the process of preparing for integrating the Amahi 7 packages in to a local repository.

Do you have a gpgkey for the A7 rpms?

When I define the local repo it would be nice to have something like this:
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-18-primary

If not then I will just disable the gpgcheck parameter in the yum repo definition.

User avatar
cpg
Administrator
Posts: 2594
Joined: Wed Dec 03, 2008 7:40 am
Contact:

Re: Pointers to start new Express Disc development

Postby cpg » Sat Jun 22, 2013 1:26 pm

No, they are not signed. Myabe one day we will, but so far there are much bigger issues.

For the same of providing actual details, so far all the ISO images with F18 rpms have two problems.

1) failed to start X and anaconda (the updated one) goes to text mode. The failure is in X, crashing with a VT_WAITACTIVE error (as you found out). Nothing posted in that thread provides concrete workarounds for it.

2) In addition, anaconda does not pick up any of the automated options in the kickstart file, therefore, it stops for user input. This defeats the purpose of the Express CD. Automation is key for the express cd. Example: rootpw --plaintext admin ... this should set the root password automatically. This does not work automatically.

The only way around issue #1 I have found is to build with Fedora 19 packages.

The only way around #2 I have found is for the user to actually have to type

Code: Select all

ks=....
at the command line in grub (after pressing TAB). Also defeats the purpose of automation. Not all the options for this part have been tested yet on Fedora 19 packages.

From my point of view, the options we have are:

1) Release without an express CD. Make people download the DVD and then add the Amahi repo. Really painful process.
2) Release a CD that makes people type something at the grub prompt
3) Root cause the issues of #2 and fix them (or work around them).

For the sake of concreteness and provide actual details, the base kickstart I am using is this (where http://mirror/ is a local repo mirror of 64-bit and noarch rpms):

Code: Select all

# Amahi Express Disc kickstart repo --name=f18-base --baseurl=http://mirror/f18/base/ repo --name=f18-amahi --baseurl=http://mirror/f18/amahi-specific/ repo --name=f18-updates --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-$releasever&arch=$basearch timezone US/Pacific --isUtc lang en_US.UTF-8 zerombr clearpart --all --initlabel bootloader --location=mbr autopart --type=plain part / --grow --fstype ext4 install cdrom %packages --excludedocs @core kernel anaconda isomd5sum grub-efi grub2 efibootmgr tmux # Amahi related hda-release hda-ctl hda-platform amahi-sync yum-plugin-fastestmirror dialog zenity wget %end rootpw --plaintext admin %post --nochroot # disable firstboot systemctl --no-reload disable firstboot-text.service 2> /dev/null || : systemctl --no-reload disable firstboot-graphical.service 2> /dev/null || : systemctl stop firstboot-text.service 2> /dev/null || : systemctl stop firstboot-graphical.service 2> /dev/null || : %end
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1

northridgegrp
Posts: 134
Joined: Sun Mar 07, 2010 9:54 am

Re: Pointers to start new Express Disc development

Postby northridgegrp » Sat Jun 22, 2013 7:05 pm

No, they are not signed. Myabe one day we will, but so far there are much bigger issues.

For the same of providing actual details, so far all the ISO images with F18 rpms have two problems.

1) failed to start X and anaconda (the updated one) goes to text mode. The failure is in X, crashing with a VT_WAITACTIVE error (as you found out). Nothing posted in that thread provides concrete workarounds for it.

2) In addition, anaconda does not pick up any of the automated options in the kickstart file, therefore, it stops for user input. This defeats the purpose of the Express CD. Automation is key for the express cd. Example: rootpw --plaintext admin ... this should set the root password automatically. This does not work automatically.

The only way around issue #1 I have found is to build with Fedora 19 packages.

The only way around #2 I have found is for the user to actually have to type

Code: Select all

ks=....
at the command line in grub (after pressing TAB). Also defeats the purpose of automation. Not all the options for this part have been tested yet on Fedora 19 packages.

From my point of view, the options we have are:

1) Release without an express CD. Make people download the DVD and then add the Amahi repo. Really painful process.
2) Release a CD that makes people type something at the grub prompt
3) Root cause the issues of #2 and fix them (or work around them).

For the sake of concreteness and provide actual details, the base kickstart I am using is this (where http://mirror/ is a local repo mirror of 64-bit and noarch rpms):

Code: Select all

# Amahi Express Disc kickstart repo --name=f18-base --baseurl=http://mirror/f18/base/ repo --name=f18-amahi --baseurl=http://mirror/f18/amahi-specific/ repo --name=f18-updates --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-$releasever&arch=$basearch timezone US/Pacific --isUtc lang en_US.UTF-8 zerombr clearpart --all --initlabel bootloader --location=mbr autopart --type=plain part / --grow --fstype ext4 install cdrom %packages --excludedocs @core kernel anaconda isomd5sum grub-efi grub2 efibootmgr tmux # Amahi related hda-release hda-ctl hda-platform amahi-sync yum-plugin-fastestmirror dialog zenity wget %end rootpw --plaintext admin %post --nochroot # disable firstboot systemctl --no-reload disable firstboot-text.service 2> /dev/null || : systemctl --no-reload disable firstboot-graphical.service 2> /dev/null || : systemctl stop firstboot-text.service 2> /dev/null || : systemctl stop firstboot-graphical.service 2> /dev/null || : %end
Regarding your Item 2. I discovered that about 4 days ago. I found out there is a Red Hat bug report that was posted in June about this. Apparently the bug is also present in F19 at present.

So far we have two bugs that are inhibiting us from building a decent Express Disc. Judging by things I have read it is not apparent when the bugs will be repaired. Apparently kickstart is going to get a pile of new features in F19. For the moment I am pursuing another experimental path and will let you know in the next few days if I am successful. I don't want to elaborate as I am not sure this path will work out.

User avatar
cpg
Administrator
Posts: 2594
Joined: Wed Dec 03, 2008 7:40 am
Contact:

Re: Pointers to start new Express Disc development

Postby cpg » Sat Jun 22, 2013 7:41 pm

Regarding your Item 2. I discovered that about 4 days ago. I found out there is a Red Hat bug report that was posted in June about this. Apparently the bug is also present in F19 at present.
exactly what bug is that?
So far we have two bugs that are inhibiting us from building a decent Express Disc. Judging by things I have read it is not apparent when the bugs will be repaired. Apparently kickstart is going to get a pile of new features in F19. For the moment I am pursuing another experimental path and will let you know in the next few days if I am successful. I don't want to elaborate as I am not sure this path will work out.
exactly where have you read that?
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1

northridgegrp
Posts: 134
Joined: Sun Mar 07, 2010 9:54 am

Re: Pointers to start new Express Disc development

Postby northridgegrp » Tue Jun 25, 2013 2:05 pm

I managed to use wget to download the hda-release rpm. Other than a standard rpm http style download how does one manually download the hda-ctl and hda-platform packages? rsync does not seem to work.

Unless I've missed some subtle syntax... :oops:

I am currently trying to add Amahi specific packages to the Spin I've been working on, still in the prototype stages. Lots of tinkering and testing at the moment... :?

User avatar
cpg
Administrator
Posts: 2594
Joined: Wed Dec 03, 2008 7:40 am
Contact:

Re: Pointers to start new Express Disc development

Postby cpg » Wed Jun 26, 2013 2:38 pm

the rpms (relative to the f18 site) are:

Code: Select all

armv5tel/hda-ctl-4.2.12-1.armv6l.rpm armv5tel/hda-platform-6.2.7-2.armv6l.rpm i386/hda-ctl-4.2.17-1.i686.rpm i386/hda-platform-6.2.17-1.i686.rpm noarch/hda-release-6.9.0-1.noarch.rpm x86_64/hda-ctl-4.2.17-1.x86_64.rpm x86_64/hda-platform-6.2.17-1.x86_64.rpm
you can also build them from the hda-platform and hda-ctl source code with "make rpm".
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1

Who is online

Users browsing this forum: No registered users and 1 guest