Hello, list!
WHile trying to generate a livecd with the git version of revisor from thursday 17.th (or wed 16.th, not sure), I get an iso file of about 3GB, although I expect it to be about 500MB. I'm not sure what debug info you need to tell me why it is so large, so I just want to ask if there is some known issues regarding theis problem. If not, I will come back with more info, e.g. output from the building process etc.
Thanks
Lars
Lars Bjørndal wrote:
Hello, list!
WHile trying to generate a livecd with the git version of revisor from thursday 17.th (or wed 16.th, not sure), I get an iso file of about 3GB, although I expect it to be about 500MB. I'm not sure what debug info you need to tell me why it is so large, so I just want to ask if there is some known issues regarding theis problem. If not, I will come back with more info, e.g. output from the building process etc.
This has been a known issue in certain cases where both the squashfs.img and the ext3.img end up on the ISO image. Please use the latest from GIT and tell us if it's solved now.
Kind regards,
Jeroen van Meeuwen -kanarip
Jeroen van Meeuwen kanarip@kanarip.com writes:
Lars Bjørndal wrote:
Hello, list! WHile trying to generate a livecd with the git version of revisor from thursday 17.th (or wed 16.th, not sure), I get an iso file of about 3GB, although I expect it to be about 500MB. I'm not sure what debug info you need to tell me why it is so large, so I just want to ask if there is some known issues regarding theis problem. If not, I will come back with more info, e.g. output from the building process etc.
This has been a known issue in certain cases where both the squashfs.img and the ext3.img end up on the ISO image. Please use the latest from GIT and tell us if it's solved now.
Yes it is. However, I'm not able to boot the livecd:
Reading from bottom and upwards:
swithroot: mount failed: No such file or directory Setuproot: error mounting /sys: no such file or directory setuproot: mounting /proc no succh file or directory setuproot: moving /dev failed no such file or directory mount: missing mount point mkrootdev: expected fs options
What could be done to fix this?
Best regards,
Lars
Lars Bjørndal wrote:
Jeroen van Meeuwen kanarip@kanarip.com writes:
Lars Bjørndal wrote:
Hello, list! WHile trying to generate a livecd with the git version of revisor from thursday 17.th (or wed 16.th, not sure), I get an iso file of about 3GB, although I expect it to be about 500MB. I'm not sure what debug info you need to tell me why it is so large, so I just want to ask if there is some known issues regarding theis problem. If not, I will come back with more info, e.g. output from the building process etc.
This has been a known issue in certain cases where both the squashfs.img and the ext3.img end up on the ISO image. Please use the latest from GIT and tell us if it's solved now.
Yes it is. However, I'm not able to boot the livecd:
Reading from bottom and upwards:
swithroot: mount failed: No such file or directory Setuproot: error mounting /sys: no such file or directory setuproot: mounting /proc no succh file or directory setuproot: moving /dev failed no such file or directory mount: missing mount point mkrootdev: expected fs options
My guess is you're trying to create a Fedora 8 LiveCD? I've seen this before, the init script in initrd0.img is missing some file labels and mount points. I've not been able to fix it in F8, but I do know it composes rawhide quite well. For composing Fedora 8 (or on Fedora 8) though, you might want to try the F-8 branch of Revisor, which will have less features (2.0.5) then the master or F-9 branch, or livecd-tools.
Kind regards,
Jeroen van Meeuwen -kanarip
Jeroen van Meeuwen kanarip@kanarip.com writes:
Lars Bjørndal wrote:
Jeroen van Meeuwen kanarip@kanarip.com writes:
Lars Bjørndal wrote:
Hello, list! WHile trying to generate a livecd with the git version of revisor from thursday 17.th (or wed 16.th, not sure), I get an iso file of about 3GB, although I expect it to be about 500MB. I'm not sure what debug info you need to tell me why it is so large, so I just want to ask if there is some known issues regarding theis problem. If not, I will come back with more info, e.g. output from the building process etc.
This has been a known issue in certain cases where both the squashfs.img and the ext3.img end up on the ISO image. Please use the latest from GIT and tell us if it's solved now.
Yes it is. However, I'm not able to boot the livecd: Reading from bottom and upwards: swithroot: mount failed: No such file or directory Setuproot: error mounting /sys: no such file or directory setuproot: mounting /proc no succh file or directory setuproot: moving /dev failed no such file or directory mount: missing mount point mkrootdev: expected fs options
My guess is you're trying to create a Fedora 8 LiveCD?
That's right.
I've seen this before, the init script in initrd0.img is missing some file labels and mount points. I've not been able to fix it in F8, but I do know it composes rawhide quite well. For composing Fedora 8 (or on Fedora 8) though, you might want to try the F-8 branch of Revisor, which will have less features (2.0.5) then the master or F-9 branch, or livecd-tools.
The command 'git branch' gives me only * master. So how do I grab the F-8 branch of Revisor?
Lars
Lars Bjørndal wrote:
The command 'git branch' gives me only * master. So how do I grab the F-8 branch of Revisor?
Go to the revisor source tree you have now, and go up one directory
Type:
git clone --reference <current-source> \ git://git.fedorahosted.org/revisor \ <new-folder>
cd <new-folder>
git checkout --track -b <new-branch> origin/<branch>
Well, I'll give you an example:
[user@machine ~]$ mkdir -p devel/revisor [user@machine ~]$ cd devel/revisor
$ git clone git://git.fedorahosted.org/revisor master # This will clone the master branch into sub-directory master
$ git clone --reference master git://git.fedorahosted.org/revisor F-8 # This will create a F-8 sub-directory based on the master/ sub- # directory
$ cd F-8
$ git checkout --track -b F-8 origin/F-8 # This will checkout branch F-8, and switch to that branch
Hope this helps,
Kind regards,
Jeroen van Meeuwen -kanarip
Jeroen van Meeuwen kanarip@kanarip.com writes:
Lars Bjørndal wrote:
The command 'git branch' gives me only * master. So how do I grab the F-8 branch of Revisor?
Go to the revisor source tree you have now, and go up one directory
Type:
git clone --reference <current-source> \ git://git.fedorahosted.org/revisor \ <new-folder>
cd <new-folder>
git checkout --track -b <new-branch> origin/<branch>
Well, I'll give you an example:
[user@machine ~]$ mkdir -p devel/revisor [user@machine ~]$ cd devel/revisor
$ git clone git://git.fedorahosted.org/revisor master # This will clone the master branch into sub-directory master
$ git clone --reference master git://git.fedorahosted.org/revisor F-8 # This will create a F-8 sub-directory based on the master/ sub- # directory
$ cd F-8
$ git checkout --track -b F-8 origin/F-8 # This will checkout branch F-8, and switch to that branch
Hope this helps,
Yes, it did!
But when I now try to build a livecd, I get lots of questions if I want to continue even if packages like ppc64-utils, elilo, s390utils and many more does not exist. What should I do to eliminate this problem? I'm building on and for Fedora F8 i386 system.
Lars
Lars Bjørndal wrote:
Yes, it did!
But when I now try to build a livecd, I get lots of questions if I want to continue even if packages like ppc64-utils, elilo, s390utils and many more does not exist. What should I do to eliminate this problem? I'm building on and for Fedora F8 i386 system.
These are packages listed in the group file, comps.xml, most likely under @core or @base, and which are arch-specific (e.g. not available for the architecture you are composing).
Start Revisor with --yes from the command-line, or specify %packages --ignoremissing in the manifest.
Revisor would still complain about the missing packages, but it'll limit itself to the terminal. It needs to complain some, as these missing packages might result in something different then one would expect. Maybe not in this case, but if you include third party packages that are missing, you would want to know and abort before the compose finishes.
I'll add this to the documentation however.
Kind regards,
Jeroen van Meeuwen -kanarip
livecd@lists.fedoraproject.org