Hi there!
On Thu, 30 Jan 2014 15:39:59 +0100, Didier 'OdyX' Raboud wrote:
Le jeudi, 30 janvier 2014, 02.51:48 Cyril Brulebois a écrit :
II. How to install a backported kernel
==
(…)
Now here's another way which doesn't look so scary:
1) Make sure the
Hi Cyril,
Le jeudi, 30 janvier 2014, 02.51:48 Cyril Brulebois a écrit :
as mentioned earlier this month, I had a little proof of concept for
Paris Mini-DebConf 2014[1]. I've polished a few things, so here we go.
1. https://lists.debian.org/debian-boot/2014/01/msg00239.html
Thanks for the
Hi folks,
as mentioned earlier this month, I had a little proof of concept for
Paris Mini-DebConf 2014[1]. I've polished a few things, so here we go.
1. https://lists.debian.org/debian-boot/2014/01/msg00239.html
[ I've set reply-to: -boot@ for a few questions I'd like answers to /
comments on;
On 22:35 Tue 06 Apr , vikram wrote:
hi,
I am trying to build d-i on Squeeze. I am getting the following error:
Ign cdrom://[Debian GNU/Linux testing _Squeeze_ - Official Snapshot i386 DVD
Binary-1 20100315-04:29] squeeze/main Packages
Err cdrom://[Debian GNU/Linux testing _Squeeze_ -
hi,
I am trying to build d-i on Squeeze. I am getting the following error:
Ign cdrom://[Debian GNU/Linux testing _Squeeze_ - Official Snapshot i386 DVD
Binary-1 20100315-04:29] squeeze/main Packages
Err cdrom://[Debian GNU/Linux testing _Squeeze_ - Official Snapshot i386 DVD
Binary-1
Hi
Fixed it, i downloaded the udeb and placed it in build/localudebs
You can also set a sources.list.udeb.local file. Doing so d-i build process
will pull necessary udebs from a repository.
regards
Lucs Brasilino
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a
Hi,
Fixed it, i downloaded the udeb and placed it in build/localudebs
Thanks,
Vikram
hi,
I did a check out of d-i source from
svn://svn.d-i.alioth.debian.org/svn/d-i/trunk/installer
I followed the instructions in installer/build/README
dpkg-checkbuilddeps - done,
when i build d-i i get the following error:
---
Hi,
- running 'by-hand':
$:~/debian/debian-installer/installer/build$ objcopy --strip-unneeded -R .note
-R .comment /lib//libpthread.so.0 ./tmp/netboot/tree/lib/libpthread.so.0-so-
stripped
BFD: BFD (GNU Binutils for Debian) 2.18.50.20080507 internal error, aborting
at../../bfd/elf.c line
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rage Callao wrote:
On 1/22/07, Eddy Petrișor [EMAIL PROTECTED] wrote:
Probably not using fakeroot or being root while trying to build the
image?
Hi EddyP, thank you for replying.
I did use fakeroot as well as tried it as root but still the
On Thursday 25 January 2007 02:40, Eddy Petrișor wrote:
Rage Callao wrote:
I did use fakeroot as well as tried it as root but still the same
error.
If you ran it as root at some point, try cleaning up by running 'make
reallyclean' _as root_ and then trying again with fakeroot.
Hi Frans and EddyP,
Its fantastic! I wiped out everything and started from scratch and I
can now build the miniiso. I'll start posting what I learn about
customizing d-i in my blog.
Thank you.
--
Rage Callao
Free Software :: empower :: educate
Blog: http://ragecallao.wordpress.com
--
To
Hi,
I'm been trying to build the d-i miniiso by following the instructions here:
http://wiki.debian.org/DebianInstaller/GUIBuild
But unfortunately I keep running into the same error:
Unpacking libslang2 (from udebs/libslang2.udeb) ...
dpkg (subprocess): failed to chroot to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rage Callao wrote:
Hi,
I'm been trying to build the d-i miniiso by following the instructions
here:
http://wiki.debian.org/DebianInstaller/GUIBuild
But unfortunately I keep running into the same error:
Unpacking libslang2 (from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been trying to build d-i and get the associated udebs. I can
successfully build now that I have reinstalled my system (which I
screwed up by doing things wrong before), but the install process fails,
and investigation reveals that (at least) the
On Thu, Jan 20, 2005 at 01:38:20AM -0500, Daniel Dickinson wrote:
I've been trying to build d-i and get the associated udebs. I can
successfully build now that I have reinstalled my system (which I
screwed up by doing things wrong before), but the install process fails,
and investigation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Colin Watson wrote:
| On Thu, Jan 20, 2005 at 01:38:20AM -0500, Daniel Dickinson wrote:
|
|Am I missing a step, or doing something wrong, the process for
|downloading udebs not up-to-date, or something else?
|
|
| If you're using the cdrom initrd,
Steve Langasek wrote:
This works well for aboot-installer, which is alpha-specific and is
probably ready to move into testing at this time
If it's ready you should make an upload to testing-proposed-updates. Or
if the version currently in unstable is the right one we can copy it
from there.
;
Hi,
I would like to help test d-i on Alpha, but it appears that I must first
build the latest version since the builds are out of date. Are there
instructions anywhere on doing this?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
On Thu, Jan 22, 2004 at 07:37:03PM +, John Goerzen wrote:
I would like to help test d-i on Alpha, but it appears that I must first
build the latest version since the builds are out of date. Are there
instructions anywhere on doing this?
Which builds are you looking at?
The images at
On Thu, Jan 22, 2004 at 07:37:03PM +, John Goerzen wrote:
Hi,
I would like to help test d-i on Alpha, but it appears that I must first
build the latest version since the builds are out of date. Are there
instructions anywhere on doing this?
The boost is getting d-i from Alioth CVS.
In
Steve Langasek wrote:
The images at http://gluck.debian.org/cdimage/testing/sid_d-i/netinst/alpha/
are built daily at should be quite usable. (The ones not in the sid
directory are built daily but are NOT usable, because there's a nice
catch-22 with only packages for beta2 will be pushed into
On Thu, Jan 22, 2004 at 06:40:08PM -0500, Joey Hess wrote:
Steve Langasek wrote:
The images at http://gluck.debian.org/cdimage/testing/sid_d-i/netinst/alpha/
are built daily at should be quite usable. (The ones not in the sid
directory are built daily but are NOT usable, because there's a
In article [EMAIL PROTECTED] you write:
I just tried to build d-i on sparc.
You'll need to patch mklibs. My patch is in bug 227291.
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It
In article [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
Btw: I can now build d-i on sparc, but how can I make a cdimage for
testing? After building d-i I got a cdrom-image.img and a cdrom-initrd.gz
Apparently you use debian-cd, which requires a local package mirror.
From my looking
Le Thu, Jan 15, 2004 at 08:42:39PM -0800, Blars Blarson écrivait:
Apparently you use debian-cd, which requires a local package mirror.
From my looking into it, debian-cd will need some minor tweeks to
build bootable sparc CDs. When I get it running, I'll submit
appropriate bugs.
Please
On Wed, 2004-01-14 at 08:59, Joerg Friedrich wrote:
I generally do a sparc32 /bin/bash do make sure everything is detected
right.
when using sparc32 /bin/bash before a make TYPE=cdrom image make
fails like this:
8 (snip)
mkdir -p ./tmp/cdrom/tree/lib/modules/2.4.21-sparc32/kernel; if [
for
testing? After building d-i I got a cdrom-image.img and a cdrom-initrd.gz
--
Jörg Friedrich
Die Songs haben irgendwie C64-Romantik.
-- Klaus Knopper
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Wed, 2004-01-14 at 07:45, Joerg Friedrich wrote:
this solved the problem. it seems that mklibs doesn't work right with
32-bit and 64-bit libraries. does anyone have an idea?
Btw: I can now build d-i on sparc, but how can I make a cdimage for
testing? After building d-i I got a cdrom
On Wed, Jan 14, 2004 at 01:45:16PM +0100, Joerg Friedrich wrote:
Btw: I can now build d-i on sparc, but how can I make a cdimage for
testing? After building d-i I got a cdrom-image.img and a cdrom-initrd.gz
Three possibilities:
- If you are confident that the kernel and initrd have been
can I make a cdimage for
testing? After building d-i I got a cdrom-image.img and a cdrom-initrd.gz
You shouldn't need to do this - Sparc is generally expected to be in 32
bit mode when you're compiling. Other packages in Debian don't do
anything to check for this.
I generally do
Hi,
I just tried to build d-i on sparc.
System was a new installed woody upgraded to unstable.
recent cvs checkout, all build-debs satisfied.
btw. its a sun e450
using make TYPE=cdrom
and this is the problem:
# Library reduction.
mkdir -p ./tmp/cdrom/tree/lib
mklibs -v -d
Blars Blarson wrote:
The sparc netcfg udebs need to get into the debian archives. (The
sparc autobuilder is either not running or still trying to catch up.
I'd rate python a higher priority.) Should I sign and upload the
package I built?
Yes, certianly.
--
see shy jo
signature.asc
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
a. Work to get the debian-installer package cleanly building for
all relevant image types.
cdrom and netboot are now cleanly building. At some future point
floppy may be added for sparc32, but that's not something I'm
concerned about.
Blars Blarson wrote:
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
a. Work to get the debian-installer package cleanly building for
all relevant image types.
cdrom and netboot are now cleanly building. At some future point
floppy may be added for sparc32, but that's not
Your message dated Tue, 30 Dec 2003 21:47:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#206531: Problems building d-i after upgrading Sid chroot
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt
After not doing anything on it for six weeks, I'm again trying to get
debian-installer working on sparc.
First iritation was needing to rebuild python2.3, as it's a dependancy
of a build-dendancy. (Apparently the sparc autobuilder is still
down.) That took 14 hours to compile. I also had to
Blars Blarson wrote:
After not doing anything on it for six weeks, I'm again trying to get
debian-installer working on sparc.
First iritation was needing to rebuild python2.3, as it's a dependancy
of a build-dendancy. (Apparently the sparc autobuilder is still
down.) That took 14 hours to
Dpkg will not be happy unpacking over a userspace served NFS filesystem.
May I suggest to drop the following note into build/README ?
diff -u -r1.22 README
--- build/README14 Oct 2003 02:06:29 - 1.22
+++ build/README4 Nov 2003 18:12:43 -
@@ -9,6 +9,8 @@
Or, create
severity 206531 critical
thanks
This problem make it impossible to build and test the new installer
(debian-installer). I raise the priority to critical, because it
makes unrelated software on the system (or the whole system) break.
We need to find a solution to this problem to continue
Processing commands for [EMAIL PROTECTED]:
severity 206531 critical
Bug#206531: Problems building d-i after upgrading Sid chroot
Severity set to `critical'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator
It appears that the problem here is caused by dso_handle.os being
omitted from the reduced libc. This leaves __dso_handle as an undefined
weak reference. Unfortunately, for a shared build, glibc assumes that
this symbol will always be available and elides the check for its
existence in
[Petter Reinholdtsen]
After upgrading my Sid chroot, the cdrom floppy built by d-i is unable
to boot properly.
I've reported this problem as #206531, Problems building d-i after
upgrading Sid chroot against libc6-pic, after discussing it on
#debian-boot.
Please add more info to it if you know
After upgrading my Sid chroot, the cdrom floppy built by d-i is unable
to boot properly.
These are the last messages printed when booting the floppy:
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 1441k freed
VFS: Mounted root (ext2 filesystem).
Mounted devsf on /dev
On Thu, Jul 03, 2003 at 12:07:30PM +0800, [EMAIL PROTECTED] wrote:
On Wed, 2 Jul 2003, Chris Tillman wrote:
On Thu, Jul 03, 2003 at 07:54:37AM +0800, [EMAIL PROTECTED] wrote:
On Wed, 2 Jul 2003, Chris Tillman wrote:
Recipe:
- install the build-dependancies on the host system
On Thu, 3 Jul 2003, Chris Tillman wrote:
I copied by deb line, changed stable to unstable and ran this command:
for p in install libdiscover1-pic libdiscover1 genext2fs mklibs libdebconfclient0
libdebian-installer3; do apt-get -qqyu install $p; done
You can list as many packages as you
On 1 Jul 2003, Gaudenz Steinlin wrote:
Am Die, 2003-07-01 um 14.40 schrieb [EMAIL PROTECTED]:
I would need to build _everything_, unless there are binaries some place
for oldworld powermacs. The build document is a little terse, and I
don't see a list of udebs at all.
No you don't have
Am Mit, 2003-07-02 um 02.03 schrieb [EMAIL PROTECTED]:
Recipe:
- install the build-dependancies on the host system
I don't know what they are, don't know how to find out so we'll see what
breaks
see build/debian/control
- run {sudo,fakeroot} make build
On Wed, Jul 02, 2003 at 08:03:57AM +0800, [EMAIL PROTECTED] wrote:
On 1 Jul 2003, Gaudenz Steinlin wrote:
Am Die, 2003-07-01 um 14.40 schrieb [EMAIL PROTECTED]:
I would need to build _everything_, unless there are binaries some place
for oldworld powermacs. The build document is a
On 2 Jul 2003, Gaudenz Steinlin wrote:
Am Mit, 2003-07-02 um 02.03 schrieb [EMAIL PROTECTED]:
Recipe:
- install the build-dependancies on the host system
I don't know what they are, don't know how to find out so we'll see what
breaks
see build/debian/control
- run
Am Mit, 2003-07-02 um 23.41 schrieb [EMAIL PROTECTED]:
On 2 Jul 2003, Gaudenz Steinlin wrote:
Am Mit, 2003-07-02 um 02.03 schrieb [EMAIL PROTECTED]:
I'll send this off while I ponder the next breakage:
Need to download : rootskel cdebconf-udeb main-menu udpkg anna
di-utils-shell
On 3 Jul 2003, Gaudenz Steinlin wrote:
Am Mit, 2003-07-02 um 23.41 schrieb [EMAIL PROTECTED]:
On 2 Jul 2003, Gaudenz Steinlin wrote:
Am Mit, 2003-07-02 um 02.03 schrieb [EMAIL PROTECTED]:
I'll send this off while I ponder the next breakage:
Need to download : rootskel cdebconf-udeb
On Wed, 2 Jul 2003, Chris Tillman wrote:
Recipe:
- install the build-dependancies on the host system
I don't know what they are, don't know how to find out so we'll see what
breaks
The build dependencies are listed in build/debian/control.in. One easy way
to have it check for
On Thu, Jul 03, 2003 at 07:54:37AM +0800, [EMAIL PROTECTED] wrote:
On Wed, 2 Jul 2003, Chris Tillman wrote:
Recipe:
- install the build-dependancies on the host system
I don't know what they are, don't know how to find out so we'll see what
breaks
The build dependencies
On Wed, 2 Jul 2003, Chris Tillman wrote:
On Thu, Jul 03, 2003 at 07:54:37AM +0800, [EMAIL PROTECTED] wrote:
On Wed, 2 Jul 2003, Chris Tillman wrote:
Recipe:
- install the build-dependancies on the host system
I don't know what they are, don't know how to find out so we'll see
On Thu, 3 Jul 2003 [EMAIL PROTECTED] wrote:
look like my greatest success:
Current default timezone: 'Australia/Perth'.
Local time is now: Thu Jul 3 12:46:42 WST 2003.
Universal Time is now: Thu Jul 3 04:46:42 UTC 2003.
Run 'tzconfig' if you wish to change it.
Setting up
On Sun, 2003-04-06 at 08:12, Petter Reinholdtsen wrote:
[Alastair McKinstry]
It's not clear to me if you intend for the package to include the whole
debian-installer source tree, or just the build directory.
Just the build directory.
I believe I've seen some buildd maintainers complain
Alastair McKinstry wrote:
On Sun, 2003-04-06 at 08:12, Petter Reinholdtsen wrote:
And I am fairly sure the buildd is compiling as a normal user and not
root. This will at the moment make it impossible to build the boot
floppies. I suspect this package will fail to build on all platforms
until
[Alastair McKinstry]
It's not clear to me if you intend for the package to include the whole
debian-installer source tree, or just the build directory.
Just the build directory.
I believe I've seen some buildd maintainers complain about packages
requiring network access when building from
Hi,
In order to get d-i built on various archs, etc. I propose to create a
package debian-installer.
(If this is documented somewhere else, a pointer would be gratefully
accepted, and uploaded to /doc)
The plan would be that debuild in ./debian-installer/build builds
Hi,
On Wed, Apr 02, 2003 at 07:06:02PM +0100, Alastair McKinstry wrote:
Alastair McKinstry [EMAIL PROTECTED]
GPG Key fingerprint = 9E64 E714 8E08 81F9 F3DC 1020 FA8E 3790 9051 38F4
Anybody else running gpg 1.0.6 or 1.2.x got 'BAD Signature' on this
message?
Cheers,
Emile.
--
E-Advies -
On Wed, Apr 02, 2003 at 09:37:07PM +0200, Emile van Bergen wrote:
Hi,
On Wed, Apr 02, 2003 at 07:06:02PM +0100, Alastair McKinstry wrote:
Alastair McKinstry [EMAIL PROTECTED]
GPG Key fingerprint = 9E64 E714 8E08 81F9 F3DC 1020 FA8E 3790 9051 38F4
Anybody else running gpg 1.0.6 or
Ok, I resent the message with signed a different mailer, to verify.
But I will be sending messages unsigned for the next while, until the
bug gets fixed in evolution / gpg.
Mail me if you need a message to be signed / encrypted.
- Alastair
On Wed, 2003-04-02 at 20:37, Emile van Bergen wrote:
Alastair McKinstry wrote:
In order to get d-i built on various archs, etc. I propose to create a
package debian-installer.
The plan would be that debuild in ./debian-installer/build builds
debian-installer-$(ARCH)_$(VERSION)_all.deb, that puts the images and
associated documentation into a
On Thu, 2003-04-03 at 00:35, Joey Hess wrote:
Alastair McKinstry wrote:
In order to get d-i built on various archs, etc. I propose to create a
package debian-installer.
The plan would be that debuild in ./debian-installer/build builds
debian-installer-$(ARCH)_$(VERSION)_all.deb, that
On Tue, Mar 18, 2003 at 06:50:37AM +0800, [EMAIL PROTECTED] wrote:
On 17 Mar 2003, Tollef Fog Heen wrote:
obviously not, since you should ordinarily not build
libdebian-installer yourself, you should just install it into your
host system. libdebian-installer is a normal debian
On Tue, 18 Mar 2003, Stephane Enten wrote:
On Tue, Mar 18, 2003 at 06:50:37AM +0800, [EMAIL PROTECTED] wrote:
On 17 Mar 2003, Tollef Fog Heen wrote:
obviously not, since you should ordinarily not build
libdebian-installer yourself, you should just install it into your
host
On Tue, Mar 18, 2003 at 09:23:00PM +0800, [EMAIL PROTECTED] wrote:
On Tue, 18 Mar 2003, Stephane Enten wrote:
I've been able to build the floppy 'net' image without any trouble only
by installing the needed packages on the host system (and removing the
bogl stuff from the floppy
[EMAIL PROTECTED] writes:
On Tue, 18 Mar 2003, Stephane Enten wrote:
On Tue, Mar 18, 2003 at 06:50:37AM +0800, [EMAIL PROTECTED] wrote:
I've been able to build the floppy 'net' image without any trouble only
by installing the needed packages on the host system (and removing the
bogl stuff
On Tue, Mar 18, 2003 at 02:55:41PM +0100, Stephane Enten wrote:
On Tue, Mar 18, 2003 at 09:23:00PM +0800, [EMAIL PROTECTED] wrote:
I have not yet found any way to make any packages from this source, and
that is why I think something is missing.
You can to to the libdebian-installer and
On Tue, 18 Mar 2003, Mario Lang wrote:
What I want to do is to build all these packages, and then go on to
create bootable disks from the results.
You do not need to do this. The whole idea of udeb packages
is that they can reside in the archives, and you do not need to build
them all
*
| I am confused. install libdebian-installer3?
yes, install it.
| I thought I was trying to build it. Are you saying we have recursive
| dependencies?
No. I'm saying to build a boot-floppy you need libdebian-installer3
somewhere. Unlike boot-floppies, d-i usually shouldn't be built full
On 17 Mar 2003, Tollef Fog Heen wrote:
*
| I am confused. install libdebian-installer3?
yes, install it.
| I thought I was trying to build it. Are you saying we have recursive
| dependencies?
No. I'm saying to build a boot-floppy you need libdebian-installer3
somewhere. Unlike
* [EMAIL PROTECTED] wrote:
I want to build the version of d-i I just checked out of CVS and
test it. I don't see that what you suggest advances that.
At buildtime d-i pulls in librarycode from the buildsystem. It uses
the evil mklibs tool, which only copies the symbols really needed by
the
*
| I want to build the version of d-i I just checked out of CVS and test
| it. I don't see that what you suggest advances that.
build libdebian-installer, install libdebian-installer, build the rest
of d-i.
--
Tollef Fog Heen,''`.
UNIX
On 17 Mar 2003, Tollef Fog Heen wrote:
*
| I want to build the version of d-i I just checked out of CVS and test
| it. I don't see that what you suggest advances that.
build libdebian-installer, install libdebian-installer, build the rest
of d-i.
My sequence of commands is now this:
*
| The 'make install' for libdebian-installer has put the libraries in
| place, but of course the next phase is trying to install stuff that
| wants the libdebian-installer package in place.
libdebian-installer is a debian package, which you build by using
dpkg-buildpackage and then install
On 17 Mar 2003, Tollef Fog Heen wrote:
obviously not, since you should ordinarily not build
libdebian-installer yourself, you should just install it into your
host system. libdebian-installer is a normal debian package, which is
built like all normal debian packages.
Please, please read
On Sun, 16 Mar 2003 [EMAIL PROTECTED] wrote:
On 15 Mar 2003, Tollef Fog Heen wrote:
*
| I don't see any build instructions there though.
build/README perhaps?
In the interests of encouraging people to improve the documentation
Recipe:
- install the build-dependancies
*
| For starters, it's woody. If there's no list, would someone mail a woody
| package list to $(echo [EMAIL PROTECTED] | sed -e s=debian=summer=)
| for a system that does build d-i and I will tell you what I needed to
| add to my system.
Sorry, but the following packages have unmet
On 17 Mar 2003, Tollef Fog Heen wrote:
*
| For starters, it's woody. If there's no list, would someone mail a woody
| package list to $(echo [EMAIL PROTECTED] | sed -e s=debian=summer=)
| for a system that does build d-i and I will tell you what I needed to
| add to my system.
[Hrishi Hrishi]
The make also gave me an error (reproduced below)
---
Error from make:
Need to download : di-utils-shell rootskel anna
main-menu busybox-udeb dash-udeb kernel-image---udeb
The kernel package seem to lack a version number. Any idea why?
I checked out of the debian-installer and used the
instructions on
http://wiki.debian.net/DebianInstallerBuild to create
a boot floppy.
When I tried to execute
dpkg-buildpackage in some of the tools/ directories I
get the error message dpkg-buildpackage: unable to
determine source package
The
I did a checkout of the debian-installer and used the instructions on
http://lists.debian.org/debian-boot/2002/debian-boot-200207/msg00441.html
and http://wiki.debian.net/DebianInstallerBuild to create a boot floppy.
Everything did go quite well until i attemted to do
make boot_floppy in /build.
Joakim Kolsjö wrote:
/build# make boot_floppy
if mount | grep -q `pwd`/mnt/ ! umount `pwd`/mnt/ ; then \
echo Error unmounting `pwd`/mnt/ 21 ; \
exit 1; \
fi
mkdir -p `pwd`/mnt/
rm -f ./tmp/net/image.tmp
install -d ./tmp/net
install -d dest
genext2fs -d ./tmp/net/tree
Something has mounted tmp/net/tree/proc and it should not be mounted at
this point. Perhaps you ran make demo at some point earlier and for some
reason it did not call make demo_clean afterwards?
Ah... thanks. Now it builds.
--
Joakim Kolsjö
A member of The Swedish Linux Society,
86 matches
Mail list logo
