Hi all,
I just installed the new disks on 4 SS and everything looks good. I installed
on SS2, SS5/110
SS10/40 single CPU and SS20/50 single CPU.
After installation I started installing single pkgs using dpkg to buil a
customized system.
I just have two questions:
1) After installing the disks
On Sun, 9 Jan 2000, Eric Delaunay wrote:
> On this topic, do you know about a way of identifying the type of console
> connected to the serial line ? Is there an escape sequence that returns vt100
> or the like ?
Unfortunately, there is no universal mechanism for detecting what kind of
terminal
On Sun, 9 Jan 2000, Michael Stone wrote:
> On Sun, Jan 09, 2000 at 04:29:40PM +0100, Eric Delaunay wrote:
> > Pass TERM=vt100 or TERM=vt102 at boot time. Current init process does not
> > enforce TERM settings anymore ;(( I don't know wether I will enable it
> > again
> > or just let the user
On Sun, 9 Jan 2000, Eric Delaunay wrote:
> [EMAIL PROTECTED] wrote:
> > Machine is a Sparc IPX with generic 4x16MB 36-bit SIMMS and OEM hard
> > drive on serial console.
> >
> >
> > Booted by TFTP
> >
> > Console is `minicom' running on Slink i386. Noticed that dbootstrap is
> > not drawing w
On Sun, Jan 09, 2000 at 04:29:40PM +0100, Eric Delaunay wrote:
> Pass TERM=vt100 or TERM=vt102 at boot time. Current init process does not
> enforce TERM settings anymore ;(( I don't know wether I will enable it again
> or just let the user pass TERM=xxx at boot time. Maybe a serial target for
>
Eric Delaunay wrote:
>
> Well, my first try is not successful at all :((
>
> Hardware: SparcClassic (sun4m), 24MB RAM, 207MB harddisk.
>
> 1. booting from network (tftpboot.img)
> --
> Report: image downloaded, then messages are displayed very slowly (could be
[EMAIL PROTECTED] wrote:
> Machine is a Sparc IPX with generic 4x16MB 36-bit SIMMS and OEM hard
> drive on serial console.
>
>
> Booted by TFTP
>
> Console is `minicom' running on Slink i386. Noticed that dbootstrap is
> not drawing with the IBM `box' characters like 2.1 dbootstrap did.
Pass TE
Hi.
I tried the disks from
http://xia01.kachinatech.com/~buildd/sparc-2.2.14-potato-boot/
on my SPARC 1+ (SUN 4c and SUN 4cdm rescue disks seem to produce
identical results.)
First, a warning is displayed when the rescue disk is automatically ejected:
"WARNING floppy change called early"
Second,
> On Sun, 9 Jan 2000, Maarten Vink wrote:
>
> > After successfully installing debian on my PC, I thought I'd give my old
> > Sparcstation a try. Since I don't have a monitor or floppy drive for it,
I
> > tried to boot it over my home network.
> > After getting the tftpboot.img file and installing t
On Sun, 9 Jan 2000, Maarten Vink wrote:
> After successfully installing debian on my PC, I thought I'd give my old
> Sparcstation a try. Since I don't have a monitor or floppy drive for it, I
> tried to boot it over my home network.
> After getting the tftpboot.img file and installing tftp on my P
Hello everybody,
After successfully installing debian on my PC, I thought I'd give my old
Sparcstation a try. Since I don't have a monitor or floppy drive for it, I
tried to boot it over my home network.
After getting the tftpboot.img file and installing tftp on my PC, I got the
following error me
I've been having bad troubles with the FDD on my Sparc IPX. Well, I booted
the 2.2.14 a.out kernel from the new testing run of install disks, and
after a fresh install with the old 2.2.1-based Slink disks I can access
the FDD. I slipped a floppy in and could cat it without any trouble.
Then I inst
Ben Collins wrote:
> > 3. booting from network+nfsroot (linux-a.out from sun4cdm/ and root.tar.gz)
> > ---
> >
> > Report: can boot the kernel but was unable to mount the nfsroot fs because
> > this
> > kernel is not config
13 matches
Mail list logo
