Re: Netscape crashing [Fwd: Re: Re: Browser for Multia]

2003-09-11 Thread Bob McElrath
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 
 Sites that crash Netscape 4.78 on my Alphas.
 
 www.zend.com (uses PHP)
 www.oceanatlas.org (uses JSP)
 www.ebay.com (uses static HTML)
 www.c-span.org
 
 Going to these and others results in an instant Netscape crash for me.
 The source is supposed to available at mozilla.org but I only see Mozilla
 itself there, not Commuicator.  My build of Mozilla 2.6 took up 2 Gig
 of disk space (wow).  It doesn't crash going to those sites, but it is
 incredibly slow, 50 sec. just to come up on the XP1000.  Is the Netscape
 really open.

Netscape is an antiquated, buggy, spec-nonconforming, unreliable piece
of shit.  The source of the Netscape browser evolved into the Mozilla
project.  Don't use Netscape 4.x unless you absolutely have to.

These days web designers use features (such as CSS) that Netscape simply
does not implement properly.  Fixing these bugs is such a large
undertaking that the Netscape team abandoned the original 4.x source and
started from scratch, a project now known as Mozilla.

There are many open browsers available in the debian/alpha binary archive,
such as mozilla, konqueror, galeon, epiphany-browser, and
mozilla-firebird.  They're already compiled in the archive, you
shouldn't need to compile it yourself.

Cheers,
Bob McElrath [Univ. of California at Davis, Department of Physics]

Knowledge will forever govern ignorance, and a people who mean to
be their own governors, must arm themselves with the power knowledge
gives. A popular government without popular information or the means
of acquiring it, is but a prologue to a farce or a tragedy or
perhaps both.
- James Madison


pgpPejXh3fVwn.pgp
Description: PGP signature


boot loader

2003-09-11 Thread Leonardo Saavedra Henriquez

Hi all

I have been traying to install Debian GNU/Linux on my Alpha server 800 and
I have a little problem with aboot loader
When I made the partitions (bsd disklabel style) I left an small empty
partition at the beginning of the disk drive (from cylinder 1 to cylinder
2) for aboot, later the instaler program cannot install the aboot boot
loader, I think the proble it could be the type of partition label.
What kind of partition label it need to be? (unsused, 4.2BSD, boot,
...)

TIA.

--
Leonardo Saavedra Henriquez
mailto:[EMAIL PROTECTED]
[leo- ~ $] cd pub  more beer




Re: boot loader

2003-09-11 Thread Rich Payne

The disk needs to be have a BSD disklabel, but you don't want a partition
at the front. Just leave some free space. You're probably OK just deleting
your existing small partition.

--rdp

On Thu, 11 Sep 2003, Leonardo Saavedra Henriquez wrote:


 Hi all

 I have been traying to install Debian GNU/Linux on my Alpha server 800 and
 I have a little problem with aboot loader
 When I made the partitions (bsd disklabel style) I left an small empty
 partition at the beginning of the disk drive (from cylinder 1 to cylinder
 2) for aboot, later the instaler program cannot install the aboot boot
 loader, I think the proble it could be the type of partition label.
 What kind of partition label it need to be? (unsused, 4.2BSD, boot,
 ...)

 TIA.

 --
 Leonardo Saavedra Henriquez
 mailto:[EMAIL PROTECTED]
 [leo- ~ $] cd pub  more beer


 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Rich Payne
http://talisman.mv.com
rdp at talisman dot mv dot com




Re: boot loader

2003-09-11 Thread Leonardo Saavedra Henriquez


Thanks Rich and Michael!. But I have yet another small problem.

 I left a small empty space in front of the disk drive,
 Now the debian installer made my system booteable without any complain.
 when the system has been rebooted  it start, jumps to bootstrap code and
 write in the console the meesage:

aboot: Linux/Alpha SRM bootloader version 0.9
aboot: switching to OSF/1 PALcode version 1.21
aboot: valid disklabel found: 6 partitions
aboot: could not find default config `a'
Welcome to aboot 0.9
Commands:
 ...
aboot

and stop!.

Aparently the reason to stop is that it internally gives the command:

 boot dka0 -flags a

When I give the command:

aboot boot dka0 -flags 0

the system start Debian/GNU Linux normally.

How can I change permanently the flags option from the SRM console?

TIA


   What's wrong?
  
   TIA
  
   On 11 Sep 2003, Michael A. Mackey wrote:
  
  That way of partitioning the disk won't work.  Delete your small
  partition and everything should be okay (you'll need to re-run
  swriteboot).
 
  The correct way to partition the disk is to start partition 1 at sector
  3, leaving unpartitioned space up front for the aboot loader.
 
 
  On Thu, 2003-09-11 at 12:31, Leonardo Saavedra Henriquez wrote:
   Hi all
  
   I have been traying to install Debian GNU/Linux on my Alpha server 
800 and
   I have a little problem with aboot loader
   When I made the partitions (bsd disklabel style) I left an small empty
   partition at the beginning of the disk drive (from cylinder 1 to 
cylinder
   2) for aboot, later the instaler program cannot install the aboot boot
   loader, I think the proble it could be the type of partition label.
   What kind of partition label it need to be? (unsused, 4.2BSD, boot,
   ...)
  
   TIA.
  
   --
   Leonardo Saavedra Henriquez
   mailto:[EMAIL PROTECTED]
   [leo- ~ $] cd pub  more beer
  --
  Prof. Michael A. Mackey ([EMAIL PROTECTED])
  Biomedical Engineering / Pathology
  University of Iowa, Iowa City, Iowa
  Voice: 319-335-6058 Fax: 319-335-5631
 
 
  
   --
   Leonardo Saavedra Henriquez
   mailto:[EMAIL PROTECTED]
   [leo- ~ $] cd pub  more beer
  
  

--
Leonardo Saavedra Henriquez
mailto:[EMAIL PROTECTED]
[leo- ~ $] cd pub  more beer





Re: Netscape crashing [Fwd: Re: Re: Browser for Multia]

2003-09-11 Thread Ionut Georgescu


On Thu, 2003-09-11 at 18:54, Bob McElrath wrote:
 [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 
 Netscape is an antiquated, buggy, spec-nonconforming, unreliable piece
 of shit.  The source of the Netscape browser evolved into the Mozilla
 project.  Don't use Netscape 4.x unless you absolutely have to.
 
 These days web designers use features (such as CSS) that Netscape simply
 does not implement properly.  Fixing these bugs is such a large
 undertaking that the Netscape team abandoned the original 4.x source and
 started from scratch, a project now known as Mozilla.
 
 There are many open browsers available in the debian/alpha binary archive,
 such as mozilla, konqueror, galeon, epiphany-browser, and
 mozilla-firebird.  They're already compiled in the archive, you
 shouldn't need to compile it yourself.
 

And none of them work in a decent manner. It seems that JavaScript
doesn't work either with konqueror 3.x, nor with mozilla 1.0.x, nor with
mozilla 1.4.x, nor with self compiled mozillas. I still don't know what
should I do on the alpha in order to book a flight ticket at
www.aua.com. Except for calling them. Which is what I finally did. :)

Cheers.
Ionut




Re: boot loader

2003-09-11 Thread Nathan Poznick
Thus spake Leonardo Saavedra Henriquez:
 How can I change permanently the flags option from the SRM console?

I believe you're looking for:
set boot_osflags 0

-- 
Nathan Poznick [EMAIL PROTECTED]

Patriotism is the last refuge of a scoundrel. - Samuel Johnson



pgphZbiGF1fsN.pgp
Description: PGP signature


Re: boot loader

2003-09-11 Thread Rich Payne


From SRM you should be able to do:

set boot_osflags 0

--rdp

On Thu, 11 Sep 2003, Leonardo Saavedra Henriquez wrote:



 Thanks Rich and Michael!. But I have yet another small problem.

  I left a small empty space in front of the disk drive,
  Now the debian installer made my system booteable without any complain.
  when the system has been rebooted  it start, jumps to bootstrap code and
  write in the console the meesage:

   aboot: Linux/Alpha SRM bootloader version 0.9
   aboot: switching to OSF/1 PALcode version 1.21
   aboot: valid disklabel found: 6 partitions
   aboot: could not find default config `a'
   Welcome to aboot 0.9
   Commands:
