Vec evo dve nedelje kako se otac vratio iz bolnice.
Vec evo dve nedelje kako se on i ja setamo. Ponekad dugo setamo kroz grad i uz kej,
nekad samo po hleb i mali obilazak obale Tamisa.
Uglavnom cutimo. Par puta smo pricali. Pricao mi je jednom prilikom o dedi koga nisam ni poznavao.
Kako je znao sa konjima. Prodavao je stasite konje istrenirane za rad i kupovao dva zdrepca i trenirao ih, dresirao ih da slusaju i razumeju komande.
No, uglavnom cutimo i hodamo.
rezimiramo godinu
januar:
majka operisala slepo crevo.
upoznao se sa Miljanom preko neta a onda i licno kasnije
cekanje
umrla tetka iz Nemacke u maju valjda.
cekanje
tata zamalo da nam ode, stavili mu pacemaker pocetkom decembra.
malo bolje shvatio sa kakvim ljudima zivim.
15.dec.2011.
majka operisala slepo crevo.
upoznao se sa Miljanom preko neta a onda i licno kasnije
cekanje
umrla tetka iz Nemacke u maju valjda.
cekanje
tata zamalo da nam ode, stavili mu pacemaker pocetkom decembra.
malo bolje shvatio sa kakvim ljudima zivim.
15.dec.2011.
thumbs proxy cheker vhost advice
pupit: hi, should i put this in my webserver root? http://vlad-tepes.bofh.it/freenode-proxy-checker.txt
spb: if you really want to
thumbs: pupit: why would you?
spb: it won't do much, mind
pupit: thumbs: a lot of errors in error_log asking that file, i though someone will know in this room
thumbs: pupit: so the only purpose is not to pollute your error log?
pupit: thumbs, yes
thumbs: pupit: note that you can make a vhost with your IP as the Servername in apache, and use /dev/log for the ErrorLog there.
spb: then that won't help much
pupit: and the 2nd question, why is asking for that file?
spb: pupit: that's our proxy checker
spb: it's checking to see whether your machine has an abusable open proxy on it
thumbs: pupit: you can then serve content with your other vhosts, and ignore the requests on http://your_ip_here/
pupit: thumbs: yeah
thumbs: pupit: much smarter than putting a dummy file in the vhost.
pupit: thumbs: i know :)
pupit: i was just curious
spb: if you really want to
thumbs: pupit: why would you?
spb: it won't do much, mind
pupit: thumbs: a lot of errors in error_log asking that file, i though someone will know in this room
thumbs: pupit: so the only purpose is not to pollute your error log?
pupit: thumbs, yes
thumbs: pupit: note that you can make a vhost with your IP as the Servername in apache, and use /dev/log for the ErrorLog there.
spb: then that won't help much
pupit: and the 2nd question, why is asking for that file?
spb: pupit: that's our proxy checker
spb: it's checking to see whether your machine has an abusable open proxy on it
thumbs: pupit: you can then serve content with your other vhosts, and ignore the requests on http://your_ip_here/
pupit: thumbs: yeah
thumbs: pupit: much smarter than putting a dummy file in the vhost.
pupit: thumbs: i know :)
pupit: i was just curious
copying one type of file from many folders
find /src -regextype posix-extended -regex '.*(jpg|gif)' -exec cp {} /dest \;
pupit: tried
cp -r /d/d/*.file
but it doesnt work :/
Qwood: pupit: One second and I'll write you a one-liner here.
Qwood: pupit:
'for fname in $(find dir | grep .ext); do cp $fname newdir; done'
pupit: Qwood: awesome, thanks a lot :)
Qwood: pupit: dir being the top of the directory tree you want to copy from, ext being the file extension you are looking for, and newdir being the directory you want to copy to.
pupit: yeah :)
pupit: its clear to me
Qwood: pupit: I do that kind of copying all the time :)
pupit: its very handy :)
pupit: Qwood: i had a bit trouble copying from directories with spaces so i find this solution:
find /src -regextype posix-extended -regex '.*(jpg|gif)' -exec cp {} /dest \;
pupit: s/find/found
Qwood: pupit: I'm lucky to not have spaces in most of my files
pupit: Qwood: yeah, well when dealing with m$ users its inevitable :)
pupit: Qwood: i mostly use _ for space mark
Qwood: pupit: Same
pupit: tried
cp -r /d/d/*.file
but it doesnt work :/
Qwood: pupit: One second and I'll write you a one-liner here.
Qwood: pupit:
'for fname in $(find dir | grep .ext); do cp $fname newdir; done'
pupit: Qwood: awesome, thanks a lot :)
Qwood: pupit: dir being the top of the directory tree you want to copy from, ext being the file extension you are looking for, and newdir being the directory you want to copy to.
pupit: yeah :)
pupit: its clear to me
Qwood: pupit: I do that kind of copying all the time :)
pupit: its very handy :)
pupit: Qwood: i had a bit trouble copying from directories with spaces so i find this solution:
find /src -regextype posix-extended -regex '.*(jpg|gif)' -exec cp {} /dest \;
pupit: s/find/found
Qwood: pupit: I'm lucky to not have spaces in most of my files
pupit: Qwood: yeah, well when dealing with m$ users its inevitable :)
pupit: Qwood: i mostly use _ for space mark
Qwood: pupit: Same
unrar, ls -l, vdir
how to unrar?
unrar e -x /DATA/Pocahontas.1995.iNTERNAL.DVDRip.XviD-SLeTDiVX/sdx-poca-int.part01.rar /DATA/shared/
You can view the access permissions of a file by doing the long directory listing with the ls -l command.
vdir
unrar e -x /DATA/Pocahontas.1995.iNTERNAL.DVDRip.XviD-SLeTDiVX/sdx-poca-int.part01.rar /DATA/shared/
You can view the access permissions of a file by doing the long directory listing with the ls -l command.
vdir
how do you do a screen capture in slackware 13.1?
Poesghost: how do you do a screen capture in slackware 13.1?
UrchLap: one way is to load up the gimp and use its "acquire image" option
Poesghost: okay, thank you.
UrchLap: another way is "import -window root shot.png"
UrchLap: (or leave off the "-window root" part and click on a window to save just that window)
adrien: import!
Poesghost: okay, I'll try that too. Cause print screen doesn't capture it to a clipboard.
adrien: sleep 2 && import -window root foo.png && optipng foo.png
adrien: don't skip the optipng part
pupit: Poesghost: http://rlworkman.net/pkgs/13.37/i486/ -> xfce4-screenshooter-1.7.9-i486-1_rlw.txz
pupit: thats for 13.37 but im sure you'll find it for 13.1
UrchLap: one way is to load up the gimp and use its "acquire image" option
Poesghost: okay, thank you.
UrchLap: another way is "import -window root shot.png"
UrchLap: (or leave off the "-window root" part and click on a window to save just that window)
adrien: import!
Poesghost: okay, I'll try that too. Cause print screen doesn't capture it to a clipboard.
adrien: sleep 2 && import -window root foo.png && optipng foo.png
adrien: don't skip the optipng part
pupit: Poesghost: http://rlworkman.net/pkgs/13.37/i486/ -> xfce4-screenshooter-1.7.9-i486-1_rlw.txz
pupit: thats for 13.37 but im sure you'll find it for 13.1
how to check to which package belongs xclock for example?
pupit: how to check to which package belongs xclock for example?
OzanBurada: slackpkg file-search
Tadgy: pupit: fgrep "/xclock" /var/log/packages/*
OzanBurada: slackpkg file-search
Tadgy: pupit: fgrep "/xclock" /var/log/packages/*
bios beep codes
So you turn on your system and you get beep error codes......not sure what those beeps mean?
Well, here you go:
1 Short Beep.
One beep is good! Everything is ok, that is if you see things on the screen. If you don't see anything, check your monitor and video card first. Is everything connected? If they seem fine, your motherboard has some bad chips on it. First reset the SIMM's and reboot. If it does the same thing, one of the memory chips on the motherboard are bad, and you most likely need to get another motherboard since these chips are soldered on.
2 Short Beeps.
Your computer has memory problems. First check video. If video is working, you'll see an error message. If not, you have a parity error in your first 64K of memory. First check your SIMM's. Reseat them and reboot. If this doesn't do it, the memory chips may be bad. You can try switching the first and second banks memory chips. First banks are the memory banks that your CPU finds its first 64K of base memory in. You'll need to consult your manual to see which bank is first. If all your memory tests good, you probably need to buy another motherboard.
3 Short Beeps.
Basically the same thing as 2 beeps. Follow that diagnosis above.
4 Short Beeps.
Basically the same thing as 2 beeps. Follow that diagnosis above. It could also be a bad timer
5 Short Beeps.
Your motherboard is complaining. Try reseating the memory and rebooting. If that doesn't help, you should consider another motherboard. You could probably get away with just replacing the CPU, but that's not too cost-effective. Its just time to upgrade!
6 Short Beeps.
The chip on your motherboard that controls your keyboard (A20 gate) isn't working. First try another keyboard. If it doesn't help, reseat the chip that controls the keyboard, if it isn't soldered in. If it still beeps, replace the chip if possible. Replace the motherboard if it is soldered in.
7 Short Beeps.
Your CPU broke overnight. Its no good. Either replace the CPU, or buy another motherboard.
8 Short Beeps.
Your video card isn't working. Make sure it is seated well in the bus. If it still beeps, either the whole card is bad or the memory on it is. Best bet is to install another video card.
9 Short Beeps.
Your BIOS is bad. Reseat or Replace the BIOS.
10 Short Beeps.
Your problem lies deep inside the CMOS. All chips associated with the CMOS will likely have to be replaced. Your best bet is to get a new motherboard.
11 Short Beeps.
Your problem is in the Cache Memory chips on the motherboard. Reseat or Replace these chips.
1 Long, 3 Short Beeps.
You've probably just added memory to the motherboard since this is a conventional or extended memory failure. Generally this is caused by a memory chip that is not seated properly. Reseat the memory chips.
1 Long, 8 Short Beeps.
Display / retrace test failed. Reseat the video card.
Author: Skyguy
AWARD BIOS beep codes
1 long, 2 short.
Indicates a video error has occurred and the BIOS cannot initialize the video screen to display any additional information
This issue can be caused by any of the below situations.
New hardware conflicting with old hardware.
Bad or failing hardware device.
Connections not connected or connected properly.
Recent electrical storm that caused a surge that damaged the computer.
Or other hardware issue.
Any other beep(s)
3 short beeps
RAM problem.
1.Remove added memory
If it boots up then you either have compatibility issues or defective ram.
2.Open computer and reseat memory
Sometimes when the computer is moved and over time a memory stick can become loose causing the computer to either get errors from trying to read the ram or does not read the ram at all.
Try fixing this issue by opening the computer taking out the memory and reseating them back in.
3.Swap the Memory
sometimes one stick could die out over time (especially if it is overclocked) but one could still be good. So swap the location of the memory. that still does not work, take out all the memory but leave one in the Dimm slot closest to the processor, and test them all out individually to see which one is causing the problem.
4. try another computer memory
if you have another computer handy that works try using the memory from that computer.
If the memory from the other computer works, then you know that you have bad memory. If the other computes memory does not work and it is compatible with your computer unfortunately your motherboard and or the slots on the motherboard are defective causing it to be unable to properly read the memory, which means the motherboard will have to be replaced.
PHOENIX BIOS beep codes
The Phoenix beep codes have a huge list of them so I will name the ones that I think would be the best to know if or when your having problems. But I could also be wrong about them, most of them I have is from notes I doodled down a while ago.
1-1-1-3 = Verify Real Mode
1-1-2-1 = checks for CPU type
2-3-1-1 = Test expanded memory, the rest of the memory after 640k
2-4-1-3 = Check for configuration errors
2-4-2-3 = Check for keyboard errors
3-4-1-3 = Post Done
3-4-2-1 = One beep
4-2-1-1 = Interupt Handler Error
4-2-1-3 = Unkown interupt error
4-2-2-3 = Initialize option ROM error
4-2-3-1 = Shutdown error
4-3-2-3 = Bios is ok
Author: Kaganader
Well, here you go:
1 Short Beep.
One beep is good! Everything is ok, that is if you see things on the screen. If you don't see anything, check your monitor and video card first. Is everything connected? If they seem fine, your motherboard has some bad chips on it. First reset the SIMM's and reboot. If it does the same thing, one of the memory chips on the motherboard are bad, and you most likely need to get another motherboard since these chips are soldered on.
2 Short Beeps.
Your computer has memory problems. First check video. If video is working, you'll see an error message. If not, you have a parity error in your first 64K of memory. First check your SIMM's. Reseat them and reboot. If this doesn't do it, the memory chips may be bad. You can try switching the first and second banks memory chips. First banks are the memory banks that your CPU finds its first 64K of base memory in. You'll need to consult your manual to see which bank is first. If all your memory tests good, you probably need to buy another motherboard.
3 Short Beeps.
Basically the same thing as 2 beeps. Follow that diagnosis above.
4 Short Beeps.
Basically the same thing as 2 beeps. Follow that diagnosis above. It could also be a bad timer
5 Short Beeps.
Your motherboard is complaining. Try reseating the memory and rebooting. If that doesn't help, you should consider another motherboard. You could probably get away with just replacing the CPU, but that's not too cost-effective. Its just time to upgrade!
6 Short Beeps.
The chip on your motherboard that controls your keyboard (A20 gate) isn't working. First try another keyboard. If it doesn't help, reseat the chip that controls the keyboard, if it isn't soldered in. If it still beeps, replace the chip if possible. Replace the motherboard if it is soldered in.
7 Short Beeps.
Your CPU broke overnight. Its no good. Either replace the CPU, or buy another motherboard.
8 Short Beeps.
Your video card isn't working. Make sure it is seated well in the bus. If it still beeps, either the whole card is bad or the memory on it is. Best bet is to install another video card.
9 Short Beeps.
Your BIOS is bad. Reseat or Replace the BIOS.
10 Short Beeps.
Your problem lies deep inside the CMOS. All chips associated with the CMOS will likely have to be replaced. Your best bet is to get a new motherboard.
11 Short Beeps.
Your problem is in the Cache Memory chips on the motherboard. Reseat or Replace these chips.
1 Long, 3 Short Beeps.
You've probably just added memory to the motherboard since this is a conventional or extended memory failure. Generally this is caused by a memory chip that is not seated properly. Reseat the memory chips.
1 Long, 8 Short Beeps.
Display / retrace test failed. Reseat the video card.
Author: Skyguy
AWARD BIOS beep codes
1 long, 2 short.
Indicates a video error has occurred and the BIOS cannot initialize the video screen to display any additional information
This issue can be caused by any of the below situations.
New hardware conflicting with old hardware.
Bad or failing hardware device.
Connections not connected or connected properly.
Recent electrical storm that caused a surge that damaged the computer.
Or other hardware issue.
Any other beep(s)
3 short beeps
RAM problem.
1.Remove added memory
If it boots up then you either have compatibility issues or defective ram.
2.Open computer and reseat memory
Sometimes when the computer is moved and over time a memory stick can become loose causing the computer to either get errors from trying to read the ram or does not read the ram at all.
Try fixing this issue by opening the computer taking out the memory and reseating them back in.
3.Swap the Memory
sometimes one stick could die out over time (especially if it is overclocked) but one could still be good. So swap the location of the memory. that still does not work, take out all the memory but leave one in the Dimm slot closest to the processor, and test them all out individually to see which one is causing the problem.
4. try another computer memory
if you have another computer handy that works try using the memory from that computer.
If the memory from the other computer works, then you know that you have bad memory. If the other computes memory does not work and it is compatible with your computer unfortunately your motherboard and or the slots on the motherboard are defective causing it to be unable to properly read the memory, which means the motherboard will have to be replaced.
PHOENIX BIOS beep codes
The Phoenix beep codes have a huge list of them so I will name the ones that I think would be the best to know if or when your having problems. But I could also be wrong about them, most of them I have is from notes I doodled down a while ago.
1-1-1-3 = Verify Real Mode
1-1-2-1 = checks for CPU type
2-3-1-1 = Test expanded memory, the rest of the memory after 640k
2-4-1-3 = Check for configuration errors
2-4-2-3 = Check for keyboard errors
3-4-1-3 = Post Done
3-4-2-1 = One beep
4-2-1-1 = Interupt Handler Error
4-2-1-3 = Unkown interupt error
4-2-2-3 = Initialize option ROM error
4-2-3-1 = Shutdown error
4-3-2-3 = Bios is ok
Author: Kaganader
ssh listener
When an incoming connection is received, sshd forks a new process which handles the connection.
For instance,
ps -x -c -a | grep sshd
gets me all sshd PIDs currently running.
did you already try,
ps -Alf | grep ssh
For instance,
ps -x -c -a | grep sshd
gets me all sshd PIDs currently running.
did you already try,
ps -Alf | grep ssh
How to Remove Windows XP Activation - xp sp1 home edition
Instructions:
1
Log on to your PC with an administrator account.
2
Open the Start menu and click the \"Run\" icon.
3
Type \"regedit\" into the text box and click on the \"OK\" button to launch the Registry Editor.
4
Navigate to the HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\WPAEvents directory in the registry.
5
Double-click on the registry entry labeled \"OOBETimer.\"
6
Change the current string of letters and numbers to \"FF D5 71 D6 8B 6A 8D 6F D5 33 93 FD\" and then hit \"OK\" to save the settings.
7
Right-click on the \"WPAEvents\" folder and select \"Permissions.\"
8
Deny permission access for the \"System\" listing and click \"OK\" to save the configuration. The WIndows XP activation reminder has now been disabled and removed.
note, from my experience, I only had to do the EIGHT STEP - Deny permission access for the \"System\"
the key is: VWPC9-HBGPC-TT92X-66QGH-M7JJG
1
Log on to your PC with an administrator account.
2
Open the Start menu and click the \"Run\" icon.
3
Type \"regedit\" into the text box and click on the \"OK\" button to launch the Registry Editor.
4
Navigate to the HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\WPAEvents directory in the registry.
5
Double-click on the registry entry labeled \"OOBETimer.\"
6
Change the current string of letters and numbers to \"FF D5 71 D6 8B 6A 8D 6F D5 33 93 FD\" and then hit \"OK\" to save the settings.
7
Right-click on the \"WPAEvents\" folder and select \"Permissions.\"
8
Deny permission access for the \"System\" listing and click \"OK\" to save the configuration. The WIndows XP activation reminder has now been disabled and removed.
note, from my experience, I only had to do the EIGHT STEP - Deny permission access for the \"System\"
the key is: VWPC9-HBGPC-TT92X-66QGH-M7JJG
Пријавите се на:
Постови (Atom)