Just dopey me forgetting to run chmod.

$ ls -l vs4000-90A_firmware.zip 
-rw-------  1 bpeanut  wheel  466394 Jan 16 09:45 vs4000-90A_firmware.zip
$ chmod a+r vs4000-90A_firmware.zip 

--- Michael Kukat <michael@bsdfans.org> wrote:
> Hi !
> 
> i don't know if this is just a local (german) problem, or if someone thinks
> he
> got too many hits on this file, but access is denied on this URL.
> 
> Anyone got this file to put on any server, or maybe accidentally mail it to
> me?
> :)
> 
> It sounds like 4000/90A, is this the same as 4000/90 according the firmware?
> Usually the A-models just have a bit faster CPUs...
> 
> Bye... Michael
> 
> On Thu, 16 Jan 2003, Baby Peanut wrote:
> 
> > $ unzip -l vs4000-90A_firmware.zip
> > Archive:  vs4000-90A_firmware.zip
> >   Length     Date   Time    Name
> >  --------    ----   ----    ----
> >     35328  12-12-01 12:22   VS4000.doc
> >    461097  12-12-01 12:28   cougar_v1_3.zip
> >  --------                   -------
> >    496425                   2 files
> >
> > The VS4000.doc seems AbiWord compatible.  It says:
> >
> > Updating Firmware by Ethernet
> >
> > To update firmware across the Ethernet, the "client" system (the target
> system
> > to be updated) and the "server" system (the system that serves boot
> requests)
> > must be on the same Ethernet segment. The maintenance operation protocol
> (MOP)
> > is the transport used to copy the network image.
> >
> > Enable the server system's NCP circuit.
> > $ MCR NCP
> > NCP>SET CIRCUIT <circuit> STATE OFF
> > NCP>SET CIRCUIT <circuit> SERVICE ENABLED
> > NCP>SET CIRCUIT <circuit> STATE ON
> > <circuit> is the system Ethernet circuit. Use the SHOW
> > KNOWN CIRCUITS command to find the name of the circuit
> >
> > Copy the file containing the updated code to the MOM$LOAD area on the
> server.
> > Use the following command:
> > $ COPY <filename>.SYS MOM$LOAD:*.*
> > This procedure may require system privileges. <filename> is the Ethernet
> > bootable filename provided in the release notes
> >
> > On the client system, enter the command
> > BOOT/100 EZ at the console prompt (>>>). The system then prompts you for
> the
> > file name.
> > Note: Do not type the .SYS file extension when entering
> > the Ethernet bootfile name. The MOP load protocol only supports
> 15-character
> > filenames
> >
> > After the FEPROM upgrade program is loaded, press Y at the prompt to start
> the
> > FEPROM blast
> > CAUTION! Once you enter the bootfile name, do not interrupt the FEPROM
> blasting
> > program, as this can damage the CPU module. The program takes several
> minutes
> > to complete
> > Note: On systems with a VCB02 terminal, an abbreviated form of the
> following
> > example appears
> >
> > -------------------------
> >
> > I don't speak that much VMS but it's clear that you just mop the file and
> run
> > it.  I slapped cougar.sys into /tftpboot/mop/COUGAR.SYS and mop'ed it and
> now
> > my box is fixed.
> >
> > http://hermes.tubas.net/vs4000-90A_firmware.zip
> >
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> > http://mailplus.yahoo.com
> >
> >
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com