<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: problem from resizing Ubuntu.vmx in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/problem-from-resizing-Ubuntu-vmx/m-p/153454#M1676</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks! Guys.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have to change onwership of /home/lucid/work from root to lucid by&lt;/P&gt;&lt;P&gt;sudo chown lucid:lucid /home/lucid/work&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then it ends up writtable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 13 Apr 2012 16:33:39 GMT</pubDate>
    <dc:creator>HuiShao</dc:creator>
    <dc:date>2012-04-13T16:33:39Z</dc:date>
    <item>
      <title>problem from resizing Ubuntu.vmx</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/problem-from-resizing-Ubuntu-vmx/m-p/153451#M1673</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Working under virtual machine shipped with QSB DVD, virtual hardisk file Ubuntu.vmx&amp;nbsp;quickly was ran out of disk space. Tried to resize the harddisk space by "virtual machin settings -&amp;gt; harddisk -&amp;gt; utilities -&amp;gt; expand" and got 20G more space in guest OS Ubuntu. However, after partition and formating it into ext4, it turns into READ ONLY after mount command.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I did is:&lt;/P&gt;&lt;P&gt;$sudo mount -t ext4 /dev/sda3 /home/lucid/work&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Plus if I go to modify /etc/mtab to add one more line similar to "/dev/sda1", it is gone after reboot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anybody help on that? I would be ideal if I can re-size root partition directly.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 00:29:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/problem-from-resizing-Ubuntu-vmx/m-p/153451#M1673</guid>
      <dc:creator>HuiShao</dc:creator>
      <dc:date>2012-04-13T00:29:00Z</dc:date>
    </item>
    <item>
      <title>Re: problem from resizing Ubuntu.vmx</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/problem-from-resizing-Ubuntu-vmx/m-p/153452#M1674</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have not tried this.&amp;nbsp; So you will understand these "offerings" are just brainstorming:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; 1) Although read/write is supposed to be the default, it seems possible you could add the &lt;EM&gt;&lt;STRONG&gt;-w&lt;/STRONG&gt;&lt;/EM&gt; option (or &lt;STRONG&gt;-o rw&lt;/STRONG&gt;).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; 2) Check the mode/owner of the directory /home/lucid/work and make sure that isn't set to preclude writing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hth,&lt;/P&gt;&lt;P&gt;pr&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 01:39:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/problem-from-resizing-Ubuntu-vmx/m-p/153452#M1674</guid>
      <dc:creator>PaulRobertson</dc:creator>
      <dc:date>2012-04-13T01:39:44Z</dc:date>
    </item>
    <item>
      <title>Re: problem from resizing Ubuntu.vmx</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/problem-from-resizing-Ubuntu-vmx/m-p/153453#M1675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may to to use option remount :&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;SPAN class="highlight"&gt;mount&lt;/SPAN&gt;&amp;nbsp;-o remount,rw /dev/sda1 /home/lucid/work&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 02:16:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/problem-from-resizing-Ubuntu-vmx/m-p/153453#M1675</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2012-04-13T02:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: problem from resizing Ubuntu.vmx</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/problem-from-resizing-Ubuntu-vmx/m-p/153454#M1676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks! Guys.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have to change onwership of /home/lucid/work from root to lucid by&lt;/P&gt;&lt;P&gt;sudo chown lucid:lucid /home/lucid/work&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then it ends up writtable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 16:33:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/problem-from-resizing-Ubuntu-vmx/m-p/153454#M1676</guid>
      <dc:creator>HuiShao</dc:creator>
      <dc:date>2012-04-13T16:33:39Z</dc:date>
    </item>
  </channel>
</rss>

