headers
Trenton Sarver | 9 Jun 2006 23:13

[BREAKING NEWS] We got the most trusted drug name brands. fruition experts incident capitalizations

We are your online solution for quality generic and brand name medications at affordable prices! We have
some great medications to offer you and will be adding many more in the coming weeks.

Free online medical consultation by a licensed U.S. physician.

Visit Us Now
rxpersona.com

Sincerely,
Trenton Sarver
rxpersona.com customer service

veuomxihlb DNuZyePemxlCrPUaTESRSbfBFTCfKC

abject Harley freewheel capitalizations consoles baneberry ducked hypophyseal airfield USAF licked
influentially devises USAF Punic confessions betrayer immediately inquisitive colt's merging
constructed glacier disables activity alienating diverting miscellaneousness feedings determines
employment's initials gadwall bronzed ducked Hermosa becalmed imposed
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Richard Nairn | 15 Jun 2006 16:56
Picon

Figureing out which device

Hi,

I have a drive which is getting I/O errors.  It is telling me that it is  
dev 08:21.

How does this translate into which scsi device is having the problem?

Thanks

--

-- 
|       Richard Nairn          Specializing in Linux
|     Nairn Consulting         Web / Database Solutions
|        Calgary, AB
| Richard <at> NairnConsulting.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 4 comments |
headers
Thomas Callahan | 15 Jun 2006 16:59
Favicon

Re: Figureing out which device

Looks like a major/minor number for device /dev/sda.....

Check your /dev/sd* entries.

Also "cat /proc/partitions" will show major/minor numbers. Then you  
can correlate that to a device.

Tom Callahan
TESSCO Technologies
Desk: (410)-229-1361
Cell: (410)-588-7605
Email: callahant <at> tessco.com

A real engineer only resorts to documentation when the keyboard dents on
the forehead get too noticeable.

On Jun 15, 2006, at 10:56 AM, Richard Nairn wrote:

> Hi,
>
> I have a drive which is getting I/O errors.  It is telling me that  
> it is
>
> dev 08:21.
>
> How does this translate into which scsi device is having the problem?
>
> Thanks
>
>
(Continue reading)

Permalink | Reply | 3 comments |
headers
Richard Nairn | 15 Jun 2006 17:05
Picon

Re: Figureing out which device

None of my devices match up like major/minor. I checked that first..

# cat partitions
major minor  #blocks  name     rio rmerge rsect ruse wio wmerge wsect wuse  
running use aveq

    8     0   35843686 sda 9649 31576 329458 67170 3475 5379 71368 192970 0  
42440 260130
    8     1   33736500 sda1 9634 31529 329274 67130 3475 5379 71368 192970  
0 42400 260090
    8     2    2104483 sda2 13 41 168 30 0 0 0 0 0 30 30
    8    16   35843686 sdb 2757 9896 100648 391070 1442 1142 21768 13410 0  
9970 404480
    8    17   35840983 sdb1 2756 9893 100640 391070 1442 1142 21768 13410 0  
9970 404480
    8    32   35843686 sdc 2291 10014 97978 11340 2377 1734 34128 16280 0  
8650 27620
    8    33   35840983 sdc1 2290 10011 97970 11330 2377 1734 34128 16280 0  
8640 27610
    9     0   71681792 md0 0 0 0 0 0 0 0 0 0 0 0

On Thu, 15 Jun 2006 08:59:29 -0600, Thomas Callahan <callahant <at> tessco.com>  
wrote:

> Looks like a major/minor number for device /dev/sda.....
>
> Check your /dev/sd* entries.
>
> Also "cat /proc/partitions" will show major/minor numbers. Then you can  
> correlate that to a device.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Andreas Unterkircher | 15 Jun 2006 18:30
Picon

Re: Figureing out which device

Probably 08:21 is hex... So it would be 8:33 in dec.

Richard Nairn schrieb:
> None of my devices match up like major/minor. I checked that first..
>
>
> # cat partitions
> major minor  #blocks  name     rio rmerge rsect ruse wio wmerge wsect
> wuse running use aveq
>
>    8     0   35843686 sda 9649 31576 329458 67170 3475 5379 71368
> 192970 0 42440 260130
>    8     1   33736500 sda1 9634 31529 329274 67130 3475 5379 71368
> 192970 0 42400 260090
>    8     2    2104483 sda2 13 41 168 30 0 0 0 0 0 30 30
>    8    16   35843686 sdb 2757 9896 100648 391070 1442 1142 21768
> 13410 0 9970 404480
>    8    17   35840983 sdb1 2756 9893 100640 391070 1442 1142 21768
> 13410 0 9970 404480
>    8    32   35843686 sdc 2291 10014 97978 11340 2377 1734 34128 16280
> 0 8650 27620
>    8    33   35840983 sdc1 2290 10011 97970 11330 2377 1734 34128
> 16280 0 8640 27610
>    9     0   71681792 md0 0 0 0 0 0 0 0 0 0 0 0
>
>
> On Thu, 15 Jun 2006 08:59:29 -0600, Thomas Callahan
> <callahant <at> tessco.com> wrote:
>
>> Looks like a major/minor number for device /dev/sda.....
(Continue reading)

