64bit Install -- No Option to set HOST NAME

I have run this install three times. I can’t find an option to set the name of the system being built/installed. :open_mouth:

Since I am building it to be my own file server (SAMBA, NFS, etc.) and do LDAP (I’d like to get PDC to work, eventually), I would like to name it at install time.

Ok, since I can’t do that, then all the examples for how to do this with yast tell one to go to Network Services and to “DHCP and Hostname”. :?

This system is not the DHCP controller. That system is up and running a completely different distro of Linux and works just fine.

So, how does one report this “bug” in LEAP 42? I have a “Novell” account and can’t find where, there, either. And if I click on the “support” area at the top of this window, I get a 404. :beat-up:

Yes, I can issue hostname xxxxx and it changes it for the duration of the boot. But reboot and I’m back to the goofy name the install generated which is going to cause problems for WINS. :rolleyes:

Regards,
Wylbur

On Sat 26 Dec 2015 01:26:02 AM CST, wylbur wrote:

I have run this install three times. I can’t find an option to set the
name of the system being built/installed. :open_mouth:

Since I am building it to be my own file server (SAMBA, NFS, etc.) and
do LDAP (I’d like to get PDC to work, eventually), I would like to name
it at install time.

Ok, since I can’t do that, then all the examples for how to do this with
yast tell one to go to Network Services and to “DHCP and Hostname”. :?

This system is not the DHCP controller. That system is up and running a
completely different distro of Linux and works just fine.

So, how does one report this “bug” in LEAP 42? I have a “Novell” account
and can’t find where, there, either. And if I click on the “support”
area at the top of this window, I get a 404. :beat-up:

Yes, I can issue hostname xxxxx and it changes it for the duration of
the boot. But reboot and I’m back to the goofy name the install
generated which is going to cause problems for WINS. :rolleyes:

Regards,
Wylbur

Hi
During the install and post install in the YaST Nework settings you can
set the hostname and domain via the hostname/dns tab for Network
Settings (I’m guessing your using wicked since a static ip). Don’t
forget to set dns servers and default route.


Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 | GNOME 3.10.1 | 3.12.51-52.31-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

Method 1: In the network setup during install, click on the tab for “Hostname/DNS”

If you don’t see that screen, then you are using ethernet and the installer was able to configure the network without your help. If you unplug the ethernet cable before you start the install, then you will get the network setup screen. Plug the cable back in as soon as that screen comes up. Then configure your interface (probably for DHCP), and go to the Hostname/DNS tab.

Method 2: On the boot command line (kernel line) enter the option “hostname=hostname.domainname” without the quotes and with your chosen values for hostname and domainname.

Method 3: After boot. Use Yast –> System –> Network Settings
and go to the “Hostname/DNS” tab. Or put “hostname.domainname” into the file “/etc/hostname” and reboot or restart the network.

Perhaps the problem is the iso that I downloaded and burned on 24DEC15 (openSUSE-Leap-42.1-DVD-x86_64.iso]. It is the second one I had to burn because the first started acting weird after the first install attempt – It seems that if I asked for repositories to be downloaded during install, it would start having problems with signatures. And that is after having it run an install media validation test.

Name Setting Problem

Method 1 doesn’t work.

There was no option to configure during the install. I even backed up and looked to see if new things showed up. When the install config was displayed, I asked for details and went to the system and there was nothing there for me to modify having to do with network adapters.

Me thinks that the system is a bit too automated and abbreviated for rapid install.

Method 2 is rather undesirable. But I will use it if that is what it takes.

Method 3 doesn’t work.

Going into yast, trust me, there is no such tab with this install. Doesn’t exist because this system is not the DHCP server, so I don’t define that, and I don’t install that. I am running Linux off a 40GB SSD (ultimate target is a 14GB SSD). It is to be a minimal system other than having the WINS server, SAMBA, etc. with LDAP on this machine (and possibly PDC, if I can figure it all out across the M/S and Apple systems with the Linux systems I have).

Static IP

The idea that I am running a Static IP would require me to have set that in the network config. would it not? But I don’t get that option. Now if you are talking about my Gateway server having a Static Config, uh no, and here’s why: My gateway firewall is fed by two different ISPs, neither of which are using static IPs. One is a Cable modem and the other is Fiber connections.


