will do
I guess you meant memtest for ram scan?
Back to top

yes, memtest, right.

Hard disk tools will vary depending on what disk you have.

In general I find the ibm and seagate ones the best, but your results may vary, especially since ibm is out of that business now for a while.
Back to top

ok good stuff that UBCD

memtest full pass ok

WD drive diagnostics quick and extended both pass ok

e2fsck -f /dev/mypartions also all good for non-swap

2) sysv-rc-conf and rcconf

I can't see hostname in rcconf hmmm

I will have to check old image and then do some reading me thinks

EDIT

silly me.....rcconf only shows what is not in rcS

oh well
Back to top

I have run out of patience

I have added

/etc/init.d/hostname.sh to my rc.local and reboot is good



thanks
Back to top

I am leaving this as solved but I finally found a google that might be the answer?

yes I had not fully resolved it...it came back!

forums.whirlpool.net.au/archive/890042




Now it happens that I do have a billion router eek

and I normally remove as much software as possible before doing a DU.

Currently I use partimage and have started more intensive investigation of my issue.

so far I am at the stage of clean install on a new partition table of aptosid.
I cull a lot of software because I prefer not to image useless data.
Yesterday I did a DU then ran smxi for the first time and completed smxi and upon reboot ...my issue arose.

Back on unaffected image at the moment and



You may wonder why I don't just report what happens when I do X or Y.

Its because I am trying to track down what I have done and what I about to do

(I don't expect many ppl to read this but this is my paranoid self eh?)
Back to top

EDIT

wrong

< Edited by aus9 :: Oct 9, 11, 21:24 >
Back to top

EDIT

wrong

< Edited by aus9 :: Oct 9, 11, 21:23 >
Back to top

no I was wrong...well it re-appeared

Initially I thought because I could run

that it was init script for hostname that was the issue.

2) Then I thought it might be my router.

But I think my router is getting incomplete info and that unkwown string is my hw MAC....Yes I have exposed it.

3) I now think its /etc/dhclient.conf

I force it to use

send host-name "sid.sid.com";
send dhcp-client-identifier <my-mac>;

and on reboot.....my terminal is resolved correct hostname
my syslog is good
My rouiter client name is no longer unknownstring but the sid sid stuff

so I am now thinking I am happy

EDIT (B) The change in dhcp behaviour is likely to a change in

isc-dhcp-client_4.2.2-1_i386.deb 734146 27-Sep-2011 09:17
and its other package

This likely explains why when I did smxi....all of a sudden my hostname was failing.
Nothing to do with smxi but DU gives the same result.
(I know because I just did a clean install from a aptosid disc to see what was going on)
altho that in hind sight was a waste of time.....not knowing whether it was a init script, a router issue or a package issue......investigation and testing was the key to my success.......until it fails again LOL
Back to top