Tech

Personally I tried this procedure on Neoware e140 wich run Neolinux 2.x but i think it’s the some with other models or os version: Power on the thin client Press ‘SHIFT’ during boot procedure Now you can get LILO prompt, type: vga simple (I have tried without success to run directly init=/bin/bash the system start but don’t load correctly the filesystem on flashdrive) After kernel starting up procedure you can’t see nothing, then you can jump on terminal 2 pressing ‘ALT + F2’ ...

If your phone (example iPhone) doesn’t have complete call forwarding menu, you can use line code, then, to activate and deactivate Call Forwarding, follow this instructions: Call Forward Immediate - Send all calls to another number instantly. enable: *21 (prefix + number) # call disable: ## 21 # call verify: * # 21 # call Call Forward No Reply - Send calls that go unanswered. enable: *61 (prefix + number) # call disable: ## 61 # call verify: * # 61 # call ...

Setting up serial connection to VAXstation 4000/60: First made a serial cable, attention Vax use a DEC423 serial port designed for long distant terminal line: --------------- 1 - DTR (Data terminal ready) I I 2 - TxD (Transmit data) I 1 2 3 4 5 6 I 3 - GND (Signal ground) I I 4 - RxC (Receive common) I I 5 - RxD (Receive data) ---------I____I 6 - DSR (Data set ready) Pin 2 of the phone connector goes to Rx pin of the serial (3 of DB25 or 2 of DB9), pins 3 & 4 go to ground (7 of DB25 or 5 of DB9), and pin 5 goes to Tx pin (2 of DB25 or 3 of DB9). ...

