[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: some ideas for 2.2.10 (documenting, messages)



On Sat, Mar 25, 2000 at 02:08:08PM -0500, Adam Di Carlo wrote:
> 
> I'd like comments on some of my ideas of things to do for 2.2.10:
> 
>   * cp /var/log/messages from root.bin into /target/var/log/messages
>     prior to reboot.  This lets the user look back at their installer
>     log and will help our debugging.
> 
>     Perhaps the file should be copied to /target/var/log/install.log ?

The latter seems like a better file. We can simply say "please submit your
/va/log/install.log with the bug report" and not worry about extracting it
from the top of the messages file.

>   * more informational log messages from dbootstrap, such as,
>     "formatting /dev/hda1 as ext2 (kernel 2.2 mode)"

Sounds good.

>   * when we're using kernels, extract the /boot/config* file and have
>     that available from the documentation so the users can seem what
>     options are compiled and and which are not; This is useful on i386
>     esp. when users are selecting flavors to use

Could be installed into the flavors directory as (sparc for example):

	sun4cdm/kernel-config-2.2.14

I also think we need to add this to kernel.sh so that the config gets
installed to the new /target/boot just like it would be if the kernel
package was installed. It could be compressed on the rescue disk as
config.gz and would only take about 2k or 3k.

-- 
 -----------=======-=-======-=========-----------=====------------=-=------
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`     bcollins@debian.org  --  bcollins@openldap.org  --  bmc@visi.net     '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'


Reply to: