Your message dated Sat, 31 Aug 2013 00:24:06 +0200
with message-id <201308310024.32985.hol...@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #685426,
regarding Package: installation-reports serial install
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
685426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
On 08/20/2012 11:23 AM, Aaron wrote:
Hello,
Will you be enabling installation with only a serial console attached
to the machine?
I am talking about no keyboard and monitor, just a serial terminal.
This is basic unix functionality that is easily enabled.
Thank you.
acs
http://lists.debian.org/debian-user/2011/06/msg02544.html
---
Following http://wiki.debian.org/DebianInstaller/Modify/CD
mkdir unpack
bsdtar -C unpack -xf debian-6.0.1a-amd64-netinst.iso [if doing it with
mount -o loop, don't miss .disk dir]
vi unpack/isolinux/isolinux.cfg [timeout 5]
vi unpack/isolinux/txt.cfg [add console=ttyS0,9600n8 to append line]
chmod +w unpack/isolinux/isolinux.bin
genisoimage -o debian-6.0.1a-amd64-netinst-plettserial.iso -r -J
-no-emul-boot -boot-load-size 4 -boot-info-table -b
isolinux/isolinux.bin -c isolinux/boot.cat ./unpack
---
I was using an amd64-netinst CD, but it should work with any CD that
uses isolinux (i386 or amd64).
--- End Message ---
--- Begin Message ---
Hi,
thank you for submitting installation reports, much appreciated.
I read through all the bugs mentioned here (and I'm sure they were read by
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to
close wishlist bugs.)
If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll
do if requested) or just file a new one - thats often better, as the bug log
will be clearer and shorter and not contain cruft.
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