Permalink | Reply | 1 comment |
headers
Richard Nairn | 15 Jun 2006 19:03
Picon

Re: Figureing out which device

Thanks - should of thought of that.. Now if I can get my data off in time  
to replace the drive!

On Thu, 15 Jun 2006 10:30:16 -0600, Andreas Unterkircher  
<unki <at> netshadow.at> wrote:

> Probably 08:21 is hex... So it would be 8:33 in dec.
>
> Richard Nairn schrieb:
>> None of my devices match up like major/minor. I checked that first..
>>
>>
>> # cat partitions
>> major minor  #blocks  name     rio rmerge rsect ruse wio wmerge wsect
>> wuse running use aveq
>>
>>    8     0   35843686 sda 9649 31576 329458 67170 3475 5379 71368
>> 192970 0 42440 260130
>>    8     1   33736500 sda1 9634 31529 329274 67130 3475 5379 71368
>> 192970 0 42400 260090
>>    8     2    2104483 sda2 13 41 168 30 0 0 0 0 0 30 30
>>    8    16   35843686 sdb 2757 9896 100648 391070 1442 1142 21768
>> 13410 0 9970 404480
>>    8    17   35840983 sdb1 2756 9893 100640 391070 1442 1142 21768
>> 13410 0 9970 404480
>>    8    32   35843686 sdc 2291 10014 97978 11340 2377 1734 34128 16280
>> 0 8650 27620
>>    8    33   35840983 sdc1 2290 10011 97970 11330 2377 1734 34128
>> 16280 0 8640 27610
>>    9     0   71681792 md0 0 0 0 0 0 0 0 0 0 0 0
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tyler Littlefield | 16 Jun 2006 01:01
Picon

patches?

Hey list,
I am working on a secure system.
I have a quick question. What kinds of things besides a firewall, and not
granting ssh to anyone can I do to secure linux? I am currently using
debian. Also, I have read about patches. How do I know which ones to
install, and where would I find them?
Thanks,
~~TheCreator~~
website:
http://tysplace.shaned.net
msn:
compgeek134 <at> hotmail.com
aim:
st8amnd2005
skype:
st8amnd127
moo coder/wizard and administrator

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 1 comment |
headers
ycsapo | 16 Jun 2006 22:50
Picon
Favicon

Re: patches?


Hi Tyler,

Your questions would be more appropriately answered by a couple of books
than a simple e-mail. However, some things that come to mind:

1. Turn off unused services. Services that aren't enabled can't be
attacked. That greatly simplifies the issues, including patch
management, since it doesn't really matter if a daemon (say, httpd the
web server) becomes vulnerable when you're not running that daemon.
Therefore, if your system is a web server there's little reason to run
anything other than Apache or similar and the minimum set of things for
Unix/linux to still work.

2. It is never enough to just run a firewall, especially some default
configuration that comes with your distro or something you find on the
web. If you're serious about security you need to learn IPtables,
understand the issues and develop your own rules and policies.

3. You do NOT want to deny ssh to everyone, unless you're certain that
you will never ever need to do remote administration. If that's the
case, don't just deny access - disable sshd altogether. But despite what
you may have heard ssh is still very safe and it beats every other
option for remote admin - as long as you pick good passwords and keep
your system up to date.

4. Use the tcp wrapper.

5. Keep your system up-to-date.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sashikanth Madduri | 19 Jun 2006 22:44
Picon

Password File Sync Script

Hi,
     I am writing a script to update password files from the server to
all the clients in the network.

I will be copying the following files periodically to all the clients:

/etc/passwd
/etc/shadow
/etc/group

scp is one option to do the remote copying. But, root ssh is disabled
in the clients and I cannot use scp. Is there any alternative
way(other than scp) to do this. Do I have to enable root ssh inorder
to do a remote copy of the above files. Please help.

PS: I am not using NIS for password management.

Thank you.

Sashikanth Madduri.
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 6 comments |

Gmane