Difference between revisions of "Talk:Install from existing Linux"

From ArchWiki
Jump to: navigation, search
(pacman.static, reorganized)
m (deleted uneeded question)
(16 intermediate revisions by 8 users not shown)
Line 1: Line 1:
=== pacman.static ===
+
== Questions ==
 +
1. Is "--no-check-certificate" needed for wget?
  
It's unclear whether pacman-static is still available anywhere but [http://aur.archlinux.org/packages.php?ID=19287 AUR]. See http://bbs.archlinux.org/viewtopic.php?id=59152 and http://bbs.archlinux.org/viewtopic.php?pid=727877 and http://bbs.archlinux.org/viewtopic.php?id=90685 and
+
2. Article says: "If you do not mind littering your install host, you can extract all the downloaded tar balls into your root directory by running as root: ... However, keep in mind that this operation could erase some of your files, and break your system."
  
pacman-static (3.2.2) isn't providing the xz archive format introduced with pacman 3.3.0...
+
Why is this suggested? Wouldn't it be better and safer to put the files elsewhere and just add to $PATH again like it did in the previous section?
  
 +
3. After "Finishing touches", it says: "See Beginners Guide:Configure the system. You can ignore 2.11, ..."
  
=== install with installer ===
+
However, there is no 2.11... I'm guessing it meant ignore "Install bootloader"?
  
Uhm. Afaik you can just install aif or archlinux-installer (deprecated) onto an existing arch system and just run it.
+
[[User:Zeniff|Zeniff]] ([[User talk:Zeniff|talk]]) 19:20, 19 July 2012 (UTC)
[[User:Dieter_be|Dieter_be]]
+
  
=== Prepare System ===
+
== Problems with the "Alternate, Simpler" method ==
  
I had to recreate the device nodes, because they were not setup as displayed in the article. Could someone add a sentence on why those nodes might be created the wrong way? Without this explanation, this section leaves a somewhat irritating impression. [[User:Aku|Aku]]
+
Users should be aware that the script seems to require a full-blown bash shell.  Neither Debian nor Ubuntu rescue environments were able to run it as they both use stripped down shells. Also, neither rescue environment has xz installed so even trying to brute force it as I did, won't work.
  
=== /dev, uname and /sys missing at step "Install Base System" ===
+
The last paragraph was a real killer.  "You will still need to do any final configuration touches as you would in a normal Arch install" should link to something or else the section should begin with a disclaimer not to try this unless you already know how to do a "normal Arch install."
  
During the "Install Base System" step, a lot of packages failed while doing "pacman -S ... base" with errors like this:
+
* You tried to brute force it? ...trying to brute force xz uncompression, ''without having xz''... does not make a lot of sense ^_^ (''sudo'' all you want, that is not gonna make xz appear, :P) I don't think is necessary to explain that is a requirement to know how to do a normal arch install; installing from another distro is an '''expert installation method''', one that is a bit harder to do than the vanilla, official way. Users should not be trying to do such thing if they can't even do a vanilla install. Anyway, I'm preparing a tutorial for a different way, one that is similar to the alternate way, and that can be used instead of that one (using the minimalist and simple style of the wiki)... and yeah, I'm going to mention the official install guide.
 
+
[[User:Chrisl|Chrisl]] ([[User talk:Chrisl|talk]]) 05:52, 6 November 2012 (UTC)
(  3/104) Aktualisiere glibc                        [#########################] 100%
+
ldconfig: Can't open configuration file /etc/ld.so.conf: No such file or directory
+
/tmp/alpm_bOqjX0/.INSTALL: line 45: init: command not found
+
usr/sbin/locale-gen: line 16: rm: command not found
+
Generating locales...
+
Generation complete.
+
+
/tmp/alpm_hcjko9/.INSTALL: line 7: /dev/null: No such file or directory
+
 
+
I then re-did that step, but this time, I bind-mounted /dev, /sys & /proc from the host to the chroot which is going to be the new arch installation (ie. /newarch). And I did NOT do "pacman -S ... pacman", but instead just installed base, as base also contains pacman. However, BEFORE doing the "mount -o bind /dev /newarch/dev", it's important to create those 3 device files in /dev!
+
 
+
Result → No such error messages.
+
 
+
--[[User:MSchmarck|MSchmarck]] 08:30, 21 April 2009 (EDT)
+

Revision as of 11:10, 3 December 2012

Questions

1. Is "--no-check-certificate" needed for wget?

2. Article says: "If you do not mind littering your install host, you can extract all the downloaded tar balls into your root directory by running as root: ... However, keep in mind that this operation could erase some of your files, and break your system."

Why is this suggested? Wouldn't it be better and safer to put the files elsewhere and just add to $PATH again like it did in the previous section?

3. After "Finishing touches", it says: "See Beginners Guide:Configure the system. You can ignore 2.11, ..."

However, there is no 2.11... I'm guessing it meant ignore "Install bootloader"?

Zeniff (talk) 19:20, 19 July 2012 (UTC)

Problems with the "Alternate, Simpler" method

Users should be aware that the script seems to require a full-blown bash shell. Neither Debian nor Ubuntu rescue environments were able to run it as they both use stripped down shells. Also, neither rescue environment has xz installed so even trying to brute force it as I did, won't work.

The last paragraph was a real killer. "You will still need to do any final configuration touches as you would in a normal Arch install" should link to something or else the section should begin with a disclaimer not to try this unless you already know how to do a "normal Arch install."

  • You tried to brute force it? ...trying to brute force xz uncompression, without having xz... does not make a lot of sense ^_^ (sudo all you want, that is not gonna make xz appear, :P) I don't think is necessary to explain that is a requirement to know how to do a normal arch install; installing from another distro is an expert installation method, one that is a bit harder to do than the vanilla, official way. Users should not be trying to do such thing if they can't even do a vanilla install. Anyway, I'm preparing a tutorial for a different way, one that is similar to the alternate way, and that can be used instead of that one (using the minimalist and simple style of the wiki)... and yeah, I'm going to mention the official install guide.

Chrisl (talk) 05:52, 6 November 2012 (UTC)