Kickstart netinstall ignores kickstart file hosted in LAN and proceeds with manual installation











up vote
0
down vote

favorite












Virtual machines are hypervised by vmware workstation.



I start my web server on vm1 - 192.168.0.31 running centos 7. I create and upload the kickstart file ks.cfg to 192.168.0.31/ks.cfg. You can look at the file below.



Every vm in my LAN can access the ks.cfg and read its content by going to 192.168.0.31/ks.cfg. I boot vm2 with netinstall iso of centos 7 and add ks=http://192.168.0.31/ks.cf to boot options and press enter. The only thing that comes to my mind is that somehow the mirror address in ks.cfg is not valid but i copied it from official centos site and tried multiple ones. I also tried mirrors found on the net, none of them solved the issue.



ks.cfg



#platform=x86, AMD64, or Intel EM64T
#version=DEVEL
# Install OS instead of upgrade
install
# Keyboard layouts
keyboard 'us'
# Use network installation
url --url="http://mirrors.mit.edu/centos/7/os/x86_64/"
# System language
lang en_US
# System authorization information
auth --useshadow --passalgo=sha512
# Use graphical install
graphical
# SELinux configuration
selinux --enforcing
# Do not configure the X Window System
skipx

# Firewall configuration
firewall --disabled
# Network information
network --bootproto=dhcp --device=eth0
# Halt after installation
halt
# System timezone
timezone Africa/Abidjan
# System bootloader configuration
bootloader --location=mbr
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all









share|improve this question
























  • are new VM actually on that network by default? e.g. can you get into the shell virtual terminal under the install and see what the network settings are, or logs of what the installer is doing?
    – thrig
    Nov 15 at 17:05










  • I restarted the machine and managed to go into the shell virtual terminal of the not yet installed system. I don't know how to go into shell virtual terminal during the manual GUI installation. It appears that there actually is no ipv4 address assigned to the only NIC this system has. I don't understand much since if it was able to fetch the ks.cfg file why wouldn't it be able to fetch something else. You can look at the ip a and ifconfig output here: i.imgur.com/0OJ6L8P.png. I also don't know how and which logs to check, there are so many different ones according to google.
    – PowerBoss Nautilus
    Nov 15 at 17:22












  • huh. that looks like the virt has no network. maybe try getting it a DHCP server (and NAT?) or otherwise on a bridged interface with all the other virts somehow? but that's more a vmware config question
    – thrig
    Nov 15 at 18:51










  • According to your comment, you have no network defined and therefore would have no access to any networks and not be able to load your ks.cfg kickstart file. You are required to define a network before the kickstart is able to be downloaded from the network (the kickstart can then define the same or a different network setup). The easiest method is to run DHCP to assign IP addresses automatically, but the kernel boot options allow you to define just about any kind of network.
    – GracefulRestart
    Nov 15 at 18:56










  • I might've just gotten some useful information! Based on the following I think that the kickstart file is bad: I made a typing error while giving path to kickstart file in boot options which resulted in this message during boot: i.imgur.com/vQTR7Ns.png. When I type the path correctly there is no error and a screen like this greets me: i.imgur.com/Hm8CZ2D.png. I compared it to screen that greets me during fully manual installation (notice it has 2 screens): i.imgur.com/xXgjrif.png and i.imgur.com/f5mEGSH.png. Can we confirm that the ks.cfg itself is wrong?
    – PowerBoss Nautilus
    Nov 16 at 20:03

















up vote
0
down vote

favorite












Virtual machines are hypervised by vmware workstation.



I start my web server on vm1 - 192.168.0.31 running centos 7. I create and upload the kickstart file ks.cfg to 192.168.0.31/ks.cfg. You can look at the file below.



Every vm in my LAN can access the ks.cfg and read its content by going to 192.168.0.31/ks.cfg. I boot vm2 with netinstall iso of centos 7 and add ks=http://192.168.0.31/ks.cf to boot options and press enter. The only thing that comes to my mind is that somehow the mirror address in ks.cfg is not valid but i copied it from official centos site and tried multiple ones. I also tried mirrors found on the net, none of them solved the issue.



