r our situation, how to build an installer image that
can PXEBOOT and then build a system on bare iron (server, no CD/DVD slot).
Thanks!
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. Yogi Berra
--
To UNSUBSCRIBE, email to debian
couple of well-defined include and exclude statements, and end up with a
systemd-free system.
So.. what can I do to help (given that I'm a sys admin, not a c coder).
Miles Fidelman
On Fri, 17 Oct 2014 13:09:19 +0900 Kenshi Muto wrote:
> At Fri, 17 Oct 2014 05:57:30 +0200,
> Cyril Brul
Kenshi Muto wrote:
At 16 Oct 14 19:36:54 GMT,
Miles Fidelman wrote:
(snip)
base-installer/includes
and/or
base-installer/excludes
So, in theory, it looks like there IS a way to preseed things during the
early install process - but
- bug #668001 in debootstrap (open since 2012) seems to
Since I asked the question, I figure I should follow up with what I
found out
Cyril Brulebois wrote:
Miles Fidelman (2014-10-16):
1. Where in the installer code does the init system get installed
into the target build?
As far as I can tell, from somewhat out-of-date documentation
(http
Cyril Brulebois wrote:
Miles Fidelman (2014-10-16):
1. Where in the installer code does the init system get installed
into the target build?
As far as I can tell, from somewhat out-of-date documentation
(http://d-i.alioth.debian.org/doc/internals/ - last updated 2010):
- the installer runs
an anybody offer any guidance as to what specific changes to make to
force installation of an alternate init system?
Thank you very much,
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. Yogi Berra
--
To UNSUBSCRIBE, email to debian
his warrants
a bug report or documentation input, point me in the right direction to do so?
Thanks!
Miles Fidelman
p.s So far - no input whatever from either the debian-user list or the
help-grub list.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of &q
Phillip,
Thanks! (more below, inline)
Philipp Kern wrote:
On Tue, Oct 02, 2012 at 03:10:48PM -0400, Miles Fidelman wrote:
The thing is, that the serial terminal is rather crippled - some
things seem to get recognized, others not (function keys are
particularly problematic, though that might
is that grub messed up to make the
installation unbootable)
Miles Fidelman wrote:
A little more info:
Miles Fidelman wrote:
Hi Folks,
Not getting a lot of help on debian-user, so thought I might raise
this here.
I've been trying to build a headless server, remotely, using the
ne
A little more info:
Miles Fidelman wrote:
Hi Folks,
Not getting a lot of help on debian-user, so thought I might raise
this here.
I've been trying to build a headless server, remotely, using the
netboot installer (PXEboot) and a serial-over-ip terminal provided by
the motherbo
P request: Any suggestions on how I can boot into
rescue mode via the remote terminal?
Thanks very much,
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. Yogi Berra
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with
Stefano Canepa wrote:
On Mon, Sep 13, 2010 at 11:29:44AM -0400, Miles Fidelman wrote:
Just for the heck of it, I copied the mini.iso to both / and /boot
on my hard disk and tried the installer again.
Now it reports, after a deep search, "no installer iso images found"
... &qu
Package: installation-reports
Severity: normal
Tags: d-i
-- Package-specific info:
Boot method: USB
Image version: squeeze, daily build 9/14/10 16:07 using netinst .iso
Date: 9/14/10 approx. 5pm
Machine: custom tower
Partitions:
r...@linuxbox:/home/milesf# df -Tl
FilesystemType 1K-block
Package: installation-reports
Severity: important
Tags: d-i
system has two mirrored disks, /dev/md0 is boot, /dev/md2 is root
selecting grub-legacy, and specifying either /dev/hda or (hd0) for installation
results in a menu.lst file with the line
groot=(md0) and all of the boot sections starting
Package: installation-reports
Severity: important
Tags: d-i
eth0 is intel board
eth1 is broadcom card
installer 1st asks for firmware (e100/d102e_ucode.bin) - download from
debian.org per install instructions, put on usb stick, insert - seems to load
(takes several minutes)
then, selecting eth1
more details as to
what specifically needs to be put onto the USB stick, and maybe that
belongs in section 4.5., rather than here.
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. Yogi Berra
--
To UNSUBSCRIBE, email to debi
Joey Hess wrote:
Miles Fidelman wrote:
Next, download a Debian netinst CD image, and copy that file to the
memory stick; any filename is ok as long as it ends in .iso.
Actually, the instructions AREN'T that clear. The instructions start
out with:
"The
Christian Perrier wrote:
Quoting Miles Fidelman (mfidel...@meetinghouse.net):
Err, you're not supposed to put the mini.iso on the USB stick, but
either the businesscard or netinst images.
the instructions page implies that you can do a netboot, using the
.iso found i
tion will need to change at release time (from: use the daily
build bits, to a final formulation), what might be the procedure for
submitting two versions of the documentation?
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. Yogi Berr
At someone's suggestion, I tried configuring syslinux.cfg to set
INSTALL_MEDIA_DEV=/dev/sdc1
Well
- the installer still can't find the .iso, but now
- exiting to shell indicates that INSTALL_MEDIA_DEV=/dev/sdc1, but...
- instead of mounting /dev/sdc1 as /hd-media, the installer has mounted
Just for the heck of it, I copied the mini.iso to both / and /boot on my
hard disk and tried the installer again.
Now it reports, after a deep search, "no installer iso images found" ...
"while one or more possible iso images were found, they did not look
like valid installer iso images"
daily build doesn't work - details at end
Christian PERRIER wrote:
tags 596633 moreinfo
thanks
Quoting Miles Fidelman (mfidel...@meetinghouse.net):
Package: installation-reports
Boot method: USB Installer
Image version: download of testing files dated 9/10/10 per USB in
Package: installation-reports
Boot method: USB Installer
Image version: download of testing files dated 9/10/10 per USB install
instructions
Date: 9/12/10 5pm EST
Machine: custom built tower
Processor:
Memory: 1G
Partitions:
Output of lspci -knn (or lspci -nn):
Base System Installation Checkl
Package: debian-installer
Version: squeeze alpha1 USB installer dated 9/10/10
Severity: grave
Justification: renders package unusable
I just build a USB key containing the squeeze installer, based on the
bits currently linked from the debian testing installer page.
After booting, the installer
Package: installation-reports
Boot method: netinstall CD
Image version:
3.1r2, downloaded July 2006 (not sure of the exact date)
downloaded from
http://cdimage.debian.org/debian-cd/3.1_r2/i386/iso-cd/debian-31r2-i386-netinst.iso
Date: 7/20-24/06
Machine: Supermicro P8SCT 1U rack-mount server
25 matches
Mail list logo
