<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>info0940 Archives - Tom Barbette</title>
	<atom:link href="https://perso.uclouvain.be/tom.barbette/tag/info0940/feed/" rel="self" type="application/rss+xml" />
	<link>https://perso.uclouvain.be/tom.barbette/tag/info0940/</link>
	<description></description>
	<lastBuildDate>Thu, 05 Feb 2015 09:59:13 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2022/04/cropped-logo-uclouvain-2021-barbette-32x32.png</url>
	<title>info0940 Archives - Tom Barbette</title>
	<link>https://perso.uclouvain.be/tom.barbette/tag/info0940/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Manual network configuration under ubuntu</title>
		<link>https://perso.uclouvain.be/tom.barbette/manual-network-configuration-under-ubuntu/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Fri, 14 Feb 2014 13:15:47 +0000</pubDate>
				<category><![CDATA[INFO-0940 Operating Systems]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[dhclient]]></category>
		<category><![CDATA[ifconfig]]></category>
		<category><![CDATA[ifup]]></category>
		<category><![CDATA[info0940]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[network problem]]></category>
		<category><![CDATA[problem]]></category>
		<guid isPermaLink="false">http://queen.run.montefiore.ulg.ac.be/~barbette/?p=212</guid>

					<description><![CDATA[<p>This procedure is only with cable, not for wifi First check that your interface is up with the command &#8220;sudo ifconfig&#8221; : If like in this screenshot you do not see an interface named &#8220;ethXXX&#8220;, you have to start the interface manually. &#160; To found which of eth0, eth1, &#8230; your network card is, you &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/manual-network-configuration-under-ubuntu/" class="more-link">Continue reading<span class="screen-reader-text"> "Manual network configuration under ubuntu"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/manual-network-configuration-under-ubuntu/">Manual network configuration under ubuntu</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><em>This procedure is only with cable, not for wifi</em></p>
<p>First check that your interface is up with the command &#8220;<em>sudo ifconfig</em>&#8221; :</p>
<p><a href="https://www.tombarbette.be/wp-content/uploads/2014/02/lo.png"><img decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2014/02/lo-300x93.png" alt="lo" width="300" height="93" class="alignnone size-medium wp-image-213" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/lo-300x93.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/lo.png 577w" sizes="(max-width: 300px) 100vw, 300px" /></a><br />
If like in this screenshot you do not see an interface named &#8220;<em>ethXXX</em>&#8220;, you have to start the interface manually.<br />
&nbsp;<br />
To found which of eth0, eth1, &#8230; your network card is, you can type &#8220;<em>dmesg | grep eth</em>&#8221;</p>
<p><a href="https://www.tombarbette.be/wp-content/uploads/2014/02/dmesg.png"><img decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2014/02/dmesg-300x80.png" alt="dmesg" width="300" height="80" class="alignnone size-medium wp-image-214" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/dmesg-300x80.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/dmesg.png 718w" sizes="(max-width: 300px) 100vw, 300px" /></a><br />
We see here that the card &#8220;Intel Pro/1000&#8221; takes the &#8220;eth0&#8221; interface name. But it&#8217;s later renamed to &#8220;<em>eth1</em>&#8220;.<br />
&nbsp;<br />
So our interface here is eth1, to bring it up, simply run &#8220;sudo ifconfig eth1 up&#8221;.<br />
<a href="https://www.tombarbette.be/wp-content/uploads/2014/02/eth1up.png"><img decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2014/02/eth1up-300x148.png" alt="eth1up" width="300" height="148" class="alignnone size-medium wp-image-215" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/eth1up-300x148.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/eth1up.png 636w" sizes="(max-width: 300px) 100vw, 300px" /></a></p>
<p>You may not have an IP Adress automatically like in this screenshot. If it&#8217;s the case, simply type &#8220;<em>sudo dhclient eth1</em>&#8221; to get one with DHCP.<br />
&nbsp;<br />
If it doesn&#8217;t work, try to directly ping an IP address like google&#8217;s dns server <em>8.8.8.8</em> with the command &#8220;<em>ping 8.8.8.8</em>&#8220;. If it works, you probably have a nameserver problem. Simply add the line &#8220;<em>nameserver 8.8.8.8</em>&#8221; in /etc/resolv.conf</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/manual-network-configuration-under-ubuntu/">Manual network configuration under ubuntu</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Remove message &#8220;Waiting for network configuration&#8230;&#8221; on ubuntu</title>
		<link>https://perso.uclouvain.be/tom.barbette/remove-message-waiting-for-network-configuration-on-ubuntu/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Fri, 14 Feb 2014 12:41:09 +0000</pubDate>
				<category><![CDATA[INFO-0940 Operating Systems]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[info0940]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[problems]]></category>
		<guid isPermaLink="false">http://queen.run.montefiore.ulg.ac.be/~barbette/?p=210</guid>

					<description><![CDATA[<p>On ubuntu, if your system boots without network in failsafe mode, it will wait a long time for network to be available. In many case, this won&#8217;t help much&#8230; Moreover, if you&#8217;re trying to do things like kernel compiling and for some reason you can&#8217;t see the boot log (including this &#8220;Waiting for network configuration&#8221; &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/remove-message-waiting-for-network-configuration-on-ubuntu/" class="more-link">Continue reading<span class="screen-reader-text"> "Remove message &#8220;Waiting for network configuration&#8230;&#8221; on ubuntu"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/remove-message-waiting-for-network-configuration-on-ubuntu/">Remove message &#8220;Waiting for network configuration&#8230;&#8221; on ubuntu</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>On ubuntu, if your system boots without network in failsafe mode, it will wait a long time for network to be available. In many case, this won&#8217;t help much&#8230;</p>
<p>Moreover, if you&#8217;re trying to do things like kernel compiling and for some reason you can&#8217;t see the boot log (including this &#8220;Waiting for network configuration&#8221; message), you&#8217;ll have the impression of being stuck with a bad kernel, but in fact it is just waiting 120 seconds&#8230;</p>
<p>Just edit the file <em>sudo vi /etc/init/failsafe.conf</em> and remove all &#8220;sleep&#8221; instructions. The message will be displayed but it won&#8217;t wait any time.</p>
<p>To repair you network problems, you might want to check <a href="https://www.tombarbette.be/vm-and-kernel-compiling-troubleshooting/">this post</a> and <a href="https://www.tombarbette.be/manual-network-configuration-under-ubuntu/">this post</a>.</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/remove-message-waiting-for-network-configuration-on-ubuntu/">Remove message &#8220;Waiting for network configuration&#8230;&#8221; on ubuntu</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Ugly things : do not ask password for sudo</title>
		<link>https://perso.uclouvain.be/tom.barbette/ugly-things-do-not-ask-password-for-sudo/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Mon, 03 Feb 2014 10:53:37 +0000</pubDate>
				<category><![CDATA[INFO-0940 Operating Systems]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[info0940]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[root]]></category>
		<category><![CDATA[sudo]]></category>
		<category><![CDATA[ugly]]></category>
		<category><![CDATA[unix]]></category>
		<category><![CDATA[visudo]]></category>
		<guid isPermaLink="false">http://queen.run.montefiore.ulg.ac.be/~barbette/?p=155</guid>

					<description><![CDATA[<p>&#8211;> Ugly but okay in a development virtual machine Launch the command &#8220;sudo visudo&#8221; in a terminal. Add at the end : student ALL=(ALL) NOPASSWD: ALL And student will have no password prompt when using sudo</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/ugly-things-do-not-ask-password-for-sudo/">Ugly things : do not ask password for sudo</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>&#8211;> Ugly but okay in a development virtual machine</p>
<p>Launch the command &#8220;sudo visudo&#8221; in a terminal.</p>
<p>Add at the end :<br />
<code sh>student ALL=(ALL) NOPASSWD: ALL</code></p>
<p>And student will have no password prompt when using sudo</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/ugly-things-do-not-ask-password-for-sudo/">Ugly things : do not ask password for sudo</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Ugly things : Autologin of console at startup</title>
		<link>https://perso.uclouvain.be/tom.barbette/ugly-things-autologin-of-console-at-startup/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Mon, 03 Feb 2014 10:51:47 +0000</pubDate>
				<category><![CDATA[INFO-0940 Operating Systems]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[info0940]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[ugly]]></category>
		<category><![CDATA[unix]]></category>
		<guid isPermaLink="false">http://queen.run.montefiore.ulg.ac.be/~barbette/?p=153</guid>

					<description><![CDATA[<p>→ Ugly but okay in a development virtual machine… Add &#8220;– – autologin root&#8221; at the end of /etc/init/tty1.conf It will auto-log you as root for the first console. For the others, do the same with /etc/init/tty[1-5].conf You can autolog as “student” by replacing root by student. It’s a little safer … but still ugly.</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/ugly-things-autologin-of-console-at-startup/">Ugly things : Autologin of console at startup</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>→ Ugly but okay in a development virtual machine…</p>
<p>Add &#8220;– – autologin <strong>root</strong>&#8221; at the end of /etc/init/tty1.conf</p>
<p>It will auto-log you as root for the first console. For the others, do the same with /etc/init/tty[1-5].conf</p>
<p>You can autolog as “student” by replacing <strong>root</strong> by student. It’s a little safer … but still ugly.</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/ugly-things-autologin-of-console-at-startup/">Ugly things : Autologin of console at startup</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How to debug at boot time</title>
		<link>https://perso.uclouvain.be/tom.barbette/how-to-debug-at-boot-time/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Mon, 03 Feb 2014 10:50:10 +0000</pubDate>
				<category><![CDATA[INFO-0940 Operating Systems]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[boot]]></category>
		<category><![CDATA[debug]]></category>
		<category><![CDATA[info0940]]></category>
		<category><![CDATA[kernel]]></category>
		<category><![CDATA[os]]></category>
		<guid isPermaLink="false">http://queen.run.montefiore.ulg.ac.be/~barbette/?p=149</guid>

					<description><![CDATA[<p>If all you get is a black screen when booting, boot in recovery mode to see a little more information : When you are in the grub menu, choose the “recovery” version If there is none or if it’s still black type “e” in the grub menu over the kernel entry you want. Find the &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/how-to-debug-at-boot-time/" class="more-link">Continue reading<span class="screen-reader-text"> "How to debug at boot time"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/how-to-debug-at-boot-time/">How to debug at boot time</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If all you get is a black screen when booting, boot in recovery mode to see a little more information :</p>
<p><a href="https://www.tombarbette.be/wp-content/uploads/2014/02/recovery.png"><img loading="lazy" decoding="async" class="alignnone size-medium wp-image-150" alt="recovery" src="https://www.tombarbette.be/wp-content/uploads/2014/02/recovery-300x225.png" width="300" height="225" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/recovery-300x225.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/recovery-1024x771.png 1024w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/recovery-160x120.png 160w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/recovery.png 1077w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a></p>
<p>When you are in the grub menu, choose the “recovery” version</p>
<p>If there is none or if it’s still black type “e” in the grub menu over the kernel entry you want. Find the line starting by linux, and add “ro single recovery” at the end.<br />
Type F10 to boot.</p>
<p><a href="https://www.tombarbette.be/wp-content/uploads/2014/02/recovery2.png"><img loading="lazy" decoding="async" class="alignnone size-medium wp-image-151" alt="recovery2" src="https://www.tombarbette.be/wp-content/uploads/2014/02/recovery2-300x227.png" width="300" height="227" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/recovery2-300x227.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/recovery2-1024x776.png 1024w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/recovery2-160x120.png 160w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2014/02/recovery2.png 1078w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a></p>
<p>Grub normally have a “Previous versions” menu to allow you to boot with the ubuntu default kernel&#8230;</p>
<p>&nbsp;</p>
<p>In fact if you get a black screen when booting, chances is that you&#8217;re missing some modules. But you can get more:</p>
<ul>
<li>Add a serial device to your virtualbox, select &#8220;file&#8221; mode, with e.g. /tmp/vbox-jerry</li>
<li>run tail -f /tmp/vbox-jerry on your machine to watch that log file,</li>
<li>before booting, press e to edit the config and add at the tail of the command line &#8221; console=ttyS0,57600&#8243;</li>
<li>this will work only for boot time, when syslogd will start, the log will go to /var/log/syslog</li>
<li>You can use the /etc/default/grub file like for the screen size (see slides of info0940) to make it permanent</li>
</ul>
<p><strong><span style="color:red">A network problem during boot may stall you for 120 seconds, with or without a black screen ! So wait a little !</span></strong></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/how-to-debug-at-boot-time/">How to debug at boot time</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
