headers
terry white | 1 Aug 2007 08:44
Favicon

Re: mgetty problem

... ciao:

: on "7-31-2007" "Martin Klier" writ:
: # init q
: should do it

    may not be necessary, but i prefer:

    init q ; init u ...

--

-- 
... i'm a man, but i can change,
    if i have to , i guess ...

-
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
Diego Alencar Alves de Lima | 6 Aug 2007 16:23
Picon

Server freeze with EIP: 0060

Greetings,

One of our servers recently stopped responding suddenly during the
night. Checking the system logs, I saw that the last messages were
these:

Aug  4 03:12:59 mailserver -- MARK --
Aug  4 03:25:32 mailserver kernel: c0196a6e
Aug  4 03:25:32 mailserver kernel: Modules linked in: tsdev ipv6
reiserfs dm_snapshot dm_mirror dm_mod ide_generic evdev snd_hda_intel
snd_hda_codec i2c_ali1535 i2c_ali15x3 snd_pcm psmouse rtc ati_agp
agpgart i2c_core uli526x pcspkr serio_raw floppy snd_timer snd soundcore
snd_page_alloc shpchp pci_hotplug parport_pc parport ext3 jbd mbcache
ide_cd cdrom ide_disk generic sata_uli libata scsi_mod alim15x3 ide_core
skge 3c59x mii ehci_hcd ohci_hcd usbcore thermal processor fan
Aug  4 03:25:32 mailserver kernel: EIP:    0060:[keyring_destroy+39/119]
Not tainted VLI
Aug  4 03:25:32 mailserver kernel: EFLAGS: 00010213   (2.6.18-3-686 #1) 
Aug  4 03:25:32 mailserver kernel:  [key_cleanup+177/202] key_cleanup
+0xb1/0xca
Aug  4 03:25:32 mailserver kernel:  [run_workqueue+120/181]
run_workqueue+0x78/0xb5
Aug  4 03:25:32 mailserver kernel:  [key_cleanup+0/202] key_cleanup
+0x0/0xca
Aug  4 03:25:32 mailserver kernel:  [worker_thread+217/267]
worker_thread+0xd9/0x10b
Aug  4 03:25:32 mailserver kernel:  [default_wake_function+0/12]
default_wake_function+0x0/0xc
Aug  4 03:25:32 mailserver kernel:  [worker_thread+0/267] worker_thread
+0x0/0x10b
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauricio Silveira | 7 Aug 2007 05:28

Re: Ethernet devide enumeration problems

Hi,

I'm just updating this thread to post useful information.

I was unable to use ifrename to do the trick ...

I have upgraded the server to slackware 12, since the disk mirroring was 
incomplete when slackware 12 was released, so I decided to rebuild the 
raid array and install slackware 12 on it :)

Tuning the file "/etc/udev/rules.d/75-network-devices.rules" as needed 
seems to solve the problem.
I encourage everyone who uses slackware as you system to upgrade to v12 :)

Although I think samba 3.0.25b needs some "monitoring", got some strange 
behavior from this version, downgrading brought everything back in place.

Thanks for all your help,

Mauricio

Mauricio Silveira wrote:
> Hi all,
>
> I'm here asking for solutions for the Damned "Ethernet device 
> enumeration" problem!
>
> I have a P5b Mobo for my office server, it has 2 integrated NICs, but 
> the order for eth0/eth1 changes at each boot! It's getting me mad!
>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Aslan Carlos | 7 Aug 2007 20:54
Favicon

Re: Ethernet devide enumeration problems

Hi,

I've this problems too, but I was using initrd to load many modules to
work with AoE, I can't change the interface using udev :(, I use the
solution was rename the interfaces using ip command intro the initrd
after up the interfaces.

Thanks in advance,
--
Aslan Carlos de M. Ramos
Network Administrator
Mobile : +55(21)9989-4932
Skype  : aslancarlos

On Tue, 2007-08-07 at 00:28 -0300, Mauricio Silveira wrote:
> Hi,
> 
> I'm just updating this thread to post useful information.
> 
> I was unable to use ifrename to do the trick ...
> 
> I have upgraded the server to slackware 12, since the disk mirroring was 
> incomplete when slackware 12 was released, so I decided to rebuild the 
> raid array and install slackware 12 on it :)
> 
> Tuning the file "/etc/udev/rules.d/75-network-devices.rules" as needed 
> seems to solve the problem.
> I encourage everyone who uses slackware as you system to upgrade to v12 :)
> 
> Although I think samba 3.0.25b needs some "monitoring", got some strange
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kirkwood, David A. | 17 Aug 2007 20:18
Picon
Favicon

