Re: [rock-user] Error in build_stage2 of building bootdisk configuration ?

Benjamin Schieder <blindcoder-1k+CIuW/[email protected]> Fri, 5 May 2006 07:53:03 +0200
Newsgroups gmane.linux.distributions.rock.user
Message-ID <[email protected]>
--===============0446931544==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="Bn2rw/3z4jIqBvZU"
Content-Disposition: inline


--Bn2rw/3z4jIqBvZU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 05.05.2006 08:45:04, Tuan Anh TRINH wrote:
> ....
> Creating initrd filesystem image (ext2fs):
> -> Creating temporary files.
>=20
> Running Build-Target cleanup procedure
> -> Killing lingering processes and removing parallel build queue.
> -> Umounting lingering mounts in build/bootdisk-TRUNK-x86-bootdisk-expert.
> -> READY.
>=20
> [root@localhost TEST]#
>=20
> And the problem is a strange line (marked with "<<---") in=20
> ./target/bootdisk/build_stage1.sh :
>=20
> ...
>          echo_status "Creating temporary files."
>          tmpdir=3D`mktemp -d` ; mkdir -p ${tmpdir}
>          dd if=3D/dev/zero of=3D${initrd_img} bs=3D${block_size}=20
> count=3D${block_count} &> /dev/null
>          tmpdev=3D"`losetup -f 2>/dev/null`"		<<---
>          if [ -z "${tmpdev}" ] ; then
> ...

There shouldn't be anything strange about that line. From losetup -h:
losetup: invalid option -- h
usage:
  losetup loop_device                                       # give info
  losetup -d loop_device                                    # delete
  losetup -f                                                # find unused
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  losetup [-e encryption] [-o offset] {-f|loop_device} file # setup

So `losetup -f` should output the name of an unused /dev/loop/* device.
Can you please post the output of `losetup -f` here?

> BTW, after use the aboved CD (I use minimun KDE desktop template) to=20
> install on my VMWare Workstation 5.5 and QEMU, it cann't run X because=20
> of driver for frame buffer device is not working. Do you have any=20
> experience in testing with QEMU or VMWare?

At least VMWare _should_ run fine from my experience. Did you configure your
X Server with

	# X -configure

?


Greetings,
	Benjamin

--=20
Today, memory either forgets things when you don't want it to,
or remembers things long after they're better forgotten.

--Bn2rw/3z4jIqBvZU
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFEWug/r0OTeImXvg8RAtRvAJwKk6Z/Dh75NVlWm1qyiKdWDcjl8gCg12v1
IgLu1LyRgd3JfUy7xnmoViw=
=aPAJ
-----END PGP SIGNATURE-----

--Bn2rw/3z4jIqBvZU--

--===============0446931544==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rock-user mailing list
[email protected]
http://www.rocklinux.net/mailman/listinfo/rock-user

--===============0446931544==--