Skip to content

Conversation

ydirson
Copy link
Contributor

@ydirson ydirson commented Sep 24, 2025

Those instructions will be useful to refer users to from forum or support tickets.

Note you can specify an interface name such as `eth1` instead of `all`
if necessary, which can be useful when you need to setup a static IP
address.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be useful to also explain:

  1. When the SSH server becomes available
  2. How to connect (which user, which hostname/IP - that's obvious but it doesn't hurt being explicit, which password - same)


### Getting remote access to host during installation

While for simple problems access through the console as described
Copy link
Collaborator

@thomas-dkmt thomas-dkmt Sep 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The wording could be a bit more natural, something like that:

While the console access method described above may be sufficient for simple issues, collecting full logs (install logs, kernel logs, etc.) often requires copying large amounts of data, which is impractical without direct file access.

To enable SSH/SCP access during installation, you can use the Linux kernel command line to:

  1. Activate the network
  2. Enable the sshd service
  3. Set a root password of your choice

For the most common case (setting up the network via DHCP), add the following parameter to the Linux boot section:

network_device=all sshpassword=YOURCHOICE
```

You may select an alternative setup using `network_config` (which
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest this wording:

You can also use the network_config parameter (which defaults to dhcp) to define an alternative network setup. Here’s how it works:

  • Replace the capitalized values with your own settings. Square brackets ([]) indicate optional parameters.
    network_config=dhcp[:vlan=VLAN]
    network_config=static:ip=IP;netmask=NETMASK[;gateway=GW][;dns=DNS1[,DNS2]][;domain=DOMAIN][;vlan=VLAN]

network_config=static:ip=IP;netmask=NETMASK[;gateway=GW][;dns=DNS1[,DNS2]][;domain=DOMAIN][;vlan=VLAN]
```

Note you can specify an interface name such as `eth1` instead of `all`
Copy link
Collaborator

@thomas-dkmt thomas-dkmt Sep 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feel free to use Docusaurus' "Note" element:

:::note
You can specify an interface name such as `eth1` instead of `all` if necessary, which can be useful when you need to setup a static IP address.
:::

## Installation logs

The installer writes in `/var/log/installer/`.
On the installed system, the installer logs are kept in `/var/log/installer/`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
On the installed system, the installer logs are kept in `/var/log/installer/`.
On the installed system, installer logs are kept in `/var/log/installer/`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants