might be able
to tweak it instead of disabling udev altogether.
Do the system logs contain any clues what is going on or does the system
kills itself before logging to harddisc comes on?
Regards,
Berend Dekens
___
CentOS mailing list
CentOS
Rudi Ahlers schreef:
Unfortunately I don't see anything useful in the logs. If I let it
bootup by itself, then it reboots just after booting udev. If,
however, I press CTRL+C the moment I see udev on the screen, I have
attached a snippet from /var/log/message - which doesn't show me
anything at
Filipe Brandenburger schreef:
Did you still not understand that we need to know what the file names
are???
The command provided shows the content of the files and yes, perhaps it
would show the filenames as well. This was however not specifically asked.
Furthermore the files are named
servers) but I am new to
CentOS so I tried to do everything by using the GUI - which in this case
keeps failing...
Regards,
Berend Dekens
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
None of the files have ONBOOT but they do have ONPARENT...
I'll add the ONBOOT param and reboot the server tonight to see if it worked.
Cheers,
Berend
Ralph Angenendt wrote:
Berend Dekens wrote:
However, after a reboot, all aliasses are disabled: they are present in
the configuration
running into that one but CentOS hasn't got the same scripts so their
solution won't help me.
Cheers,
Berend
Berend Dekens wrote:
None of the files have ONBOOT but they do have ONPARENT...
I'll add the ONBOOT param and reboot the server tonight to see if it
worked.
Cheers,
Berend
___
CentOS
Tony Mountifield wrote:
Could you post the output of: head -20
/etc/sysconfig/network-scripts/ifcfg-eth0*
Cheers
Tony
[EMAIL PROTECTED] network-scripts]# head -20
/etc/sysconfig/network-scripts/ifcfg-eth0*
# Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]
DEVICE=eth0
BOOTPROTO=none
Tony Mountifield wrote:
Hmmm, in a previous post you said you had multiple aliases and three errors.
But above, you have only posted one main device and one alias. Are they ones
that succeed of fail?
Every one of them fails except eth0 itself (which is good or I would
have locked myself
Kai Schaetzl schreef:
or, at the same time while you are waiting for more replies, you could try
starting up with only the first alias and if that succeeds try the next
one and so on ...
I was doing exactly that. And I was trying to figure out how the
networking scripts work and what they do -
in a virtual machine (don't think the
latter matters but right now I don't know where to look for the cause).
Regards,
Berend Dekens
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
John schreef:
Berend Writes:
svnserve: error while loading shared libraries: libexpat.so.0: cannot
open shared object file: No such file or directory
JohnStanley Writes:
#]yum whatprovides libexpat.so.0
expat.i386 : A library for parsing XML.
mysql-gui-tools.i386 : GUI Tools for MySQL 5.0
John schreef:
JohnStanley Writes:
Sometimes conlflicts can be created between the two. RPM and Yum. Run rpm
--rebuilddb
No change in there - SVN still fails.
Alternatively:
Maybe then your problem lies in the kind of install you did with Subversion.
Installed from source or Binary RPM
I just found out that the other machine holding the SVN repository was
recently updated. So after trying on that one I got the same error!
(Which ofcourse made me think)
It seems that SVN invokes a remote copy of the binary for reading the
repo and simply pipes back the results... So while I
13 matches
Mail list logo
