Date: Fri, 9 Jul 2010 11:48:05 +0200 From: Karsten Behrmann <BearPerson@gmx.net> To: freebsd-sysinstall@freebsd.org Subject: Re: silly, silly sysinstall Message-ID: <756E9A5F-D580-42DE-A088-9F6FBACB5249@gmx.net> In-Reply-To: <1278649973.3102.14.camel@localhost.localdomain> References: <1278649973.3102.14.camel@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
Heya, Let's see if we can get a proper bug report from this, shall we? > I then did something non-standard and partitioned my USB stick and put > the i386 and x86_64 images on the same disk. Much hilarity ensued. > -- partition 1 houses grub and friends > -- partition 2 has i386-current install > -- parition 3 has x86_64 install All three UFS, or something different entirely? > 1. Sysinstall assumes that the files to be installed are on > slice/partition 1. In this odd ball case, they were not. I think that > sysinstall *could* be made a little smarter, but I am wrong so often > that its becoming a pattern. Wait, so you're talking about the actual distribution packages? Asin, the thing boots correctly, seems to use the proper-OS image as root (otherwise it'd have a hard time finding sysinstall at all), yet sysinstall mounts slice 1 and is confused that it cannot find packages to unpack to the destination? If one configured "installation source" to FTP, so it does not need any packages from disk at all, would that still work? > 2. *IF* the network configuration fails due to link down or broken > network driver, you never get another chance to DHCP an address. Minor > but made me want to go stabby. The network-setup code is tied in somewhat strangely sometimes. Also, in many places. Where exactly are you needing network, causing sysinstall to bring up a network-config dialog the first time, but never afterwards? ... actually, since you're installing from disk, why do you need networking during install at all? Or am I misunderstanding the issue? > 3. What the heck am I supposed to do in the "emergency holographic > shell" anyway? Can we get that thing removed or some kind of "howto" > with it? In my "special" case, I couldn't figure out how to get to the > fixit image because sysinstall wasn't aware that it's files were > actually on partition 2 or 3. It's a shell. Unfortunately, since the environment sysinstall runs in is extremely limited, so are the things you can do in it (no ifconfig, amongst others) Learn to do "echo *" instead of "ls" ;-) I'm still a little confused about the "files on partition 2 or 3" though. Sysinstall isn't spending its time parsing partition tables and reading from raw disk, it uses the filesystem like everyone else. At some point stuff gets mounted, then it gets used. The correct partition must already have gotten mounted, otherwise the kernel would never have a chance to execute the sysinstall binary, no? What is the error message you get that seems to indicate it is "not finding the partition"? > Want me to poke about in sysinstall, is this an easy fix and I shouldn't > bother or should I go away with my madness and never return? :-) It might be an easy fix if we could get a proper bug description. It might be not, I don't know yet. If you want, you're of course free to look at the code, although at this stage I can make no guarantees about your sanity when you do that :P But first, we should turn your email from "here's some gripes, y'all" into "there seem to be some bugs, here is what I did, what I expected, what I saw instead, and what I assume the problem is." Things get always a little problematic if people only provide you with what they feel the problem is, but not with what they saw to lead them to that assumption. So Far, Karsten
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?756E9A5F-D580-42DE-A088-9F6FBACB5249>