Re: [Cooker] Install description need to be update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nora Etukudo wrote: > Am 29. Oktober 2003 um 15:19:48 +0200 schrieb Buchan Milne: > > >>Or allow network installation to install files direcltly from other >>urpmi media (like PLF)? ;-) > > > Yes! Please. > I would like this. :-) > > But it should work with AutoInstall also. Of course, since you may want to be able to have some internal applications installed during installation (and some other features related to unattended package installation could still be nice). Regards, Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/n8xRrJK6UGDSBKcRApSoAJ0SLvUytfAsHE7bvDczCWIcfsAgSgCgkeKk Hr92UPXz+xjWWkGsg1ktefA= =hfUV -END PGP SIGNATURE-
Re: [Cooker] Install description need to be update
Am 29. Oktober 2003 um 15:19:48 +0200 schrieb Buchan Milne: > Or allow network installation to install files direcltly from other > urpmi media (like PLF)? ;-) Yes! Please. I would like this. :-) But it should work with AutoInstall also. Liebe Grüße, Nora. -- [EMAIL PROTECTED] IM-NETZ Neue Medien, Berlin http://www.im-netz.de/ WWW von Frauen für Frauen, Hamburghttp://www.w4w.net/ Lesbian Computer Networks, Helsinki http://www.sappho.net/
Re: [Cooker] Install description need to be update
Olivier Thauvin <[EMAIL PROTECTED]> writes: > Internet: Some tools to send and read mail (pine, mutt) [...] > > Isn't time to remove pine from example ??? Except you plan to take > pine from plf and put it back into main ;) just fixed in cvs thanks.
Re: [Cooker] Install description need to be update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Olivier Thauvin wrote: > During 9.2 install, in package section, language French: > (I translate from french to english) > Internet: Some tools to send and read mail (pine, mutt) [...] > > Isn't time to remove pine from example ??? Except you plan to take pine from > plf and put it back into main ;) Or allow network installation to install files direcltly from other urpmi media (like PLF)? ;-) - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/n75zrJK6UGDSBKcRAlnDAKDCx01YdrHBeLcJ32a0zEkFQo0w5ACgx+/G VfCZuBM4SUKCCwrkX1bjsTY= =ekFL -END PGP SIGNATURE-
[Cooker] RE: cooker install
Hi ALL: I have Mandrake 9.1 installed and I have set-up 2 sources one for cooker and one for contrib. I did urpmi.update -a and the urpmi --auto-select which proceeded to download a lot of files. It then said there were 2 deps. devel libnoatunarts > needed by kdemultimedia-devel and that xemacs and emacs had file conflicts. So I got rid of kdemultimedia-devel and xemacs. Then urpmi --auto-select gave me this: Installation failed: error while ordering dependencies I thought the deps would be figured out before the install went on? man_linux _ Signup for free MacPunk email! [EMAIL PROTECTED] http://www.macpunk.com
Re: [Cooker] Install error - turba-1.2-1mdk
Levi Ramsey <[EMAIL PROTECTED]> writes: > > # rpm -q --whatprovides 'perl(Getopt::Std)' > > no package provides perl(Getopt::Std) > > > > # locate Getopt > > /usr/share/man/man3pm/Getopt::Long.3pm.bz2 > > /usr/share/man/man3pm/Getopt::Std.3pm.bz2 > > /usr/share/pear/.registry/Console_Getopt.reg > > /usr/share/pear/Console/Getopt.php > > /usr/lib/perl5/5.8.0/Getopt > > /usr/lib/perl5/5.8.0/Getopt/Long > > /usr/lib/perl5/5.8.0/Getopt/Long.pm > > /usr/lib/perl5/5.8.0/Getopt/Std.pm > > > > Any ideas why this is happening? try "rpm -q perl", i believe you don't have the latest release. > > Another flaw in the autorequires/autoprovides... nope ;p
Re: [Cooker] Install error - turba-1.2-1mdk
On Wed Jul 02 16:08 -0400, magic wrote: > Pixel wrote: > > >> Installation failed: > >> perl(Getopt::Std) is needed by turba-1.2-1mdk > >> > >> > > > >% rpm -q --whatprovides 'perl(Getopt::Std)' > >perl-5.8.0-25mdk > > > > Yes, and it appears to be installed: > > # rpm -q --whatprovides 'perl(Getopt::Std)' > no package provides perl(Getopt::Std) > > # locate Getopt > /usr/share/man/man3pm/Getopt::Long.3pm.bz2 > /usr/share/man/man3pm/Getopt::Std.3pm.bz2 > /usr/share/pear/.registry/Console_Getopt.reg > /usr/share/pear/Console/Getopt.php > /usr/lib/perl5/5.8.0/Getopt > /usr/lib/perl5/5.8.0/Getopt/Long > /usr/lib/perl5/5.8.0/Getopt/Long.pm > /usr/lib/perl5/5.8.0/Getopt/Std.pm > > Any ideas why this is happening? Another flaw in the autorequires/autoprovides... Surprise, surprise, surprise. I've given up on tracking cooker until the perl auto(requires|provides) are fixed... -- Levi Ramsey [EMAIL PROTECTED] [EMAIL PROTECTED] Take due notice and govern yourselves accordingly. Linux 2.4.21-0.15mdk 17:22:00 up 2 days, 8:34, 11 users, load average: 0.33, 0.30, 0.22
Re: [Cooker] Install error - turba-1.2-1mdk
Pixel wrote: Installation failed: perl(Getopt::Std) is needed by turba-1.2-1mdk % rpm -q --whatprovides 'perl(Getopt::Std)' perl-5.8.0-25mdk Yes, and it appears to be installed: # rpm -q --whatprovides 'perl(Getopt::Std)' no package provides perl(Getopt::Std) # locate Getopt /usr/share/man/man3pm/Getopt::Long.3pm.bz2 /usr/share/man/man3pm/Getopt::Std.3pm.bz2 /usr/share/pear/.registry/Console_Getopt.reg /usr/share/pear/Console/Getopt.php /usr/lib/perl5/5.8.0/Getopt /usr/lib/perl5/5.8.0/Getopt/Long /usr/lib/perl5/5.8.0/Getopt/Long.pm /usr/lib/perl5/5.8.0/Getopt/Std.pm Any ideas why this is happening? Thanks, S
Re: [Cooker] Install error - turba-1.2-1mdk
magic <[EMAIL PROTECTED]> writes: >Installation failed: > perl(Getopt::Std) is needed by turba-1.2-1mdk % rpm -q --whatprovides 'perl(Getopt::Std)' perl-5.8.0-25mdk
Re: [Cooker] Install Experience
Pascal <[EMAIL PROTECTED]> writes: > 1. graphic install ou text install - If you first choose an installation > language in simple mode, then change your mind and use the advanced mode to > select several other languages, then ALL languages choosen in simple AND > advanced mode will be installed. Unfortunatly once you click on next you > cannot revert language changes without restarting the installaion process > from boot. in text install, i think it's broken, i talk about graphics install. normal and advanced mode are *different* things. the language selected in normal view is the default language, and the language used during install. in advanced view, it's additional languages which will be available after install, to switch to. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install Experience
@Mr. Williamson: I'll try what you've suggested, it seems to be a logical step, I'm hoping it works, thanks for the tip :) @Pixel: $ ls -la /etc/mandrake-release -rw-r--r--1 root root 45 Oct 8 12:47 /etc/mandrake-release Content: Mandrake Linux release 9.1 (Cooker) for i586 Could it be that setup doesn't realize that this is a diferent version, and thats why it doesnt offer to upgrade? Although, it still seems there is an upgrade problem with the installer, but hopefully Mr. Williamson's suggestion will allow us to upgrade while the installer bug is fixed. @All: Thanks for the replies and help :) On Thursday 27 March 2003 09:17 am, Adam Williamson wrote: > On Thu, 2003-03-27 at 14:01, Pascal Cavy wrote: > > > > can you tell us what criterias are used to check this on DrakX ? > > > > (is it the mandrake-release rpm ?) > > > > > > well, /etc/mandrake-release *file* > > > > so cooker beta testers can upgrade their machines by replacing this file > > with the one from 9.0 ? > > Here's what both you and Adam Caudill actually want to know: > > You don't need to run the CDs to update 9.1RC2 or a recentish Cooker to > 9.1. All you need to do is define urpmi sources for main and contrib > from a mirror's 9.1 directory, then run 'urpmi --auto-select -v' (as > root), and it'll update to 9.1. No need to use the installer.
Re: [Cooker] Install Experience
On Thu, 2003-03-27 at 14:01, Pascal Cavy wrote: > > > can you tell us what criterias are used to check this on DrakX ? > > > (is it the mandrake-release rpm ?) > > > > well, /etc/mandrake-release *file* > > so cooker beta testers can upgrade their machines by replacing this file with > the one from 9.0 ? Here's what both you and Adam Caudill actually want to know: You don't need to run the CDs to update 9.1RC2 or a recentish Cooker to 9.1. All you need to do is define urpmi sources for main and contrib from a mirror's 9.1 directory, then run 'urpmi --auto-select -v' (as root), and it'll update to 9.1. No need to use the installer. -- adamw
Re: [Cooker] Install Experience
Better yet, no option to upgrade a 9.1rc2 install anywhere so it seems. I checked both the graphical & text modes... Looks like no upgrade for me. Is this the same error, or just a Microsoft type way of annoying the beta testers who switch to soon? I do hope there is a way around this one... On Wednesday 26 March 2003 05:01 pm, Pascal wrote: > Le Mercredi 26 Mars 2003 21:54, Rocco Stanzione a écrit : > > I suppose it's too late to fix it now, but this seems the best place to > > bring it up. I thought to upgrade my 9.0 installation to 9.1. I assume > > that I was asked at some point whether I wanted to do a fresh install or > > an upgrade, but if so it was sufficiently quiet that I missed it. I got > > a screen asking whether I wanted automatic partitioning, custom > > partitioning, or to keep my existing partitions. Thinking that keeping > > my existing partitions would be the only option compatible with an > > upgrade, I chose that. And without further adieu or even so much as a > > "by your leave", it formatted my lone partition. No confirmation dialog, > > no nothing. Having run cooker on my main machine for some time, I had > > high hopes for this release and expected better. Formatting partitions > > during install should be taken a little less lightly, I think. > > > > Rocco > > I can second this. > > Today I upgraded 2 machines from 8.0 and 8.2 with 9.1 cdroms. I noticed 3 > problems : > > > 3. I had the problem noticed by Rocco above. In graphic mode, I was not > asked for an upgrade and went to the disk partition menu. As this seems > suspect to me, I rebooted in text install mode. There I was asked to > upgrade my installation. A silly bug here... > Hope it will not break too many installations ! > An errata could be posted asap, as soon as others confirm this behaviour...
Re: [Cooker] Install Experience
Le Mercredi 26 Mars 2003 21:54, Rocco Stanzione a écrit : > I suppose it's too late to fix it now, but this seems the best place to > bring it up. I thought to upgrade my 9.0 installation to 9.1. I assume > that I was asked at some point whether I wanted to do a fresh install or an > upgrade, but if so it was sufficiently quiet that I missed it. I got a > screen asking whether I wanted automatic partitioning, custom partitioning, > or to keep my existing partitions. Thinking that keeping my existing > partitions would be the only option compatible with an upgrade, I chose > that. And without further adieu or even so much as a "by your leave", it > formatted my lone partition. No confirmation dialog, no nothing. Having > run cooker on my main machine for some time, I had high hopes for this > release and expected better. Formatting partitions during install should be > taken a little less lightly, I think. > > Rocco I can second this. Today I upgraded 2 machines from 8.0 and 8.2 with 9.1 cdroms. I noticed 3 problems : 1. graphic install ou text install - If you first choose an installation language in simple mode, then change your mind and use the advanced mode to select several other languages, then ALL languages choosen in simple AND advanced mode will be installed. Unfortunatly once you click on next you cannot revert language changes without restarting the installaion process from boot. 2. In some low res graphic modes (vga16 for ex) there is no progression indication on screen of what's going on between the end of cdrom boot and the second stage install. One can think the process is frozen. If graphics cannot be used there, an ascii progression could have ben provided. 3. I had the problem noticed by Rocco above. In graphic mode, I was not asked for an upgrade and went to the disk partition menu. As this seems suspect to me, I rebooted in text install mode. There I was asked to upgrade my installation. A silly bug here... Hope it will not break too many installations ! An errata could be posted asap, as soon as others confirm this behaviour... -- Pascal __ Running 2:35, 4 users, load average: 0.45, 0.60, 0.43 (gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)) Kernel Linux version 2.4.21-0.13mdkenterprise pgp0.pgp Description: signature
Re: [Cooker] install feature request
Pixel wrote: "J. Greenlees" <[EMAIL PROTECTED]> writes: Pixel wrote: "J. Greenlees" <[EMAIL PROTECTED]> writes: nothing really big, just when configuring the mouse during installation, add the option to map it for left handed use, then set the system to map left handed throughout by default. it actually slows me down drastically using a mouse mapped right handed. and every install is a pain because the buttons aren't mapped left handed. uh... maybe we can have a theme that would cause left and right button to do the same? Pixel, it's a request, not a scream of something being broken. ~grin~ not a rush to have for 9.1 but for concideration for future releases. ( 9.2 maybe ) at this point, adding a new feature is not something to work on, making sure the beta series gets the bugs worked out is much more important. ok. But i think it should not be too hard since right button is not used during install. Making it do the same as left button would fix it, uh? PS: i'm left handed... but i don't switch buttons :) yeah it would work for the install. and would be simple to add the right button to the installer since it's not used at all.
Re: [Cooker] install feature request
"J. Greenlees" <[EMAIL PROTECTED]> writes: > Pixel wrote: > > "J. Greenlees" <[EMAIL PROTECTED]> writes: > > > >>nothing really big, just when configuring the mouse during installation, add > >>the option to map it for left handed use, then set the system to map left > >>handed throughout by default. > >> > >>it actually slows me down drastically using a mouse mapped right handed. > >>and every install is a pain because the buttons aren't mapped left handed. > > uh... maybe we can have a theme that would cause left and right button > > to do the same? > > > Pixel, > it's a request, not a scream of something being broken. ~grin~ > not a rush to have for 9.1 but for concideration for future releases. > ( 9.2 maybe ) > at this point, adding a new feature is not something to work on, making sure > the beta series gets the bugs worked out is much more important. ok. But i think it should not be too hard since right button is not used during install. Making it do the same as left button would fix it, uh? PS: i'm left handed... but i don't switch buttons :)
Re: [Cooker] install feature request
Pixel wrote: "J. Greenlees" <[EMAIL PROTECTED]> writes: nothing really big, just when configuring the mouse during installation, add the option to map it for left handed use, then set the system to map left handed throughout by default. it actually slows me down drastically using a mouse mapped right handed. and every install is a pain because the buttons aren't mapped left handed. uh... maybe we can have a theme that would cause left and right button to do the same? Pixel, it's a request, not a scream of something being broken. ~grin~ not a rush to have for 9.1 but for concideration for future releases. ( 9.2 maybe ) at this point, adding a new feature is not something to work on, making sure the beta series gets the bugs worked out is much more important.
Re: [Cooker] install feature request
"J. Greenlees" <[EMAIL PROTECTED]> writes: > nothing really big, just when configuring the mouse during installation, add > the option to map it for left handed use, then set the system to map left > handed throughout by default. > > it actually slows me down drastically using a mouse mapped right handed. > and every install is a pain because the buttons aren't mapped left handed. uh... maybe we can have a theme that would cause left and right button to do the same?
Re: [Cooker] install feature request
Ooh, I second this! --- "J. Greenlees" <[EMAIL PROTECTED]> wrote: > nothing really big, just when configuring the mouse > during installation, > add the option to map it for left handed use, then > set the system to map > left handed throughout by default. > > it actually slows me down drastically using a mouse > mapped right handed. > and every install is a pain because the buttons > aren't mapped left handed. > > __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
Re: [Cooker] Install Report of mdk91beta
Guillaume Cottenceau <[EMAIL PROTECTED]> writes: > roger <[EMAIL PROTECTED]> writes: > > > 1) [When booting with the rescue cdrom] That @#$@#$ terminal beep on the > > rescue boot of the mdk91 cdrom is turned on! > > Could you try to rephrase? I don't understand. After re-reading and re-reading I finally made the right grouping of words in your sentence, hence understood the meaning :). Is it a new bug/feature for you? I think it's always been the same, and it's just the default terminal beep (visual bell, or even "nothing", being options). -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install Report of mdk91beta
roger <[EMAIL PROTECTED]> writes: > 1) [When booting with the rescue cdrom] That @#$@#$ terminal beep on the > rescue boot of the mdk91 cdrom is turned on! Could you try to rephrase? I don't understand. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install Mandrake from an external ieee1394 cdrom?
roger <[EMAIL PROTECTED]> writes: > Anybody know if one can yet install mandrake from an external ieee1394 > (firewire) cdrom? If it didn't break, yes, it's a supported feature with "usb.img" and "all.img" (hence, CDROM booting - thus, if your bios can boot from your firewire CDROM, you even have no bootdisk to mess with). Since not many people use that, it may be broken, though :). Just tell me, if it's broken I'll try to fix. [...] > I did spend sometime trying to create my own ieee1394.img, however, > failed and forget the problem that I was having. I believe it was !? strange. > something like I was able to package the image file with the > ieee1394.o/ohci1394.o/sbp2.o modules but for some reason, the diskette > wouldn't recognize the device. I do believe i was also ending up hum normally if you insmod'ed by hand the three above modules, it should have worked.. > modprobing the modules manually. yep. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] install : french UTF8 -> english
I have clicked on "advance", unselected "french", selected "french UTF8" and I get only en_US, during and after the install. Pixel wrote: "Combelles, Christophe (MED, ALTEN)" <[EMAIL PROTECTED]> writes: I have choosed only "french UTF8" for install, and the install is in english. you can't choose only "french UTF8", you will always get the language chosen in the upper part of the language choice window.
Re: [Cooker] install : automatic logon should be told "not recommended"
"John Danielson, II" <[EMAIL PROTECTED]> writes: > Since one can get to console from the X login screen a few ways, one does not > need the option to autoload a desktop at all in the installer, IMHO. many don't like having [xkg]dm running, so it's needed > Simply > set the X login to a lower res and color depth that is VESA if the video test > failed-- branch past that setting of res only IF the video test suceeded. alas video test doesn't work well during install and is disabled on many cards. > most > video cards still in use can handle 640x480x256 (8 Bit) color, so poke a > default like that, overwrite\replace after video test suceeds. No video test, > default to fail action. A lot of pre-1996 monitors have a lack of a good > versatile 800x600x16 bit mode set, and those things last so long if well > treated that there are lots of them handed down and in use. installation already defaults to 800x600x16 with not many people yelling ;p in any way XFree "vesa" module is not very good, much safer is "fbdev" (as redhat learned...) > Doing just that would eliminate the hardest thing for many newbies to grasp > and work around-- video failure during boot(as THEY see it, boot ends when > desktop is up and running). > > I agree about the recommended part, but the basic assumptions need to be > filled in if the advanced button is not selected and choices not completed > through any needed choice testing. Default minimal until better tested, > insofar as video goes. I would myself just change recommended to basic or > SAFER. i don't think automatic configuration is so bad that we have to go down that way. There are problems, but most of them are better fixed than work-arounded the way proposed above. *Many* people would be pissed of with a default config using framebuffer with a low resolution (KDE/Gnome are hardly usable in 800x600, and don't even try 640x480!)
Re: [Cooker] install : french UTF8 -> english
"Combelles, Christophe (MED, ALTEN)" <[EMAIL PROTECTED]> writes: > I have choosed only "french UTF8" for install, and the install is in english. you can't choose only "french UTF8", you will always get the language chosen in the upper part of the language choice window.
Re: [Cooker] install : automatic logon should be told "not recommended"
Pixel wrote: "John Danielson, II" <[EMAIL PROTECTED]> writes: (which is what the login to KDE does) but DO go to the X-gui'd login. The first 10 installs I made of Mandrake got wiped because the video settings for X were scragged and I did not know how NOT to autoad KDE. in the old recommended mode, it was that way when it was decided "safe" to have X without asking. Just perspective. Wish list for longer term-- ask if the user has used Linux before first thing in install, then do certain things like forced\defaulted gui'd login but not a force\default to desktop if answer is no, and be more verbose about choices and logic for choosing if no or offer to show a tutorial (and recommend seeing it) before installing. the current trend is to remove the "recommended" install and have the option to choose expert choices in the dialog boxes (using the "Advanced" button). alas, this change impacts quite a lot of things... hopefully in the end there will be both freedom-of-choice and ease :-/ Actually, usually was able to get to the login if the X login was used-- it was a VESA video mode login. The problems I had came when the desktop manager did a mode and resolution shift (or X did) that caused a different pick from the refresh table, and the acceptable monitor ranges were out of bounds-- in one case, 2 KHz out of range for horizontal sync totally TRASHED display as the system load progressed and desktop inited. Since one can get to console from the X login screen a few ways, one does not need the option to autoload a desktop at all in the installer, IMHO. Simply set the X login to a lower res and color depth that is VESA if the video test failed-- branch past that setting of res only IF the video test suceeded. most video cards still in use can handle 640x480x256 (8 Bit) color, so poke a default like that, overwrite\replace after video test suceeds. No video test, default to fail action. A lot of pre-1996 monitors have a lack of a good versatile 800x600x16 bit mode set, and those things last so long if well treated that there are lots of them handed down and in use. Doing just that would eliminate the hardest thing for many newbies to grasp and work around-- video failure during boot(as THEY see it, boot ends when desktop is up and running). I agree about the recommended part, but the basic assumptions need to be filled in if the advanced button is not selected and choices not completed through any needed choice testing. Default minimal until better tested, insofar as video goes. I would myself just change recommended to basic or SAFER. John.
Re: [Cooker] install : automatic logon should be told "not recommended"
"John Danielson, II" <[EMAIL PROTECTED]> writes: > (which is what the login to KDE does) but DO go to the X-gui'd login. The > first 10 installs I made of Mandrake got wiped because the video settings for > X were scragged and I did not know how NOT to autoad KDE. in the old recommended mode, it was that way when it was decided "safe" to have X without asking. > Just perspective. Wish list for longer term-- ask if the user has used Linux > before first thing in install, then do certain things like forced\defaulted > gui'd login but not a force\default to desktop if answer is no, and be more > verbose about choices and logic for choosing if no or offer to show a tutorial > (and recommend seeing it) before installing. the current trend is to remove the "recommended" install and have the option to choose expert choices in the dialog boxes (using the "Advanced" button). alas, this change impacts quite a lot of things... hopefully in the end there will be both freedom-of-choice and ease :-/
Re: [Cooker] install : automatic logon should be told "not recommended"
"Combelles, Christophe (MED, ALTEN)" <[EMAIL PROTECTED]> writes: > Pixel wrote: > > but, i do agree that the dialog box for choosing autologin or not is > > not clear > > > > OK, so what do you think of this UI : > If you don't know, you just click "next" : > > --- > I can set up your computer to automatically logon a user... > Do you want to use this feature ? > > (x) no (default for most cases) > > > > ( ) yes (useful for single user at home) it could be that way, but I must see first what our ergonomy team decided (well, "will decide" is more correct since the final spec is not out yet :)
Re: [Cooker] install : automatic logon should be told "not recommended"
J. Greenlees wrote: Pixel wrote: Christophe Combelles <[EMAIL PROTECTED]> writes: Matter of ergonomics : The automatic logon is not a very secure feature. [...] Either : Add the string "(not recommended)" just after the string "do you want to use this feature", to give the good advice, Or better : replace the two buttons "YES" and "NO" with two radio buttons "yes" and "no". The radion button enabled by default should be "no". And add a standard "next" button. So the user which does not understand this feature will just click on "next" and won't have this feature enabled, which is a good choice. i agree the ergonomics of this box is no good. but i do not agree this is that unsafe. i'd agree to add "(not recommended)" iff the user has a password-secured bootloader. and in that case, it's even better not to propose autologin :) for people new to linux from windows, the automatic login is what windows gives them. for single user home use it may not be as much a risk, which is where linux will have to get people from windows to expand user base. would definitely put a "not recommended for business/company/corporate computers" tag in. though most network admins should know that anyway. been discussing in a forum about linux/ windows, most windows users won't switch until point and click ui is all they have to deal with. maybe a single cd version set up for complete new users that gives them the mushroom treatment windows users are used to from ms. no options to speak of during install, no choice in ui, and set to runlevel 5 after install with automatic login. this would allow un-informed windows users to check Mandrake out in a way they are used to being treated. ;) (though I would recommend against completely removing their windows partitions during the install, even though windows would demand that any other partitions be rebuilt. As a Windows user from 3.0 up, AND as a Linux user for a couple years, I can tell you that what Windows users are used to is a graphical login, but do not need an autologin straight into a desktop for the most part in order to be comfortable. My Mandrake and Redhat installs do NOT go to a desktop autoload (which is what the login to KDE does) but DO go to the X-gui'd login. The first 10 installs I made of Mandrake got wiped because the video settings for X were scragged and I did not know how NOT to autoad KDE. Just perspective. Wish list for longer term-- ask if the user has used Linux before first thing in install, then do certain things like forced\defaulted gui'd login but not a force\default to desktop if answer is no, and be more verbose about choices and logic for choosing if no or offer to show a tutorial (and recommend seeing it) before installing. John.
Re: [Cooker] install : mountpoint choice : "/" appears twice
Randy Welch <[EMAIL PROTECTED]> writes: > During install, while creating the partitions, when I want to choose a > mountpoint for a partition, the "/" appears twice in the list of choices. > >>> > >>>weird, i don't have this... > >>>. > >>> > >> > >>I have seen it on the 9.1b iso. Perhaps you've fixed it! ;-) > > that would be nice, but dreams are not often the reality :) > > when does it happen? in the dialog box when pressing "Create" in > > diskdrake? > > When you have selected an already existing partition and you select the mount > point for the file system you will see two rows that have just /. well it must have gone away on its own :) since i can't reproduce... please try cooker or upcoming beta2!
Re: [Cooker] install user : "accept' button not very well placed.
Pixel a écrit: Todd Lyons <[EMAIL PROTECTED]> writes: Christophe Combelles wrote on Tue, Jan 14, 2003 at 10:36:52PM +0100 : This is a matter of ergonomics : During install, when new users can be added, the button "accept" (a user) should be placed at the right of the text fields, or just below them. The current place for this button is not correct, because after having entered the username, name and passwords, one may click on the "done" button to confirm this user. Then the user will in fact not be installed, because the correct button was "accept" and not "done". I don't understand this, but maybe I haven't done the same thing as you. I do a full install. At the new user, I enter name, username, password twice and click done. When it reboots, I have two users, root and todd. According to your description the user todd shouldn't be there. But it is, so you must be doing something different. Please elaborate. you're right, "Done" do add the user but, even if things do work, i agree this is not very nice. OK, I'm wrong for the "done" button. In this case my only suggestion is to move the "accept" button either at the right of the text fields, or just below them. This would be a bit clearer.
Re: [Cooker] install : french UTF8 -> english
Not only the install : If you choose ONLY french/UTF8 during install, the i18n is configured for en_US after install Combelles, Christophe (MED, ALTEN) a écrit: I have choosed only "french UTF8" for install, and the install is in english.
Re: [Cooker] install : mountpoint choice : "/" appears twice
Pixel wrote: Randy Welch <[EMAIL PROTECTED]> writes: Pixel wrote: "Combelles, Christophe (MED, ALTEN)" <[EMAIL PROTECTED]> writes: During install, while creating the partitions, when I want to choose a mountpoint for a partition, the "/" appears twice in the list of choices. weird, i don't have this... . I have seen it on the 9.1b iso. Perhaps you've fixed it! ;-) that would be nice, but dreams are not often the reality :) when does it happen? in the dialog box when pressing "Create" in diskdrake? When you have selected an already existing partition and you select the mount point for the file system you will see two rows that have just /. (I have a partition that I use specifically for doing test installs of cooker or other linuxes so I never create a new partition at install time unless it's a new disk.) By the way I really have to tip my hat to Mandrake on the installer. Tried the RH beta. It is very unforgiving of failures in the install. ( got a clean install with it but it hangs on boot.. *sigh*). -randy
Re: [Cooker] install : automatic logon should be told "not recommended"
Pixel wrote: but, i do agree that the dialog box for choosing autologin or not is not clear OK, so what do you think of this UI : If you don't know, you just click "next" : --- I can set up your computer to automatically logon a user... Do you want to use this feature ? (x) no (default for most cases) ( ) yes (useful for single user at home) user :[(v) user1] desktop : [(v) KDE ] [<- back ] [ next ->] -
Re: [Cooker] install user : "accept' button not very well placed.
Todd Lyons <[EMAIL PROTECTED]> writes: > Christophe Combelles wrote on Tue, Jan 14, 2003 at 10:36:52PM +0100 : > > This is a matter of ergonomics : > > > > During install, when new users can be added, the button "accept" (a > > user) should be placed at the right of the text fields, or just below them. > > > > The current place for this button is not correct, because after having > > entered the username, name and passwords, one may click on the "done" > > button to confirm this user. Then the user will in fact not be > > installed, because the correct button was "accept" and not "done". > > I don't understand this, but maybe I haven't done the same thing as you. > I do a full install. At the new user, I enter name, username, password > twice and click done. When it reboots, I have two users, root and todd. > According to your description the user todd shouldn't be there. But it > is, so you must be doing something different. Please elaborate. you're right, "Done" do add the user but, even if things do work, i agree this is not very nice.
Re: [Cooker] install : mountpoint choice : "/" appears twice
Randy Welch <[EMAIL PROTECTED]> writes: > Pixel wrote: > > "Combelles, Christophe (MED, ALTEN)" <[EMAIL PROTECTED]> writes: > > > >>During install, while creating the partitions, when I want to choose a > >>mountpoint for a partition, the "/" appears twice in the list of choices. > > weird, i don't have this... > > . > > > > I have seen it on the 9.1b iso. Perhaps you've fixed it! ;-) that would be nice, but dreams are not often the reality :) when does it happen? in the dialog box when pressing "Create" in diskdrake?
Re: [Cooker] install : automatic logon should be told "not recommended"
"J. Greenlees" <[EMAIL PROTECTED]> writes: > personally, I never use automatic login, after working in a bank and having to > go through 3 different log ins, with 3 different user names and passwords, > just to turn terminal on and activate app for the day I got used to a decently > organized security system. so tell me you have: a password in the bootloader! OR no physical access to the box OR only keyboard/monitor access (ie no access to the central unit) and disabled sys-req & disabled ctrl-alt-suppr but, i do agree that the dialog box for choosing autologin or not is not clear
Re: [Cooker] install : automatic logon should be told "not recommended"
Buchan Milne wrote: J. Greenlees wrote: for people new to linux from windows, the automatic login is what windows gives them. Depends: 1)Win9x defaults to no login, until you enable profiles or join the machine to a network unless you allow the default microsoft family login, then, if no password input, no login. microsoft network login isn't automatic, and doesn't offer the option, majority of home users go with family login to get rid of having to log in. 2)Winnt/win2k/winxp (AFAIK) force login really? my wife's xp-pro box doesn't require login at all, with networking used for internet connection. ( she did as most do, and told it automatically login. ) for single user home use it may not be as much a risk, which is where linux will have to get people from windows to expand user base. ANy home user connected to the internet is asked to login AFAICR. would definitely put a "not recommended for business/company/corporate computers" tag in. though most network admins should know that anyway. been discussing in a forum about linux/ windows, most windows users won't switch until point and click ui is all they have to deal with. How does this make a difference to whether it's point&click ? automatic login is part of point and click, to the people that made / agreed with that assessment. these same people do not want options during install, so their judgment may be suspect. ;) personally, I never use automatic login, after working in a bank and having to go through 3 different log ins, with 3 different user names and passwords, just to turn terminal on and activate app for the day I got used to a decently organized security system. ( scary was that the bank upgraded from win 3.1.1 to win 95 while I was working there. ^shudder^ ).
Re: [Cooker] install : automatic logon should be told "not recommended"
J. Greenlees wrote: > for people new to linux from windows, the automatic login is what > windows gives them. Depends: 1)Win9x defaults to no login, until you enable profiles or join the machine to a network 2)Winnt/win2k/winxp (AFAIK) force login > for single user home use it may not be as much a risk, which is where > linux will have to get people from windows to expand user base. ANy home user connected to the internet is asked to login AFAICR. > > would definitely put a "not recommended for business/company/corporate > computers" tag in. though most network admins should know that anyway. > > been discussing in a forum about linux/ windows, most windows users > won't switch until point and click ui is all they have to deal with. > How does this make a difference to whether it's point&click ? -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
Re: [Cooker] install : automatic logon should be told "not recommended"
Pixel wrote: > Christophe Combelles <[EMAIL PROTECTED]> writes: > i agree the ergonomics of this box is no good. > > but i do not agree this is that unsafe. > > i'd agree to add "(not recommended)" iff the user has a > password-secured bootloader. and in that case, it's even better not to > propose autologin :) Make it dependant on msec level? Have it dedault to off in msec>3 ? Buchan -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
Re: [Cooker] install : cannot skip the bootlader step !
Christophe Combelles wrote: > During install, the bootloader step cannot be skipped. > > Worse : I wanted to install just on my partition hdd10 So put the boot loader on hdd10. Then set your other linux install to boot an "Other" OS from hdd10. Back button issues are known. Buchan -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
Re: [Cooker] install : mountpoint choice : "/" appears twice
Pixel wrote: "Combelles, Christophe (MED, ALTEN)" <[EMAIL PROTECTED]> writes: During install, while creating the partitions, when I want to choose a mountpoint for a partition, the "/" appears twice in the list of choices. weird, i don't have this... . I have seen it on the 9.1b iso. Perhaps you've fixed it! ;-) -randy
Re: [Cooker] install user : "accept' button not very well placed.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christophe Combelles wrote on Tue, Jan 14, 2003 at 10:36:52PM +0100 : > This is a matter of ergonomics : > > During install, when new users can be added, the button "accept" (a > user) should be placed at the right of the text fields, or just below them. > > The current place for this button is not correct, because after having > entered the username, name and passwords, one may click on the "done" > button to confirm this user. Then the user will in fact not be > installed, because the correct button was "accept" and not "done". I don't understand this, but maybe I haven't done the same thing as you. I do a full install. At the new user, I enter name, username, password twice and click done. When it reboots, I have two users, root and todd. According to your description the user todd shouldn't be there. But it is, so you must be doing something different. Please elaborate. - -- ...and I will strike down upon thee with great vengeance and furious anger, those who attempt to poison and destroy my binaries, and you will know my name is root, when I lay my vengeance upon thee. Cooker Version mandrake-release-9.1-0.1mdk Kernel 2.4.20-2mdk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+JLRvlp7v05cW2woRAnIHAJ4mMeOM5zBL8ZdmDdG5tMFg+eqL1QCfbo47 5nORyv96aYgUQAmFku+IVpI= =kb5w -END PGP SIGNATURE-
Re: [Cooker] install : automatic logon should be told "not recommended"
J. Greenlees a écrit: Pixel wrote: Christophe Combelles <[EMAIL PROTECTED]> writes: Matter of ergonomics : The automatic logon is not a very secure feature. [...] Either : Add the string "(not recommended)" just after the string "do you want to use this feature", to give the good advice, Or better : replace the two buttons "YES" and "NO" with two radio buttons "yes" and "no". The radion button enabled by default should be "no". And add a standard "next" button. So the user which does not understand this feature will just click on "next" and won't have this feature enabled, which is a good choice. i agree the ergonomics of this box is no good. but i do not agree this is that unsafe. i'd agree to add "(not recommended)" iff the user has a password-secured bootloader. and in that case, it's even better not to propose autologin :) for people new to linux from windows, the automatic login is what windows gives them. Not since people are discovering multiuser with 2000/XP (at last) So, as a summary : automatic logon is for "single user at home" manual logon is for every other case : several users So I post a modified version of my suggested UI : --- I can set up your computer to automatically logon a user... Do you want to use this feature ? (x) no (default for most cases) ( ) yes (useful for single user at home) user :[(v) user1] desktop : [(v) KDE ] [<- back ] [ next ->] - for single user home use it may not be as much a risk, which is where linux will have to get people from windows to expand user base. would definitely put a "not recommended for business/company/corporate computers" tag in. though most network admins should know that anyway. been discussing in a forum about linux/ windows, most windows users won't switch until point and click ui is all they have to deal with. maybe a single cd version set up for complete new users that gives them the mushroom treatment windows users are used to from ms. no options to speak of during install, no choice in ui, and set to runlevel 5 after install with automatic login. this would allow un-informed windows users to check Mandrake out in a way they are used to being treated. ;) (though I would recommend against completely removing their windows partitions during the install, even though windows would demand that any other partitions be rebuilt.
Re: [Cooker] install : automatic logon should be told "not recommended"
Pixel wrote: Christophe Combelles <[EMAIL PROTECTED]> writes: Matter of ergonomics : The automatic logon is not a very secure feature. [...] Either : Add the string "(not recommended)" just after the string "do you want to use this feature", to give the good advice, Or better : replace the two buttons "YES" and "NO" with two radio buttons "yes" and "no". The radion button enabled by default should be "no". And add a standard "next" button. So the user which does not understand this feature will just click on "next" and won't have this feature enabled, which is a good choice. i agree the ergonomics of this box is no good. but i do not agree this is that unsafe. i'd agree to add "(not recommended)" iff the user has a password-secured bootloader. and in that case, it's even better not to propose autologin :) for people new to linux from windows, the automatic login is what windows gives them. for single user home use it may not be as much a risk, which is where linux will have to get people from windows to expand user base. would definitely put a "not recommended for business/company/corporate computers" tag in. though most network admins should know that anyway. been discussing in a forum about linux/ windows, most windows users won't switch until point and click ui is all they have to deal with. maybe a single cd version set up for complete new users that gives them the mushroom treatment windows users are used to from ms. no options to speak of during install, no choice in ui, and set to runlevel 5 after install with automatic login. this would allow un-informed windows users to check Mandrake out in a way they are used to being treated. ;) (though I would recommend against completely removing their windows partitions during the install, even though windows would demand that any other partitions be rebuilt.
Re: [Cooker] install : automatic logon should be told "not recommended"
So what about the radio buttons ? --- I can set up your computer to automatically logon a user... Do you want to use this feature ? (x) no (default) ( ) yes user :[(v) user1] desktop : [(v) KDE ] [<- back ] [ next ->] - Pixel a écrit: Christophe Combelles <[EMAIL PROTECTED]> writes: Matter of ergonomics : The automatic logon is not a very secure feature. [...] Either : Add the string "(not recommended)" just after the string "do you want to use this feature", to give the good advice, Or better : replace the two buttons "YES" and "NO" with two radio buttons "yes" and "no". The radion button enabled by default should be "no". And add a standard "next" button. So the user which does not understand this feature will just click on "next" and won't have this feature enabled, which is a good choice. i agree the ergonomics of this box is no good. but i do not agree this is that unsafe. i'd agree to add "(not recommended)" iff the user has a password-secured bootloader. and in that case, it's even better not to propose autologin :)
Re: [Cooker] install : cannot skip the bootlader step !
Christophe Combelles <[EMAIL PROTECTED]> writes: > During install, the bootloader step cannot be skipped. > > Worse : I wanted to install just on my partition hdd10, when the bootloader > question comes up, there was no choice to not install it. So I thought that > the "back" button would act like a "cancel" button, but NO ! It has installed > the bootloader at clicking on "back" ! fixed. "back" button now do cancel. as for back-meaning-cancel, it will be taken care of... thanks!
Re: [Cooker] install : automatic logon should be told "not recommended"
Christophe Combelles <[EMAIL PROTECTED]> writes: > Matter of ergonomics : > > The automatic logon is not a very secure feature. [...] > Either : Add the string "(not recommended)" just after the string "do you want > to use this feature", to give the good advice, > > Or better : replace the two buttons "YES" and "NO" with two radio buttons > "yes" and "no". The radion button enabled by default should be "no". And add a > standard "next" button. > So the user which does not understand this feature will just click on "next" > and won't have this feature enabled, which is a good choice. i agree the ergonomics of this box is no good. but i do not agree this is that unsafe. i'd agree to add "(not recommended)" iff the user has a password-secured bootloader. and in that case, it's even better not to propose autologin :)
Re: [Cooker] install : formatted partition without confirmation
Pixel a écrit: Christophe Combelles <[EMAIL PROTECTED]> writes: I Started install I deleted my partition hdd10 I recreated the partition hdd10 with a different size. I choosed "/" as mountpoint for this partition. I validated --> the partition is formatted without confirmation Is it normal ?? yes, you created a new partition... mmh, yes, but in this case I really hope there is no bug when building the list of partitions to automatically format...
Re: [Cooker] install : formatted partition without confirmation
Christophe Combelles <[EMAIL PROTECTED]> writes: > I Started install > I deleted my partition hdd10 > I recreated the partition hdd10 with a different size. > I choosed "/" as mountpoint for this partition. > I validated > > --> the partition is formatted without confirmation > > Is it normal ?? yes, you created a new partition...
Re: [Cooker] install : mountpoint choice : "/" appears twice
"Combelles, Christophe (MED, ALTEN)" <[EMAIL PROTECTED]> writes: > During install, while creating the partitions, when I want to choose a > mountpoint for a partition, the "/" appears twice in the list of choices. weird, i don't have this...
Re: [Cooker] install problems
On Mon, 23 Dec 2002 23:50:50 +0100 Stefan van der Eijk <[EMAIL PROTECTED]> wrote: > "an error occurred > error ordering package list: cannot open Requirename index using db3 - > No such file or directory (2)" took me some time to figure the meaning of this message. The file (/mnt)/var/lib/rpm/Requirename doesn't exist, along with the other rpm db files except Packages. Someone suggested that this might be due to the new glibc but I can't see how this connects to the failed db creation at install. - Mark
Re: [Cooker] Install partition manager hoses Highpoint Raid array
On Wednesday 16 October 2002 03:04 pm, Guillaume Cottenceau wrote: > > Is the mount point or type written to the partition table? > > Yes the filesystem type is part of the partition table. If you > set your partition to ext3 and format it, before rebooting into > the installer, it should fix your pb. But these were already ext3 partitions for /home and / on a working rc1 version. But even though there was no reason for the installer to mess with the partition table, it shouldnt have broken the raid array when it re-wrote the partition table. Must be some bug left in the diskdrake or ataraid/hptraid modules. I have successfully on a number of occassions written the partition table with the open source driver, so it may not be diskdrake. Jack
Re: [Cooker] Install partition manager hoses Highpoint Raid array
Jack and Melissa McSwain <[EMAIL PROTECTED]> writes: > Is the mount point or type written to the partition table? Yes the filesystem type is part of the partition table. If you set your partition to ext3 and format it, before rebooting into the installer, it should fix your pb. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install troubles
"J. Greenlees" <[EMAIL PROTECTED]> writes: > Guillaume Cottenceau wrote: > > You might try a boot floppy from /images/alternatives/, also. > > > > not always possible, no floppy on my laptop. > so boot floppy becomes problematic with diskless workstations. :-) we can't support all the configurations. for you you'll need to burn a CD with the alternatives cdrom.img on it. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install troubles
Guillaume Cottenceau wrote: > > You might try a boot floppy from /images/alternatives/, also. > not always possible, no floppy on my laptop. so boot floppy becomes problematic with diskless workstations. :-) hmm and idea for installer, add more support on cdrom boot install specifically for laptop installations.
Re: [Cooker] Install troubles
Austin Acton <[EMAIL PROTECTED]> writes: > Hey guys, > Can you help? > > My brother is trying to install Mandrake 9 on a Toshiba laptop (I forget > the model, it's a PIII, about 2 years old...). And he gets these weird > errors I can't figure out. P.S. Mandrake 8 and RedHat 7 and 8 all > installed without any troubles... > P.P.S. The MD5's are fine... > Any ideas? > > Boot install CD... > > Error > Could not uncompress second stage ramdisk. This is probably an hardware > error while reading the data. (this may be caused by a hardware error or > by a Linux kernel bug) Probably a badly burnt CD. Have you checked messages from the console #4? You might try a boot floppy from /images/alternatives/, also. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install of 9.0 - raid ?
Bruno Prior <[EMAIL PROTECTED]> writes: > This was my first guess as well, but the system still wouldn't > come up after I built my own initrd with raid1 and raid5 support. > I added aliases for md-personality-3 and md-personality-4 to > /etc/modules.conf, but no luck. Every array would still fail to > startup with "kmod: failed to exec /sbin/modprobe -s -k > md-personality-x, errno=2\n md: personality x is not loaded!". I > would guess that Mandrake's initrd has RAID support built in > (they would have to go out of their way to exclude it, which > seems unlikely). Although this looks like the problem, it seems > actually to be more fundamental. To boot a Mandrake system, you need a "working" /etc/raidtab file (e.g. containing right infos about your / partition at least). -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install of 9.0 - raid ?
Bruno Prior <[EMAIL PROTECTED]> writes: > down. Or at least, this is my interpretation of why every time I > upgrade my root-RAID Mandrake-based server, I have to remember to http://www.linux-mandrake.com/en/errata.php3#raid -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install bug, vmlinuz symlink on seperate /boot not updated
Buchan Milne <[EMAIL PROTECTED]> writes: > On a clean isntall, if you had a seperate /boot, and chose not to format /boot > (which is the default), the sylink to vmlinuz is left as it was before, so you > end up booting the previous kernel with no modules availble. bug accepted :) will be fixed
Re: [Cooker] Install of 9.0 - raid ?
Bruno Prior <[EMAIL PROTECTED]> writes: [...] > One thought. Was yours a completely fresh install? Mine was an install over > the top of 9.0 RC1, and I was trying in the first instance to retain the old > arrays. The errata indicates that this is what goes wrong - diskdrake > identifies the old arrays correctly, but does not successfully recreate the > raidtab. Because Mandrake's raid startup depends on the raidtab, everything > then falls down. The perl-script attached to the errata rebuilds the raidtab, > which is a kludge to get round the problem (but probably too late by the time > you encounter the problem and find the solution). But the main point of my > previous message was that this is the wrong way to do it. It is _much_ better > for your arrays to fire up under auto-recognition, than to do it via raidtab > and rc.sysinit. agreed. I even thought it was that way and that raidtab was only used by mkraid. In fact, raidtab is used by mkinird and rc.sysinit. Not using raidtab in - mkinitrd: the only problem is knowing which personality to put in initrd. This can be done by looking at /proc/mdstat. - rc.sysinit: i don't know. Maybe patching mount to do an ioctl RAID_AUTORUN on md* devices?
Re: [Cooker] Install of 9.0 - raid ?
On Mon, 2002-09-30 at 05:46, Bruno Prior wrote: > This was my first guess as well, but the system still wouldn't come up > after I built my own initrd with raid1 and raid5 support. I added > aliases for md-personality-3 and md-personality-4 to /etc/modules.conf, > but no luck. Every array would still fail to startup with "kmod: failed > to exec /sbin/modprobe -s -k md-personality-x, errno=2\n md: personality > x is not loaded!". I would guess that Mandrake's initrd has RAID support > built in (they would have to go out of their way to exclude it, which > seems unlikely). Although this looks like the problem, it seems actually > to be more fundamental. Perhaps the issues I had with creating RAID-0 volumes in diskdrake are cropping up in the installer? > Is the clue the reference to RAID-0? Did you move /boot to a RAID-0 > array? If so, this will fail. Alternatively, you are hitting the same > problem as before. Try building a kernel with support for whichever RAID > levels you need. As long as /boot is not on RAID-0 or RAID-5, this > should work. No, I kept /boot as /dev/sda1 (ext3). The system works fine if I do everything manually (fdisk, vi /etc/raidtab, mkraid, mke2fs, cp -a, vi /etc/fstab, reboot).
Re: [Cooker] Install of 9.0 - raid ?
That's not very helpful if the damn thing won't come up even in single user mode. ;) I could use the rescue mode from the CD, but I'd rather everything work right w/o having to do that. On Mon, 2002-09-30 at 04:15, Thomas Backlund wrote: > From: "Wes Kurdziolek" <[EMAIL PROTECTED]> > > On Sun, 2002-09-29 at 22:43, Bruno Prior wrote: > > > > Basically I've got a ASUS A7V133 RAID m/b with 1G ram, althon 1500XP > and > > > > two 40G > > > > 7200rpm disks. One disk on the main controller, the other on the > > > > onboard promise controller. > > > > > > > > Booted mandrake 9.0 disk #1, partitioned as follows: > > > > > > > > /dev/hda1256M-/boot [ext2] > > > > /dev/hda224G-added to md0 > > > > /dev/hda31Gswap > > > > /dev/hds4reat-addes to md1 > > > > > > > > /dev/hde1256M-/tmp [reiserfs] > > > > /dev/hde224G-added to md0 > > > > /dev/hde31Gswap > > > > /dev/hde4reat-addes to md1 > > > > > > > > md0 is mode 0/ > > > > md1 is mode 1/home > > > > > > > > Installed mandrake, went fine, rebooted, failed ! > > > > > > > > When I did an MDK 9.0 install that resembled this (ext3 /boot, RAID-0 /, > > /usr, /usr/local, /var/, and /tmp -- yes, performance is critical), the > > system failed to come up after rebooting b/c the raid0 module was not > > included in the initrd and/or not loaded by the initrd's linuxrc script > > therefore / couldn't be mounted. I believe this is a simple fix that > > involves checking to see if / is a software RAID volume, including the > > correct module in the initrd, and loading it in the initrd's linuxrc. I > > will submit a patch if someone can tell me if this is part of mdkinst or > > mkinitrd that is broken. > > > > Have you tried to recreate the initrd: > mkinitrd /boot/initrd-2.4.19-16mdk.img 2.4.19-16mdk > (according to docs, it should be able to recognize all needed modules) > > if not... > > mkinitrd --with=raid0 /boot/initrd-2.4.19-16mdk.img 2.4.19-16mdk > > dont forget to rerun lilo after you have made the new initrd, > or it won't be mapped correctly... > > Thomas > > > > > *** Tämä viesti on VirusTarkistettu INRITEL OY:n postipalvelimella!! *** >
Re: [Cooker] Install of 9.0 - raid ?
Wes Kurdziolek wrote: > > When I did an MDK 9.0 install that resembled this (ext3 /boot, RAID-0 /, > /usr, /usr/local, /var/, and /tmp -- yes, performance is critical), the > system failed to come up after rebooting b/c the raid0 module was not > included in the initrd and/or not loaded by the initrd's linuxrc script > therefore / couldn't be mounted. I believe this is a simple fix that > involves checking to see if / is a software RAID volume, including the > correct module in the initrd, and loading it in the initrd's linuxrc. I > will submit a patch if someone can tell me if this is part of mdkinst or > mkinitrd that is broken. This was my first guess as well, but the system still wouldn't come up after I built my own initrd with raid1 and raid5 support. I added aliases for md-personality-3 and md-personality-4 to /etc/modules.conf, but no luck. Every array would still fail to startup with "kmod: failed to exec /sbin/modprobe -s -k md-personality-x, errno=2\n md: personality x is not loaded!". I would guess that Mandrake's initrd has RAID support built in (they would have to go out of their way to exclude it, which seems unlikely). Although this looks like the problem, it seems actually to be more fundamental. > Also, the diskdrake that comes with 9.0 seems to have some issues with > software RAID as well: in order to get my server up and running, I first > installed w/ an ext3 /boot and a just big enough ext3 /. Then after a > successful reboot, I fired up diskdrake and proceeded to create software > RAID partitions and then volumes. When it successfully created all my > mount points and moved the files (all except / -- non-RAID-0 performance > is fine), and I exited, diskdrake saved my changes and recommended I > reboot. Upon doing so, none of the software RAID volumes came up -- they > all had invalid superblocks (but *were* recognized as Linux software > RAID autodetect partitions), and my system was useless (had to > reinstall). This leads me to believe that diskdrake never actually ran > mkraid on the new volumes, just raidstart. I will poke around diskdrake > this week if I get a chance to see if that is true. Is the clue the reference to RAID-0? Did you move /boot to a RAID-0 array? If so, this will fail. Alternatively, you are hitting the same problem as before. Try building a kernel with support for whichever RAID levels you need. As long as /boot is not on RAID-0 or RAID-5, this should work. Cheers, Bruno
Re: [Cooker] Install of 9.0 - raid ?
Thomas Backlund wrote:
> Funny, I have no problem what so ever with the soft raid, and I have 3
> systems
> set up this way, 2 with scsi disks, and one with ide disks...
>
> my setup: RAID -1
>
> /dev/md0 -> /boot (sda1,sdb1 or hda1,hdc1)
> /dev/md1 -> / (sda6,sdb6 or hda6,hdc6)
> /dev/md2 -> /usr(sda7,sdb7 or hda7,hdc7)
> /dev/md3 -> /var (sda8,sdb8 or hda8,hdc8)
> /dev/md4 -> /home (sda9,sdb9 or hda9,hdc9)
>
> the swaps are on /dev/sda5 and /dev/sdb5 (or /dev/hda5 and /dev/hdc5)
> (the swaps could also be on raid, but I haven't felt the need to
place them
> there...)
Interesting. I wonder what the difference is. My setup is:
/dev/md0 -> /boot (hda1 + hdc1, RAID-1)
/dev/md1 -> / (hda2 + hde2, RAID-1)
/dev/md2 -> /home (hda3 + hdc3 + hde3 + hdg3, RAID-5)
/dev/md3 -> /usr (hda4 + hdc4 + hde5 + hdg4, RAID-5)
I too intend to go with swap on RAID-1 (which is why there are a few
missing partitions above), but for the timebeing swap is on hdg5. I
personally believe the logic is the same for swap on RAID as for root on
RAID. If you are using RAID for High-Availability, you want to prevent
your machine crashing if a disk fails. This will happen if the disk dies
that carries either / or swap. Putting them both on RAID should prevent
this happening, which is why I personally believe there is a need to put
swap on RAID.
All in all our setups look quite similar, which makes this all the more
confusing. I don't think it should make much difference that /home and
/usr are on RAID-5, it's / and /boot that count. Nor should it make any
difference that my / partitions are primary, while yours are extended.
One thought. Was yours a completely fresh install? Mine was an install
over the top of 9.0 RC1, and I was trying in the first instance to
retain the old arrays. The errata indicates that this is what goes wrong
- diskdrake identifies the old arrays correctly, but does not
successfully recreate the raidtab. Because Mandrake's raid startup
depends on the raidtab, everything then falls down. The perl-script
attached to the errata rebuilds the raidtab, which is a kludge to get
round the problem (but probably too late by the time you encounter the
problem and find the solution). But the main point of my previous
message was that this is the wrong way to do it. It is _much_ better for
your arrays to fire up under auto-recognition, than to do it via raidtab
and rc.sysinit. (a) because you want your arrays fired up as early as
possible, and (b) because you do not necessarily want the system to try
to follow your raidtab - it might have been corrupted (as in this case),
or you might be experimenting with arrays, failed-disks etc. in which
case you may want some of the arrays in raidtab to start when you
raidstart them, and not necessarily on every boot.
And another thought. What type of filesystem are you using for / and
/boot? I have a suspicion that the move to ext3 has made things worse.
Could there be some conflict between the ext3 and RAID superblocks,
and/or could the presence of 2 superblocks confuse lilo?
> and btw. take a look at lilo docs
> (/usr/share/doc/lilo-22.3.2/README.raid1.bz2)
>
> at the beginning it states:
>
> RESTRICTIONS
>
>
> Only RAID1 is supported. LILO may be used to boot a system
> containing other RAID level partitions, but it may not be installed
> on any RAID partition other than RAID 1.
Exactly. Which is why I said:
> you putting / on RAID. Likewise, diskdrake does nothing to stop
> you putting /boot on any flavour of RAID, when the only flavour that
> will work (even with a purpose-built kernel) is RAID-1.
Maybe I wasn't explicit, but I was assuming the boot image and initrd
are in /boot. This is a fairly obscure feature, although obvious when
one thinks about it (lilo doesn't remotely have space to handle disk
striping). So, it would be a good idea for diskdrake either to warn
about this or prevent people from putting /boot (or / if they do not
have a separate /boot partition) on RAID-0 or RAID-5.
> Thomas
One interesting aspect of the problem I had with 9.0, was that I could
not even boot using one of the partitions in the root array as /. I
booted with the rescue disk and mounted / on /mnt. I edited
/mnt/etc/lilo.conf to use hda2 as root (and ran "lilo -r /mnt"). I
edited /mnt/etc/fstab so that / was on hda2 and /boot was on hda1, both
as ext2 filesystems. I changed the type of the partitions in md0 and md1
so that they would not be auto-recognised. Even then, with only /usr and
/home on RAID, the system failed to boot, with the same error message
("Kernel panic: No init found"), which I believe indicates that / failed
to mount. This would have worked previously. My strong suspicion is that
this now fails because of the move to ext3 (the panic was preceded by
the messages "Mounting root filesystem\n EXT3-fs: unable to read
superblock").
The question is, is it prematur
Re: [Cooker] Install of 9.0 - raid ?
From: "Wes Kurdziolek" <[EMAIL PROTECTED]> > On Sun, 2002-09-29 at 22:43, Bruno Prior wrote: > > > Basically I've got a ASUS A7V133 RAID m/b with 1G ram, althon 1500XP and > > > two 40G > > > 7200rpm disks. One disk on the main controller, the other on the > > > onboard promise controller. > > > > > > Booted mandrake 9.0 disk #1, partitioned as follows: > > > > > > /dev/hda1256M-/boot [ext2] > > > /dev/hda224G-added to md0 > > > /dev/hda31Gswap > > > /dev/hds4reat-addes to md1 > > > > > > /dev/hde1256M-/tmp [reiserfs] > > > /dev/hde224G-added to md0 > > > /dev/hde31Gswap > > > /dev/hde4reat-addes to md1 > > > > > > md0 is mode 0/ > > > md1 is mode 1/home > > > > > > Installed mandrake, went fine, rebooted, failed ! > > > > When I did an MDK 9.0 install that resembled this (ext3 /boot, RAID-0 /, > /usr, /usr/local, /var/, and /tmp -- yes, performance is critical), the > system failed to come up after rebooting b/c the raid0 module was not > included in the initrd and/or not loaded by the initrd's linuxrc script > therefore / couldn't be mounted. I believe this is a simple fix that > involves checking to see if / is a software RAID volume, including the > correct module in the initrd, and loading it in the initrd's linuxrc. I > will submit a patch if someone can tell me if this is part of mdkinst or > mkinitrd that is broken. > Have you tried to recreate the initrd: mkinitrd /boot/initrd-2.4.19-16mdk.img 2.4.19-16mdk (according to docs, it should be able to recognize all needed modules) if not... mkinitrd --with=raid0 /boot/initrd-2.4.19-16mdk.img 2.4.19-16mdk dont forget to rerun lilo after you have made the new initrd, or it won't be mapped correctly... Thomas *** Tämä viesti on VirusTarkistettu INRITEL OY:n postipalvelimella!! ***
Re: [Cooker] Install of 9.0 - raid ?
On Sun, 2002-09-29 at 22:43, Bruno Prior wrote: > > Basically I've got a ASUS A7V133 RAID m/b with 1G ram, althon 1500XP and > > two 40G > > 7200rpm disks. One disk on the main controller, the other on the > > onboard promise controller. > > > > Booted mandrake 9.0 disk #1, partitioned as follows: > > > > /dev/hda1256M-/boot [ext2] > > /dev/hda224G-added to md0 > > /dev/hda31Gswap > > /dev/hds4reat-addes to md1 > > > > /dev/hde1256M-/tmp [reiserfs] > > /dev/hde224G-added to md0 > > /dev/hde31Gswap > > /dev/hde4reat-addes to md1 > > > > md0 is mode 0/ > > md1 is mode 1/home > > > > Installed mandrake, went fine, rebooted, failed ! When I did an MDK 9.0 install that resembled this (ext3 /boot, RAID-0 /, /usr, /usr/local, /var/, and /tmp -- yes, performance is critical), the system failed to come up after rebooting b/c the raid0 module was not included in the initrd and/or not loaded by the initrd's linuxrc script therefore / couldn't be mounted. I believe this is a simple fix that involves checking to see if / is a software RAID volume, including the correct module in the initrd, and loading it in the initrd's linuxrc. I will submit a patch if someone can tell me if this is part of mdkinst or mkinitrd that is broken. Also, the diskdrake that comes with 9.0 seems to have some issues with software RAID as well: in order to get my server up and running, I first installed w/ an ext3 /boot and a just big enough ext3 /. Then after a successful reboot, I fired up diskdrake and proceeded to create software RAID partitions and then volumes. When it successfully created all my mount points and moved the files (all except / -- non-RAID-0 performance is fine), and I exited, diskdrake saved my changes and recommended I reboot. Upon doing so, none of the software RAID volumes came up -- they all had invalid superblocks (but *were* recognized as Linux software RAID autodetect partitions), and my system was useless (had to reinstall). This leads me to believe that diskdrake never actually ran mkraid on the new volumes, just raidstart. I will poke around diskdrake this week if I get a chance to see if that is true.
Re: [Cooker] Install of 9.0 - raid ?
> From: "Bruno Prior" <[EMAIL PROTECTED]> > > > Basically I've got a ASUS A7V133 RAID m/b with 1G ram, althon 1500XP and > > > two 40G > > > 7200rpm disks. One disk on the main controller, the other on the > > > onboard promise controller. > > > > > > Booted mandrake 9.0 disk #1, partitioned as follows: > > > > > > /dev/hda1256M-/boot [ext2] > > > /dev/hda224G-added to md0 > > > /dev/hda31Gswap > > > /dev/hds4reat-addes to md1 > > > > > > /dev/hde1256M-/tmp [reiserfs] > > > /dev/hde224G-added to md0 > > > /dev/hde31Gswap > > > /dev/hde4reat-addes to md1 > > > > > > md0 is mode 0/ > > > md1 is mode 1/home > > > > > > Installed mandrake, went fine, rebooted, failed ! > > > > I've been using Mandrake for a while (since the 7.x versions), and I am > > a huge admirer. However, Mandrake's implementation of software-RAID is, > > and has been as long as I have used it, complete pants! It is, by a long > > chalk, the worst thing about the distro. > > > > Software-RAID has been fantastically simple since Ingo Molnar wrote the > > new raidtools several years ago. Auto-recognition makes everything very > > easy. But as far as I can tell, Mandrake have yet to get to grips with > > auto-recognition. It seems that they are still trying to fire up the > > arrays from rc.sysinit. This is presumably because they have always left > > RAID support as modules, rather than building it into the default > > kernels. This is OK, so long as none of the files involved in booting > > are on any of your arrays. As soon as you try something like root-RAID, > > it all falls down. Or at least, this is my interpretation of why every > > time I upgrade my root-RAID Mandrake-based server, I have to remember to > > leave behind a purpose-built kernel and add an extra entry to lilo.conf > > to point to it. If you forget to do this, you are stuffed. Every version > > of Mandrake I have used has kernel-paniced on bootup when using the > > default kernels and initrds on my root-RAID system. As soon as you use a > > kernel with RAID-support built in, it boots fine. This says to me that > > Mandrake does not support root-RAID. > > > > If I were setting up a root-RAID system based on Mandrake, I would do > > the following (I am assuming that this is on RAID-1 or -5, it's not a > > good plan to put / on RAID-0 anyway): > > > > Install / originally to one of the partitions that will be in the > > root-RAID. Leave the other partitions in the array unassigned for now. > > Funny, I have no problem what so ever with the soft raid, and I have 3 systems set up this way, 2 with scsi disks, and one with ide disks... my setup: RAID -1 /dev/md0 -> /boot (sda1,sdb1 or hda1,hdc1) /dev/md1 -> / (sda6,sdb6 or hda6,hdc6) /dev/md2 -> /usr(sda7,sdb7 or hda7,hdc7) /dev/md3 -> /var (sda8,sdb8 or hda8,hdc8) /dev/md4 -> /home (sda9,sdb9 or hda9,hdc9) the swaps are on /dev/sda5 and /dev/sdb5 (or /dev/hda5 and /dev/hdc5) (the swaps could also be on raid, but I haven't felt the need to place them there...) and btw. take a look at lilo docs (/usr/share/doc/lilo-22.3.2/README.raid1.bz2) at the beginning it states: RESTRICTIONS Only RAID1 is supported. LILO may be used to boot a system containing other RAID level partitions, but it may not be installed on any RAID partition other than RAID 1. Thomas *** Tämä viesti on VirusTarkistettu INRITEL OY:n postipalvelimella!! ***
Re: [Cooker] Install of 9.0 - raid ?
> Basically I've got a ASUS A7V133 RAID m/b with 1G ram, althon 1500XP and > two 40G > 7200rpm disks. One disk on the main controller, the other on the > onboard promise controller. > > Booted mandrake 9.0 disk #1, partitioned as follows: > > /dev/hda1256M-/boot [ext2] > /dev/hda224G-added to md0 > /dev/hda31Gswap > /dev/hds4reat-addes to md1 > > /dev/hde1256M-/tmp [reiserfs] > /dev/hde224G-added to md0 > /dev/hde31Gswap > /dev/hde4reat-addes to md1 > > md0 is mode 0/ > md1 is mode 1/home > > Installed mandrake, went fine, rebooted, failed ! I've been using Mandrake for a while (since the 7.x versions), and I am a huge admirer. However, Mandrake's implementation of software-RAID is, and has been as long as I have used it, complete pants! It is, by a long chalk, the worst thing about the distro. Software-RAID has been fantastically simple since Ingo Molnar wrote the new raidtools several years ago. Auto-recognition makes everything very easy. But as far as I can tell, Mandrake have yet to get to grips with auto-recognition. It seems that they are still trying to fire up the arrays from rc.sysinit. This is presumably because they have always left RAID support as modules, rather than building it into the default kernels. This is OK, so long as none of the files involved in booting are on any of your arrays. As soon as you try something like root-RAID, it all falls down. Or at least, this is my interpretation of why every time I upgrade my root-RAID Mandrake-based server, I have to remember to leave behind a purpose-built kernel and add an extra entry to lilo.conf to point to it. If you forget to do this, you are stuffed. Every version of Mandrake I have used has kernel-paniced on bootup when using the default kernels and initrds on my root-RAID system. As soon as you use a kernel with RAID-support built in, it boots fine. This says to me that Mandrake does not support root-RAID. If I were setting up a root-RAID system based on Mandrake, I would do the following (I am assuming that this is on RAID-1 or -5, it's not a good plan to put / on RAID-0 anyway): Install / originally to one of the partitions that will be in the root-RAID. Leave the other partitions in the array unassigned for now. Having rebooted after installation, rebuild the kernel with whichever RAID levels you need built in (and anything else that would otherwise have to be in the initrd). Do the usual make menuconfig; make dep; make clean; make bzImage; make modules; make modules_install; cp boot/arch/i386/bzImage /boot etc. Edit lilo.conf to add an extra option to boot from this kernel. Lose the initrd line for this option, as you shouldn't need it. Run lilo and then reboot, selecting this option, to check that the new kernel boots OK. Setup the array that will hold /, with the partition that is currently / set as "failed-disk" in your raidtab. This should setup the array in degraded mode. You will want to make sure the partitions in the array other than the "failed-disk" partition are set to type "fd" for RAID auto-recognition before building the array. Having built the array, check /proc/mdstat to see that everything worked out. If so, reboot again, to test whether the new kernel will automatically recognise and start the array. Build the filesystem on the array, mount the array at a temporary mount-point (e.g. /mnt/disk), and copy all the files on / to the array, making sure not to include files from other partitions (tar is good for the job). Edit the copy of lilo.conf on the array to add an extra option that has root on /dev/mdX (where X is the number of this array), rather than on /dev/hd??. Run e.g. "lilo -r /mnt/disk" to install the new boot option. Edit /mnt/disk/etc/fstab to change the root device from /dev/hd?? to /dev/mdX. Reboot and select the option to boot with the RAID as root from the lilo prompt. If this boots successfully, you have a working root-RAID system, and don't need the partition that you originally installed to (the failed-disk). Make sure this partition is not mounted anywhere. Change its partition type to "fd". Edit /etc/raidtab so that this partition is now a normal "raid-disk", rather than a "failed-disk". raidhotadd the partition to the array. Watch the resync progress in /proc/mdstat. When it has completed, reboot again. You probably want to make the root-RAID option in lilo the default option, so you don't have to remember to select it when you boot. You will also want to get rid of the lilo options that point to the original partition for /, as the data on this partition has been destroyed. If you are using RAID-1 (which is much the better option for root-RAID), you can actually leave these options, as the individual mirrors in a RAID-1 can be mounted in their own right, so these boot options should still work, and coul
Re: [Cooker] Install of 9.0 - raid ?
> Basically I've got a ASUS A7V133 RAID m/b with 1G ram, althon 1500XP and > two 40G > 7200rpm disks. One disk on the main controller, the other on the > onboard promise controller. > > Booted mandrake 9.0 disk #1, partitioned as follows: > > /dev/hda1256M-/boot [ext2] > /dev/hda224G-added to md0 > /dev/hda31Gswap > /dev/hds4reat-addes to md1 > > /dev/hde1256M-/tmp [reiserfs] > /dev/hde224G-added to md0 > /dev/hde31Gswap > /dev/hde4reat-addes to md1 > > md0 is mode 0/ > md1 is mode 1/home > > Installed mandrake, went fine, rebooted, failed ! > > Initially because I had 1G ram it used enterprise kernel, removed 512M > of RAM, reinstalled, > failed at reboot try recompiling the kernel with built in md, raid-0 and probably promise driver and the fs you used on other PC, make boot floppy , in case you don't have place on the floppy skip all modules, if you have a ZIP drive and can boot from it use it :) start your installed raid system with the floppy or ZIP linux root=/dev/md0 init single recompile the kernel the same way, install it, run lilo & everything is ok if you use a system with the same gcc libc ... you can copy the modules and the kernel from the first compilation to the raid system, so you wont need the second compilation > If raidtab is on /etc how does bootloader/kernel know about md0 & md1. > Fails to load > > Tried a couple of times with no luck > > oshould I boot from the second install CD ? > oDo I need the enterprise kernel ? > oShould /etc be on /dev/hde1 [ext2] rather than /tmp? > > -- > Steve > >
Re: [Cooker] Install of 9.0 - raid ?
On Thursday, September 26, 2002, at 12:32 PM, Stephen Pickering wrote:
>> Before 9.0, detecting current RAID was not supported so it was
>> not so good. Now it's even better, yep.
>>
> Any tips on how to install using raid ?
>
> I tried this morning with no sucess, so I went back to non raid.
Have you checked the errata pages? There is info on RAID there and a
patch that may work for you.
http://www.mandrakelinux.com/en/90errata.php3
--
MandrakeSoft Security; http://www.mandrakesecure.net/
"lynx - source http://linsec.ca/vdanen.asc | gpg --import"
{FE6F2AFD: 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
PGP.sig
Description: PGP signature
Re: [Cooker] Install of 9.0 - raid ?
Guillaume Cottenceau wrote: >Linux Autrement <[EMAIL PROTECTED]> writes: > > > >>done folks at Mandrake. But why is it not shouted load and clear that >>Mandrake since at least 8.2 can install straight onto a RAID? >> >> > >Before 9.0, detecting current RAID was not supported so it was >not so good. Now it's even better, yep. > Any tips on how to install using raid ? I tried this morning with no sucess, so I went back to non raid. Basically I've got a ASUS A7V133 RAID m/b with 1G ram, althon 1500XP and two 40G 7200rpm disks. One disk on the main controller, the other on the onboard promise controller. Booted mandrake 9.0 disk #1, partitioned as follows: /dev/hda1256M-/boot [ext2] /dev/hda224G-added to md0 /dev/hda31Gswap /dev/hds4reat-addes to md1 /dev/hde1256M-/tmp [reiserfs] /dev/hde224G-added to md0 /dev/hde31Gswap /dev/hde4reat-addes to md1 md0 is mode 0/ md1 is mode 1/home Installed mandrake, went fine, rebooted, failed ! Initially because I had 1G ram it used enterprise kernel, removed 512M of RAM, reinstalled, failed at reboot If raidtab is on /etc how does bootloader/kernel know about md0 & md1. Fails to load Tried a couple of times with no luck oshould I boot from the second install CD ? oDo I need the enterprise kernel ? oShould /etc be on /dev/hde1 [ext2] rather than /tmp? -- Steve
Re: [Cooker] Install of 9.0
Linux Autrement <[EMAIL PROTECTED]> writes: > done folks at Mandrake. But why is it not shouted load and clear that > Mandrake since at least 8.2 can install straight onto a RAID? Before 9.0, detecting current RAID was not supported so it was not so good. Now it's even better, yep. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install problems MDK9 RC3
Per Lindström <[EMAIL PROTECTED]> writes: > > > Is this the correct file? > > > > According to the logs, you didn't format your / partition, which > > is pretty strange if you really want to do an install. Maybe > > there is some sort of problem during this "pseudo" update which > > makes that the /etc directory is no more available (or that > > /etc/resolv.conf is non available for writing for whatever > > reason). > > How do I fix this? Just reformatting the partition during install or > sometkhing else? It's probably OK to format as I don't have anything I'm > terribly upset to lose on that partition anyway. Well I don't really know why the /etc was missing, but if you want to do an install yes you need to format the / partition. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install problems MDK9 RC3
onsdagen den 25 september 2002 15.19 skrev Guillaume Cottenceau: > Per Lindström <[EMAIL PROTECTED]> writes: > > tisdagen den 24 september 2002 13.35 skrev du: > > > Per Lindström <[EMAIL PROTECTED]> writes: > > > > I have problems installing Linux Mandrake. When I reach network > > > > configuration I get this error message: > > > > > > > > cannot write /etc/resolv.conf > > [...] > > > Is this the correct file? > > According to the logs, you didn't format your / partition, which > is pretty strange if you really want to do an install. Maybe > there is some sort of problem during this "pseudo" update which > makes that the /etc directory is no more available (or that > /etc/resolv.conf is non available for writing for whatever > reason). How do I fix this? Just reformatting the partition during install or sometkhing else? It's probably OK to format as I don't have anything I'm terribly upset to lose on that partition anyway.
Re: [Cooker] Install problems MDK9 RC3
Please remove my name from the mailing list Marcos colome [EMAIL PROTECTED] Guillaume Cottenceau <[EMAIL PROTECTED]>wrote: Per Lindström <[EMAIL PROTECTED]>writes:> tisdagen den 24 september 2002 13.35 skrev du:> > Per Lindström <[EMAIL PROTECTED]>writes:> > > I have problems installing Linux Mandrake. When I reach network> > > configuration I get this error message:> > >> > > cannot write /etc/resolv.conf[...]> Is this the correct file?According to the logs, you didn't format your / partition, whichis pretty strange if you really want to do an install. Maybethere is some sort of problem during this "pseudo" update whichmakes that the /etc directory is no more available (or that/etc/resolv.conf is non available for writing for whateverreason).-- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/Do you Yahoo!? New DSL Internet Access from SBC & Yahoo!
Re: [Cooker] Install problems MDK9 RC3
Per Lindström <[EMAIL PROTECTED]> writes: > tisdagen den 24 september 2002 13.35 skrev du: > > Per Lindström <[EMAIL PROTECTED]> writes: > > > I have problems installing Linux Mandrake. When I reach network > > > configuration I get this error message: > > > > > > cannot write /etc/resolv.conf [...] > Is this the correct file? According to the logs, you didn't format your / partition, which is pretty strange if you really want to do an install. Maybe there is some sort of problem during this "pseudo" update which makes that the /etc directory is no more available (or that /etc/resolv.conf is non available for writing for whatever reason). -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install problems MDK9 RC3
tisdagen den 24 september 2002 13.35 skrev du: > Per Lindström <[EMAIL PROTECTED]> writes: > > I have problems installing Linux Mandrake. When I reach network > > configuration I get this error message: > > > > cannot write /etc/resolv.conf > > can you attach the report.bug? > to get it: > > during install, switch to console 2, > put a dos floppy in floppy drive, > and type "bug" > > -> it will put report.bug on floppy and this file interests us > > you can also get it after the install in /root/drakx/ Is this the correct file? * lspci unknown : VIA Technologies|VT8367 [KT266] [NOT_DEFINED] unknown : VIA Technologies|VT8367 [KT266 AGP] [NOT_DEFINED] snd-cmipci : C-Media Electronics Inc|CM8738 [NOT_DEFINED] unknown : VIA Technologies|VT8233 PCI to ISA Bridge [NOT_DEFINED] unknown : VIA Technologies|VT82C586 IDE [Apollo] [NOT_DEFINED] usb-uhci: VIA Technologies|VT82C586B USB [NOT_DEFINED] usb-uhci: VIA Technologies|VT82C586B USB [NOT_DEFINED] via-rhine : VIA Technologies|VT6102 [Rhine II 10/100] [NOT_DEFINED] Card:NVIDIA GeForce2 DDR (generic): nVidia Corporation|NV17 GeForce4 MX 440 [NOT_DEFINED] unknown : Virtual|Hub unknown : Virtual|Hub * pci_devices 110630990 e008 0400 00081106b0990 007013f60111b d001 0100 0088110630740 0089110605710 d401 0010 008a11063038a d801 0020 usb-uhci 008b11063038a dc01 0020 usb-uhci 009011063065b e401e600 0100 0100 via-rhine 010010de0171b e400d008d808 0100 08000008 0002 * fdisk Disk /dev/hda: 255 heads, 63 sectors, 10011 cylinders Units = cylinders of 16065 * 512 bytes Device BootStart EndBlocks Id System /dev/hda1 * 1 1251 100486267 HPFS/NTFS /dev/hda2 3757 5324 12594960f Win95 Ext'd (LBA) /dev/hda5 3757 3822530113+ 82 Linux swap /dev/hda6 3823 4073 2016126 83 Linux /dev/hda7 4074 5324 10048626 83 Linux * scsi Attached devices: none * lsmod vfat8820 1 fat29368 0 [vf
Re: [Cooker] Install problems MDK9 RC3
Per Lindström <[EMAIL PROTECTED]> writes: > I have problems installing Linux Mandrake. When I reach network configuration > I get this error message: > > cannot write /etc/resolv.conf can you attach the report.bug? to get it: during install, switch to console 2, put a dos floppy in floppy drive, and type "bug" -> it will put report.bug on floppy and this file interests us you can also get it after the install in /root/drakx/ -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Install failed from latest mirror
On Sunday 11 August 2002 17:58, Pixel wrote: >Chuck Shirley <[EMAIL PROTECTED]> writes: > >> in the ddebug file of the machine in question. :^( I will gladly >> try any other diagnostic, exclusive of re-installing again, if you >> tell me what to do. > >well i hope someone will give me a precise bug report about this "isa" >bug. > >if it occurs to anyone, please have a look at console 3! I have some Slackware machines that I want to migrate to Mandrake for testing the clustering tools that Mandrak inludes lately. I will use cooker, and if the error occurs, I will report fully. -Chuck -- +-% He's a real UNIX Man $-+-+ \ Sitting in his UNIX LAN \ Charles A. Shirley \ \ Making all his UNIX plans \ cashirley (at) comcast (dot) net \ +--# For nobody @--+-+
Re: [Cooker] Install failed from latest mirror
Chuck Shirley <[EMAIL PROTECTED]> writes: > in the ddebug file of the machine in question. :^( I will gladly > try any other diagnostic, exclusive of re-installing again, if you > tell me what to do. well i hope someone will give me a precise bug report about this "isa" bug. if it occurs to anyone, please have a look at console 3!
Re: [Cooker] Install failed from latest mirror
On Sunday 11 August 2002 15:54, Pixel wrote: >Chuck Shirley <[EMAIL PROTECTED]> writes: > >> ran fine, and XFdrake was able to properly configure X. On the >> down side, I was never able to find any more detailed errors in the >> virtual console windows of the installer. :^( > >you may still have it in /root/drakx/ddebug.log > No such luck it seems. There is no section for * starting step `setupBootloader' nor for * starting step `configureX' in the ddebug file of the machine in question. :^( I will gladly try any other diagnostic, exclusive of re-installing again, if you tell me what to do. The file ends abruptly with these lines: [root@visigoth root]# tail drakx/ddebug.log changed mode of /etc/rc.d/init.d/prelude from 755 to 700 changed mode of /etc/rc.d/init.d/keytable from 755 to 700 changed mode of /etc/rc.d/init.d/iptables from 755 to 700 changed mode of /var/log/kernel/errors from 600 to 640 changed mode of /etc/rc.d/init.d/functions from 755 to 700 changed mode of /etc/rc.d/init.d/ntpd from 755 to 700 changed mode of /var/log/daemons/warnings from 600 to 640 error: cannot open Packages index using db3 - No such file or directory (2) error: cannot open Packages index using db3 - No such file or directory (2) error: cannot open Packages index using db3 - No such file or directory (2) [root@visigoth root]# Above that it was an account of msec doing it's work, and the last step mentioned before the end was "* starting step `summary'" -Chuck -- +-% He's a real UNIX Man $-+-+ \ Sitting in his UNIX LAN \ Charles A. Shirley \ \ Making all his UNIX plans \ cashirley (at) comcast (dot) net \ +--# For nobody @--+-+
Re: [Cooker] Install failed from latest mirror
Chuck Shirley <[EMAIL PROTECTED]> writes: > ran fine, and XFdrake was able to properly configure X. On the > down side, I was never able to find any more detailed errors in the > virtual console windows of the installer. :^( you may still have it in /root/drakx/ddebug.log
Re: [Cooker] Install failed from latest mirror
On Sunday 11 August 2002 14:29, Pixel wrote: >Olivier Thauvin <[EMAIL PROTECTED]> writes: > >> Mandrake Linux Cooker-i586 20020811 15:47 >> >> Lastest installeur on cooker seems to be a bit broken. > >weird pbs. Anyway, i'm going to upload again soon. > >> >> At end of install, summary -> configuring printers, I have only a box "call >> isa method failed with unset paramters" >> Same thing when I try to install X. > >can you give the complete error message (available on console 3), >especially the file and line number where the pb occured Pixel, et al., I had the same problem with "call isa method..." problem on Friday/Saturday, but attributed it to imperfect local mirror. The installer also failed to install a bootloader, so I had to boot my mirror in rescue-mode and manually install lilo, to include hand- crafting the /etc/lilo.conf Once this was all done, the system ran fine, and XFdrake was able to properly configure X. On the down side, I was never able to find any more detailed errors in the virtual console windows of the installer. :^( -Chuck -- +-% He's a real UNIX Man $-+-+ \ Sitting in his UNIX LAN \ Charles A. Shirley \ \ Making all his UNIX plans \ cashirley (at) comcast (dot) net \ +--# For nobody @--+-+
Re: [Cooker] install problems
Igor Izyumin <[EMAIL PROTECTED]> writes: > > I'm still suspecting the DNS resolving code. Have you tried in > > static IP to not provide any IP for the DNS server, does it make > > any change? > > OK, you're absolutely right. When you remove the DNS server, it brings up the Nice, we're at least stripped it down to the DNS resolving code. > network just fine and asks you to tell it the name of the computer. When you > put the DNS server in, it crashes. I have essentially the same setup as Adam > Williamson (above). My computer is 192.168.1.2 and the nameserver is > 192.168.1.10 (it's an e-smith server and gateway box, version 5.5). The What's an e-smith server? > nameserver should give pc-2 as the name of the computer I am trying to > install it on. Maybe I should update dietlibc dns resolving code, but I fear it would need me a lot of work :-((. Thanks for your debugging input! -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] install problems
On Thu, 2002-08-01 at 08:29, Guillaume Cottenceau wrote: > Adam Williamson <[EMAIL PROTECTED]> writes: > > > 192.168.2.1, into which our systems (between two and five, depending) > > are plugged; on both systems that failed I tried DHCP and static IP > > addresses with the same crash. In the spirit of scientific enquiry, next > > I'm still suspecting the DNS resolving code. Have you tried in > static IP to not provide any IP for the DNS server, does it make > any change? OK! This is confirmed as far as i'm concerned. Setting the DNS server as a space (you can't set it to nothing, it autofills) makes it work fine, providing the correct DNS server address causes the segfault. The modified image whose address you posted to the list doesn't change anything. Whew, good to have located this at last =). Any chance of a fix, or are we just using IP addresses instead? :) Now I have to decide whether to mess with my working SuSE on the laptop and install Cooker instead...decisions, decisions :). I'll try the stuff you suggested for my CD install problems once 9.0 beta 2 comes out, let's see if we can't pin that one down too :) -- adamw
Re: [Cooker] install problems
On Thursday 01 August 2002 05:00 am, Guillaume Cottenceau wrote: > Can you try with the following image? It has an option that is > supposed to fix some problems in applications segfaulting with > gcc 3.x. > > http://people.mandrakesoft.com/~gc/files/network.img Just tried it. Same thing. "install exited abnormally... sending termination signals" -- -- Igor
Re: [Cooker] install problems
On Thursday 01 August 2002 03:21 am, Guillaume Cottenceau wrote: > Wait, maybe this could originate from a mirroring problem (beuh, > 0% chance but anyway); is the latest network.img from your mirror > the same md5sum than me? > > 72b12e8fdd829acee960ad73cbca186d No, my disk has the same md5sum as the one in the MD5SUMS file in the images directory for beta1. 44bacf1ccbe8290ffd504ed7a09c541f > > I verified the floppy (dd-ed from /dev/fd0 to another file and compared > > md5sum to the network.img). I also tried booting off of it several > > times, with DHCP and static, same thing every time. > > Can you try to boot off the cdrom, and select the network install > from there? Same behavior: crashes with DNS server, OK without. This is a beta1 cdrom, md5sum 1ac4f14dcc71a0a2ed7ef56264e95551 -- -- Igor
Re: [Cooker] install problems
On Thursday 01 August 2002 03:29 am, Guillaume Cottenceau wrote: > Adam Williamson <[EMAIL PROTECTED]> writes: > > 192.168.2.1, into which our systems (between two and five, depending) > > are plugged; on both systems that failed I tried DHCP and static IP > > addresses with the same crash. In the spirit of scientific enquiry, next > > I'm still suspecting the DNS resolving code. Have you tried in > static IP to not provide any IP for the DNS server, does it make > any change? OK, you're absolutely right. When you remove the DNS server, it brings up the network just fine and asks you to tell it the name of the computer. When you put the DNS server in, it crashes. I have essentially the same setup as Adam Williamson (above). My computer is 192.168.1.2 and the nameserver is 192.168.1.10 (it's an e-smith server and gateway box, version 5.5). The nameserver should give pc-2 as the name of the computer I am trying to install it on. -- -- Igor
Re: [Cooker] install problems
Adam Williamson <[EMAIL PROTECTED]> writes: > 192.168.2.1, into which our systems (between two and five, depending) > are plugged; on both systems that failed I tried DHCP and static IP > addresses with the same crash. In the spirit of scientific enquiry, next I'm still suspecting the DNS resolving code. Have you tried in static IP to not provide any IP for the DNS server, does it make any change? -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] install problems
Igor Izyumin <[EMAIL PROTECTED]> writes: > On Wednesday 31 July 2002 01:26 pm, Guillaume Cottenceau wrote: > > Yep, I'd really like we could fix it. I've posted a request for > > testing to the developers of our office, maybe one of them can > > reproduce and then it would be real easy for me to debug & fix. > > How does one go about debugging a boot floppy? None of the Well at initial debugging stage I did it myself with a special network bootable version of the stage1 (using grub network boot feature with tftp transfers); now that it's almost stable when I have trouble I try to add some logging message to help me understand the origin of the problem, try to fix, test again, etc. For that problem, since I don't know where the origin of the problem could be, it's almost impossible to blindly put some logging messages, ask you to test, retry, etc.. > virtual terminals give you access to a console. Is there some Yep, I don't have enough space on the floppy to put a shell, neither any useful tool to edit files etc.. > command to switch the installer into debug mode? There are no > interesting messages on any of the log screens. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] install problems
Igor Izyumin <[EMAIL PROTECTED]> writes: > > Ouch, you too? What is your hardware? > - 3com PCI network card (3c590, I think). Anyway, it uses the 3c59x driver. My test machine uses the very same driver and I have no problem :-(. Wait, maybe this could originate from a mirroring problem (beuh, 0% chance but anyway); is the latest network.img from your mirror the same md5sum than me? 72b12e8fdd829acee960ad73cbca186d > - Advansys SCSI adapter Same as my test machine! :-) > - HPT-something RAID controller (on-board); used for regular IDE (no raid) > - anything else that could matter? Don't know... > I verified the floppy (dd-ed from /dev/fd0 to another file and compared md5sum > to the network.img). I also tried booting off of it several times, with DHCP > and static, same thing every time. Can you try to boot off the cdrom, and select the network install from there? -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] install problems
Igor Izyumin <[EMAIL PROTECTED]> writes: > On Wednesday 31 July 2002 05:13 pm, Roland wrote: > > Me too, I have done a network installation with a 3com 509 without > > problems. > The md5sums for the network.img in 9.0 beta1 and cooker are different. Could > that be why? I was having problems with beta1. Cooker is rebuilt quite often, check the rebuilds in the "changelog" list. At each rebuild, `network.img' md5sum changes even if the code inside doesn't change. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] install problems
Adam Williamson <[EMAIL PROTECTED]> writes: > > By the way, I'm beginning to ask myself if we're not trapped in a > > gcc-3.2 miscompilation since the whole network code of stage1 has > > not changed at all for the past months :-(. > > > > If only I could have a machine at hands with the problem.. > > Nope, it's not GCC 3.2 - when I got the error we were still on GCC 3.1, > and it also occurs with the Mandrake 8.2 version of the bootdisk. Mmmmh I don't remember anyone reporting segfaults on network.img with 8.2, that's peculiar.. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] install problems
On Wed, 2002-07-31 at 18:41, Guillaume Cottenceau wrote: > Guillaume Cottenceau <[EMAIL PROTECTED]> writes: > > > what is your network card? (lspcidrake -v) > > Sorry, I didn't read your other mail at that time. > > By the way, I'm beginning to ask myself if we're not trapped in a > gcc-3.2 miscompilation since the whole network code of stage1 has > not changed at all for the past months :-(. > > If only I could have a machine at hands with the problem.. Nope, it's not GCC 3.2 - when I got the error we were still on GCC 3.1, and it also occurs with the Mandrake 8.2 version of the bootdisk. -- adamw
RE: [Cooker] install problems
On Wed, 2002-07-31 at 19:19, David Walser wrote: > If I've been following the discussion successfully, > people are having problems with network.img? > > I'm using it quite successfully with newest Cooker > with both 8139too and 3c905C-TX network cards. It's not consistent; there's three of us experiencing the error but we've also heard from others like you for whom it works fine. This is part of the problem - we can't identify a common feature between the systems it's failing on :( -- adamw
Re: [Cooker] install problems
OK, my relevant extra info: Theories about differing versions in Cooker, beta 1, from different sites don't really wash IMO because I have the same problem with the 8.2 network bootdisk; can others having the problem check this? It seems some people with the problem use 3Com cards, but i'm afraid i'll have to shoot this promising line down, since one of my systems on which it fails has a Genius PCMCIA card (uses the pcnet_cs module) and the other had some no-name card when I tried, I forget what module but it wasn't 3com. Our network setup - we have an ADSL connection which comes in through an ADSL modem / router (D-Link brand, I think) at 192.168.1.1 and is passed to a router / gateway (ActionTec Wireless-Ready Home Gateway) at 192.168.2.1, into which our systems (between two and five, depending) are plugged; on both systems that failed I tried DHCP and static IP addresses with the same crash. In the spirit of scientific enquiry, next time I try it i'll throw our new wireless LAN cards into the mix. =). Damn, hope we can fix this sometime soon; as I mentioned i'll try the install again when beta 2 comes out, to provide further info on my problems with both floppy and CD installs... -- adamw
Re: [Cooker] install problems
On Wednesday 31 July 2002 12:25 pm, you wrote: > Igor Izyumin <[EMAIL PROTECTED]> writes: > > 1. The network.img reports that it's for 8.2 and exits abnormally after > > you tell it the IP addresses or tell it to use DHCP. Using 3c59x. > > Ouch, you too? What is your hardware? > > > 4. Also, I think the user should be able to choose between quiet and > > regular startup. It is hard to troubleshoot errors and track down > > booting slowdowns when they don't show up! > > Pixel, could sound nice, why not "linux-noquiet" instead of > "linux-nonfb"? Is easy to do with existing tools: 1. To disable bootsplash, simply create a new section in lilo.conf which is identical to the one with the label 'linux' and change the label to say 'nobootsplash', 2. if you want to see the start up messages, just remove the quiet option in the append line, again in lilo.conf. just my 2 cents, Dave
Re: [Cooker] install problems
On Wednesday 31 July 2002 05:13 pm, Roland wrote: > Me too, I have done a network installation with a 3com 509 without > problems. The md5sums for the network.img in 9.0 beta1 and cooker are different. Could that be why? I was having problems with beta1. -- -- Igor
Re: [Cooker] install problems
On Wednesday 31 July 2002 02:26 pm, Andy Neillans wrote: > > If I've been following the discussion successfully, > > people are having problems with network.img? > > > > I'm using it quite successfully with newest Cooker > > with both 8139too and 3c905C-TX network cards. > > You follow it right - can I ask a silly question - which mirror / site > did you use to get the cooker build from? I used ftp://ftp.chello.se/pub/Linux/Mandrake-iso/i586/ to get the ISO images for 9.0beta1. I'm having the same problem, with a 3com card. MD5 sums: 1ac4f14dcc71a0a2ed7ef56264e95551 MandrakeLinux-9.0beta1-CD1.i586.iso 198e3de1978111945462ea6e213cc35e MandrakeLinux-9.0beta1-CD2.i586.iso (didn't download the third image) -- -- Igor