3 days ago I find a nice VAX Station 4000/60 on ebay for only 41 Euro (about 60 Dollars), obviously I bought it, and today delivery boy knock my door! I paste the command/console output of the recovery procedure: > KA46-A V1.4-38E-V4.2 > 08-00-2B-92-4E-C7 > 24MB > ?? 001 9 NI 0172 > >>> sh config > KA46-A V1.4-38E-V4.2 > 08-00-2B-92-4E-C7 > 24MB > DEVNBR DEVNAM INFO > ------ -------- -------------------------- > 1 NVR OK > 2 LCG OK > HR - 8 PLN FB - V1.2 > 3 DZ OK > 4 CACHE OK > 5 MEM OK > 24MB = SY=8MB, S0/1=8MB, S2/3=8MB, S4/5=0MB > 6 FPU OK > 7 IT OK > 8 SYS OK > 9 NI ?? 001 0172 > 10 SCSI OK > 3-L0-RZ26B 6-INITR > 11 AUD OK > >>> ? > BOOT [/[R5:]<bflg>] [<ddau>[:]] > CONTINUE > DEPOSIT [{ /B | /W | /L | /Q | /A }] [{ /P | /V | /I }] [/G] [/U] [/N:<n>] > [{ <addr> | <sym> | + | - | * | @ } [<datum>]] > EXAMINE [{ /B | /W | /L | /Q | /A }] [{ /P | /V | /I }] [/G] [/U] [/N:<n>] > [{ <addr> | <sym> | + | - | * | @ }] > FIND [{ /MEMORY | /RPB }] > HALT > HELP > INITIALIZE > LOGIN > REPEAT <cmd> > SET BOOT <ddau> > SET BFLG <bflg> > SET DIAGENV <1-3> > SET FBOOT <0-1> > SET HALT <1-3> > SET KBD <0-15> > SET MOP <0-1> > SET PSE <0-1> > SET PSWD > SET SCSI <0-7> > SET TRIG <0-1> > SHOW { BOOT | BFLG | CONFIG | DEV | DIAGENV | FBOOT | ETHER | ERROR | > ESTAT | HALT | KBD | MEM | MOP | PSE | SCSI | TRIG } > START <addr> > TEST [/UTIL] <devnam | devnbr> > UNJAM > X <addr> <cnt> ... > ? > >>> B/1 > -DKA300 > SYSBOOT> SET/STARTUP OPA0: > SYSBOOT> SET WINDOWS_SYSTEM 0 > %SYSBOOT-E-NOPARAM, no such parameter WINDOWS_SYSTEM > SYSBOOT> SET WRITESYSPARAMS 0 > SYSBOOT> CONTINUE > VAX/VMS Version V5.5-2H4 Major version id = 1 Minor version id = 0 > PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 27-NOV-2009 3:51 > $ > $ SPAWN > SPAWN > %DCL-S-SPAWNED, process SYSTEM_1 spawned > %DCL-S-ATTACHED, terminal now attached to process SYSTEM_1 > $ @SYS$SYSTEM:STARTUP > $! Copyright (c) 1993 Digital Equipment Corporation. All rights reserved. > %STDRV-I-STARTUP, VMS startup begun at 27-NOV-2009 04:00:59.19 > The VAX/VMS system is now executing the system startup procedure. > %SET-I-NEWAUDSRV, identification of new audit server process is 00000088 > The VAX/VMS system is now executing the site-specific startup commands. > %RUN-S-PROC_ID, identification of created process is 0000008C > %NCP-W-FILOPE, File open error , Permanent database > %NML-E-OPENOUT, error opening SYS$SYSROOT:[SYSEXE]NETLOGING.DAT; as output > -RMS-F-PLV, unsupported prolog version > %NCP-W-OPEFAI, Operation failure > %SYSTEM-F-TIMEOUT, device timeout > , timeout > , unit is active > , fatal hardware error > %NCP-W-UNRCMP, Unrecognized component , Circuit > Circuit = SVA-0 > %NCP-I-NOINFO, No information in database > %RUN-S-PROC_ID, identification of created process is 0000008D > Job NCPSTART (queue SYS$BATCH, entry 1) started on SYS$BATCH > %RUN-S-PROC_ID, identification of created process is 0000008F > %SET-I-INTSET, login interactive limit = 20, current interactive value = 1 > 27-NOV-2009 04:03:07 > Process SYSTEM_1 logged out at 27-NOV-2009 04:03:08.62 > Accounting information: > Buffered I/O count: 3431 Peak working set size: 888 > Direct I/O count: 1440 Peak page file size: 3806 > Page faults: 16606 Mounted volumes: 0 > Charged CPU time: 0 00:00:22.71 Elapsed time: 0 00:02:18.06 > %DCL-S-RETURNED, control returned to process STARTUP > $ SET DEFAULT SYS$SYSTEM > SET DEFAULT SYS$SYSTEM > $ RUN SYS$SYSTEM:AUTHORIZE > RUN SYS$SYSTEM:AUTHORIZE > UAF> MODIFY SYSTEM /PASSWORD=system > %UAF-I-MDFYMSG, user record(s) updated > UAF> EXIT > %UAF-I-DONEMSG, system authorization file modified > %UAF-I-RDBNOMODS, no modifications made to rights data base > $ LOGOUT > LOGOUT > SYSTEM job terminated at 27-NOV-2009 04:04:26.81 > Accounting information: > Buffered I/O count: 99 Peak working set size: 1056 > Direct I/O count: 46 Peak page file size: 3978 > Page faults: 471 Mounted volumes: 0 > Charged CPU time: 0 00:00:00.41 Elapsed time: 0 00:05:33.58 > Welcome to VAX/VMS V5.5-2H4 > Username:

Yesterday after 1 year and 2 month uptime, my poor Sun Ultra 10 (Solaris OS10) running into home server room, was crashed.. I’m so sick, here the paste of console recovery procedure: Type 'go' to resume ok ? 1000000 Stack Underflow ok sync panic[cpu0]/thread=2a100057ca0: sync initiated sched: software trap 0x7f pid=0, pc=0xf0050c7c, sp=0x2a100056e81, tstate=0x8800001401, context=0x0 g1-g7: 104da44, 0, 183f000, 0, 1082400, 5, 2a100057ca0 00000000fffa9d10 unix:sync_handler+138 (fffe5718, 1000000, 1, 1083400, 1, 181500 0) %l0-3: 00000000018621b0 0000000001862000 000000000000017f 0000000001845800 %l4-7: 0000000000000000 000000000183f000 0000000000000009 0000000001810400 00000000fffa9de0 unix:vx_handler+80 (fffe5718, 181dfe8, f0000000, fffe0000, 181e 0f0, f003bda1) %l0-3: 000000000181e0f0 0000000000000000 0000000000000001 0000000000000001 %l4-7: 0000000001810c00 00000000f0000000 0000000001000000 0000000001018998 00000000fffa9e90 unix:callback_handler+20 (fffe5718, 1, 0, 0, 0, 0) %l0-3: 0000000000000016 00000000fffa9741 00000000f004a64c 00000000fffe0000 %l4-7: 0000000000000016 0000000000000000 0000000000000000 000000000180c000 syncing file systems... 3 done dumping to /dev/dsk/c0t0d0s7, offset 107413504, content: kernel 100% done: 15712 pages dumped, compression ratio 2.54, dump succeeded rebooting... Resetting ... Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 440MHz), No Keyboard OpenBoot 3.25, 512 MB (50 ns) memory installed, Serial #15184795. Ethernet address 8:0:20:e7:b3:9b, Host ID: 80e7b39b. Rebooting with command: boot Boot device: /pci@1f,0/pci@1,1/ide@3/disk@0,0:a File and args: SunOS Release 5.10 Version Generic_137111-06 64-bit Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hostname: ultra10 Loading smf(5) service descriptions: 1/1 WARNING: svccfg import /var/svc/manifest/application/database/mysql.xml failed svccfg import warnings. See /var/svc/log/system-manifest-import:default.log . /dev/rdsk/c0t0d0s1 is clean ultra10 console login: root Password: Sep 29 23:02:52 ultra10 login: ROOT LOGIN /dev/console Last login: Tue Sep 29 22:21:42 from 192.168.2.15 Sun Microsystems Inc. SunOS 5.10 Generic January 2005 root@ultra10 ~ #

Durante una migrazione di datacenter mi è capitato di aver fuori uso la console di un server perchè la risoluzione della scheda video è fuori range del monitor, avendo accesso RDP la soluzione è presto trovata dal registro di sistema nella seguente posizione: My Computer\HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\VIDEO Trovando la stringa “Monitor” si potrebbe cambiare direttamente la risoluzione, ma personalmente ho cancellato tutto il contenuto e riavviato così facendo ha ricreato le configurazione di default.

OpenSSH require different keys depending if you use SSH1 or SSH2 protocol. All keys are generated by “ssh-keygen” commad, that one should be available on your system with the ssh package. Default key lengths are also appropriate (2048 bits for rsa and 1024 bits for dsa) For SSH1 protocol, you need a rsa1 key generated has follow: # ssh-keygen -q -f /etc/ssh/ssh_host_key -N '' -t rsa1 For SSH2 protocol, you need two keys, one rsa key and one dsa key generated has follow: ...

If you have tried to setup SSH access on a new ASA, it might not have worked the way you wanted. That is because the RSA keys need to be generated first. To do that: from configure terminal: fw01/act(config)# crypto key generate rsaINFO: The name for the keys will be: Keypair generation process begin. Please wait… And then configure SSH to be allowed from the inside interface: fw01/act(config)# ssh (inser your ip) (insert your netmask) outside ...

A little fix for arrow keys in Vim, that display A B C D on remote terminal if in the system you don’t wanna declare “TERM” just insert into yout ~/.vimrc the terminal type like this: set term=xterm

Memo: Solaris package. CSW packaging home.