1.windows sys and linux
2.windows has opensshd and http proxy app
3.linux has openssh
4.windows willl listen on sshd and forward to localhost port of http proxy
5.linux will configure mozilla to use SOCKS proxy
Thursday, December 1, 2011
Monday, November 14, 2011
ip layer topologies
1.gw in route entry, job is to forward the packet to ip layer in gw, ip forwarding
will ensure it reaches other interfaces
2.gw(router) is a layer3 device , with ip forwarding enabled
3.iptables is the control structure for ip-upper/ip-lower filter
will ensure it reaches other interfaces
2.gw(router) is a layer3 device , with ip forwarding enabled
3.iptables is the control structure for ip-upper/ip-lower filter
Saturday, November 12, 2011
home office
1.Add a domain controller ubuntu+samba+bind+
2.on all machines in network keep only root local account, protect by password
3.on each machine, keep the home folder in separate disk/partition
4.keep a disk for public file sharing
5.keep a disk for nfs rootfs, single machine with chroot environment can drive N machines
6.So all machines have kernel with basic chroot + rootfs, single master server have matured chroot + optional rootfs
7.All machines in the domain uses account in master dc for login,users are created in
dc and supplied to respective machines
8.ring of kernel + nwdriver + nfs client driver machines AND ring of kernel + nfs server rootfs
9.dc uses dns name for each machine on nw
10.looks like local admin account should setup dns prefix and domain name
11.use rsync to backup client periodically
12.radius server for multipurpose can coexist with vpn server, using localhost as link b/w
13.domain controller preferably is on another machine,openradius for auth
2.on all machines in network keep only root local account, protect by password
3.on each machine, keep the home folder in separate disk/partition
4.keep a disk for public file sharing
5.keep a disk for nfs rootfs, single machine with chroot environment can drive N machines
6.So all machines have kernel with basic chroot + rootfs, single master server have matured chroot + optional rootfs
7.All machines in the domain uses account in master dc for login,users are created in
dc and supplied to respective machines
8.ring of kernel + nwdriver + nfs client driver machines AND ring of kernel + nfs server rootfs
9.dc uses dns name for each machine on nw
10.looks like local admin account should setup dns prefix and domain name
11.use rsync to backup client periodically
12.radius server for multipurpose can coexist with vpn server, using localhost as link b/w
13.domain controller preferably is on another machine,openradius for auth
Saturday, November 5, 2011
at home
1.laser - micro
2.portable genset
led lantern
biolite
3.polk car audio spk, amp
4.tent 2
sleeping bags
5.chair 4
Bangalore :
Wildcraft India Private Limited
Manufacturers of tents, camping, etc.
Address: 121, 3rd Block, 8th Main, Jayanagar,
Bangalore - 560 011, India
Phone: +(91)-(80)-6538354/6753876/
6757599/2241636/2222749/6647036
Fax: +(91)-(80)-2234818
Ozone India
www.ozoneindia.com
6.car pad
7.pico projector
8.check swift plugs power, space in dimension,mini refreg
Honda generator
ModelGK300(made in Japan)
2500 Watt
Push button start
Excellent condition, hardly used
9.configurable umbrella
10.tata photon
11.fryer
12.table ,food rack , array, dismantle
13.white screen, adjustable back pluggable
14.projector holder to chairs
15.coaxial and component car speakers .. with or without amp
=======
JBL X333 - 3.8k (3 pre outs)
Pioneer 2390 - 6k (just 1 pre out in it)
Kenwood U449 - 6.5k (2 pre outs)
Hertz DCX 165 comps - 5k (when i googled there are no comps by that name , i guess he wrote that by mistake and actually it is DSK 165)
Audison wiring - 400rs
Mdf ring / Socket - 150+150rs[*]He said if i wouldn't be including amp with this setup still it will do fine (amp is actually out of my budget and subs i will get in future). What do you think about this?
==============
ipad2+wifi+3g
proclip for suzuki swift
A/V cable
2.portable genset
led lantern
biolite
3.polk car audio spk, amp
4.tent 2
sleeping bags
5.chair 4
Bangalore :
Wildcraft India Private Limited
Manufacturers of tents, camping, etc.
Address: 121, 3rd Block, 8th Main, Jayanagar,
Bangalore - 560 011, India
Phone: +(91)-(80)-6538354/6753876/
6757599/2241636/2222749/6647036
Fax: +(91)-(80)-2234818
Ozone India
www.ozoneindia.com
6.car pad
7.pico projector
8.check swift plugs power, space in dimension,mini refreg
Honda generator
ModelGK300(made in Japan)
2500 Watt
Push button start
Excellent condition, hardly used
9.configurable umbrella
10.tata photon
11.fryer
12.table ,food rack , array, dismantle
13.white screen, adjustable back pluggable
14.projector holder to chairs
15.coaxial and component car speakers .. with or without amp
=======
JBL X333 - 3.8k (3 pre outs)
Pioneer 2390 - 6k (just 1 pre out in it)
Kenwood U449 - 6.5k (2 pre outs)
Hertz DCX 165 comps - 5k (when i googled there are no comps by that name , i guess he wrote that by mistake and actually it is DSK 165)
Audison wiring - 400rs
Mdf ring / Socket - 150+150rs[*]He said if i wouldn't be including amp with this setup still it will do fine (amp is actually out of my budget and subs i will get in future). What do you think about this?
==============
ipad2+wifi+3g
proclip for suzuki swift
A/V cable
Sunday, October 23, 2011
iscasi
1.normal --- disk,partition/volume,filesystem
2.iscasi --- disk,partition/volume/lun,filesystem
3.create lun
arg - the disk
arg - size of partition
arg - ip address associated
arg - tcp port associated
arg - filesystem
4.can non iscasi and iscasi exist together
5.can a folder be shared through iscasi and scasi
2.iscasi --- disk,partition/volume/lun,filesystem
3.create lun
arg - the disk
arg - size of partition
arg - ip address associated
arg - tcp port associated
arg - filesystem
4.can non iscasi and iscasi exist together
5.can a folder be shared through iscasi and scasi
account this
1.dsp on board runs using dhcp
2.using nfs
need server side
check during boot suppress permission issues
verified kernel args for nfs
verified dhcp can be used
issue dhcp on client,nfs req on client dhcp on server
issue server needs .tar.bz2 or expanded ones
issue use /tftboot with symbolic links with kernel and rootfs
solved issue sdcard does not see media , ??
solved dns gateway, ??
3.android - tiny android
4.stripping packages
5.pipeline -- sources,binaries,confi files,system.img,data.img,root file system
6.pipeline - - kernel
7.sipdroid
8.dolby
9.diceplayer
2.using nfs
need server side
check during boot suppress permission issues
verified kernel args for nfs
verified dhcp can be used
issue dhcp on client,nfs req on client dhcp on server
issue server needs .tar.bz2 or expanded ones
issue use /tftboot with symbolic links with kernel and rootfs
solved issue sdcard does not see media , ??
solved dns gateway, ??
3.android - tiny android
4.stripping packages
5.pipeline -- sources,binaries,confi files,system.img,data.img,root file system
6.pipeline - - kernel
7.sipdroid
8.dolby
9.diceplayer
Sunday, October 16, 2011
more on alsa v4l2 saa
1.sox is a master application used to test many sound related functions
2.alsa 1.0.19/21/24 are latest needed for nvidia gt400 pro working
3.alsa has tools that list the properties of sound card
4.aplay can play mp3s or wav
5.alsa can be compiled from source
6.saa alsa usually comes with kernel with saa dvb,tuner,radio etc , it doesnt have a separate branch outside to compile with any needed kernel
7.tuners are designed for saa specification, all analog , digital tuners are complaint
8.saa71xx is for video and saa71xx-alsa for audio
9.these are interfaced to v4l2 and alsa in the system
10.v4l2-ctl can show details of all video devices in the system
11.pinnacle pctv 310i can do sound in 2 ways , through an internal wire it can give the sound to
real sound card IN hence the sound cards LINEIN can be used as capture device
or
it can expose a sound device interface
12.issue with saa incompatibility b.w in kernel saa alsa and external updated alsa
13.v4l2 sees video devices as /dev/video0
14.saa alsa? sees devices as /dev/dsp /dev/dsp1
15.latest alsa sees devices as hw:1,0 plughw:1,0 ??
16.like alsa oss and pulse audio are independent drivers , they can run sound without alsa
17.can work parallely on different devices, on one device only one can work
18.pulse and oss have a glue layer for alsa??
19.there are sound stack for each of them independently
20.digital video devices are /dev/adapter/dvb0
21.xbmc needs plugin to show bind with vdr
22.vdr needs components from private repo to be functional
23.video with hw accel and non hw accel has different drivers, according to what driver is loaded
for the device hw accel is exposed or disabled.
24.powerful card can expose sterio functionality if old drivers are loaded for it
25.video drivers have persistant switch entries in conf files only at restart they are looked up
26.there is always way to bring up vga
27.codec stack comes on top of saa,and other alsa drivers
28.similar to alsa nvidia and other hw will have latest in place compilable oss and pulseaudio
drivers provided by vendor
29.similarly for video v4l2 ES 1/2/3 compatible drivers updated
30.codecs eat on low level v4l2 and alsa drivers
31.v4l2 and alsa provides apis to apps
32.main apps like flash will use plugins that use these apis
33.xclient startx will use these apis for remote/local sessions
34.for a 5.1 system each channel is a sound device
35.linux has a master firmeare directory used to keep latest fw of all devices
36.vpdau is a v4l2 specification ie from v4l2 to vpdau driver, ES is specification from within vpdau to real hw
37.lirc is v4l2 of ir commn
38.fm radio other radio uses tuner devices and alsa
39.tuner will have /dev/vvv alsa with /dev/aaa
40.they can use v4l2-ctl for scanning and freq
41.so tuner device , sound device, video device basics of multimedia
2.alsa 1.0.19/21/24 are latest needed for nvidia gt400 pro working
3.alsa has tools that list the properties of sound card
4.aplay can play mp3s or wav
5.alsa can be compiled from source
6.saa alsa usually comes with kernel with saa dvb,tuner,radio etc , it doesnt have a separate branch outside to compile with any needed kernel
7.tuners are designed for saa specification, all analog , digital tuners are complaint
8.saa71xx is for video and saa71xx-alsa for audio
9.these are interfaced to v4l2 and alsa in the system
10.v4l2-ctl can show details of all video devices in the system
11.pinnacle pctv 310i can do sound in 2 ways , through an internal wire it can give the sound to
real sound card IN hence the sound cards LINEIN can be used as capture device
or
it can expose a sound device interface
12.issue with saa incompatibility b.w in kernel saa alsa and external updated alsa
13.v4l2 sees video devices as /dev/video0
14.saa alsa? sees devices as /dev/dsp /dev/dsp1
15.latest alsa sees devices as hw:1,0 plughw:1,0 ??
16.like alsa oss and pulse audio are independent drivers , they can run sound without alsa
17.can work parallely on different devices, on one device only one can work
18.pulse and oss have a glue layer for alsa??
19.there are sound stack for each of them independently
20.digital video devices are /dev/adapter/dvb0
21.xbmc needs plugin to show bind with vdr
22.vdr needs components from private repo to be functional
23.video with hw accel and non hw accel has different drivers, according to what driver is loaded
for the device hw accel is exposed or disabled.
24.powerful card can expose sterio functionality if old drivers are loaded for it
25.video drivers have persistant switch entries in conf files only at restart they are looked up
26.there is always way to bring up vga
27.codec stack comes on top of saa,and other alsa drivers
28.similar to alsa nvidia and other hw will have latest in place compilable oss and pulseaudio
drivers provided by vendor
29.similarly for video v4l2 ES 1/2/3 compatible drivers updated
30.codecs eat on low level v4l2 and alsa drivers
31.v4l2 and alsa provides apis to apps
32.main apps like flash will use plugins that use these apis
33.xclient startx will use these apis for remote/local sessions
34.for a 5.1 system each channel is a sound device
35.linux has a master firmeare directory used to keep latest fw of all devices
36.vpdau is a v4l2 specification ie from v4l2 to vpdau driver, ES is specification from within vpdau to real hw
37.lirc is v4l2 of ir commn
38.fm radio other radio uses tuner devices and alsa
39.tuner will have /dev/vvv alsa with /dev/aaa
40.they can use v4l2-ctl for scanning and freq
41.so tuner device , sound device, video device basics of multimedia
Subscribe to:
Posts (Atom)