ks.cfg



#platform=x86, AMD64, or Intel EM64T
#version=DEVEL
# Install OS instead of upgrade
install
# Keyboard layouts
keyboard 'us'
# Use network installation
url --url="http://mirrors.mit.edu/centos/7/os/x86_64/"
# System language
lang en_US
# System authorization information
auth --useshadow --passalgo=sha512
# Use graphical install
graphical
# SELinux configuration
selinux --enforcing
# Do not configure the X Window System
skipx

# Firewall configuration
firewall --disabled
# Network information
network --bootproto=dhcp --device=eth0
# Halt after installation
halt
# System timezone
timezone Africa/Abidjan
# System bootloader configuration
bootloader --location=mbr
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all









share|improve this question
























  • are new VM actually on that network by default? e.g. can you get into the shell virtual terminal under the install and see what the network settings are, or logs of what the installer is doing?
    – thrig
    Nov 15 at 17:05










  • I restarted the machine and managed to go into the shell virtual terminal of the not yet installed system. I don't know how to go into shell virtual terminal during the manual GUI installation. It appears that there actually is no ipv4 address assigned to the only NIC this system has. I don't understand much since if it was able to fetch the ks.cfg file why wouldn't it be able to fetch something else. You can look at the ip a and ifconfig output here: i.imgur.com/0OJ6L8P.png. I also don't know how and which logs to check, there are so many different ones according to google.
    – PowerBoss Nautilus
    Nov 15 at 17:22












  • huh. that looks like the virt has no network. maybe try getting it a DHCP server (and NAT?) or otherwise on a bridged interface with all the other virts somehow? but that's more a vmware config question
    – thrig
    Nov 15 at 18:51










  • According to your comment, you have no network defined and therefore would have no access to any networks and not be able to load your ks.cfg kickstart file. You are required to define a network before the kickstart is able to be downloaded from the network (the kickstart can then define the same or a different network setup). The easiest method is to run DHCP to assign IP addresses automatically, but the kernel boot options allow you to define just about any kind of network.
    – GracefulRestart
    Nov 15 at 18:56










  • I might've just gotten some useful information! Based on the following I think that the kickstart file is bad: I made a typing error while giving path to kickstart file in boot options which resulted in this message during boot: i.imgur.com/vQTR7Ns.png. When I type the path correctly there is no error and a screen like this greets me: i.imgur.com/Hm8CZ2D.png. I compared it to screen that greets me during fully manual installation (notice it has 2 screens): i.imgur.com/xXgjrif.png and i.imgur.com/f5mEGSH.png. Can we confirm that the ks.cfg itself is wrong?
    – PowerBoss Nautilus
    Nov 16 at 20:03















up vote
0
down vote

favorite









up vote
0
down vote

favorite











Virtual machines are hypervised by vmware workstation.



I start my web server on vm1 - 192.168.0.31 running centos 7. I create and upload the kickstart file ks.cfg to 192.168.0.31/ks.cfg. You can look at the file below.



Every vm in my LAN can access the ks.cfg and read its content by going to 192.168.0.31/ks.cfg. I boot vm2 with netinstall iso of centos 7 and add ks=http://192.168.0.31/ks.cf to boot options and press enter. The only thing that comes to my mind is that somehow the mirror address in ks.cfg is not valid but i copied it from official centos site and tried multiple ones. I also tried mirrors found on the net, none of them solved the issue.



ks.cfg



#platform=x86, AMD64, or Intel EM64T
#version=DEVEL
# Install OS instead of upgrade
install
# Keyboard layouts
keyboard 'us'
# Use network installation
url --url="http://mirrors.mit.edu/centos/7/os/x86_64/"
# System language
lang en_US
# System authorization information
auth --useshadow --passalgo=sha512
# Use graphical install
graphical
# SELinux configuration
selinux --enforcing
# Do not configure the X Window System
skipx

