Re: [Cooker] Installer suggestion

2003-08-03 Thread Pixel
David Walser <[EMAIL PROTECTED]> writes:

> Given that, it seems to me the best thing for services
> we don't want enabled by default on installation, is
> to just have them not run _post_service in the SPEC
> file.  They'll get chkconfig --add run when they're
> enabled, and they don't lose the list of runlevels
> they should be run in.

agreed (i don't see any pb doing so, except having rpmlint whining,
but that's ok :)

for example, packages that don't a working default config file should
do this..



Re: [Cooker] Installer suggestion

2003-08-02 Thread David Walser
--- Pixel <[EMAIL PROTECTED]> wrote:
> David Walser <[EMAIL PROTECTED]> writes:
> 
> > > maybe we could disable nfs by default, agreed.
> > > 
> > > for the others, i don't know :-/
> > > if you are right, I do agree they should not be
> > > running by default,
> > > and it's a bug. And you should report to the
> > > maintainers.
> > 
> > So the package decides not drakx?  What do the
> > packagers have to do to change it?
> 
> % grep chkconfig /etc/init.d/*
> ...
> /etc/init.d/portmap:# chkconfig: 345 11 89
> ...
> /etc/init.d/ypserv:# chkconfig: - 16 84
> ...
> 
> - portmap will run by default at runlevels 3, 4 and
> 5
> - ypserv will not run by default (notice the "-")

I was just looking into this again, and I'm not sure I
see why that's the best way to not have something
start by default when it's installed, as opposed to
just having the SPEC file not run _post_service.

By changing the first part of the chkconfig line to -,
you lose that information: what runlevels should the
service be started in if it is used.

All _post_service does anyway is run chkconfig --add,
but when you enable a service in drakxservices, it
runs that anyway.  If the init script has the -, it'll
just enable the service for runlevels 3 and 5.

Given that, it seems to me the best thing for services
we don't want enabled by default on installation, is
to just have them not run _post_service in the SPEC
file.  They'll get chkconfig --add run when they're
enabled, and they don't lose the list of runlevels
they should be run in.

__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com



Re: [Cooker] Installer: text issues

2003-02-17 Thread Pixel
John Allen <[EMAIL PROTECTED]> writes:

> The "Choose Packages to install" is to long to fit, please change it to 
> "Choose Packages"

hum, you cheater is still using the "expert" option in bootloader :)

ok, hiding it ;p
(that's the way it is in standard install)




Re: [Cooker] Installer suggestion

2003-02-02 Thread David Walser
--- Pixel <[EMAIL PROTECTED]> wrote:
> David Walser <[EMAIL PROTECTED]> writes:
> 
> [...]
> 
> > > % grep chkconfig /etc/init.d/*
> > > ...
> > > /etc/init.d/portmap:# chkconfig: 345 11 89
> > > ...
> > > /etc/init.d/ypserv:# chkconfig: - 16 84
> > > ...
> > > 
> > > - portmap will run by default at runlevels 3, 4
> and
> > > 5
> > > - ypserv will not run by default (notice the
> "-")
> > 
> > And that won't break chkconfig?  If you in the
> future
> > chkconfig --add whatever by hand (or
> drakxservices),
> > how will it know what runlevels to add it to?
> 
> redhat has "-" for most of its services, and in that
> case they use
> "chkconfig --level 35 the_service"

So I guess it doesn't break drakxservices.

> > Is this really the correct way to not have a
> service
> > activated automatically after installation? 
> 
> it is!

Thank you Pixel!

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com




Re: [Cooker] Installer suggestion

2003-02-02 Thread Pixel
David Walser <[EMAIL PROTECTED]> writes:

[...]

> > % grep chkconfig /etc/init.d/*
> > ...
> > /etc/init.d/portmap:# chkconfig: 345 11 89
> > ...
> > /etc/init.d/ypserv:# chkconfig: - 16 84
> > ...
> > 
> > - portmap will run by default at runlevels 3, 4 and
> > 5
> > - ypserv will not run by default (notice the "-")
> 
> And that won't break chkconfig?  If you in the future
> chkconfig --add whatever by hand (or drakxservices),
> how will it know what runlevels to add it to?

redhat has "-" for most of its services, and in that case they use
"chkconfig --level 35 the_service"

> 
> Is this really the correct way to not have a service
> activated automatically after installation? 

it is!





Re: [Cooker] Installer suggestion

2003-02-01 Thread David Walser
--- Pixel <[EMAIL PROTECTED]> wrote:
> David Walser <[EMAIL PROTECTED]> writes:
> 
> > > maybe we could disable nfs by default, agreed.
> > > 
> > > for the others, i don't know :-/
> > > if you are right, I do agree they should not be
> > > running by default,
> > > and it's a bug. And you should report to the
> > > maintainers.
> > 
> > So the package decides not drakx?  What do the
> > packagers have to do to change it?
> 
> % grep chkconfig /etc/init.d/*
> ...
> /etc/init.d/portmap:# chkconfig: 345 11 89
> ...
> /etc/init.d/ypserv:# chkconfig: - 16 84
> ...
> 
> - portmap will run by default at runlevels 3, 4 and
> 5
> - ypserv will not run by default (notice the "-")

And that won't break chkconfig?  If you in the future
chkconfig --add whatever by hand (or drakxservices),
how will it know what runlevels to add it to?

Is this really the correct way to not have a service
activated automatically after installation?  Or what
what Buchan suggested right, to just not use
%_post_service (remember if the daemon is running it
still has to be restarted on package upgrade)?

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com




Re: [Cooker] Installer failed to install bootloader

2002-09-23 Thread Guillaume Cottenceau

-L- <[EMAIL PROTECTED]> writes:

> 2 out of 5 times that i have installed mandrake9.0RC3 the installer
> fails to install the bootloader because it requests for it on CD1,When
> you put cd1 it will not find it on there and keep requesting. So you
> have to restart the install or boot off a floppy. I believe the
> bootloader is on CD3.

Do you have a Video/TV card by any chance?

-- 
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/




Re: [Cooker] Installer failed to install bootloader

2002-09-23 Thread Guillaume Cottenceau

"H. Narfi Stefansson" <[EMAIL PROTECTED]> writes:

> On Sunday 22 September 2002 15:16, Todd Lyons wrote:
> > -L- wrote on Sat, Sep 21, 2002 at 10:31:05PM -0500 :
> > > 2 out of 5 times that i have installed mandrake9.0RC3 the installer
> > > fails to install the bootloader because it requests for it on CD1,When
> > > you put cd1 it will not find it on there and keep requesting. So you
> > > have to restart the install or boot off a floppy. I believe the
> > > bootloader is on CD3.
> >
> > No, the lilo rpm is on CD1, the code that instantiates it is on the
> > ramdisk that got loaded from CD1.  If it asks for CD1, that means that
> > something didn't get installed earlier in the install process, but at
> > this point, it's really too late to go back to CD's (that's why lots of
> > things are copied to a temporary cache directory during the install)
> >
> > Blue skies...   Todd
> 
> Guillaume, isn't the same thing going on there as I reported?

I don't know; the culprit was buggy handling of bttv cards.


-- 
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/




Re: [Cooker] Installer failed to install bootloader

2002-09-22 Thread H. Narfi Stefansson

On Sunday 22 September 2002 15:16, Todd Lyons wrote:
> -L- wrote on Sat, Sep 21, 2002 at 10:31:05PM -0500 :
> > 2 out of 5 times that i have installed mandrake9.0RC3 the installer
> > fails to install the bootloader because it requests for it on CD1,When
> > you put cd1 it will not find it on there and keep requesting. So you
> > have to restart the install or boot off a floppy. I believe the
> > bootloader is on CD3.
>
> No, the lilo rpm is on CD1, the code that instantiates it is on the
> ramdisk that got loaded from CD1.  If it asks for CD1, that means that
> something didn't get installed earlier in the install process, but at
> this point, it's really too late to go back to CD's (that's why lots of
> things are copied to a temporary cache directory during the install)
>
> Blue skies... Todd

Guillaume, isn't the same thing going on there as I reported?
My message: 
http://marc.theaimsgroup.com/?l=mandrake-cooker&m=103241096406420&w=2
GC's reply:
http://marc.theaimsgroup.com/?l=mandrake-cooker&m=103243775726447&w=2

My bug report has hopefully been solved already.

Narfi.




Re: [Cooker] Installer failed to install bootloader

2002-09-22 Thread Todd Lyons

-L- wrote on Sat, Sep 21, 2002 at 10:31:05PM -0500 :
> 2 out of 5 times that i have installed mandrake9.0RC3 the installer
> fails to install the bootloader because it requests for it on CD1,When
> you put cd1 it will not find it on there and keep requesting. So you
> have to restart the install or boot off a floppy. I believe the
> bootloader is on CD3.

No, the lilo rpm is on CD1, the code that instantiates it is on the
ramdisk that got loaded from CD1.  If it asks for CD1, that means that
something didn't get installed earlier in the install process, but at
this point, it's really too late to go back to CD's (that's why lots of
things are copied to a temporary cache directory during the install)

Blue skies...   Todd
-- 
   MandrakeSoft USA   http://www.mandrakesoft.com
Mandrake: An amalgam of good ideas from RedHat, Debian, and MandrakeSoft.
All in all, IMHO, an unbeatable combination.   --Levi Ramsey on Cooker ML
   Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-12mdk



msg76338/pgp0.pgp
Description: PGP signature


Re: [Cooker] installer got stuck in a loop

2002-09-19 Thread Guillaume Cottenceau

"H. Narfi Stefansson" <[EMAIL PROTECTED]> writes:

> RC3: Just before installing the bootloader, the installer got stuck in a 
> loop, it kept asking for installation cd 1, I put it in, it ejected it and 
> asked for it again. We argued like this for a while, I tried to put all 3 
> of the CDs in several times and I ended up having to hit cancel.
> 
> Things went downhill from there, and I ended up having to reboot. 
> The short story is that I received messages about: 
> 1) "mkinitrd failed"

Ok, thanks, after more brainstorming we guessed what happened.
It's fixed in the CVS. Thanks!

-- 
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/




Re: [Cooker] installer got stuck in a loop

2002-09-19 Thread Guillaume Cottenceau

"H. Narfi Stefansson" <[EMAIL PROTECTED]> writes:

> RC3: Just before installing the bootloader, the installer got stuck in a 
> loop, it kept asking for installation cd 1, I put it in, it ejected it and 
> asked for it again. We argued like this for a while, I tried to put all 3 
> of the CDs in several times and I ended up having to hit cancel.
>
> Things went downhill from there, and I ended up having to reboot. 
> The short story is that I received messages about: 
> 1) "mkinitrd failed"

Narfi, thanks for your bugreport.

Till -> I've intensively reviewed the bug report
(http://www.cs.wisc.edu/~narfi/9.0RC3failure/report.bug.gz), it
seems that right after the printer configuration, the install
stops gpm, portmap, and rwho services then tries to create an
initrd. By any chance, do you know where it may come from? I
tried to review the installer code but couldn't find who is
actually stopping these services and who calls mkinitrd...

As a workaround we will modprobe "loop" right after
format-mount'ing so that if it happens again, the install might
be able to not fail miserably but it's just an horrible temporary
hack.

Also, it seems that the bttv configuration made an "use
standalone" during install which is forbidden and dangerous -
titi agreed to remove it for now, so it should maybe fix a few
other side-effect problems.


-- 
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/




Re: [Cooker] installer got stuck in a loop (no loopback found!)

2002-09-19 Thread Ben Reser

On Thu, Sep 19, 2002 at 02:47:26AM -0400, Andrew Bielecki wrote:
> Hi,
> The only time I had this problem if I try to upgrade kernel twice (or
> more) without rebooting the system and removed older kernels. If the
> loop back device will get removed (auto cleaned), then the second time
> you try to upgrade kernel the system can't find loopback driver for the
> current running kernel.

Maybe it's more like a problem with upgrading MAKEDEV or dev and not
rebooting before upgrading the kernel?  Or some other interaction with
those packages?

-- 
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org

Never take no as an answer from someone who isn't authorized to say yes.




RE: [Cooker] installer got stuck in a loop (no loopback found!)

2002-09-18 Thread Andrew Bielecki

Hi,
The only time I had this problem if I try to upgrade kernel twice (or
more) without rebooting the system and removed older kernels. If the
loop back device will get removed (auto cleaned), then the second time
you try to upgrade kernel the system can't find loopback driver for the
current running kernel.

Andrew Bielecki

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of H. Narfi Stefansson
Sent: Thursday, September 19, 2002 12:33 AM
To: [EMAIL PROTECTED]
Subject: [Cooker] installer got stuck in a loop

RC3: Just before installing the bootloader, the installer got stuck in a

loop, it kept asking for installation cd 1, I put it in, it ejected it
and 
asked for it again. We argued like this for a while, I tried to put all
3 
of the CDs in several times and I ended up having to hit cancel.

Things went downhill from there, and I ended up having to reboot. 
The short story is that I received messages about: 
1) "mkinitrd failed"
2) "isa ??? failed" in drakx
3) "no loopback found" or something similar to that. That's when I had
no 
option but to reboot.

I copied the logs from /root/drakx/, they are accessible at:

http://www.cs.wisc.edu/~narfi/9.0RC3failure/ddebug.log.gz
http://www.cs.wisc.edu/~narfi/9.0RC3failure/install.log.gz
http://www.cs.wisc.edu/~narfi/9.0RC3failure/report.bug.gz
 and will stay there until 9.0 is released

Something similar happened to me in one setup of RC2, but I tried to 
reproduce it, but couldn't and I lost the /root/drakx/* files from the 
failed installation.

Narfi.






Re: [Cooker] Installer won't upgrade on "dirty" filesystems

2002-09-12 Thread J. Greenlees

gee I saw that message a lot, when looking at Red Hat 7.2
got no mountable root partition message, went and bought Mandrake 8.1 
from local store because of it. ( currently running 8.2 power pack )

Hal Black wrote:
> My 8.2 machine ended up having dirty filesystems after rebooting becayse 
> of bug in the network drive shutdown code in 8.2.  When I tried to 
> upgrade this system, 9.0RC2's installer couldnt' find the / filesystem 
> to upgrade.  I assume this is because it was dirty.  The problem went 
> away and I was able to upgrade on these filesystems after hacking out 
> parts of the shutdown script.
> 
> The message given wasn't very informative.  It was something like 
> "unable to find / filesystem" or "unable to find mandrake linux 
> installation"  It would have been better to say - "all filesystems need 
> repair before installation" (or better yet ask, fsck & repair them, but 
> problably not time for that for 9.0).
> 
> 
> 






Re: [Cooker] Installer suggestion

2002-08-16 Thread Nick Brown

http://lisa-home.sourceforge.net/src/lisa.mandrake
has init scripts for lisa. This is mandrake specfic (though it was written for 
8.0)
Thre are also init scripts for redhat (7.2, 7.3) and suse (7.1 )listed at
 http://lisa-home.sourceforge.net/download.html

Perhaps Madrake could include this init script (or a updated one) for lisa, so 
that as you said it works on startup. (it did take me a while to figure out 
why konqueror did not work to browser lans and how to fix it)
If mandrake included a init script for this it would make it much easier for 
people.

thanks,
Nick

Gary Greene wrote:

> On Friday 16 August 2002 05:58 pm, David Walser wrote:
>> --- Mark Piper <[EMAIL PROTECTED]> wrote:
>> > And perhaps we should have LISa AT LEAST LISTED in
>> > the services, if not
>> > on by default, so that an inexperienced user will be
>> > able to see
>> > something aside from an error message when clicking
>> > on Konqueror's LAN
>> > browser.
>> >
>> > It has a useful default.  Turn off the port
>> > scanning.  Enable the search
>> > using nmblookup only.  Then you'll see computers
>> > like you would in
>> > Windows.
>>
>> Can you write an init script that would do this?  If
>> so, maybe Laurent would be willing to include it.
> 
> SuSE has an init script for this. If I had my SuSE box here I'd get it to
> you...
> 

-- 
<[EMAIL PROTECTED]> IOS Development, Cisco Systems UK.




Re: [Cooker] Installer suggestion

2002-08-16 Thread Gary Greene

On Friday 16 August 2002 05:58 pm, David Walser wrote:
> --- Mark Piper <[EMAIL PROTECTED]> wrote:
> > And perhaps we should have LISa AT LEAST LISTED in
> > the services, if not
> > on by default, so that an inexperienced user will be
> > able to see
> > something aside from an error message when clicking
> > on Konqueror's LAN
> > browser.
> >
> > It has a useful default.  Turn off the port
> > scanning.  Enable the search
> > using nmblookup only.  Then you'll see computers
> > like you would in
> > Windows.
>
> Can you write an init script that would do this?  If
> so, maybe Laurent would be willing to include it.

SuSE has an init script for this. If I had my SuSE box here I'd get it to 
you...

-- 
Gary 
 
Sent from seele.gvsu.edu
  6:32pm  up  1:23,  2 users,  load average: 0.64, 0.28, 0.20
 
=
Founder GVLUG.   
Chief Systems Architect, S4, Inc. - OS Department.   
 -==-
Project Lead for the Sentinel Linux OS Project (KOMODO)  
Chairman and Project Lead of the E-media Committee of AltReal.   
PHONE : 331-0542 
EMAIL : [EMAIL PROTECTED]   
[EMAIL PROTECTED] 
[EMAIL PROTECTED] 
 
--changing the code of the Virtual Human Brain FS Driver...  
Mounting /dev/brain0 is still causing problems...
 
Here's the error:
 
#mounting local filesystems[   OK   ]
#Virtual Human Brain Driver v0.0.5 (EXPERIMENTAL) R/W fs module  
#Virtual Nerve Node Driver v0.4.1 (EXPERIMENTAL) R/W FS module   
#Insmod Adaptive Technology Device module..[   OK   ]
#Writing Sync state to Journalled VHBFS[   OK   ]

Kernel Sys Oops.. Flushing registers.. Back-trace follows..  
=





Re: [Cooker] Installer suggestion

2002-08-16 Thread David Walser

--- Mark Piper <[EMAIL PROTECTED]> wrote:
> And perhaps we should have LISa AT LEAST LISTED in
> the services, if not
> on by default, so that an inexperienced user will be
> able to see
> something aside from an error message when clicking
> on Konqueror's LAN
> browser.
> 
> It has a useful default.  Turn off the port
> scanning.  Enable the search
> using nmblookup only.  Then you'll see computers
> like you would in
> Windows.

Can you write an init script that would do this?  If
so, maybe Laurent would be willing to include it.

__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com




Re: [Cooker] Installer suggestion

2002-08-16 Thread Mark Piper

On Thu, 2002-08-15 at 18:09, Buchan Milne wrote:
> 
> 
> [EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
> >
> >David Walser <[EMAIL PROTECTED]> writes:
> >> > - only services that have a useful default
> >> > configuration are on by
> >> > default
> >>
> >> Wrong, apcupsd, dhcpd, jabber, named, nfs, ntpd, smb,
> >> ypbind, and maybe mysql and ldap (can't remember) are
> >> on by default if you install them, and they need to be
> >> configured before they're useful.
> 
> But what are the chances that you're going to install apcupsd and not use it? And
> ntpd can be configured during install.
> 
> >hum, smb has a useful default configuration, no? (home exported)

And perhaps we should have LISa AT LEAST LISTED in the services, if not
on by default, so that an inexperienced user will be able to see
something aside from an error message when clicking on Konqueror's LAN
browser.

It has a useful default.  Turn off the port scanning.  Enable the search
using nmblookup only.  Then you'll see computers like you would in
Windows.





Re: [Cooker] Installer suggestion

2002-08-15 Thread Pixel

David Walser <[EMAIL PROTECTED]> writes:

> I thought that field let chkconfig know what runlevels
> to enable the service for with chkconfig service on. 
> How does it know then?

well it's quite ugly but that's redhat you've done it so.

they have decided to put "-" everywhere, and they use 
"chkconfig --level 35 on" to enable a service





Re: [Cooker] Installer suggestion

2002-08-15 Thread David Walser

--- Pixel <[EMAIL PROTECTED]> wrote:
> David Walser <[EMAIL PROTECTED]> writes:
> 
> > > maybe we could disable nfs by default, agreed.
> > > 
> > > for the others, i don't know :-/
> > > if you are right, I do agree they should not be
> > > running by default,
> > > and it's a bug. And you should report to the
> > > maintainers.
> > 
> > So the package decides not drakx?  What do the
> > packagers have to do to change it?
> 
> % grep chkconfig /etc/init.d/*
> ...
> /etc/init.d/portmap:# chkconfig: 345 11 89
> ...
> /etc/init.d/ypserv:# chkconfig: - 16 84
> ...
> 
> - portmap will run by default at runlevels 3, 4 and
> 5
> - ypserv will not run by default (notice the "-")

I thought that field let chkconfig know what runlevels
to enable the service for with chkconfig service on. 
How does it know then?

__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com




Re: [Cooker] Installer suggestion

2002-08-15 Thread Pixel

David Walser <[EMAIL PROTECTED]> writes:

> > maybe we could disable nfs by default, agreed.
> > 
> > for the others, i don't know :-/
> > if you are right, I do agree they should not be
> > running by default,
> > and it's a bug. And you should report to the
> > maintainers.
> 
> So the package decides not drakx?  What do the
> packagers have to do to change it?

% grep chkconfig /etc/init.d/*
...
/etc/init.d/portmap:# chkconfig: 345 11 89
...
/etc/init.d/ypserv:# chkconfig: - 16 84
...

- portmap will run by default at runlevels 3, 4 and 5
- ypserv will not run by default (notice the "-")






Re: [Cooker] Installer suggestion

2002-08-15 Thread David Walser

--- Pixel <[EMAIL PROTECTED]> wrote:
> David Walser <[EMAIL PROTECTED]> writes:
> 
> > > - only services that have a useful default
> > > configuration are on by
> > > default
> > 
> > Wrong, apcupsd, dhcpd, jabber, named, nfs, ntpd,
> smb,
> > ypbind, and maybe mysql and ldap (can't remember)
> are
> > on by default if you install them, and they need
> to be
> > configured before they're useful.
> 
> hum, smb has a useful default configuration, no?
> (home exported)

Ok.

> maybe we could disable nfs by default, agreed.
> 
> for the others, i don't know :-/
> if you are right, I do agree they should not be
> running by default,
> and it's a bug. And you should report to the
> maintainers.

So the package decides not drakx?  What do the
packagers have to do to change it?

__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com




Re: [Cooker] Installer suggestion

2002-08-15 Thread Pixel

David Walser <[EMAIL PROTECTED]> writes:

> > - only services that have a useful default
> > configuration are on by
> > default
> 
> Wrong, apcupsd, dhcpd, jabber, named, nfs, ntpd, smb,
> ypbind, and maybe mysql and ldap (can't remember) are
> on by default if you install them, and they need to be
> configured before they're useful.

hum, smb has a useful default configuration, no? (home exported)

maybe we could disable nfs by default, agreed.

for the others, i don't know :-/
if you are right, I do agree they should not be running by default,
and it's a bug. And you should report to the maintainers.




Re: [Cooker] Installer suggestion

2002-08-13 Thread andre

On Tuesday 13 August 2002 04:04, Austin Acton wrote:
> Thanks for your support.
> You have good ideas, but some of them won't fly.
>
> We NEED rpm to keep things uniform.  Easy to upgrade, easy to replace,
> (not-so)easy to build, and the same for every package.  Seriously.  If
> there is ANYTHING that linux needs to survive it's a bit of
> standardization (even WITHIN each distro).  Having two package systems
> could be a nightmare.
>
> Also, you CAN just download ISO1 and do the rest via ftp/http.  I've
> done it many times.  You can even just download one floppy and install
> everything by ftp!  (Thanks to rpm...)
>
> It would be nice to have a "semi-network" install option on CD1 though.
> You boot CD1, pick some sort of hybrid install with VERY few options and
> menus and such.  This installs basesystem, X, a window manager, and the
> "draks" and lets you select a mirror, and CONFIGURES the mirror in urpmi
> BEFORE rebooting.  Then you reboot and install the rest from you new
> super-speedy Mandrake system.
>
> Great idea.
>
> Austin
>

I think the idea is something like http://www.virtual-linux.org/. Which is 
AFAIK just a standard and not so basic Mandrake installation which is tarred 
up from a harddisk installation and put on a cd and with some foo works. If 
you would untar it on a harddisk and removed the foo you couldn't tell the 
difference between it and a normal way of installing




Re: [Cooker] Installer suggestion (one more)

2002-08-13 Thread Pixel

[EMAIL PROTECTED] writes:

> Cheers Pixel. Does this mean the screen is gone or do you simply "tick" the
> groups of packages you want to upgrade and if they are installed it adds up
> the upgrade size and compares it to the size available??

it computes the size as done in 8.2, ie it does:
  sum(new_packages) - sum(upgraded_packages)

and compares it to the size available. (which must be what you said,
but i'm not completly sure :)




Re: [Cooker] Installer suggestion (one more)

2002-08-13 Thread newslett

Cheers Pixel. Does this mean the screen is gone or do you simply "tick" 
the groups of packages you want to upgrade and if they are installed it 
adds up the upgrade size and compares it to the size available??

Hasta~~

Jason

Pixel wrote:
> [EMAIL PROTECTED] writes:
> 
> 
>>And I have one more suggestion. I ran into this while upgrading via CD from
>>9.0 B1 to B2...when doing an "expert upgrade" and it comes to package
>>selection time it gets VERY confusing. If you select all the groups of
>>packages you want to upgrade by ticking next to them (and turn off individual
>>package selection) the installer ADDS the space needed to that for the space
>>needed to upgrade the already installed packages often making the amount
>>calculated more that the partition size.
> 
> 
> bug fixed in cooker
> 





Re: [Cooker] Installer suggestion

2002-08-13 Thread David Walser


--- Pixel <[EMAIL PROTECTED]> wrote:
> - RedHat has (very) few packages which explain why
> "Install All" is no
> such big deal for them (hell, they don't even have
> "rxvt" anymore!)

Yeah, I noticed that.  RedHat sucks!  No xlockmore
either!

> - only services that have a useful default
> configuration are on by
> default

Wrong, apcupsd, dhcpd, jabber, named, nfs, ntpd, smb,
ypbind, and maybe mysql and ldap (can't remember) are
on by default if you install them, and they need to be
configured before they're useful.

__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com




Re: [Cooker] Installer suggestion (one more)

2002-08-13 Thread Pixel

[EMAIL PROTECTED] writes:

> And I have one more suggestion. I ran into this while upgrading via CD from
> 9.0 B1 to B2...when doing an "expert upgrade" and it comes to package
> selection time it gets VERY confusing. If you select all the groups of
> packages you want to upgrade by ticking next to them (and turn off individual
> package selection) the installer ADDS the space needed to that for the space
> needed to upgrade the already installed packages often making the amount
> calculated more that the partition size.

bug fixed in cooker




Re: [Cooker] Installer suggestion

2002-08-13 Thread Pixel

Austin Acton <[EMAIL PROTECTED]> writes:

> I only have one request to add to v9.0 in the installer. I want an
> "Install All" button - ala Redhat. Disks are cheap. The time required to
> get the system fully operational isn't. Having an install all capability
> would be a real productivity enhancer for one-off configurations.

- installation time is not linear with the size to install. It grows
slower with big installs.

- moreover many packages are dangerous, doing various things you would
not want.

- if you really want a "Install All", you can have it quite easily
after install.

- RedHat has (very) few packages which explain why "Install All" is no
such big deal for them (hell, they don't even have "rxvt" anymore!)

> It would be even nicer if all extra services beyond those required to
> normally operate the system are OFF by default when installed. That way,
> you don't soak up memory and add more security holes. (At least until
> the software is configured

- we've trolling on the choice to have services on by default. Cf
cooker archives

- only services that have a useful default configuration are on by
default




Re: [Cooker] Installer suggestion (and a modest proposal about that)

2002-08-12 Thread allen


Quick additional thought...

Maybe now IS a good time to bring this up...

DVD...

That would give enough room to have one of more base images, kernel selection,
plus everything that needs installing while you're already up and running...

Don't forget though some HDD needs available for run-time so a minimal base
must partition, fmt, and install some basic goodies so the running image has
a place for things to write.

Hmn...

Double hmn...

-AEF


On Monday 12 August 2002 11:45 pm, allen wrote:
> On Monday 12 August 2002 11:15 pm, Leon Brooks wrote:
>
>  minimal install cd1 with base file system that has rpm database of
> what is "rpm -ivh'd in advance into the base file system so it is rpm
> -Uvh-able"...






Re: [Cooker] Installer suggestion (and a modest proposal about that)

2002-08-12 Thread allen

On Monday 12 August 2002 11:15 pm, Leon Brooks wrote:

 minimal install cd1 with base file system that has rpm database of 
what is "rpm -ivh'd in advance into the base file system so it is rpm 
-Uvh-able"...

> If I did it that way (or the following way), I'd install a minimal amount
> of RPM information on/from the CD and nice -19 rebuild the indexes and
> stuff after the install.

rpm verify perhaps. The base file system should be "binary" diff match with
what is on the cd.  Either it worked or it didn't.  There should be no rebuild
stuff.  

Granted, some things would HAVE to be put on via RPM, but not the whole
dang thing that is common everywhere, and only where differences warrant... 
which X, which video, scsi, no scsi, which additional kernel, etc.,

Extreme difference can happen via rpm --erase... ;)  Easier to destroy than
to create...

 nice'd rpm install of everything else in the background

Hmn...

> Maybe it also caches reads from the CD onto the HDD so that as you pull
> your most-used stuff off the CD in the course of actually using it, it
> makes it to the HDD and doesn't need re-reading next time.

Not enough detail to know "why" exactly...   kinda sounds a little like 
sorcerer...  which I enjoy using, but has its own set of problems...
Not that it is a bad idea...  It's not what you do... but how you do it...

> Knoppix is already useful for offices wherein the entire place has been
> trashed with a virus. If Mandrake could install this way, you could walk in
> with a Mandrake CD and have people up and running within minutes, and
> permanently Mandrake'd within the hour.

Market study.  How likely, how much market share will this gain vs. will
it loose any ?  What is the cost justification ?  
"What cost, it is open source !" ?

> This could be done as a separate project to the `standard' Mandrake CD
> sets, released a month or two after 9.0, and take the world by storm.

What exactly ?  The idea about fixing up a whole virus nailed network ?  Or
the "distribution server" ?

> Additional wishlist items:
>
>  * Ability to configure a single workstation and use its RPM selection
>for all following.

There is supposed to be a create a floppy thing. I think I tried it before
and I think it worked.  Floppy has the package selection so when you
boot up another install cd on another machine, put the floppy in, you
just walk away and come back later...  ?

You mean this, but from sort of "network registry" / "install/update server" ?

>Imagery: power up virussed Windows box. 30 seconds later it is a
>working Mandrake machine. Walk to next machine, power it up. By the
>time you've powered up the 20th machine, the first is a fully
>installed standalone workstation.

So earlier you meant actually boot and actually RUN from CD until the
HDD is complete... ?   Heh...  are you a systems/software architect too ?

We're on the save wamelength methinks...

There would need to be either a selection mechanism what to boot
to support what wildly different hardware, or a few different CD1 
images...

> How say you? The perfect time to bring this up? 

I don't know when is a good time to bring up stuff like this...  Better to do 
it and beg forgiveness... I hope...

-AEF




Re: [Cooker] Installer suggestion (and a modest proposal about that)

2002-08-12 Thread Leon Brooks

On Tue, 13 Aug 2002 11:45, allen wrote:
> On Monday 12 August 2002 09:05 pm, Ryan Little wrote:
>>> 1.  Say CD1 is a minimal installer and a file system, rudimentary,
>>> ready to go.  ( And yes, I've actually created such a thing on contract
>>> for a company in the Northwest so I know this pretty well... )

>>> 2.  You do the "install" and partition, and format, and BL !

>> The only problem I could see with not having it in an RPM is if for some
>> reason it needed to be upgraded (i.e. a release upgrade on which the fs
>> changed, or a bug fix.) It's much easier to upgrade things with RPM (If
>> it's done correctly).

> Are you assuming there would be no rpm database of what is on the base
> file system IN the base file system ?

If I did it that way (or the following way), I'd install a minimal amount of 
RPM information on/from the CD and nice -19 rebuild the indexes and stuff 
after the install.

What I'd _really_ like to see is a CD that boots like Knoppix, autodetects 
everything in sight, asks enough questions to get a user up and your LAN etc 
running (and/or filches it from an existing Windows or Linux system), and 
then you just start using it.

When the system's been idle for a few seconds, it starts (niced) partitioning 
and copying stuff across from the running filesystem on the CD. If the user 
hits a key, moves the mouse, or has a busy app, the copying process is 
SIGSTOPped until shortly after all falls quiet again.

Maybe it also caches reads from the CD onto the HDD so that as you pull your 
most-used stuff off the CD in the course of actually using it, it makes it to 
the HDD and doesn't need re-reading next time.

This could easily be done with a temporary bitmap file on the HDD so it 
survives a reboot. When `stealth installation' is complete, the HDD 
partitions are remounted, pivotrooted or whatever so that the system is now 
running from the HDD, and the CD is ejected.

Knoppix is already useful for offices wherein the entire place has been 
trashed with a virus. If Mandrake could install this way, you could walk in 
with a Mandrake CD and have people up and running within minutes, and 
permanently Mandrake'd within the hour.

Another useful feature would be to nominate a machine as Keeper of the 
Install, so after it's installed and up (or before!) it offers an RO NFS 
share with an image of the CD on it, asks for each RPM CD in turn, and adds 
them to its collection. Then individual machines could be booted from a CD, 
remounted pretty much instantly on the NFS share, startup/install continues 
on NFS as from the CD, and the CD is ejected for use in the next machine. The 
RPMs are then available to both the `server' and newborn workstations for 
adding packages as required.

This could be done as a separate project to the `standard' Mandrake CD sets, 
released a month or two after 9.0, and take the world by storm.

+-+
| |
|  Do you like me enough to keep me?  |
| |
|   [ install ]   [ nag later ]   [ i'll call you ]   |
| |
+-+

Additional wishlist items:

 * Ability to configure a single workstation and use its RPM selection
   for all following.

 * Ability to deduce network card drivers from their ARP signature or
   MAC address, and either offer boot images for them to do all of the
   above, or make boot floppies to do same in case they don't have PXE
   or EtherBoot ROMs. As well as simplifying installation, you could
   make a whole trashed office functional (LTSP style RO from your
   server, with the option of making it permanent) in about ten
   minutes. (-:

   Imagery: power up virussed Windows box. 30 seconds later it is a
   working Mandrake machine. Walk to next machine, power it up. By the
   time you've powered up the 20th machine, the first is a fully
   installed standalone workstation.

How say you? The perfect time to bring this up? 

Cheers; Leon





Re: [Cooker] Installer suggestion

2002-08-12 Thread Igor Izyumin

On Monday 12 August 2002 09:04 pm, Austin Acton wrote:
> Thanks for your support.
> You have good ideas, but some of them won't fly.
>
> We NEED rpm to keep things uniform.  Easy to upgrade, easy to replace,
> (not-so)easy to build, and the same for every package.  Seriously.  If
> there is ANYTHING that linux needs to survive it's a bit of
> standardization (even WITHIN each distro).  Having two package systems
> could be a nightmare.

Are there any official specifications for Mandrake-compatible RPMs?  I wanted 
to make some once (Club, etc.), but the only thing I could find was the 
Mandrake RPM howto which seemed fairly vague and outdated.  Is anyone 
planning on updating that?
-- 
-- Igor




Re: [Cooker] Installer suggestion

2002-08-12 Thread allen



On Monday 12 August 2002 09:05 pm, Ryan Little wrote:
> > 1.  Say CD1 is a minimal installer and a file system, rudimentary, ready
> > to go.  ( And yes, I've actually created such a thing on contract for a
> > company in the Northwest so I know this pretty well... )
> >
> > 2.  You do the "install" and partition, and format, and BL !

> The only problem I could see with not having it in an RPM is if for some
> reason it needed to be upgraded (i.e. a release upgrade on which the fs 
> changed, or a bug fix.) It's much easier to upgrade things with RPM (If it's
> done correctly).


Um...

Are you assuming there would be no rpm database of what is on the base
file system IN the base file system ?

???

;)

-AEF




Re: [Cooker] Installer suggestion

2002-08-12 Thread Austin Acton

Thanks for your support.
You have good ideas, but some of them won't fly.

We NEED rpm to keep things uniform.  Easy to upgrade, easy to replace,
(not-so)easy to build, and the same for every package.  Seriously.  If
there is ANYTHING that linux needs to survive it's a bit of
standardization (even WITHIN each distro).  Having two package systems
could be a nightmare.

Also, you CAN just download ISO1 and do the rest via ftp/http.  I've
done it many times.  You can even just download one floppy and install
everything by ftp!  (Thanks to rpm...)

It would be nice to have a "semi-network" install option on CD1 though. 
You boot CD1, pick some sort of hybrid install with VERY few options and
menus and such.  This installs basesystem, X, a window manager, and the
"draks" and lets you select a mirror, and CONFIGURES the mirror in urpmi
BEFORE rebooting.  Then you reboot and install the rest from you new
super-speedy Mandrake system.

Great idea.

Austin

On Mon, 2002-08-12 at 21:39, allen wrote:
> 
> I would like to 2nd this concept.
> 
> 
> Also I would like to add a little something for some day in the future, 
> maybe...
> 
> Follow the thought, it would be too hard to describe otherwise...
> 
> 1.  Say CD1 is a minimal installer and a file system, rudimentary, ready to 
> go.  ( And yes, I've actually created such a thing on contract for a 
> company in the Northwest so I know this pretty well... )
> 
> 2.  You do the "install" and partition, and format, and BL !
> 
>  Your whole entire basic file system is copied over ready to go.
> 
> 3.  Reboot.
> 
> 4.  Now add the things you want.
> 
> How hard is that ?  
> 
> I don't want to start a flame thing, but compared to this sort of capability, 
> initially, I do not like rpm's.
> 
> This sort of "install" is a LOT faster, a LOT LOT faster.
> 
> Heck, you could even fit a few more architecture specific base file systems
> on there...  Maybe just X needs to "go on" the rpm way initially...
> 
> Is the rpms thing really so necessary all the way "from the beginning" ?
> 
> ( Humble and sincere question )
> 
> The other thing is that perhaps you really don't need to download a whole
> bunch of ISO's.  Maybe just part of one.  The rest can install itself as 
> needed over the net...  uprmi.addmedia (somewhere)  urpmi.finishinstalling ;)
> 
> ?
> 
> -AEF
> 
> 
> On Monday 12 August 2002 08:18 pm, Austin Acton wrote:
> 
> 
> 
> > Hello!
> >
> > I only have one request to add to v9.0 in the installer. I want an
> > "Install All" button - ala Redhat. Disks are cheap. The time required to
> > get the system fully operational isn't. Having an install all capability
> > would be a real productivity enhancer for one-off configurations.
> >
> > It would be even nicer if all extra services beyond those required to
> > normally operate the system are OFF by default when installed. That way,
> > you don't soak up memory and add more security holes. (At least until
> > the software is configured
> 





Re: [Cooker] Installer suggestion

2002-08-12 Thread Ryan Little


> 1.  Say CD1 is a minimal installer and a file system, rudimentary, ready to 
> go.  ( And yes, I've actually created such a thing on contract for a 
> company in the Northwest so I know this pretty well... )
> 
> 2.  You do the "install" and partition, and format, and BL !
> 
>  Your whole entire basic file system is copied over ready to go.
>/Snip/
> 
> This sort of "install" is a LOT faster, a LOT LOT faster.
I like your idea, install all the "base" system stuff in one shot, (ala a 

slackwareish tarball).

The only problem I could see with not having it in an RPM is if for some reason it 

needed to be upgraded (i.e. a release upgrade on which the fs changed, 

or a bug fix.) It's much easier to upgrade things with RPM (If it's done correctly).


Ryan
 





Re: [Cooker] Installer suggestion (one more)

2002-08-12 Thread newslett

And I have one more suggestion. I ran into this while upgrading via CD 
from 9.0 B1 to B2...when doing an "expert upgrade" and it comes to 
package selection time it gets VERY confusing. If you select all the 
groups of packages you want to upgrade by ticking next to them (and turn 
off individual package selection) the installer ADDS the space needed to 
that for the space needed to upgrade the already installed packages 
often making the amount calculated more that the partition size. To 
avoid this, you must untick everything then it calculates only the 
amount of space needed to upgrade the installed packages. I would 
venture to say this screen is not even necessary when doing an update as 
once installed packages are detected and updates on the CD are found to 
be available shouldn't it just start updating them??

I had to figure out what the heck the installer was doing before I could 
proceed. NOT good for newbies.

Cheers,

Jason

allen wrote:
> I would like to 2nd this concept.
> 
> 
> Also I would like to add a little something for some day in the future, 
> maybe...
> 
> Follow the thought, it would be too hard to describe otherwise...
> 
> 1.  Say CD1 is a minimal installer and a file system, rudimentary, ready to 
> go.  ( And yes, I've actually created such a thing on contract for a 
> company in the Northwest so I know this pretty well... )
> 
> 2.  You do the "install" and partition, and format, and BL !
> 
>  Your whole entire basic file system is copied over ready to go.
> 
> 3.  Reboot.
> 
> 4.  Now add the things you want.
> 
> How hard is that ?  
> 
> I don't want to start a flame thing, but compared to this sort of capability, 
> initially, I do not like rpm's.
> 
> This sort of "install" is a LOT faster, a LOT LOT faster.
> 
> Heck, you could even fit a few more architecture specific base file systems
> on there...  Maybe just X needs to "go on" the rpm way initially...
> 
> Is the rpms thing really so necessary all the way "from the beginning" ?
> 
> ( Humble and sincere question )
> 
> The other thing is that perhaps you really don't need to download a whole
> bunch of ISO's.  Maybe just part of one.  The rest can install itself as 
> needed over the net...  uprmi.addmedia (somewhere)  urpmi.finishinstalling ;)
> 
> ?
> 
> -AEF
> 
> 
> On Monday 12 August 2002 08:18 pm, Austin Acton wrote:
> 
> 
> 
>>Hello!
>>
>>I only have one request to add to v9.0 in the installer. I want an
>>"Install All" button - ala Redhat. Disks are cheap. The time required to
>>get the system fully operational isn't. Having an install all capability
>>would be a real productivity enhancer for one-off configurations.
>>
>>It would be even nicer if all extra services beyond those required to
>>normally operate the system are OFF by default when installed. That way,
>>you don't soak up memory and add more security holes. (At least until
>>the software is configured
> 
> 
> 





Re: [Cooker] Installer suggestion

2002-08-12 Thread allen


I would like to 2nd this concept.


Also I would like to add a little something for some day in the future, 
maybe...

Follow the thought, it would be too hard to describe otherwise...

1.  Say CD1 is a minimal installer and a file system, rudimentary, ready to 
go.  ( And yes, I've actually created such a thing on contract for a 
company in the Northwest so I know this pretty well... )

2.  You do the "install" and partition, and format, and BL !

 Your whole entire basic file system is copied over ready to go.

3.  Reboot.

4.  Now add the things you want.

How hard is that ?  

I don't want to start a flame thing, but compared to this sort of capability, 
initially, I do not like rpm's.

This sort of "install" is a LOT faster, a LOT LOT faster.

Heck, you could even fit a few more architecture specific base file systems
on there...  Maybe just X needs to "go on" the rpm way initially...

Is the rpms thing really so necessary all the way "from the beginning" ?

( Humble and sincere question )

The other thing is that perhaps you really don't need to download a whole
bunch of ISO's.  Maybe just part of one.  The rest can install itself as 
needed over the net...  uprmi.addmedia (somewhere)  urpmi.finishinstalling ;)

?

-AEF


On Monday 12 August 2002 08:18 pm, Austin Acton wrote:



> Hello!
>
> I only have one request to add to v9.0 in the installer. I want an
> "Install All" button - ala Redhat. Disks are cheap. The time required to
> get the system fully operational isn't. Having an install all capability
> would be a real productivity enhancer for one-off configurations.
>
> It would be even nicer if all extra services beyond those required to
> normally operate the system are OFF by default when installed. That way,
> you don't soak up memory and add more security holes. (At least until
> the software is configured





Re: [Cooker] Installer won't save package selection - LS120 drive

2002-02-22 Thread Pixel

"Vincent Meyer, MD" <[EMAIL PROTECTED]> writes:

> The installer doesn't want to save the package selection if the 
> floppy is an LS-120.  Says it's full, no room for the file.  WILL
> try and "update" installation later and attempt this again, and will
> take better notes. (hey, was 3AM.. was in no condition to take notes)

ok. I don't understand why it may go wrong. Install is trying to mount it as
vfat. This doesn't seem non LS-120 dependent.




Re: [Cooker] Installer - when vgahi doesn't work

2002-01-18 Thread François Pons

Vincent Meyer <[EMAIL PROTECTED]> writes:

> Hi,

Hi!

>   The install floppy is booted, if it can't display a graphic,
> it just displays the prompt for boot.  Problem is, if you DON'T hit
> F1 for help, then things like vgahi don't work.. of course to find 
> out what these options are.  Is there any way to make these work 
> WITHOUT hitting F1 first?

Maybe display is not updated when you press key, but there should be no
problem hitting vgahi and enter and booting. This is the same in graphic mode,
if you press vgahi (you don't see anything) and press enter, you should have it
(this is the same as typing rescue, ...).

If display is not updating in text mode, this is a bug to fix in syslinux
graphic patch.

François.




Re: [Cooker] Installer broken - HELP!!

2001-12-21 Thread Vincent Meyer

OK, so now it works, and I'm back in business again.  Odd thing -
the install worked, but all the pictures went away!

V.

On Thursday 20 December 2001 12:12 pm, you wrote:
> Hello
>
>   As of last night the installer bombs after package
> selection with the message:
>
> perl: rpmio_internal.h:410: c2f: Assertion `fd &&
> fd->magic=0x04463138' failed.
>
> It does this anywhere from 3 to 5 times when it tried
> to load a package.  It does this for ALL packages.
>
> Since this is the machine I get my e-mail on, I am
> unable to get any response there.. so please e-mail a
> copy to this yahoo address.
>
> Also, is it possible to install KDE3.0 beta from an
> install instead of 2.2 ?  If not, has anyone been able
> to install this without breaking everything?
>
> Vinny
>
> __
> Do You Yahoo!?
> Check out Yahoo! Shopping and Yahoo! Auctions for all of
> your unique holiday gifts! Buy at http://shopping.yahoo.com
> or bid at http://auctions.yahoo.com




Re: [Cooker] installer bug

2001-09-01 Thread François Pons

Vincent Meyer <[EMAIL PROTECTED]> writes:

> Hi, I know it's a minor bug, but passing the installer has a problem if you want
> to pass it something at the boot: prompt.
> 
> I install with vgahi vga=791.  If I do this after the boot: prompt it doesn't

Using vgahi together with vga=791 is somewhat redondant.

vgahi is already providing vga=791 on the command line.

> work... however, if I hit F1 first to bring up the help screen, THEN use it, it
> works.

Do you see the prompt ? You should have the boot image instead unless you BIOS
does not support VESA 1.2 640x480 in 256 colors (or you use hd.img)

Using F1 first switch to text mode (if you the image) and maybe BIOS prefer
initializing linear frame buffer from text mode instead of bank switched frame
buffer used to display the boot image.

> Also, help screen mentions vgalo, but not vgahi.

Don't you see a F2 - Advanced Help ?

Type it, you will find vgahi entry, but you may have if you are booting from
floppy to rebuild the floppy if you don't see anything.

François.




Re: [Cooker] installer title

2001-08-30 Thread Loic Paillotin




> Installer says "Mandrake Linux install 8.1". With my limited English
> knowledge I expect "Mandrake Linux 8.1 install". Version number applies
> to OS not to installer?
> 
> -andrej
> 
yes you're right. 





Re: [Cooker] Installer sets wrong partition-label, and other "small" inst. problems

2001-08-29 Thread Pixel

Claudio <[EMAIL PROTECTED]> writes:

[...]

> swap  --> primary --> hda1 OK
> /boot --> primary --> hda5 SHOULD BE HDA2!!!
> / --> primary --> hda6 BAD... SHOULD BE HDA3...
> if I try
> /boot --> extended--> hda5 OK
> So I can only make ONE primary partition now?

oops, was a typo. fixed.

> 
> 2.
> "Disable automount" is still missing during configuration (I wish only to 
> remember... I know you're working on it ;o))

it will be back... at least when we have supermount back :p




Re: [Cooker] installer error msg

2001-03-11 Thread Pixel

David Hart <[EMAIL PROTECTED]> writes:

>   At the summary section of the installer (current cooker), both my sound
> cards are shown as having been correctly detected. Nice! But, when I click the
> button for either of them, I get the msg, "An error occurred. Not a CODE
> reference."

fixed, thanks.

> I don't know what clicking those buttons is supposed to do, but I'm
> fairly sure it's not just supposed to give an error ;)

well, it doesn't do anything for now...




Re: [Cooker] installer error msg

2001-03-10 Thread Michael Brown

On Fri, 9 Mar 2001, David Hart wrote:
>   At the summary section of the installer (current cooker), both my sound
> cards are shown as having been correctly detected. Nice! But, when I click the
> button for either of them, I get the msg, "An error occurred. Not a CODE
> reference." I don't know what clicking those buttons is supposed to do, but I'm
> fairly sure it's not just supposed to give an error ;)

I don't know if this is happening to anyone else, or just to me:

I have now received over 500 copies of the above message.  Can someone
PLEASE fix this mail loop!!!

Michael






Re: [Cooker] Installer - why no expert mode?

2001-01-22 Thread Pixel

Peter Ruskin <[EMAIL PROTECTED]> writes:

> Updated cooker again this weekend - from hd.img.  I wanted to choose expert 
> development upgrade as usual, but the only options I had were "Recommended" 
> and "Customized".  
> 
> I chose "Customized" and selected "Individual package selection" with the 
> slider at 100%.  I wasn't given the opportunity to select the packages, 
> however, the damned thing just went ahead with updating.
> 
> Although the update appears to have run otherwise without problems (good 
> work), now I have the onerous task of manually removing all the crap I didn't 
> want.
> 
> Can we please get this fixed?

done, will be uploaded. But expect pbs, currently removing the Custom mode...




Re: [Cooker] Installer says it's formatting when you chose Upgrade

2000-12-09 Thread Peter Ruskin

On Saturday 09 December 2000 18:53, Pixel wrote:
> Peter Ruskin <[EMAIL PROTECTED]> writes:
> > Cooker Expert Upgrade Development (almost full) - using hd.img.
> > VERSION: Linux-Mandrake Cooker-i586 20001209  4:01
> >
> > This was the best upgrade yet, as far as the installer is concerned, the
> > only blemish being that scary dialog that says "Please wait. 
> > Formatting...".  The menu item on the left pane says "Miscellaneous" at
> > this stage.  Please reflect in the dialog what is happening, otherwise
> > I'll never believe you when you tell me you are formatting.
>
> ok, i modify this. The popup will now appears only if needed.
Thanks Pixel.
-- 
   
Peter Ruskin,  Wrexham, UK  <[EMAIL PROTECTED]> 
Preferred desktop environment KDE 1.1.2
  Linux 2.2.17-21mdkWin4Lin, Uptime 1 hour 21 minutes




Re: [Cooker] Installer says it's formatting when you chose Upgrade

2000-12-09 Thread Alan Olsen

On Sat, 9 Dec 2000, Peter Ruskin wrote:

> Cooker Expert Upgrade Development (almost full) - using hd.img.
> VERSION: Linux-Mandrake Cooker-i586 20001209  4:01
> 
> This was the best upgrade yet, as far as the installer is concerned, the only 
> blemish being that scary dialog that says "Please wait.  Formatting...".  The 
> menu item on the left pane says "Miscellaneous" at this stage.  Please 
> reflect in the dialog what is happening, otherwise I'll never believe you 
> when you tell me you are formatting.

That exists in 7.2 as well.  (You get that dialog if you are formatting or
not formatting.)  Scared the crap out of me when I first got the message.
I had about 20 gigs of unbacked up files on the primary drive.

I would also like to see added code where the upgrade would check for an
existing set of RPM databases and do a "rpm --rebuilddb" before starting
to add files.  This will help clean up accumulated cruft in the databases.

[EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply
Alan Olsen| to my mail, just hit the ctrl, alt and del keys.
"In the future, everything will have its 15 minutes of blame."





Re: [Cooker] Installer still won't build RAID when partioning filesystem!

2000-10-09 Thread Thierry Vignaud

Claudio <[EMAIL PROTECTED]> writes:
>   /dev/hda1   512MB   SWAP
>   /dev/hda2   60MB/boot
>   /dev/hda5 + /dev/hdb5   8.0GB   /   (raid 0)
>   /dev/hda6 + /dev/hdc6   7.0GB   /home   (raid 1)
> 
> As I click on "done" (in diskdrake) it tells me: "You must a root (/) partition
> to procede with install"... BUT I HAVE IT!!! I USED SUCH A SCHEME WITH
> MANDRAKE 7.1 AND I WORKED PERFECTLY!!!
> Any suggestion about that?
> Please, developers, don't let me make the raid devices by hand!  :°°(

for the moment, you've to make a small non raid / fs.

-- 
www.linux-mandrake.com
somewhere between the playstation and the craystation
Thierry




Re: [Cooker] Installer/reiser/detailed

2000-09-01 Thread Pixel

Veit Waltemath <[EMAIL PROTECTED]> writes:

> hey,
> I think i'am the only one who has this problems with installing cooker
> from a reiserfs-partition via hd.img.

reiserfs is not available in hd.img

you can only install from fat/ext2 (and iso-loopback on fat/ext2)




Re: [Cooker] Installer/insmod reiserfs again

2000-08-31 Thread Veit Waltemath

...here he didn't work. I've tried again and again...
On console 5 the messages is insmod /modules/reiserfs.o failed,
module not found. hd.img(1474560) mod. 2000-08-29 13:45
-- 
Veit Waltemath  [EMAIL PROTECTED]
01896 Pulsnitz / Sa -Germany
 




Re: [Cooker] Installer/insmod reiserfs again

2000-08-30 Thread Pixel

Veit Waltemath <[EMAIL PROTECTED]> writes:

> last rsync from today 20:00 
> 
> The installer fails at insmod reiserfs.o again.
> This time he didn't say 'was not found', only failed.

works here...




Re: [Cooker] Installer

2000-08-29 Thread Phil Lavigna


Pixel,

  A network install from ftp.sunet.se, which seems to have the latest updates,
is working OK now. The installer didn't have any trouble getting into
DiskDrake.


-- 
Phil Lavigna
[EMAIL PROTECTED]
http://www.linux-mandrake.com/en/demos/




Re: [Cooker] Installer

2000-08-29 Thread Pixel

Veit Waltemath <[EMAIL PROTECTED]> writes:

> Hey
> I've just rsynced cooker and tried to install via the hd.img.
> I've only reiserfs partitions and the installer fails loading
> reiserfs.o at insmod with module not found.

yes, re-rsync!

the modules.cz containing all modules didn't want to give any modules anymore
:'-(






Re: [Cooker] Installer (20000829 00:04 network.img) problems...

2000-08-29 Thread Phil Lavigna


Hi,

> * starting step 'doPartitionDisk'
> * warning: An error as occured - no valid devices were found on which to 
> create new filesystems. Please check your hardware for the cause of this 
> problem at /usr/bin/perl-install/fsedit.pm line 423.

  This just happened to me also, the installer doesn't see the IDE hard drive
and won't install. I don't think it's an issue with the latest network.img,
the previous one from Aug 23 worked OK several times on previous installs but
also won't work with a current install from rpmfind.net. Is it thinking it's a
SCSI drive?




Cheers.
-- 
Phil Lavigna
[EMAIL PROTECTED]
http://www.linux-mandrake.com/en/demos/




Re: [Cooker] Installer upgrade - problem in mount partition if in fstab declared ro ntfs and...

2000-08-22 Thread Pixel

Franco Silvestro <[EMAIL PROTECTED]> writes:

[...]

> partitions and "no such device" and stop when encounter two ntfs ro . 

ok, fixed (only mounts ext2 and reiserfs)

> Also using hd.img, if in fstab is declared just using cooker mirror partition 
> (as /mnt/MIRROR) , installer can' find hdlist on his failed mount point :  to 
> continue upgrade I need to remove from fstab ntfs and mirror partitions 

?? hope the fix above will fix this.

[...]

> BUG IN DYNAMIC LINKER ld.so: dl-version.c: 210: _dl_check_map_versions: 
> Assertion `needed != ((void *)0)' failed!

bug in kde2, will get fixed :-/

[...]

> XFree3 (flashing screen and need manual retouch in XF86config to work : on my 
> laptop (ATImobilityP) option DPMS removed and changed with option power_saver)

yep, already reported, but i had not fixed. now it is.

[...]

> Also problem on install local printer, it failed probe on parport and found 
> inexistent usb/lp0 but I've /dev/lp0... Before correctly installed and used 
> as hp deskjet500

hum, fpons, you take care of this one?

[...]

> cu and good debugging...;o)

thanks a lot for this interesting report!




Re: [Cooker] Installer question

2000-07-02 Thread Pixel

Civileme <[EMAIL PROTECTED]> writes:

[...]

> and we have /dev/scd0 in /etc/fstab but /dev/sr0 in
> dmesg--this looks like a dodge to burn without
> un(super)mounting

sr0 and scd0 is the same.


[...]

> cat /proc/modules | grep ide-sc
> 
> " "
> (everything between the quotes)

you mean empty? this is a bug.

one thing that's bad without supermount, is that scsi_hostadapter(n) when n not
empty is not auto-loaded nor loaded :-(

i'm gonna put any scsi_hostadapter(n) in /etc/modules, dirty but only always
working way (it won't change anything for supermount users)




Re: [Cooker] Installer

2000-05-28 Thread Pixel

Andrew M <[EMAIL PROTECTED]> writes:

> I have one issue with the installer: colors. The default blue scheme can
> be somewhat confusing (for example, small status boxes that pop up (like
> in the partitioner), tend to get "camouflaged"). And I don't think
> multiple themes for the installer are really necessary. How about just
> creating one VERY clean theme? Dark lines on a light backround gives the
> best contrast.

the main pb is to have a theme dark enough. Otherwise it tends to blink a lot
(low frequency)




Re: [Cooker] Installer

2000-05-25 Thread Graham Percival

On Thu, May 25, 2000 at 09:55:29PM -0400, Andrew M wrote:
> I have one issue with the installer: colors. The default blue scheme can
> be somewhat confusing (for example, small status boxes that pop up (like
> in the partitioner), tend to get "camouflaged"). And I don't think
> multiple themes for the installer are really necessary. How about just
> creating one VERY clean theme? Dark lines on a light backround gives the
> best contrast.

I agree that some of the themes aren't very clear, but I think that the choice
is nice.  I quite liked the light blue theme in 7.1 (with stars for checkmarks
:), and will probably always use that one.  But giving people the opportunity
to play with them kind-of introduces them to the choice available in Linux
itself.  I can't stand half the window managers out there, but I love the fact
that they're out there.





Re: [Cooker] Installer

2000-04-24 Thread Pixel

"David Foresman" <[EMAIL PROTECTED]> writes:

> Would it be possible to get a changelog on the installer so we can see what was
> changed and what we should be testing during changes to the installer?

you can access it at:

pixel@leia:~/tmp>cvs -d :pserver:[EMAIL PROTECTED]:/home/cvs/cooker login
(Logging in to [EMAIL PROTECTED])
CVS password: cvs
pixel@leia:~/tmp>cvs -d :pserver:[EMAIL PROTECTED]:/home/cvs/cooker checkout 
gi/perl-install/ChangeLog


PS: alas, it is not always filled in :(




Re: [Cooker] Installer

2000-03-11 Thread Pixel

frank <[EMAIL PROTECTED]> writes:

> i'm having the same problems...though it appears from the several changes to
> the base folder, that someone is working on it, they've not yet got it
> right...for a while it demanded the hdlist.cz2, which wasn't there...i renamed
> hdlist to that, and got to a next level of error, "no dependencies found"...now
> they've got a hdlist.cz2 in /base but i'm getting that "no hdlists found"
> message...

i've just verified, hdlists was missing, thanks for telling. I've added it.

but don't bother wait for mirror updating, it's just

% echo hdlist.cz2 > Mandrake/base/hdlists


tell me if how install is working. It was kind of broken but should be better
now (if only i wasn't getting so much oopses :(


hopefully the new tree for package selection will be better appreciated :)

also, be carefull, grub by default for the moment!



Re: [Cooker] Installer

2000-03-11 Thread Pixel

"David Foresman" <[EMAIL PROTECTED]> writes:

> The lates cooker off the mirrors doesn't seem to work.
> 
> When doing a expert/development install via ftp off a local machine that =
> i mirrored off of 2 different mirror sites i get "Cannot find hdlists" =
> during install.

which kind of install? DrakX should work now. 
But old install is definitively broken!

new install uses hdlist.cz2



Re: [Cooker] Installer

2000-03-11 Thread frank

i'm having the same problems...though it appears from the several changes to
the base folder, that someone is working on it, they've not yet got it
right...for a while it demanded the hdlist.cz2, which wasn't there...i renamed
hdlist to that, and got to a next level of error, "no dependencies found"...now
they've got a hdlist.cz2 in /base but i'm getting that "no hdlists found"
message...

frank

On Sat, 11 Mar 2000, David Foresman wrote:
> 
> The lates cooker off the mirrors doesn't seem to work.
> 
> When doing a expert/development install via ftp off a local machine that i mirrored 
>off of 2 different mirror sites i get "Cannot find hdlists" during install.
> 


Content-Type: text/html; name="unnamed"
Content-Transfer-Encoding: quoted-printable
Content-Description: