IOError: [Errno 13] Permission denied: '/var/tmp/...'
by Andrew Overholt
Hi,
For the past few days I've been unable to create a live image on my laptop.
Is there something wrong with my machine or with the way I'm invoking
livecd-creator? I'm on F7 i386 with some rawhide stuff.
$ sudo ../creator/livecd-creator --cache /tmp/fedoradevelcache -c livecd-fedora-developer.ks -f Fedora-Developer-20070923
mke2fs 1.40.2 (12-Jul-2007)
Filesystem label=Fedora-Developer
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
524288 inodes, 1048576 blocks
10485 blocks (1.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1073741824
32 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 20 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.40.2 (12-Jul-2007)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
No Repositories Available to Set Up
No Repositories Available to Set Up
Retrieving http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os/re... ...OK
Retrieving http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os/re... ...OK
Traceback (most recent call last):
File "../creator/livecd-creator", line 1480, in <module>
sys.exit(main())
File "../creator/livecd-creator", line 1453, in main
target.install()
File "../creator/livecd-creator", line 876, in install
self.installPackages()
File "../creator/livecd-creator", line 519, in installPackages
self.ayum.selectPackage(pkg)
File "../creator/livecd-creator", line 248, in selectPackage
return self.install(pattern = pkg)
File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 1830, in install
parsePackages(self.pkgSack.returnPackages(),[kwargs['pattern']] , casematch=1)
File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 517, in <lambda>
pkgSack = property(fget=lambda self: self._getSacks(),
File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 377, in _getSacks
self.repos.populateSack(which=repos)
File "/usr/lib/python2.5/site-packages/yum/repos.py", line 239, in populateSack
sack.populate(repo, mdtype, callback, cacheonly)
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 151, in populate
db_fn = repo.retrieveMD(mydbtype)
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 839, in retrieveMD
cache=self.http_caching == 'all')
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 607, in _getFile
http_headers=headers,
File "/usr/lib/python2.5/site-packages/urlgrabber/mirror.py", line 411, in urlgrab
return self._mirror_try(func, url, kw)
File "/usr/lib/python2.5/site-packages/urlgrabber/mirror.py", line 397, in _mirror_try
return func_ref( *(fullurl,), **kwargs )
File "/usr/lib/python2.5/site-packages/urlgrabber/grabber.py", line 927, in urlgrab
return self._retry(opts, retryfunc, url, filename)
File "/usr/lib/python2.5/site-packages/urlgrabber/grabber.py", line 845, in _retry
r = apply(func, (opts,) + args, {})
File "/usr/lib/python2.5/site-packages/urlgrabber/grabber.py", line 915, in retryfunc
fo._do_grab()
File "/usr/lib/python2.5/site-packages/urlgrabber/grabber.py", line 1196, in _do_grab
else: new_fo = open(self.filename, 'wb')
IOError: [Errno 13] Permission denied: '/var/tmp/livecd-creator-G7ZrvX/install_root/var/cache/yum/development/primary.sqlite.bz2'
Thanks,
Andrew
16 years, 7 months
booting from non-DMA IDE CF card
by Thorsten von Eicken
I am trying to boot off a CF card plugged into an IDE adapter and the
card doesn't support DMA. The problem is that with the new libata stuff,
the traditional "ide-nodma" kernel option doesn't do anything. How do I
turn DMA off so it boots properly. As it is, it tries MWDMA2 mode, fails
a few times, switches to MWDMA1 mode, but never goes down to PIO.
Apologies if this a FAQ, but couldn't find a solution anywhere.
Thorsten
16 years, 7 months
[PATCH] make ram overlay sparse file ridiculously large
by Douglas McClendon
This patch increases the default size of the ram overlay from 512M to 1T.
I thought about adding an option in the same way as the prior
num_loopdevs option, but I don't think that controlling the overlay size
in this way is actually useful.
IMO the solution to controlling the ram overlay size, coincides with the
solution to exposing the user to how much ram overlay they have
available. The solution would be as follows-
1) take this patch, making the sparse ram overlay ridiculously large,
i.e. 1T
2) instead of putting the ram overlay sparse file in the root of the
initramfs tmpfs, create a tmpfs dedicated to it. Perhaps
/mnt/.LiveOS/overlayfs (which then gets mount --move(d) to
/sysroot/mnt/.LiveOS/overlayfs)
3) and then to support clean shutdown, modify /etc/rc.d/init.d/functions
and halt such that they don't try to unmount that filesystem at
shutdown. Code that does this was in my persistence/overlay patch
submitted here a while back.
The result of this, is that "df -h /mnt/.LiveOS/overlayfs" will show you
how much space is available there, and thus how much available for the
read-write rootfs ram overlay.
You can then also remount that tmpfs with a different size at runtime,
or based on a kernel argument, to increase/decrease at will (as opposed
to the tmpfs default of half of existing ram)
NOTE: applying this patch will also suggest recompiling mkinitrd/nash
with largefile support, to clear up the stat error on file-too-large
which I believe is caused when the contents of the initramfs are deleted
by nash/run-init/switchroot. (I think that is the fix).
This problem of not being able for users to detect how much ram space
they have available for copy-on-write-rootfs has come up a few times on
this list in the past, so I strongly suggest the above or some other
solution to the problem.
-dmc
16 years, 7 months
Where to turn off filesystem writing spew..
by Jon Steer
I'd like to make the livecd create a little quieter and not have it print
out the block writing like below.
32539/32769 99%[===========================================================
]-
I can't seem to find where this is written? I added a quiet argument to
mkisofs but that apparently wasn't it.
Where can I turn this off?
thanks,
jon
16 years, 7 months
Re: [Fedora-livecd-list] LiveCD Issues
by asmith11＠cox.net
Jeremy,
Thanks for the feedback. Couple of quick follow-up comments below...
---- Jeremy Katz <katzj(a)redhat.com> wrote:
> On Thu, 2007-09-20 at 09:34 -0400, asmith11(a)cox.net wrote:
> > 1) Installing to Live Image vs. Installing to System
> >
> > Is there a good way (or best practice) in my kickstart %post section
> > to determine whether I am installing to a live image vs. installing to
> > a system (or said differently whether the installation is happening
> > via the GUI installer vs. the livecd-creator? We have certain
> > operations we'd like to perform (format some large partitions, etc.)
> > that don't really make sense for the live image but we would like
> > installed on the real target system as part of a "real"
> > installation.
>
> Hrmm -- there's nothing at the moment. But I can definitely see it
> making some sense. And being able to differentiate for pungi as well.
> It would be easy enough to set an environment variable if that would
> help. I guess you could also key off of the existence
> of /root/anaconda-ks.cfg for it being an anaconda install, but that's
> definitely into heuristics territory
This was basically the direction we were thinking we would end up heading. We're biased towards what we are calling the "real" installation because the live image is primarily a pretty installation vehicle for us.
>
> > 2) Redhat Enterprise 5 Problem
> >
> > We've been able to successfully bundle RHEL5 as a live image. Things
> > are generally working pretty well. We have been using LiveCD Tools
> > 008 and 009 up till now. When we tried to upgrade to LiveCD tools 011
> > the images we created would no longer boot (in QEMU or via CD/DVD if
> > burned to a disk). The error we see at boot is the one where it says
> > that "/dev/root" is missing and that we should create the link and
> > then exit the shell. This has normally been working fine. Is this a
> > problem with a missing kernel module? Any ideas on how to fix this?
>
> Yeah, if you look in livecd-creator, you'll see that we now write out
> things like "=ata" as the modules to use. Which won't work for RHEL5 as
> it doesn't have the file to do that mapping. At the same time, I really
> don't want to have to keep around the list of all of the pata/sata
> modules and have to keep updating it as the list changes over time :-/.
> Open to suggestions, though.
I took a look at the livecd-creator script modules section that you mentioned and I understand now why this is no longer working for RHEL5. I think we can just modify that section of livecd-creator to add the specific modules we'll need.
It raises the question though, how should a livecd-creator user customize the set of modules that they need installed (in a case like this one). Obvious options would be:
1) livecd-creator command-line parameters (requires livecd-creator changes)
2) modify livecd-creator to taste on a case-by-case basis (yuck)
3) kickstart syntax (I don't know if this is really a valid option)
Any thoughts?
Thanks,
-Andy
>
> Jeremy
>
> --
> Fedora-livecd-list mailing list
> Fedora-livecd-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-livecd-list
16 years, 7 months
LiveCD Issues
by asmith11＠cox.net
Hello,
I've been using the LiveCD tools for some time with a good deal of success. Kudos to all of the developers that have put together these tools.
I have run into a few problems recently and was hoping for some guidance. If anyone can help with these it is much appreciated.
1) Installing to Live Image vs. Installing to System
Is there a good way (or best practice) in my kickstart %post section to determine whether I am installing to a live image vs. installing to a system (or said differently whether the installation is happening via the GUI installer vs. the livecd-creator? We have certain operations we'd like to perform (format some large partitions, etc.) that don't really make sense for the live image but we would like installed on the real target system as part of a "real" installation.
2) Redhat Enterprise 5 Problem
We've been able to successfully bundle RHEL5 as a live image. Things are generally working pretty well. We have been using LiveCD Tools 008 and 009 up till now. When we tried to upgrade to LiveCD tools 011 the images we created would no longer boot (in QEMU or via CD/DVD if burned to a disk). The error we see at boot is the one where it says that "/dev/root" is missing and that we should create the link and then exit the shell. This has normally been working fine. Is this a problem with a missing kernel module? Any ideas on how to fix this?
Thanks,
-Andy
16 years, 7 months
LiveCD Issues
by asmith11＠cox.net
Hello,
I've been using the LiveCD tools for some time with a good deal of success. Kudos to all of the developers that have put together these tools.
I have run into a few problems recently and was hoping for some guidance. If anyone can help with these it is much appreciated.
1) Installing to Live Image vs. Installing to System
Is there a good way (or best practice) in my kickstart %post section to determine whether I am installing to a live image vs. installing to a system (or said differently whether the installation is happening via the GUI installer vs. the livecd-creator? We have certain operations we'd like to perform (format some large partitions, etc.) that don't really make sense for the live image but we would like installed on the real target system as part of a "real" installation.
2) Redhat Enterprise 5 Problem
We've been able to successfully bundle RHEL5 as a live image. Things are generally working pretty well. We have been using LiveCD Tools 008 and 009 up till now. When we tried to upgrade to LiveCD tools 011 the images we created would no longer boot (in QEMU or via CD/DVD if burned to a disk). The error we see at boot is the one where it says that "/dev/root" is missing and that we should create the link and then exit the shell. This has normally been working fine. Is this a problem with a missing kernel module? Any ideas on how to fix this?
Thanks,
-Andy
16 years, 7 months
[PATCH] mayflower: use dynamically allocated loop devices
by Douglas McClendon
The attached patch causes mayflower to use dynamically allocated loop
devices for the rootfs readonly-base, readwrite-overlay, squashfs, and
osmin loop devices, rather than /dev/loop118,119,120&121.
udev rules were updated, and two new ones added, so that
/dev/live-osmin, /dev/live-squashed, /dev/live-osimg, and
/dev/live-overlay links will be created by udev.
Also, the unnecessary mknod calls referencing those devices were removed.
I tested with a minimal spin under qemu, and everything appeared as it
should. I could mount /dev/mapper/live-osimg-min and it looked fine.
I did another minimal spin with --skip-compression. For some reason I
had to hit ctrl-c at to get past udev starting. I'm pretty sure I've
seen this before and it has nothing to do with this patch. After doing
that, and logging in, I verified that it correctly handled the absence
of a squashfs loop device.
Comments?
-dmc
16 years, 7 months
[PATCH 6/7] anaconda: liveinst.sh: support turboLiveInst/genMinInstDelta
by Douglas McClendon
this patch takes care of the anaconda side of taking advantage of
livecd's created with a livecd-tools that has
turboLiveInst/genMinInstDelta support. But the code does check for the
legacy situation, and handles it gracefully. Thus this patch is safe
even in the absence of the actual beneficial final patch to livecd-tools.
16 years, 7 months