...
   aboot

 and stop!.

 Aparently the reason to stop is that it internally gives the command:

boot dka0 -flags a

 When I give the command:

   aboot boot dka0 -flags 0

 the system start Debian/GNU Linux normally.

 How can I change permanently the flags option from the SRM console?

 TIA


What's wrong?
   
TIA
   
On 11 Sep 2003, Michael A. Mackey wrote:
   
   That way of partitioning the disk won't work.  Delete your small
   partition and everything should be okay (you'll need to re-run
   swriteboot).
  
   The correct way to partition the disk is to start partition 1 at 
 sector
   3, leaving unpartitioned space up front for the aboot loader.
  
  
   On Thu, 2003-09-11 at 12:31, Leonardo Saavedra Henriquez wrote:
Hi all
   
I have been traying to install Debian GNU/Linux on my Alpha server 
 800 and
I have a little problem with aboot loader
When I made the partitions (bsd disklabel style) I left an small 
 empty
partition at the beginning of the disk drive (from cylinder 1 to 
 cylinder
2) for aboot, later the instaler program cannot install the aboot 
 boot
loader, I think the proble it could be the type of partition label.
What kind of partition label it need to be? (unsused, 4.2BSD, boot,
...)
   
TIA.
   
--
Leonardo Saavedra Henriquez
mailto:[EMAIL PROTECTED]
[leo- ~ $] cd pub  more beer
   --
   Prof. Michael A. Mackey ([EMAIL PROTECTED])
   Biomedical Engineering / Pathology
   University of Iowa, Iowa City, Iowa
   Voice: 319-335-6058 Fax: 319-335-5631
  
  
   
--
Leonardo Saavedra Henriquez
mailto:[EMAIL PROTECTED]
[leo- ~ $] cd pub  more beer
   
   

 --
 Leonardo Saavedra Henriquez
 mailto:[EMAIL PROTECTED]
 [leo- ~ $] cd pub  more beer



 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Rich Payne
http://talisman.mv.com
rdp at talisman dot mv dot com




Re: boot loader