FW: 64 bit or 32 bit


From: Kirkwood, David A. 
Sent: Friday, August 17, 2007 1:13 PM
To: Linux group (linux-admin <at> vger.kernel.org)
Subject: 64 bit or 32 bit

How can I tell if a given system is running a 32bit krnel or a 64bit kernel. I  a system capable of running
either, but I cannot figure out which kernel is installed on it.

David A. Kirkwood

-
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 | 8 comments |
headers
terry white | 17 Aug 2007 23:42
Favicon

Re: FW: 64 bit or 32 bit

... ciao:

: on "8-17-2007" "Kirkwood, David A." writ:
: How can I tell if a system running a 32bit or 64bit kernel.

   my first inclination is 'uname -a', which might offer a hint by virtue
of the cpu.  in addition, you might take a look at "./.config" at the
root of the kernel source ...

--

-- 
... i'm a man, but i can change,
    if i have to , i guess ...

-
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
Benoit Rouits | 19 Aug 2007 21:48
Picon
Favicon
Gravatar

Re: FW: 64 bit or 32 bit

just make a C program like this:

int main()
{
	printf("address bus is %d bytes\n",sizeof(void*));
}
and compile it with cc then run it.
If it prints 8, it is a 64 bit OS, if it prints 4, it is a 32 bit OS.
cheers
- Ben
Le vendredi 17 août 2007 à 14:18 -0400, Kirkwood, David A. a écrit :
> 
> From: Kirkwood, David A. 
> Sent: Friday, August 17, 2007 1:13 PM
> To: Linux group (linux-admin <at> vger.kernel.org)
> Subject: 64 bit or 32 bit
> 
> How can I tell if a given system is running a 32bit krnel or a 64bit kernel. I  a system capable of running
either, but I cannot figure out which kernel is installed on it.
> 
> David A. Kirkwood
> 
> 
> -
> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
(Continue reading)

Permalink | Reply | 3 comments |
headers
Glynn Clements | 20 Aug 2007 20:34

Re: FW: 64 bit or 32 bit


Kirkwood, David A. wrote:

> How can I tell if a given system is running a 32bit krnel or a 64bit
> kernel. I  a system capable of running either, but I cannot figure out
> which kernel is installed on it.

	gzip -dc /proc/config.gz | fgrep CONFIG_X86_64

There may be similar information elsewhere in /proc; I don't know what
/proc/cpuinfo says for 64-bit architectures.

--

-- 
Glynn Clements <glynn <at> gclements.plus.com>
-
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 | 2 comments |
headers
Glynn Clements | 20 Aug 2007 20:36

Re: FW: 64 bit or 32 bit


Benoit Rouits wrote:

> > How can I tell if a given system is running a 32bit krnel or a 64bit
> > kernel. I a system capable of running either, but I cannot figure
> > out which kernel is installed on it.
> 
> just make a C program like this:
> 
> int main()
> {
> 	printf("address bus is %d bytes\n",sizeof(void*));
> }
> and compile it with cc then run it.
> If it prints 8, it is a 64 bit OS, if it prints 4, it is a 32 bit OS.

That tells you which architecture the program was compiled for, not
which architecture the kernel was compiled for. x86_64 can run both
32- and 64-bit code.

--

-- 
Glynn Clements <glynn <at> gclements.plus.com>
-
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 | 2 comments |
headers
Benoit Rouits | 21 Aug 2007 01:30
Picon
Favicon
Gravatar

Re: FW: 64 bit or 32 bit

Le lundi 20 août 2007 à 19:36 +0100, Glynn Clements a écrit :
> Benoit Rouits wrote:
> 
> > > How can I tell if a given system is running a 32bit krnel or a 64bit
> > > kernel. I a system capable of running either, but I cannot figure
> > > out which kernel is installed on it.
> > 
> > just make a C program like this:
> > 
> > int main()
> > {
> > 	printf("address bus is %d bytes\n",sizeof(void*));
> > }
> > and compile it with cc then run it.
> > If it prints 8, it is a 64 bit OS, if it prints 4, it is a 32 bit OS.
> 
> That tells you which architecture the program was compiled for, not
> which architecture the kernel was compiled for. x86_64 can run both
> 32- and 64-bit code.
> 
well, if we have a 64-bit kernel /and/ a compiler for 64 bits
architectures, i think that a long int must be 8 bytes, no ?
-
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 |

Gmane