Hello, I notice a bug in new amd64 minimal cd 20120917.iso 30-Sep-2012 04:14 version. I tried upto for mirrors, to check where the bugs came from but they all still remain the same. The last version before this date above I used at the middle of September last month boots well with no error, but I lost the cd and download after formatting my pc. Please, How do I get links to previous September versions? I do hope to hear from you soon. Thank you.
You didn't explain what was the error, but I just tried the CD and see it doesn't boot. The stage building for amd64 has been failing since Jun 16th, so there was no September CD. I believe the only public CDs built per release specs are the ones I built on my box[1]. The latest one was built on September 3rd[2]. [1] - http://www.jmbsvicetto.name/releases/amd64/default/ [2] - http://www.jmbsvicetto.name/releases/amd64/default/20120903/install-amd64-minimal-20120903.iso I just verified that my last build CD[2] boots, so I need to check what is breaking.
Yes, it does boot but when I tried 20120621.iso cd after selecting keymap e.g(uk) the last loading that will get to run [#] at the right side you see [ok] always appear in green color no error. While in this new 20120917.iso cd you see multiple errors with [!!] and you can not even press the power button to shutdown the installation as I always do on 20120621.iso cd. I trying to dual boot Windows 7/ Gentoo in Dell Inspiron 14z N411z laptop for over two weeks still no success yet. That is how I notice this bug. I'll welcome you help on the installation process. Thank you.
On install-amd64-minimal-20120917.iso (the only amd64 installcd iso on the public mirrors newer than June), /var/run is a symlink to a non-existent /run. If you "mkdir /run" then most services will start up ok. You can "init 1" then "init 3" and all services seem to come up ok, now that /run exists. ---------- livecd ~ # ls -l /var/run /run ls: cannot access /run: No such file or directory lrwxrwxrwx 1 root root 4 Oct 3 21:18 /var/run -> /run livecd ~ # --------- (hand-typed so forgive any minor typos)
*** Bug 437138 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 421839 ***