# Firewall configuration
firewall --disabled
# Network information
network --bootproto=dhcp --device=eth0
# Halt after installation
halt
# System timezone
timezone Africa/Abidjan
# System bootloader configuration
bootloader --location=mbr
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all









share|improve this question















Virtual machines are hypervised by vmware workstation.



I start my web server on vm1 - 192.168.0.31 running centos 7. I create and upload the kickstart file ks.cfg to 192.168.0.31/ks.cfg. You can look at the file below.



Every vm in my LAN can access the ks.cfg and read its content by going to 192.168.0.31/ks.cfg. I boot vm2 with netinstall iso of centos 7 and add ks=http://192.168.0.31/ks.cf to boot options and press enter. The only thing that comes to my mind is that somehow the mirror address in ks.cfg is not valid but i copied it from official centos site and tried multiple ones. I also tried mirrors found on the net, none of them solved the issue.



ks.cfg



#platform=x86, AMD64, or Intel EM64T
#version=DEVEL
# Install OS instead of upgrade
install
# Keyboard layouts
keyboard 'us'
# Use network installation
url --url="http://mirrors.mit.edu/centos/7/os/x86_64/"
# System language
lang en_US
# System authorization information
auth --useshadow --passalgo=sha512
# Use graphical install
graphical
# SELinux configuration
selinux --enforcing
# Do not configure the X Window System
skipx

# Firewall configuration
firewall --disabled
# Network information
network --bootproto=dhcp --device=eth0
# Halt after installation
halt
# System timezone
timezone Africa/Abidjan
# System bootloader configuration
bootloader --location=mbr
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all






centos system-installation kickstart






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 2 days ago









sourcejedi

21.9k43396




21.9k43396










asked Nov 15 at 16:47









PowerBoss Nautilus

214




214












  • are new VM actually on that network by default? e.g. can you get into the shell virtual terminal under the install and see what the network settings are, or logs of what the installer is doing?
    – thrig
    Nov 15 at 17:05










  • I restarted the machine and managed to go into the shell virtual terminal of the not yet installed system. I don't know how to go into shell virtual terminal during the manual GUI installation. It appears that there actually is no ipv4 address assigned to the only NIC this system has. I don't understand much since if it was able to fetch the ks.cfg file why wouldn't it be able to fetch something else. You can look at the ip a and ifconfig output here: i.imgur.com/0OJ6L8P.png. I also don't know how and which logs to check, there are so many different ones according to google.
    – PowerBoss Nautilus
    Nov 15 at 17:22












  • huh. that looks like the virt has no network. maybe try getting it a DHCP server (and NAT?) or otherwise on a bridged interface with all the other virts somehow? but that's more a vmware config question
    – thrig
    Nov 15 at 18:51










  • According to your comment, you have no network defined and therefore would have no access to any networks and not be able to load your ks.cfg kickstart file. You are required to define a network before the kickstart is able to be downloaded from the network (the kickstart can then define the same or a different network setup). The easiest method is to run DHCP to assign IP addresses automatically, but the kernel boot options allow you to define just about any kind of network.
    – GracefulRestart
    Nov 15 at 18:56










  • I might've just gotten some useful information! Based on the following I think that the kickstart file is bad: I made a typing error while giving path to kickstart file in boot options which resulted in this message during boot: i.imgur.com/vQTR7Ns.png. When I type the path correctly there is no error and a screen like this greets me: i.imgur.com/Hm8CZ2D.png. I compared it to screen that greets me during fully manual installation (notice it has 2 screens): i.imgur.com/xXgjrif.png and i.imgur.com/f5mEGSH.png. Can we confirm that the ks.cfg itself is wrong?
    – PowerBoss Nautilus
    Nov 16 at 20:03




















  • are new VM actually on that network by default? e.g. can you get into the shell virtual terminal under the install and see what the network settings are, or logs of what the installer is doing?
    – thrig
    Nov 15 at 17:05










  • I restarted the machine and managed to go into the shell virtual terminal of the not yet installed system. I don't know how to go into shell virtual terminal during the manual GUI installation. It appears that there actually is no ipv4 address assigned to the only NIC this system has. I don't understand much since if it was able to fetch the ks.cfg file why wouldn't it be able to fetch something else. You can look at the ip a and ifconfig output here: i.imgur.com/0OJ6L8P.png. I also don't know how and which logs to check, there are so many different ones according to google.
    – PowerBoss Nautilus
    Nov 15 at 17:22












  • huh. that looks like the virt has no network. maybe try getting it a DHCP server (and NAT?) or otherwise on a bridged interface with all the other virts somehow? but that's more a vmware config question
    – thrig
    Nov 15 at 18:51










  • According to your comment, you have no network defined and therefore would have no access to any networks and not be able to load your ks.cfg kickstart file. You are required to define a network before the kickstart is able to be downloaded from the network (the kickstart can then define the same or a different network setup). The easiest method is to run DHCP to assign IP addresses automatically, but the kernel boot options allow you to define just about any kind of network.
    – GracefulRestart
    Nov 15 at 18:56










  • I might've just gotten some useful information! Based on the following I think that the kickstart file is bad: I made a typing error while giving path to kickstart file in boot options which resulted in this message during boot: i.imgur.com/vQTR7Ns.png. When I type the path correctly there is no error and a screen like this greets me: i.imgur.com/Hm8CZ2D.png. I compared it to screen that greets me during fully manual installation (notice it has 2 screens): i.imgur.com/xXgjrif.png and i.imgur.com/f5mEGSH.png. Can we confirm that the ks.cfg itself is wrong?
    – PowerBoss Nautilus
    Nov 16 at 20:03


















