Re: SPECS (AC-branch): filesystem.spec - release 5: %ghost for /initrd...

2007-03-17 Thread Radoslaw Zielinski
Elan Ruusamäe [EMAIL PROTECTED] [13-03-2007 21:25]:
 On Tuesday 13 March 2007, Radoslaw Zielinski wrote:
 Because it's impossible to upgrade if old root (from boot time) is
 mounted on /initrd.  cpio fails on unpacking the *.rpm.

 It has been broken for quite a while... :-/
 so fix what's broken.
 I have fixed what was broken.  At least one part of it.
 no, that's not fixing. it's workarounding problem from wrong direction. 
 initrd needs fixing, not filesystem.spec having workarounds.

If a package can't be upgraded (even in wrong environment), it can be
considered a problem with this package.  And IMO this is the case.

 anyway not being able to umount /initrd (due unmounted /initrd/dev) is
 fixed in geninitrd 8142.
   $ rpm -q geninitrd
   geninitrd-8286-1
 installing geninitrd package doesn't fix your problem.

Indeed, it doesn't fix filesystem.spec.

 you need to regenerate initrd using fixed geninitrd.

No kidding...?

 if you've all done that, then please show your initrd contents (while /initrd 
 still mounted to be sure to compare initrd used for boot): 
 # cat /initrd/linuxrc

#! /bin/sh

set -x
insmod /lib/modules/2.6.20-0.12/kernel/drivers/ide/ide-core.ko 
insmod /lib/modules/2.6.20-0.12/kernel/drivers/ide/pci/piix.ko 
insmod /lib/modules/2.6.20-0.12/kernel/drivers/ide/ide-disk.ko 
insmod /lib/modules/2.6.20-0.12/kernel/fs/xfs/xfs.ko 
: 'Creating /dev'
mount -o mode=0755 -t tmpfs none /dev
mknod /dev/console c 5 1
mknod /dev/null c 1 3
mknod /dev/zero c 1 5
mkdir /dev/pts
mkdir /dev/shm
mount -t proc none /proc
mount -t sysfs none /sys
: 'Starting udev'
/sbin/udevd --daemon
kill udevd
umount /proc
umount /sys
set +x
mount -t proc none /proc
root=$(busybox awk ' /root=\/dev\// { gsub(/.*root=\/dev\//,NIL,$0); gsub(/ 
.*/,NIL,$0); print $0; } ' /proc/cmdline)
if [ -n $root ]; then
rootnr=$(busybox awk -v root=$root ' { if ($4 == root) { print 
256*$1+$2; } } ' /proc/partitions)
if [ -n $rootnr ]; then
echo $rootnr  /proc/sys/kernel/real-root-dev
fi
fi
umount /proc
set -x

-- 
Radosław Zieliński [EMAIL PROTECTED]


pgpvNSUN5H7CL.pgp
Description: PGP signature
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: SPECS (AC-branch): filesystem.spec - release 5: %ghost for /initrd...

2007-03-13 Thread Radoslaw Zielinski
Uh, this reply certainly took me a while.

Elan Ruusamäe [EMAIL PROTECTED] [12-02-2007 10:19]:
 On Monday 12 February 2007, radek wrote:
 why?
 Because it's impossible to upgrade if old root (from boot time) is
 mounted on /initrd.  cpio fails on unpacking the *.rpm.

 It has been broken for quite a while... :-/
 so fix what's broken.

I have fixed what was broken.  At least one part of it.

 it should not be mounted for normal system run.

But it *is* mounted on three of four of my PLD systems.  Which are
working perfectly fine, apart from not being able to upgrade filesystem:

  $ LANG=C poldek -iv filesystem  
  [...]
  I filesystem-2.0-6
  Need to get 10.0KB of archives. 
  Executing sudo /bin/rpm --install -vh --root / --noorder...
  Preparing...### [100%]
 1:filesystem ### [100%]
  error: unpacking of archive failed on file /initrd: cpio: chown failed - 
Read-only file system

So, you have reverted it to the broken state.  Is this a ping-pong club or
what?

 anyway not being able to umount /initrd (due unmounted /initrd/dev) is fixed 
 in geninitrd 8142.

  $ rpm -q geninitrd
  geninitrd-8286-1

 doesn't it break fresh installs as i don't think /initrd is mkdir at boot
 No.  %ghost %dir creates it.
 no, it does not (go and test it)

Hmm, true.  I must have messed something up while testing this.  Any
better ideas than %ghost and mkdir in %post?

-- 
Radosław Zieliński [EMAIL PROTECTED]


pgptnQkNwdloS.pgp
Description: PGP signature
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: SPECS (AC-branch): filesystem.spec - release 5: %ghost for /initrd...

2007-02-11 Thread Elan Ruusamäe
why?

doesn't it break fresh installs as i don't think /initrd is mkdir at boot

On Saturday 10 February 2007, radek wrote:
 Author: radekDate: Sat Feb 10 20:04:31 2007 GMT
 Module: SPECS Tag: AC-branch
  Log message:
 - release 5: %ghost for /initrd; STBR

  Files affected:
 SPECS:
filesystem.spec (1.71.2.7 - 1.71.2.8)


-- 
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en