2003-09-11 Thread james fowler
Or you can change the settings in /etc/aboot.conf to reflect what you want
passed to aboot. This way you can still auto boot. Otherwise, hit ctl-c
lots of times to get back to SRM (while booting). Set the boot_os (I
think) flag to 0 or none (I don't recall the value). And it will pause in
SRM for you to give it what you want.

James

James Fowler
[EMAIL PROTECTED]
[EMAIL PROTECTED]
ICQ: 59959089
AIM: spledos
MSN: [EMAIL PROTECTED]

Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away.  - Antoine de Saint Exupery

On Thu, 11 Sep 2003, Leonardo Saavedra Henriquez wrote:



 Thanks Rich and Michael!. But I have yet another small problem.

  I left a small empty space in front of the disk drive,
  Now the debian installer made my system booteable without any complain.
  when the system has been rebooted  it start, jumps to bootstrap code and
  write in the console the meesage:

   aboot: Linux/Alpha SRM bootloader version 0.9
   aboot: switching to OSF/1 PALcode version 1.21
   aboot: valid disklabel found: 6 partitions
   aboot: could not find default config `a'
   Welcome to aboot 0.9
   Commands:
...
   aboot

 and stop!.

 Aparently the reason to stop is that it internally gives the command:

boot dka0 -flags a

 When I give the command:

   aboot boot dka0 -flags 0

 the system start Debian/GNU Linux normally.

 How can I change permanently the flags option from the SRM console?

 TIA


What's wrong?
   
TIA
   
On 11 Sep 2003, Michael A. Mackey wrote:
   
   That way of partitioning the disk won't work.  Delete your small
   partition and everything should be okay (you'll need to re-run
   swriteboot).
  
   The correct way to partition the disk is to start partition 1 at 
 sector
   3, leaving unpartitioned space up front for the aboot loader.
  
  
   On Thu, 2003-09-11 at 12:31, Leonardo Saavedra Henriquez wrote:
Hi all
   
I have been traying to install Debian GNU/Linux on my Alpha server 
 800 and
I have a little problem with aboot loader
When I made the partitions (bsd disklabel style) I left an small 
 empty
partition at the beginning of the disk drive (from cylinder 1 to 
 cylinder
2) for aboot, later the instaler program cannot install the aboot 
 boot
loader, I think the proble it could be the type of partition label.
What kind of partition label it need to be? (unsused, 4.2BSD, boot,
...)
   
TIA.
   
--
Leonardo Saavedra Henriquez
mailto:[EMAIL PROTECTED]
[leo- ~ $] cd pub  more beer
   --
   Prof. Michael A. Mackey ([EMAIL PROTECTED])
   Biomedical Engineering / Pathology
   University of Iowa, Iowa City, Iowa
   Voice: 319-335-6058 Fax: 319-335-5631
  
  
   
--
Leonardo Saavedra Henriquez
mailto:[EMAIL PROTECTED]
[leo- ~ $] cd pub  more beer
   
   

 --
 Leonardo Saavedra Henriquez
 mailto:[EMAIL PROTECTED]
 [leo- ~ $] cd pub  more beer



 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]





Kernel upgrade from 2.2.20 to 2.4.18

2003-09-11 Thread Hunt, Chandi
Title: Kernel upgrade from 2.2.20 to 2.4.18





Hi:


I recently installed Woody 30r1 on an AlphaServer 800 without a hitch. I wanted some of the RAID and LVM options, and so went to upgrade my kernel to a 2.4.18 version.

I am new to linux, so I am sure I am just missing something!


Currently, it is running well using the 2.2.20-generic kernel (no customizations).


I used the apt-get install kernel-image-2.4.18-generic and installed the kernel (without configuring a ram disk image - BTW - why would I need a ram disk?).

When I reboot, it panics when it tries to mount the root fs VFS: Cannot open root device sda1 or 08:01 - it seems this is a fairly common occurrence (I browsed through usenet) - but the reasons vary from kernel config options to aboot configs.

I looked at aboot.conf, and the sda1 (my first partition) is configured as my boot partition (filesystem is ext2). I browsed through the config-2.4.18-generic file and it lists support for my SCSI disks and for ext2 ... I can choose vmlinuz.old from the aboot menu and boot up just fine (VFS: Mounted root (ext2 filesystem)) - what am I missing here?

Thank You,
Chandi





Re: Kernel upgrade from 2.2.20 to 2.4.18

2003-09-11 Thread Sander van Malssen
On Thursday, 11 September 2003 at 13:42:34 -0700, Hunt, Chandi wrote:

Currently,  it  is  running  well  using the 2.2.20-generic kernel (no
customizations).
 
I  used  the apt-get install kernel-image-2.4.18-generic and installed
the  kernel  (without configuring a ram disk image - BTW - why would I
need a ram disk?).

You would, because:


When  I  reboot,  it  panics  when it tries to mount the root fs VFS:
Cannot  open  root device sda1 or 08:01 - it seems this is a fairly
common  occurrence  (I  browsed through usenet) - but the reasons vary
from kernel config options to aboot configs.

All the disk and filesystem drivers are built as modules and are
contained on the initrd ramdisk. Try reinstalling the kernel deb (or
maybe just run a dpkg-reconfigure kernel-image-2.4.18-generic?  Can't
check from home, but may suffice) and have it build the initrd image.
And make sure the aboot.conf line has initrd=/initrd.img added to it.
That should do the job!


Cheers,
Sander

-- 
 Sander van Malssen -- [EMAIL PROTECTED] -- http://www.kozmix.org/
  http://www.peteandtommysdayout.com/ -- http://www.1-2-5.net/