The above makes me not the normal or typical user. In my day job I deal with SLES 11 Linux Guests on a z/Frame running z/VM. My job is to tune them for max efficiency (whatever that means). And we are getting in Red Hat for z for a few guests.

Also, I’ve been running SUSE Linux desktop systems since at least 10.1. My current operating towers are running 13.2 64 bit hosting Vbox and W7 while also doing 90% of the work in Linux (gotta pay that MS tax to be able to handle all the “State” stuff that requires Winderz since Adobed abandoned the Linux Reader).


Machine in Question

The IP address of this server will be the same because the mac address of this box is defined to my DHCP server and it gives it the same address from boot to boot. After all, this is going to be my file server. Plus, this box has two ethernet adapters, only one is connected, so surely (not Shirley) I should be asked to go through config of network adapters, Yes? But that did not happen.

So I’m perplexed, and googling all the various ways to set the hostname doesn’t seem to work with this hyhrid – The SLED 12 method I couldn’t find. The SUSE 13.2 method isn’t available.

And I can’t logon as root and use an editor (e.g. Kate) to fix files because root isn’t an option for logon, even after I defined a new ID that is a member of root!! It is not offered for logon.

Hi
Sounds like a suspect download of the DVD, the option to set all that up is there… I have SLE installs here that I use to set the hostname so that the name/domain registered at SCC.

If your wanting a custom build, have you heard of SUSE Studio You can use the same username/password from here)? You will be able to build/test to your hearts content and check out the gallery others may already have what your after?
https://susestudio.com/

I’m confused you telling us that there is no Yast-netwrok settings??? how are you connecting to the internet? that is where you can set and adjust things for your network device. That is also where you can change the machine name. It has nothing directly to do with the system being a DHCP node or not. Just change the name forget DHCP if it does not apply in the host name/DNS tab

for 3 you probably need to reboot or at the least restart networking

I agree, it looks like a suspect DVD iso. I also have SLED and SLES installs that I have done – my day job involves running SUSE for z on IBM Mainframes under zVM.

SLED 12 that I got about a year ago, I could not get to install correctly and dropped it. I just didn’t have time to spend with Novell trying to fix it.

As for custom builds, I have a Studio account. But a LEAP 42.1 install is what I want for the File Server. Studio is what I use to work on Gateway builds (small, firewall components, DHCP, DNS, etc.).

Let me help you with your confusion. The install looked at the ethernet adapters, detected that the one was connected, did a DHCP query, and moved on.

After the boot, I got into yast and selected the server apps I wanted and this is what yast shows for in its network services tab: authentication client, authentication server, Host names, mail server, NFS client, NFS Server, NTP Config, Network Services (xinetd), open LDAP mirrormode, PROXY, remote Administration (VNC), SLP Server, Samba Server, Windows Domain Membership, and last but not least, iSCSI Initiator.

Nothing to be confused about. The noobie, per number of posts, actually knows what he’s talking about.

Something is not correct.

How does one open a problem/bug against the install?

Things have changes since I worked with SUSE 13.2 and reported bugs from there. My 13.2 installations today are pretty solid.

So with this Hybrid situation, how do bugs get reported?

Regards,
Wylbur

Hi
You need to be looking under YaST->System->Network Settings, not YaST->Network Services.

If you think it’s a bug;
https://en.opensuse.org/openSUSE:Submitting_bug_reports

Well, I was working away preparing for a reboot, when I noticed in yast that under “System” there is “Network Settings”. So I went in and fixed it there. I had already edited /etc/HOSTNAME.

nrickert: Sorry, I had been reading another post and then read yours, and so for whatever reason I read it as “Network Services”. Yes, it was there, large as life under “SYSTEM”.:embarrassed:

Well, I have just rebooted, and it took. So this part is solved.

But why am I not given that option during the build? That is still my question, and I think it is a bug that one is not given that option.

Regards,
Wylbur

Hi
As previously indicated, leave the ethernet cable disconnected and the Network Settings should pop up, else on the final page prior to pressing the install button there is a summary when it can all be configured? For openSUSE I always configure post install, in your case leave the cable out…