are new VM actually on that network by default? e.g. can you get into the shell virtual terminal under the install and see what the network settings are, or logs of what the installer is doing?
– thrig
Nov 15 at 17:05




are new VM actually on that network by default? e.g. can you get into the shell virtual terminal under the install and see what the network settings are, or logs of what the installer is doing?
– thrig
Nov 15 at 17:05












I restarted the machine and managed to go into the shell virtual terminal of the not yet installed system. I don't know how to go into shell virtual terminal during the manual GUI installation. It appears that there actually is no ipv4 address assigned to the only NIC this system has. I don't understand much since if it was able to fetch the ks.cfg file why wouldn't it be able to fetch something else. You can look at the ip a and ifconfig output here: i.imgur.com/0OJ6L8P.png. I also don't know how and which logs to check, there are so many different ones according to google.
– PowerBoss Nautilus
Nov 15 at 17:22






I restarted the machine and managed to go into the shell virtual terminal of the not yet installed system. I don't know how to go into shell virtual terminal during the manual GUI installation. It appears that there actually is no ipv4 address assigned to the only NIC this system has. I don't understand much since if it was able to fetch the ks.cfg file why wouldn't it be able to fetch something else. You can look at the ip a and ifconfig output here: i.imgur.com/0OJ6L8P.png. I also don't know how and which logs to check, there are so many different ones according to google.
– PowerBoss Nautilus
Nov 15 at 17:22














huh. that looks like the virt has no network. maybe try getting it a DHCP server (and NAT?) or otherwise on a bridged interface with all the other virts somehow? but that's more a vmware config question
– thrig
Nov 15 at 18:51




huh. that looks like the virt has no network. maybe try getting it a DHCP server (and NAT?) or otherwise on a bridged interface with all the other virts somehow? but that's more a vmware config question
– thrig
Nov 15 at 18:51












According to your comment, you have no network defined and therefore would have no access to any networks and not be able to load your ks.cfg kickstart file. You are required to define a network before the kickstart is able to be downloaded from the network (the kickstart can then define the same or a different network setup). The easiest method is to run DHCP to assign IP addresses automatically, but the kernel boot options allow you to define just about any kind of network.
– GracefulRestart
Nov 15 at 18:56




According to your comment, you have no network defined and therefore would have no access to any networks and not be able to load your ks.cfg kickstart file. You are required to define a network before the kickstart is able to be downloaded from the network (the kickstart can then define the same or a different network setup). The easiest method is to run DHCP to assign IP addresses automatically, but the kernel boot options allow you to define just about any kind of network.
– GracefulRestart
Nov 15 at 18:56












I might've just gotten some useful information! Based on the following I think that the kickstart file is bad: I made a typing error while giving path to kickstart file in boot options which resulted in this message during boot: i.imgur.com/vQTR7Ns.png. When I type the path correctly there is no error and a screen like this greets me: i.imgur.com/Hm8CZ2D.png. I compared it to screen that greets me during fully manual installation (notice it has 2 screens): i.imgur.com/xXgjrif.png and i.imgur.com/f5mEGSH.png. Can we confirm that the ks.cfg itself is wrong?
– PowerBoss Nautilus
Nov 16 at 20:03






I might've just gotten some useful information! Based on the following I think that the kickstart file is bad: I made a typing error while giving path to kickstart file in boot options which resulted in this message during boot: i.imgur.com/vQTR7Ns.png. When I type the path correctly there is no error and a screen like this greets me: i.imgur.com/Hm8CZ2D.png. I compared it to screen that greets me during fully manual installation (notice it has 2 screens): i.imgur.com/xXgjrif.png and i.imgur.com/f5mEGSH.png. Can we confirm that the ks.cfg itself is wrong?
– PowerBoss Nautilus
Nov 16 at 20:03












1 Answer
1






active

oldest

votes

















up vote
2
down vote



accepted










The fault was kickstart file not including all necessary information for the automated installation to take place. The network is working fine. If the ks.cfg fails to get fetched the following message would appear:enter image description here
If the ks.cfg gets fetched successfully but the contents are insufficient the following could greet us: enter image description here



To fix No disks selected define partitioning manually in GUI. Or use automatic partitioning (impossible in GUI, leaving everything blank won't result in automatic partitioning) - ks.cfg needs to be edited, just add autopart --type=lvm to the # System bootloader configuration section of the file. To fix Nothing selected in SOFTWARE SELECTION I just added the following:



%packages
%end


at the end of the file.



TL;DR:



After creating kickcstart file in GUI there will be need to supplement it with:



%packages
%end


If auto partitioning is wanted it can be done by supplementing the file with: autopart --type=lvm in # System bootloader configuration section.
My mistake in that particular situation was leaving all partitioning options blank in GUI thinking it will result in automatic partitioning.






share|improve this answer










New contributor




PowerBoss Nautilus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.


















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














     

    draft saved


    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481990%2fkickstart-netinstall-ignores-kickstart-file-hosted-in-lan-and-proceeds-with-manu%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote



    accepted










    The fault was kickstart file not including all necessary information for the automated installation to take place. The network is working fine. If the ks.cfg fails to get fetched the following message would appear:enter image description here
    If the ks.cfg gets fetched successfully but the contents are insufficient the following could greet us: enter image description here



    To fix No disks selected define partitioning manually in GUI. Or use automatic partitioning (impossible in GUI, leaving everything blank won't result in automatic partitioning) - ks.cfg needs to be edited, just add autopart --type=lvm to the # System bootloader configuration section of the file. To fix Nothing selected in SOFTWARE SELECTION I just added the following:



    %packages
    %end


    at the end of the file.



    TL;DR:



    After creating kickcstart file in GUI there will be need to supplement it with:



    %packages
    %end


    If auto partitioning is wanted it can be done by supplementing the file with: autopart --type=lvm in # System bootloader configuration section.
    My mistake in that particular situation was leaving all partitioning options blank in GUI thinking it will result in automatic partitioning.






    share|improve this answer










    New contributor




    PowerBoss Nautilus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






















      up vote
      2
      down vote



      accepted










      The fault was kickstart file not including all necessary information for the automated installation to take place. The network is working fine. If the ks.cfg fails to get fetched the following message would appear:enter image description here
      If the ks.cfg gets fetched successfully but the contents are insufficient the following could greet us: enter image description here



      To fix No disks selected define partitioning manually in GUI. Or use automatic partitioning (impossible in GUI, leaving everything blank won't result in automatic partitioning) - ks.cfg needs to be edited, just add autopart --type=lvm to the # System bootloader configuration section of the file. To fix Nothing selected in SOFTWARE SELECTION I just added the following:



      %packages
      %end


      at the end of the file.



      TL;DR:



      After creating kickcstart file in GUI there will be need to supplement it with:



      %packages
      %end


      If auto partitioning is wanted it can be done by supplementing the file with: autopart --type=lvm in # System bootloader configuration section.
      My mistake in that particular situation was leaving all partitioning options blank in GUI thinking it will result in automatic partitioning.






      share|improve this answer










      New contributor




      PowerBoss Nautilus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















        up vote
        2
        down vote



        accepted







        up vote
        2
        down vote



        accepted






        The fault was kickstart file not including all necessary information for the automated installation to take place. The network is working fine. If the ks.cfg fails to get fetched the following message would appear:enter image description here
        If the ks.cfg gets fetched successfully but the contents are insufficient the following could greet us: enter image description here



        To fix No disks selected define partitioning manually in GUI. Or use automatic partitioning (impossible in GUI, leaving everything blank won't result in automatic partitioning) - ks.cfg needs to be edited, just add autopart --type=lvm to the # System bootloader configuration section of the file. To fix Nothing selected in SOFTWARE SELECTION I just added the following:



        %packages
        %end


        at the end of the file.



        TL;DR:



        After creating kickcstart file in GUI there will be need to supplement it with:



        %packages
        %end


        If auto partitioning is wanted it can be done by supplementing the file with: autopart --type=lvm in # System bootloader configuration section.
        My mistake in that particular situation was leaving all partitioning options blank in GUI thinking it will result in automatic partitioning.






        share|improve this answer










        New contributor




        PowerBoss Nautilus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        The fault was kickstart file not including all necessary information for the automated installation to take place. The network is working fine. If the ks.cfg fails to get fetched the following message would appear:enter image description here
        If the ks.cfg gets fetched successfully but the contents are insufficient the following could greet us: enter image description here



        To fix No disks selected define partitioning manually in GUI. Or use automatic partitioning (impossible in GUI, leaving everything blank won't result in automatic partitioning) - ks.cfg needs to be edited, just add autopart --type=lvm to the # System bootloader configuration section of the file. To fix Nothing selected in SOFTWARE SELECTION I just added the following:



        %packages
        %end


        at the end of the file.



        TL;DR:



        After creating kickcstart file in GUI there will be need to supplement it with:



        %packages
        %end


        If auto partitioning is wanted it can be done by supplementing the file with: autopart --type=lvm in # System bootloader configuration section.
        My mistake in that particular situation was leaving all partitioning options blank in GUI thinking it will result in automatic partitioning.







        share|improve this answer










        New contributor




        PowerBoss Nautilus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer








        edited 13 hours ago









        sourcejedi

        21.9k43396




        21.9k43396






        New contributor




        PowerBoss Nautilus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 15 hours ago









        PowerBoss Nautilus

        214




        214




        New contributor




        PowerBoss Nautilus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        PowerBoss Nautilus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        PowerBoss Nautilus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






























             

            draft saved


            draft discarded



















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481990%2fkickstart-netinstall-ignores-kickstart-file-hosted-in-lan-and-proceeds-with-manu%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Accessing regular linux commands in Huawei's Dopra Linux

            Can't connect RFCOMM socket: Host is down

            Kernel panic - not syncing: Fatal Exception in Interrupt