AW: bootcd questions
Hi,
I have successfully booted at last.
I have removed the read-only in the fstab and build the kernel with
make-kpkg and wrote another bootcd :
(bootcd 2.32)
linux2:/etc/bootcd# bootcdwrite
To see full output: tail -f /var/log/bootcdwrite.log
--- Cleanup ---
/var/spool/bootcd/cdimage.iso will be created !
/var will be cleaned (apt-get clean) !
Ok to continue? (y/n) y
--- Checking for possible Problems ---
--- Sizes in KByte (du -klsc ) ---
NOT_TO_CD = . . . . . . . . . . . . . . . . . . . . . . . . . . . 10866184
CD_ALL (SRCDISK v NOT_TO_CD) = . . . . . . . . . . . . . . . . . . 11502728
Needed = CD_ALL - NOT_TO_CD . . . . . . . . . . . . . . . . . . . 636544
CD (650 MB) = . . . . . . . . . . . . . . . . . . . . . . . . . . 665600
OK - SRCDISK does fit on CD (Needed <= CD)
VAR = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8116416
OK - enough space in /var/spool/bootcd (Needed <= VAR)
NOT_TO_RAMCD (NOT_TO_RAM v NOT_TO_CD) = . . . . . . . . . . . . . 10866160
RAM_ALL (etc v home v root v NOT_TO_RAM v NOT_TO_CD) = . . . . . . 10872292
Needed RAM (RAM_ALL - NOT_TO_RAMCD) = . . . . . . . . . . . . . . 6132
90 % of RAM = . . . . . . . . . . . . . . . . . . . . . . . . . . 360000
OK - enough RAM (Needed RAM <= 90 % of RAM)
--- Building Modifications ---
--- Creating /ram[1|2].cpio.gz for FASTBOOT ---
--- Creating CD-Image ---
Size of boot image is 4 sectors -> No emulation
298624 extents written (583 Mb)
--- Testing CD-Image ---
--- Cleanup ---
linux2:/etc/bootcd#
Why did it not function before?
Where does it look for a kernel config file if I want to make an iso over
nfs?
Murat
-----Ursprüngliche Nachricht-----
Von: 'Thomas Krennwallner' [mailto:djmaecki@ull.at]
Gesendet: Donnerstag, 17. Juli 2003 11:45
An: Debian-User
Betreff: Re: bootcd questions
Hi!
On Thu Jul 17, 2003 at 11:37:45AM +0200, Yildiz, Murat wrote:
> I wrote a new cd and booted with it...the first error is :
>
> cpio : /var/........ read-only filesystem
> loading modules.... /var/log/ksymoops...... read-only filesystem
> .
> .
> .
> .
> .
>
>
>
> I think the /var was mounted read-only...
>
> I have NOT_TO_RAM=""
> Why is the var being mounted read-only???
Hm, it still doesn't work? But the {DriveReady SeekComplete Error}
errors are away now?
It could be that your self compiled kernel doesn't have some features
compiled in which bootcd needs to work. Since it couldn't test your
configuration you have to check it for yourself. Have a look at
/usr/share/doc/bootcd/FAQ.gz.
Maybe there's a bug in bootcd. Try to contact the maintainer of this
package first. You can find his email address here[1]. Then you should
file a bugreport[2] against bootcd.
So long
Thomas
1. http://packages.qa.debian.org/b/bootcd.html
2. http://www.debian.org/Bugs/Reporting
--
.''`. Obviously we do not want to leave zombies around. - W. R. Stevens
: :' : Thomas Krennwallner <djmaecki at ull dot at>
`. `'` 1024D/67A1DA7B 9484 D99D 2E1E 4E02 5446 DAD9 FF58 4E59 67A1 DA7B
`- http://bigfish.ull.at/~djmaecki/
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Reply to: