Hostname and user changed to postgres

[blocked]

I'm trying to remaster a Backtrack 5 build.  I know it isn't pure ubuntu, but any help is appreciated.

Each time I rebuild (Backup Mode), I see the message in the output screen "Creating the casper.conf file."

The problem is that I have modified the hostname and username variables in my systems casper.conf.  Each time I rebuild, those get reset to postgres.

Is there anyway to lock the casper.conf file so that it doesn't get recreated each time?

Thanks,
Eddie

[fragadelic]

Those get populated based on what you set as the LIVEUSER name in the /etc/remastersys.conf file.  If you want to bypass that, just edit /usr/bin/remastersys and comment out the section that creates the casper.conf file.

Remastersys is just a bash script at the moment so you just have to put a # at the beginning of the lines you want to comment out.

Coment out the following lines:

Code:

   cat > /etc/casper.conf <<FOO
# This file should go in /etc/casper.conf
# Supported variables are:
# USERNAME, USERFULLNAME, HOST, BUILD_SYSTEM

export USERNAME="$LIVEUSER"
export USERFULLNAME="Live session user"
export HOST="$LIVEUSER"
export BUILD_SYSTEM="Ubuntu"
FOO
    cp /etc/casper.conf $WORKDIR/dummysys/etc/

to be like so:

Code:

#    cat > /etc/casper.conf <<FOO
# This file should go in /etc/casper.conf
# Supported variables are:
# USERNAME, USERFULLNAME, HOST, BUILD_SYSTEM

#export USERNAME="$LIVEUSER"
#export USERFULLNAME="Live session user"
#export HOST="$LIVEUSER"
#export BUILD_SYSTEM="Ubuntu"
#FOO
    cp /etc/casper.conf $WORKDIR/dummysys/etc/

Edit - uncommented the copy of the casper.conf as that still has to happen.

[blocked]

Thank you so much for the quick reply.  I've made that change and am testing now.

The weird part is that the LIVEUSER was set to the username I was trying to populate, it just wouldn't use that one for some reason.

Hopefully my next build will work as expected.... (famous last words)

Thank you again for such a great product.

--Eddie

[fragadelic]

What username were you trying to use?
Username must be in lowercase and can't be anything already in use.  I also think if you are setting a root password and want to keep it, you should be using backup mode so there is no user creation during live boot.

[blocked]

The LIVEUSER is "scanuser", all lower case.

I am using backup mode, and haven't had any issues with my root or user accounts or passwords.  I can still login as root or scanuser, but just kept loosing my username and host in casper.conf. 

The goal is to have a set of scripts fire off when the scanuser logs in.  One of the tools was/is (still testing) having issues with the hostname changing. 

Thanks,
Eddie

[fragadelic]

That should be fine and on normal ubuntu whatever you set for liveuser gets used as the live name and hostname.  Maybe the Backtrack folks have changed something else in the live boot.