Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add/remove some components to be compliant with the latest arch-iso image #6

Open
mountaround opened this issue Aug 4, 2020 · 1 comment

Comments

@mountaround
Copy link
Contributor

mountaround commented Aug 4, 2020

@jorgeluiscarrillo

Since I think your script is very good, I have given some thought to improve it a bit and to be compliant with the latest arch-live-iso.

  • Remove the check for an existing internet connection
    -> If the user follows your instructions, then they will already download because of the pacman -Sy git dialog command and this means that a connection to the Internet has already been established successfully.

  • Remove the (optional) check of mirror servers for speed
    -> the latest arch-live-iso already executes this as soon as there is an internet connection and sorts the servers according to speed.

  • Add intel-ucode/amd-ucode depending on CPU / matching CPU
    -> to make CPU attacks more difficult and to use the latest microcode in general.

  • Add an info at README.md that the xf86-video-intel driver is generally used for intel graphics
    -> Then the users know immediately and do not have to check whether the xf86-video-intel or mod-set will be used.

  • Consider leaving out linux-firmware if the user installs in a VM
    -> The arch-wiki describes that this can then be omitted (when using VM or container).

@jorgeluiscarrillo
Copy link
Owner

I will keep this open for now. It is important that we stay up to date with the latest arch iso. It is difficult to keep track since a new ISO is released each month and they are constantly changing things (sometimes even breaking my script). Thanks for bringing attention to these issues and I will consider these changes

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

No branches or pull requests

2 participants