Thanks for all hints here !
But I have no luck in that Debian setup.
I did following experiment, and I can give a list
of problems. And those problems I have, although
I have many experience in
net booting of i386 (etherboot+GRUB)
net booting ELKS (was developed by me)
net booting of HP-PARISC with rbootd and BOOTP/TFTP
net booting sparc via RARP and TFTP
net booting VAX via BOOTP/TFTP and mopd
and more on that. Also have experience in setting up
root file systems for NFS and locally and with embedded
target systems.
But I have problems with the debian default procedures:
Machine to become debian workstation: IPC Sparc 4/40
(25MHz, 36MB RAM).
If I boot my self-made kernel (2.2.20) I can boot
the debian root image for installation, but there are
problems with network access. No package can be down-
loaded, independent if network is configured or not
(not means: default setup via BOOTP). Even doing a
bootp configuration does not work. BTW: This kernel
is loaded via "boot net root=/dev/nfs ip=bootp".
The original debian tftp image: Error at the end of
loading: alignment error ...
Then I tried it with the `linux-a.out' kernel (I did
a padding to full 512byte boundary with zeros, otherwise
the loader hangs at the end. I load this kernel with
the parameter `ip=bootp' otherwise it doesn't have
thr nfsroot. And this "Bootp" request done by the kernel
is not working. I have no idea why ? I never had this
problem with selfbuilt kernels. On `tcpdump' I see the
request AND the answer, but the Linux kernel ignores
this and repeats requests ...
The eth0 driver was recongnized correctly by the driver.
To sum up, I cannot understand the whole thing. Is this
IPC a problem, I should do the test on my other SUN
machine, the SparcStation 2. But I cannot see, why
your Linux kernel shows such problems.
Is the "woody" the right source ? Is there a difference
between "woody" and "release 3.0" ?
It was my strategy now, to use debian everywhere. Up to
now I used RedHat, and I also did a short work on Suse.
But both destributions become to thick and complex.
Debian has a small base, and I am responsible for myself
to select a set of functionality.
So I hope, I will solve all the startup problems.
With friendly regards
Christoph P.
Christoph Plattner wrote:
>
> Hello Debian Hackers,
>
> here is a further dependent question:
>
> Although I am not new in Linux-stuff, and although
> a participate some GNU projects or even HP and VAX Linux
> projects (device driver development), I am not able
> to fully understand the debian installation (sorry).
>
> To get a fully naked installation (empty machine),
> I need the current rescue floppy, containing SILO
> and kernel. This floppy isinstrumented to ask for
> a root floppy.
>
> The root floppy download from the web is one, which
> is only possible to use for locally installation,
> for example for CD ROM. But which floppy or image
> I have to use for the "standard" network installation
> via ftp ? I cannot find it !
>
> The drivers are only drivers (I think), the base system
> is the tar ball for a root file system (debootstrap
> cannot unpack it on a i386 system, as I want to install
> a SPARC machine).
>
> Which root floppy I have to use ???
>
> I already installed debian from CD on a HP-PA-RISC
> machine, and I updated a Athlon-PC from RedHat to
> debian via debootstrap (which worked quite well).
>
> So I miss the cross-install between different
> target types (see mail before), I missed the offline
> install for a root file system on a NFS server
> for NFS-Root clients, and I miss the default
> procedure for network install (root floppy).
>
> I hope you can give some hints here ...
>
> Christoph P.
>
> --
> -------------------------------------------------------
> private: [EMAIL PROTECTED]
> company: [EMAIL PROTECTED]
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--
-------------------------------------------------------
private: [EMAIL PROTECTED]
company: [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
