Fwd: Re: [Cooker] new install floppies, more modules dropped

2003-02-03 Thread David Eastcott

Did not see this get through the first time.

--  Forwarded Message  --

Subject: Re: [Cooker] new install floppies, more modules dropped
Date: Sun, 2 Feb 2003 09:40:53 -0700
From: David Eastcott [EMAIL PROTECTED]
To: [EMAIL PROTECTED]

On Thursday 30 January 2003 15:11, Pixel wrote:
...

 - good news: many gigabit drivers are now available
 - bad news: the following modules are not available on install floppies

   disk/scsi: NCR53c406a aha152x psi240i qlogicfas qlogicfc wd7000 sim710
   t128 ultrastor 53c7,8xx dc395x_trm BusLogic seagate fdomain g_NCR5380
   3w- pci2220i qla2x00 eata eata_pio eata_dma in2000 pas16 a100u2w
   AM53C974 u14-34f

...

I am using 3w- modules one servers, any chance that they can be left on
the boot floppies?

Dave

---





Re: [Cooker] new install floppies, more modules dropped

2003-02-02 Thread David Eastcott
On Thursday 30 January 2003 15:11, Pixel wrote:
...
 - good news: many gigabit drivers are now available
 - bad news: the following modules are not available on install floppies

   disk/scsi: NCR53c406a aha152x psi240i qlogicfas qlogicfc wd7000 sim710
   t128 ultrastor 53c7,8xx dc395x_trm BusLogic seagate fdomain g_NCR5380
   3w- pci2220i qla2x00 eata eata_pio eata_dma in2000 pas16 a100u2w
   AM53C974 u14-34f

...

I am using 3w- modules one servers, any chance that they can be left on 
the boot floppies?

Dave




Re: [Cooker] new install - background/desktop problems

2001-09-22 Thread James Ray Kenney

Date sent:  Thu, 20 Sep 2001 14:03:21 +0200
From:   Guillaume Cottenceau [EMAIL PROTECTED]
Subject:Re: [Cooker] new install - background/desktop problems
To: [EMAIL PROTECTED]
Send reply to:  [EMAIL PROTECTED]

 Borsenkow Andrej [EMAIL PROTECTED] writes:
 
  Where have you found these 99% of people? Obviously, of all posting in
  this thread just two people have seen it - one of them developer. So,
  speaking about *users* the score is currently 100% against it :-)
 
 Well, here at Mandrake we sure do tweaking of system all day long, and no
 one of us is logged as root of course.
 
 Some of us use sudo a lot, some of us (like me) open one terminal and
 become root with su in this terminal, and that's fine, but no one logs
 into the WM as root. It's especially dangerous to do mail/web/news, cvs
 stuff, and any normal operations with root, and I don't see a good reason
 to do that provided you have su and sudo.
 
 
 
 -- 
 Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
 
Here is another vote to have an option in 'expert' to disable this 
behavior.
I spent half a day at work trying to figure out what happened to the 
desktop...Removing the Desktop dir and the .kde dir and restarting 
to see if it would come back and run the wizard again(which I 
thought was the problem.)
If you want to make the background a different color, fine, but do 
not disable important icons like the shell and kill icon!
Expecialy as you have not fixed the problem with installing on Dell 
Optiplex GX110s yet.
I still cannot get anything but 640x480x16color working on the Dell 
with intel video.
This is with RC1.
MD8 worked fine, but ALL versions of MD8.1 have not worked at all.
It does not even ask to test the video anymore, just goes directly to 
the 'boot x on startup' question.

James Ray Kenney

-BEGIN PGP PUBLIC KEY BLOCK-
Version: 2.6.2

mQCNAzDGh+IAAAEEALtoCTrqvHd8tCifWK8hXwqdZuvbWOZOPo8RWKUm697HLOMr
T5yfr40LaoZpCgec/ErcPJlOoZ3Ok1d5J8K/xrl8U7t+mNag00VMpmz/AfRhsPnQ
+iVcTvtcw+opIoO++Ei4LiY/99H+5raPnTe7icucTkYKdxyAqJT7hiQSTfy1AAUR
tCJKYW1lcyBSYXkgS2VubmV5IDxqa2VubmV5QHNhdC5uZXQ+iQCVAwUQMPYvf5T7
hiQSTfy1AQEY6QQAhHGkbKDE7rGaQ5t/KdgeobCmIv6UWT/YKr1n49Tjl8P8Ntr1
16BWocObvAWESiunutYHqiy7She5ncP3PlOs39VuBdw6Nr9ehu6tblufOyiHeZN6
T6qJUwWpDXqDJDf1ecS+2QgVWsx7Qt4b6TyB1C0zMTtq2/encVHWOQ5PU70=
=TcJB
-END PGP PUBLIC KEY BLOCK-




RE: [Cooker] new install - background/desktop problems

2001-09-20 Thread Michael Bollozos

Im a Mandrake user(newbie), and I would like to log-in
as root in my Box, but with the current 8.1's 
new behavior I think I would just stick to 8.0
coz i normally log-in as root in my box this
box is not plugged in the network BTW... I have
used LM 7, 7.2, and 8.0 but with the current info
that I can no longer log-in as root in 8.1 I think
I should pass this upgrade.. But I hope you just make
it an option when you choose expert Install so that
we newbies can experiment with Linux and not further
push us to M$.. and also have Linux gain a more wide
acceptance... thank you...

Miko.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Borsenkow Andrej
Sent: Thursday, September 20, 2001 1:21 PM
To: [EMAIL PROTECTED]
Subject: RE: [Cooker] new install - background/desktop problems


Where have you found these 99% of people? Obviously, of all posting in
this thread just two people have seen it - one of them developer. So,
speaking about *users* the score is currently 100% against it :-)

It is exactly that Mandrake took time to change *existing* behavior into
something different. As if it was the only remaining problem and there
is nothing more to do on 8.1 ... 

-andrej




Re: [Cooker] new install - background/desktop problems

2001-09-20 Thread Radek Vybiral

On Wed, 19 Sep 2001, Vincent Meyer wrote:

 True, it might not be, however why should I loose features because
 I choose to do this?  I log in as root because I am often installing, 
 fiddling, testing, etc with things that most user shouldn't - at the 
 same time I'm getting my user work - e-mail, word processing, etc
 done.  I DON't want to have to log out and back in again all the
 time.  I KNOW what risks I am taking - and choosing to take then, 
 however I'm now  faced with a number of nice KDE features being
 removed to influence me not to do that.

Same for me.

I solve this bad things:
Copy  ~/Desktop and ~/.kde/config from normal user to /root

Why MDK hates logging as root in KDE?
  
 
 The warning at the begining should be enough.
 

Yes. Red background is OK.

R.V.






Re: [Cooker] new install - background/desktop problems

2001-09-20 Thread Fabrice FACORAT

Le Jeudi 20 Septembre 2001 10:51, Radek Vybiral scribit :
 I solve this bad things:
 Copy  ~/Desktop and ~/.kde/config from normal user to /root

NO. the best way is to not log as root !

 Why MDK hates logging as root in KDE?
  The warning at the begining should be enough.
 Yes. Red background is OK.

No as you log as root and don't understand why it is dangerous.

there's also su and sudo
+ open a term
+ []$ su -
give the root password
make what you want, and you can launch what you want. reduce the term or put 
it for example in the third that you will reserve for 
management/configuration, and that's it ! ( God bless virtual desktop ).

You can also try sudo ( man sudo, man sudoers )

so YOU DON'T NEED AT ALL TO LOG IN KDE/Gnome AS ROOT. You can even launch 
kcontrol for root from the console while you're logging as a normal user.

-- 
Copyleft Faber's prod. 2001
http://perso.wanadoo.fr/linux_wizard/index.html




Re: [Cooker] new install - background/desktop problems

2001-09-20 Thread Radek Vybiral

On Thu, 20 Sep 2001, Fabrice FACORAT wrote:

 No as you log as root and don't understand why it is dangerous.
 
 there's also su and sudo
 + open a term
 + []$ su -
 give the root password
 make what you want, and you can launch what you want. reduce the term or put 
 it for example in the third that you will reserve for 
 management/configuration, and that's it ! ( God bless virtual desktop ).

Yes, I know about this. I'm working with Linux/Unix 7+ years only as root 
user, so I think its too late changing me :)

IMHO disabling root login to the KDE or Gnome in higher security levels
will be OK.
Is this acceptable?

R.V.





RE: [Cooker] new install - background/desktop problems

2001-09-20 Thread Borsenkow Andrej

 
  Where have you found these 99% of people? Obviously, of all posting
in
  this thread just two people have seen it - one of them developer.
So,
  speaking about *users* the score is currently 100% against it :-)
 
 Well, here at Mandrake we sure do tweaking of system all day long, and
no
 one of us is logged as root of course.
 
 Some of us use sudo a lot, some of us (like me) open one terminal and
 become root with su in this terminal, and that's fine, but no one
logs
 into the WM as root. It's especially dangerous to do mail/web/news,
cvs
 stuff, and any normal operations with root, and I don't see a good
reason
 to do that provided you have su and sudo.
 

Sigh ... you argue wrong point. Me too not working as root @home (window
manager or no window manager). I happened to notice it only because it
was test system that is reinstalled from scratch every day and I see no
point in creating additional users every time (if I need to test
something specific I always can do it).

But now, when I noticed it, I just say it is way too intrusive. We
already have root warnings and that is quite enough. You may advice, you
may teach, you should not force. 

So I am not against the idea, I am against the way it is implemented.

Actually, I'd say that carefully selected tools do much less harm than
newbie starting terminal emulator as root and trying to learn basic Unix
skills. 

-andrej

rm -rf *;bak
bak: not found






Re: [Cooker] new install - background/desktop problems

2001-09-20 Thread andre

On do, 2001-09-20 at 04:28, Fabrice FACORAT wrote:
 Le Jeudi 20 Septembre 2001 04:21, Sergio P.Korlowsky a écrit :
  Well... if it goes to votes, I vote to leave it as it is now, and I haven't
  seen it yet
 
 so do I, but I'm going to test RC 1 so I will see it maybe.
 
  it is true, you a see lot of people logged in as root, unreal!
 
 unreal is the word.
 
  So the red background is a good idea.
 
  How many people didn't see the warning and the instructions on NOT using
  the software manager to update the kernel..?  and they did!
  they didn't READ the info.
 
 indeed. Pixel had to remove kernel from the possible update packages !
 
  Why would anyone want to log in as root, if you can do the same things
  as user and then 'su'  (Super User)
  
 su = switch user
 su - or su - root for root
 su - user to log as a user
 
 
 
superuser aka root
su for superuser

with su you don't become an other user. You mainly change uid and gid.
Almost nothing else 




RE: [Cooker] new install - background/desktop problems

2001-09-20 Thread Radek Vybiral

On Thu, 20 Sep 2001, Borsenkow Andrej wrote:

  
   Where have you found these 99% of people? Obviously, of all posting
 in
   this thread just two people have seen it - one of them developer.
 So,
   speaking about *users* the score is currently 100% against it :-)
  
  Well, here at Mandrake we sure do tweaking of system all day long, and
 no
  one of us is logged as root of course.
  
  Some of us use sudo a lot, some of us (like me) open one terminal and
  become root with su in this terminal, and that's fine, but no one
 logs
  into the WM as root. It's especially dangerous to do mail/web/news,
 cvs
  stuff, and any normal operations with root, and I don't see a good
 reason
  to do that provided you have su and sudo.
  
 
 Sigh ... you argue wrong point. Me too not working as root @home (window
 manager or no window manager). I happened to notice it only because it
 was test system that is reinstalled from scratch every day and I see no
 point in creating additional users every time (if I need to test
 something specific I always can do it).
 

You exactly described my situation. Especially for last weeks when Beta
series comes out.


 But now, when I noticed it, I just say it is way too intrusive. We
 already have root warnings and that is quite enough. You may advice, you
 may teach, you should not force. 
 
 So I am not against the idea, I am against the way it is implemented.
 

IMHO best solution will be disable root login on higher security levels.
This works for console why not for KDE or Gnome?

R.V.






Re: [Cooker] new install - background/desktop problems

2001-09-20 Thread Tom Badran


 superuser aka root
 su for superuser

 with su you don't become an other user. You mainly change uid and gid.
 Almost nothing else

but su username changes you to any user on the sytem, hence the command 
is abbreviated switch user, and not super user
-- 
Tom Tomahawk Badran
Department of Computing, Imperial College




RE: [Cooker] new install - background/desktop problems

2001-09-20 Thread Yura Gusev

On Thu, 20 Sep 2001, Michael Bollozos wrote:

 Im a Mandrake user(newbie), and I would like to log-in
 as root in my Box, but with the current 8.1's
 new behavior I think I would just stick to 8.0
 coz i normally log-in as root in my box this
 box is not plugged in the network BTW... I have
 used LM 7, 7.2, and 8.0 but with the current info
 that I can no longer log-in as root in 8.1 I think
 I should pass this upgrade.. But I hope you just make
 it an option when you choose expert Install so that
 we newbies can experiment with Linux and not further
 push us to M$.. and also have Linux gain a more wide
 acceptance... thank you...

Can you please echo $SECURE_LEVEL?

If it is 3 then msec 2

Also check msec manual. Mandarke have diffrent security levels. So use one
you like.

-- 
  9:17pm  up 27 days, 10:21,  3 users,  load average: 0.12, 0.11, 0.09
__
 | /  \ |Iouri Goussev//  \\
\_\\  //_/   [EMAIL PROTECTED]   _\\()//_
 .'/()\'.   Foo-Bar / //  \\ \
   jgs\\  //   http://foobar.irc-unix.net| \__/ |
I am not 31337. But I can use the Vi editor... ;-0





Re: [Cooker] new install - background/desktop problems

2001-09-20 Thread Yura Gusev

On 20 Sep 2001, andre wrote:

  su = switch user
  su - or su - root for root
  su - user to log as a user
 
 
 
 superuser aka root
 su for superuser

 with su you don't become an other user. You mainly change uid and gid.
 Almost nothing else

Nah. Also all env variables. su -, but with su yes only uid and gid.

-- 
  9:36pm  up 27 days, 10:40,  3 users,  load average: 0.00, 0.07, 0.07
__
 | /  \ |Iouri Goussev//  \\
\_\\  //_/   [EMAIL PROTECTED]   _\\()//_
 .'/()\'.   Foo-Bar / //  \\ \
   jgs\\  //   http://foobar.irc-unix.net| \__/ |
I am not 31337. But I can use the Vi editor... ;-0





Re: [Cooker] new install - background/desktop problems

2001-09-19 Thread Fabrice FACORAT

Le Mercredi 19 Septembre 2001 15:39, David BAUDENS scribit :
 On Wednesday 19 September 2001 10:19, you wrote:
  1. Background has nasty and distasteful dark red color (blood color
  is probably right term). When wizard starts background is changed to
  usual blue. I cancelled Wizard and KDE came up with this new color.
 You are root. Red color is normal.
  2. There is no desktop items in KDE except Home and Trash bin. To
  remind, I have cancelled wizard. But yesterday I did *not* cancelled
  it and got the same result.
 You are root. It's normal.
  3. There is no quick launch bar in KDE (or it is empty). Again it was
  yesterday as well.
 You are root. It's normal.
  All problems are not related to 2.2.1, they were yesterday.

It's a great idea, a good move : KEEP ON IT AND NEVER CHANGE THIS BEAHAVIOUR.
How many times it have to say people don't log as root and use su or sudo 
instead. How many times ... even if root is not in the login screen, they do 
it. Really great.

-- 
Copyleft Faber's prod. 2001
http://perso.wanadoo.fr/linux_wizard/index.html




Re: [Cooker] new install - background/desktop problems

2001-09-19 Thread Fabrice FACORAT

Le Jeudi 20 Septembre 2001 03:25, Vincent Meyer scribit :
 Maybe so - but I hate it.  I spend half of my time logged in as root
 because I WANT to be logged in as root.  

why do YOU want to do that ? don't do it !
You don't NEED to log as root in KDE, and what YOU want may not be the best.

 Loosing a lot of the things
 I use in KDE in order to keep me from being a user logged in as root
 is obnoxious.

 The KDE warning that comes up is plenty.  

no, not at all. I see plenty of people logging in KDE as root. grrr
back to win9x if it is for doing such things.

 If this is not a cast in
 stone policy, I vote we either change it back, 

no

 or that there be an
 option to re-enable the stuff.

maybe, that sounds sensible. but a very hidden option ( for example in 
userdrake as few people have a look at it  and as to access root config is 
hide also ).

  It's a great idea, a good move : KEEP ON IT AND NEVER CHANGE THIS
  BEAHAVIOUR. How many times it have to say people don't log as root and
  use su or sudo instead. How many times ... even if root is not in the
  login screen, they do it. Really great.

-- 
Copyleft Faber's prod. 2001
http://perso.wanadoo.fr/linux_wizard/index.html




Re: [Cooker] new install - background/desktop problems

2001-09-19 Thread Vincent Meyer

True, it might not be, however why should I loose features because
I choose to do this?  I log in as root because I am often installing, 
fiddling, testing, etc with things that most user shouldn't - at the 
same time I'm getting my user work - e-mail, word processing, etc
done.  I DON't want to have to log out and back in again all the
time.  I KNOW what risks I am taking - and choosing to take then, 
however I'm now  faced with a number of nice KDE features being
removed to influence me not to do that.

The warning at the begining should be enough.



Fabrice FACORAT wrote:
 
 Le Jeudi 20 Septembre 2001 03:25, Vincent Meyer scribit :
  Maybe so - but I hate it.  I spend half of my time logged in as root
  because I WANT to be logged in as root.
 
 why do YOU want to do that ? don't do it !
 You don't NEED to log as root in KDE, and what YOU want may not be the best.
 
  Loosing a lot of the things
  I use in KDE in order to keep me from being a user logged in as root
  is obnoxious.
 
  The KDE warning that comes up is plenty.
 
 no, not at all. I see plenty of people logging in KDE as root. grrr
 back to win9x if it is for doing such things.
 
NO!  Just because I don't choose to use what you consider are safe
or good practices shouldn't force me to go back to Windows!!!  Plenty
of people logging into KDE as root isn't the same as plenty of
developers
logging into KDE as root.

  If this is not a cast in
  stone policy, I vote we either change it back,
 
 no
 
  or that there be an
  option to re-enable the stuff.
 
 maybe, that sounds sensible. but a very hidden option ( for example in
 userdrake as few people have a look at it  and as to access root config is
 hide also ).
 
   It's a great idea, a good move : KEEP ON IT AND NEVER CHANGE THIS
   BEAHAVIOUR. How many times it have to say people don't log as root and
   use su or sudo instead. How many times ... even if root is not in the
   login screen, they do it. Really great.
 
 --
 Copyleft Faber's prod. 2001
 http://perso.wanadoo.fr/linux_wizard/index.html




Re: [Cooker] new install - background/desktop problems

2001-09-19 Thread Tom Badran


 NO!  Just because I don't choose to use what you consider are safe
 or good practices shouldn't force me to go back to Windows!!!  Plenty
 of people logging into KDE as root isn't the same as plenty of
 developers
 logging into KDE as root.

If you feel that you can use it safely enough, then surely you must have the 
abililty to change/enable any of the features you want, why should mandrake 
be changed for 1 person, when 99%  of people want it the way it is, or dont 
know better to make that judgment themselves.

And why log in as root to install software etc? I havent logged in as root 
directly for over a year and i can do all those things. You can set kdesktop 
icons to load administative programs as another user (root) and then it will 
ask for a password on loading that program. 

-- 
Tom Tomahawk Badran
Department of Computing, Imperial College




Re: [Cooker] new install - background/desktop problems

2001-09-19 Thread Fabrice FACORAT

Le Jeudi 20 Septembre 2001 04:11, Tom Badran scribit :
 If you feel that you can use it safely enough, then surely you must have
 the abililty to change/enable any of the features you want, why should
 mandrake be changed for 1 person, when 99%  of people want it the way it
 is, or dont know better to make that judgment themselves.

 And why log in as root to install software etc? I havent logged in as root
 directly for over a year and i can do all those things. You can set
 kdesktop icons to load administative programs as another user (root) and
 then it will ask for a password on loading that program.

there's also su and sudo
+ open a term
+ []$ su -
give the root password
make what you want, and you can launch what you want. reduce the term or put 
it for example in the third that you will reserve for 
management/configuration, and that's it ! ( God bless virtual desktop ).

You can also try sudo ( man sudo, man sudoers )

so YOU DON'T NEED AT ALL TO LOG IN KDE/Gnome AS ROOT. You can even launch 
kcontrol for root from the console while you're logging as a normal user.

-- 
Copyleft Faber's prod. 2001
http://perso.wanadoo.fr/linux_wizard/index.html




Re: [Cooker] new install - background/desktop problems

2001-09-19 Thread Sergio P.Korlowsky

On Wednesday 19 September 2001 20:33, you wrote:
 Le Jeudi 20 Septembre 2001 03:25, Vincent Meyer scribit :
  Maybe so - but I hate it.  I spend half of my time logged in as root
  because I WANT to be logged in as root.

 why do YOU want to do that ? don't do it !
 You don't NEED to log as root in KDE, and what YOU want may not be the
 best.

  Loosing a lot of the things
  I use in KDE in order to keep me from being a user logged in as root
  is obnoxious.
 
  The KDE warning that comes up is plenty.

 no, not at all. I see plenty of people logging in KDE as root. grrr
 back to win9x if it is for doing such things.

  If this is not a cast in
  stone policy, I vote we either change it back,

 no

Well... if it goes to votes, I vote to leave it as it is now, and I haven't 
seen it yet

it is true, you a see lot of people logged in as root, unreal!

So the red background is a good idea.

How many people didn't see the warning and the instructions on NOT using the 
software manager to update the kernel..?  and they did!  
they didn't READ the info.  

Why would anyone want to log in as root, if you can do the same things 
as user and then 'su'  (Super User) 

my .02

  or that there be an
  option to re-enable the stuff.

 maybe, that sounds sensible. but a very hidden option ( for example in
 userdrake as few people have a look at it  and as to access root config is
 hide also ).

   It's a great idea, a good move : KEEP ON IT AND NEVER CHANGE THIS
   BEAHAVIOUR. How many times it have to say people don't log as root and
   use su or sudo instead. How many times ... even if root is not in the
   login screen, they do it. Really great.

-- 
SedeComp Comunicaciones Internet Solutions
MandrakeSoft's VAR and System Integrator
mailto:[EMAIL PROTECTED]
OpenPGP key available on:http://www.keyserver.net/en/
|--|


Current Linux kernel 2.4.8-24mdk uptime: 0 hours 32 minutes.




Re: [Cooker] new install - background/desktop problems

2001-09-19 Thread Fabrice FACORAT

Le Jeudi 20 Septembre 2001 04:21, Sergio P.Korlowsky a écrit :
 Well... if it goes to votes, I vote to leave it as it is now, and I haven't
 seen it yet

so do I, but I'm going to test RC 1 so I will see it maybe.

 it is true, you a see lot of people logged in as root, unreal!

unreal is the word.

 So the red background is a good idea.

 How many people didn't see the warning and the instructions on NOT using
 the software manager to update the kernel..?  and they did!
 they didn't READ the info.

indeed. Pixel had to remove kernel from the possible update packages !

 Why would anyone want to log in as root, if you can do the same things
 as user and then 'su'  (Super User)
 
su = switch user
su - or su - root for root
su - user to log as a user



-- 
Copyleft Faber's prod. 2001
http://perso.wanadoo.fr/linux_wizard/index.html




RE: [Cooker] new install - background/desktop problems

2001-09-19 Thread Borsenkow Andrej

 On Wednesday 19 September 2001 10:19, you wrote:
  Just did new install, Configuration, Console, Gnome, KDE groups
  selected, ni manual package selection, Russian locale KOI8-R. First
  time login, startx.
 
  1. Background has nasty and distasteful dark red color (blood color
  is probably right term). When wizard starts background is changed to
  usual blue. I cancelled Wizard and KDE came up with this new color.
 
 You are root. Red color is normal.
 
 
  2. There is no desktop items in KDE except Home and Trash bin. To
  remind, I have cancelled wizard. But yesterday I did *not* cancelled
  it and got the same result.
 
 You are root. It's normal.
 
 
  3. There is no quick launch bar in KDE (or it is empty). Again it
was
  yesterday as well.
 
 You are root. It's normal.
 
 
  All problems are not related to 2.2.1, they were yesterday.
 
 Don't log as root and all will be as yesterday.
 

Pardon me, I am not new to Mandrake, this list or cooker as you may
suspect and it *never* was this way. This new feature (just like first
time wizard) should have been added very recently. If it were *always*
so I would not ask this question in the first place.

You may advice. You should not dictate. As was already pointed out, it
is my choice. You should not deprive me of features in this case.

I find it overly regrettable that such major changes in behavior are
done shortly before release, thus making it even more difficult for
people to test.

-andrej




Re: [Cooker] new install - background/desktop problems

2001-09-19 Thread J.P.Pasnak

On September 19, 2001 23:20 pm, you wrote:
   NO!  Just because I don't choose to use what you consider are safe
   or good practices shouldn't force me to go back to Windows!!!

 Plenty

   of people logging into KDE as root isn't the same as plenty of
   developers
   logging into KDE as root.
 
  If you feel that you can use it safely enough, then surely you must
  have the
  abililty to change/enable any of the features you want, why should
  mandrake
  be changed for 1 person, when 99%  of people want it the way it is,
  or dont
  know better to make that judgment themselves.

 Where have you found these 99% of people? Obviously, of all posting in
 this thread just two people have seen it - one of them developer. So,
 speaking about *users* the score is currently 100% against it :-)


I think it's a good sign that barely anyone saw it :) .  And I'm a user, and 
I like it.   I also spend a little bit of time over at MandrakeExpert, and I 
can tell you, this will be a definate bonus. 


-- 
Live fast, die young,
you're sucking up my bandwidth

J.P. Pasnak, CD
Warped Systems
http://www.warpedsystems.sk.ca
http://canopener.ca




Re: [Cooker] New install - first boot hangs on Starting Devfs

2001-08-22 Thread Chmouel Boudjnah

Blue Lizard [EMAIL PROTECTED] writes:

 I let it sit, got breakfast, took shower, read book, played ball, and it
 still not finished (slow machine).  I decided to go with devfs=nomount.

edit /etc/devfsd.conf and remove the line that talk about /sbin/pam_console_apply




Re: [Cooker] New install - first boot hangs on Starting Devfs

2001-08-22 Thread Blue Lizard

On 22 Aug 2001 10:43:08 +0200, Chmouel Boudjnah wrote:
 Blue Lizard [EMAIL PROTECTED] writes:
 
  I let it sit, got breakfast, took shower, read book, played ball, and it
  still not finished (slow machine).  I decided to go with devfs=nomount.
 
 edit /etc/devfsd.conf and remove the line that talk about /sbin/pam_console_apply
 
Thank you.  I take it things have changed in the install to reflect this neccessity.
Blue-going to look up how to spell that word.




RE: [Cooker] New install - first boot hangs on Starting Devfs

2001-08-21 Thread Borsenkow Andrej

 
 Synced two hours ago, almost default install, root on reiser, first
boot
 - system hangs on starting DevFs. Install yesterday was still O.K. :-)
 
 The only difference I use chained lilo loader from the first install,
on
 test installation (hda5) lilo is installed on partinion.
 

O.K. it's up, but it definitely took several minutes to continue
booting. ??

-andrej




RE: [Cooker] New install - first boot hangs on Starting Devfs

2001-08-21 Thread Blue Lizard

I let it sit, got breakfast, took shower, read book, played ball, and it
still not finished (slow machine).  I decided to go with devfs=nomount.




Re: [Cooker] new install

2001-04-05 Thread Frederic Crozat

Dans l'article
[EMAIL PROTECTED], "Rajesh
Veerappan" [EMAIL PROTECTED] a crit :

 Installing nautilus-trilobite will fix the eazel services problem.

I'm going to fix nautilus to no longer display Eazel service icon if
nautilus-trilobite is not installed..

-- 
Frdric Crozat
MandrakeSoft




Re: [Cooker] new install

2001-04-05 Thread Guillaume Cottenceau

"joabb2" [EMAIL PROTECTED] writes:


[...]

 Great install, photo's broke up boredom of waiting wished for
 names attached.

was posted once on this ML and on the Forum.


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




Re: [Cooker] new install

2001-04-05 Thread joabb2

Thanks,
Found it.
 a cable installer knocked me off for 30hrs :-/
just catching up.
JoAnne
- Original Message -
From: "Rajesh Veerappan" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, April 04, 2001 7:48 PM
Subject: Re: [Cooker] new install


 Installing nautilus-trilobite will fix the eazel services problem.

 On Wed, 4 Apr 2001, joabb2 wrote:

  I refuse to use Netscape since a telco isp tried to shove it
  down my throat and wouldnt budge.
  Konqureor starts out at 14k/bps and gradually rises to a max of 292k/bps
  after ten minutes.
  I know it has something to do with handshaking and number of packets
  received with out error but haven't a clue where to start debugging
 
  BTW initialized Gnome, Eazel and evolution got my email going
  once. Now clicking on icon says eazel is misspelled  :?
  Thank you for reply
 
  JoAnne
  - Original Message -
  From: "Vadim Plessky" [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Wednesday, April 04, 2001 12:03 PM
  Subject: Re: [Cooker] new install
 
 
   On Tuesday 03 April 2001 07:49, joabb2 wrote:
   |   BTW  I still use win/Gozilla for d/ld. get 500-600k/bps.
   |   cant get more than 292k/bps with Linux :((
   |   (yes traceroute and ping are about same)
   |
  
   Do you use Netscape/Mozilla inder Linux?
   Try Konqueror.
  
   I am on dialup, and transfer rate (on ftp download) is higher for me
under
   Linux, comparing to Win98.
   I am using KDE 2.1 / Konqueror 2.1.
  
   |   JoAnne
  
   --
  
   Vadim Plessky
   http://kde2.newmail.ru  (English)
   http://kde2.newmail.ru/index_rus.html  (Russian)
   Do you have Arial font installed? Just test it!
   http://kde2.newmail.ru/font_test_arial.html
  
  
 
 







Re: [Cooker] new install

2001-04-04 Thread Vadim Plessky

On Tuesday 03 April 2001 07:49, joabb2 wrote:
|   BTW  I still use win/Gozilla for d/ld. get 500-600k/bps.
|   cant get more than 292k/bps with Linux :((
|   (yes traceroute and ping are about same)
|

Do you use Netscape/Mozilla inder Linux?
Try Konqueror.

I am on dialup, and transfer rate (on ftp download) is higher for me under 
Linux, comparing to Win98.
I am using KDE 2.1 / Konqueror 2.1.

|   JoAnne

-- 

Vadim Plessky
http://kde2.newmail.ru  (English)
http://kde2.newmail.ru/index_rus.html  (Russian)
Do you have Arial font installed? Just test it!
http://kde2.newmail.ru/font_test_arial.html





Re: [Cooker] new install

2001-04-04 Thread joabb2

I refuse to use Netscape since a telco isp tried to shove it
down my throat and wouldnt budge.
Konqureor starts out at 14k/bps and gradually rises to a max of 292k/bps
after ten minutes.
I know it has something to do with handshaking and number of packets
received with out error but haven't a clue where to start debugging

BTW initialized Gnome, Eazel and evolution got my email going
once. Now clicking on icon says eazel is misspelled  :?
Thank you for reply

JoAnne
- Original Message -
From: "Vadim Plessky" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, April 04, 2001 12:03 PM
Subject: Re: [Cooker] new install


 On Tuesday 03 April 2001 07:49, joabb2 wrote:
 |   BTW  I still use win/Gozilla for d/ld. get 500-600k/bps.
 |   cant get more than 292k/bps with Linux :((
 |   (yes traceroute and ping are about same)
 |

 Do you use Netscape/Mozilla inder Linux?
 Try Konqueror.

 I am on dialup, and transfer rate (on ftp download) is higher for me under
 Linux, comparing to Win98.
 I am using KDE 2.1 / Konqueror 2.1.

 |   JoAnne

 --

 Vadim Plessky
 http://kde2.newmail.ru  (English)
 http://kde2.newmail.ru/index_rus.html  (Russian)
 Do you have Arial font installed? Just test it!
 http://kde2.newmail.ru/font_test_arial.html







Re: [Cooker] new install

2001-04-04 Thread Rajesh Veerappan

Installing nautilus-trilobite will fix the eazel services problem.

On Wed, 4 Apr 2001, joabb2 wrote:

 I refuse to use Netscape since a telco isp tried to shove it
 down my throat and wouldnt budge.
 Konqureor starts out at 14k/bps and gradually rises to a max of 292k/bps
 after ten minutes.
 I know it has something to do with handshaking and number of packets
 received with out error but haven't a clue where to start debugging
 
 BTW initialized Gnome, Eazel and evolution got my email going
 once. Now clicking on icon says eazel is misspelled  :?
 Thank you for reply
 
 JoAnne
 - Original Message -
 From: "Vadim Plessky" [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Wednesday, April 04, 2001 12:03 PM
 Subject: Re: [Cooker] new install
 
 
  On Tuesday 03 April 2001 07:49, joabb2 wrote:
  |   BTW  I still use win/Gozilla for d/ld. get 500-600k/bps.
  |   cant get more than 292k/bps with Linux :((
  |   (yes traceroute and ping are about same)
  |
 
  Do you use Netscape/Mozilla inder Linux?
  Try Konqueror.
 
  I am on dialup, and transfer rate (on ftp download) is higher for me under
  Linux, comparing to Win98.
  I am using KDE 2.1 / Konqueror 2.1.
 
  |   JoAnne
 
  --
 
  Vadim Plessky
  http://kde2.newmail.ru  (English)
  http://kde2.newmail.ru/index_rus.html  (Russian)
  Do you have Arial font installed? Just test it!
  http://kde2.newmail.ru/font_test_arial.html
 
 
 
 





Re: [Cooker] New Install...

2000-09-22 Thread Pixel

[EMAIL PROTECTED] writes:

 Now stage2 works, can find HDA,HDB... but something happens and a new
 error is here :)))

can you mail me the report.bug? 
to get it:

switch to console 2
put a fat floppy in floppy drive
and type "bug"

- it will put report.bug on floppy  and this file interests me :)


thanks, cu Pixel.




Re: [Cooker] new install

2000-04-24 Thread Pixel

Brook humphrey [EMAIL PROTECTED] writes:

 Thanks pixel actually what I've had to do so far is boot up with my
 linux rescue disk. Start fdisk delete all the partitions and then guess
 at were they were before. Anyway I got enough of it that I can mount
 part of the root partition and the boot.0300 file is there now what do I
 do with it. 

dd if=boot.0300 of=/dev/hda

explaination: the first time you call "lilo", it creates a backup of your mbr.

pb: if you had some extended partitions, it won't recover them, as the
information is not on the mbr (first sector of disk)




Re: [Cooker] new install

2000-04-24 Thread Brook humphrey

Thanks my /home and ftp/pub partitions made it ok but root and swap are
bad. At lest none of the important stuff is gone and I made copies a
long time ago of things like rc.masq and samba.conf to my /home dir so
all should be ok.

Pixel wrote:
 
 Brook humphrey [EMAIL PROTECTED] writes:
 
  Thanks pixel actually what I've had to do so far is boot up with my
  linux rescue disk. Start fdisk delete all the partitions and then guess
  at were they were before. Anyway I got enough of it that I can mount
  part of the root partition and the boot.0300 file is there now what do I
  do with it.
 
 dd if=boot.0300 of=/dev/hda
 
 explaination: the first time you call "lilo", it creates a backup of your mbr.
 
 pb: if you had some extended partitions, it won't recover them, as the
 information is not on the mbr (first sector of disk)




Re: [Cooker] new install

2000-04-24 Thread Chmouel Boudjnah

Christopher Molnar [EMAIL PROTECTED] writes:

 Hey, on a different note, what do you do if you , very dumbly, delete your
 lilo.conf file? 

i don't this there is a way.

 Any way to retreve from lilo?

do you mean the lilo.conf file ?

-- 
MandrakeSoft Inchttp://www.mandrakesoft.com
San-Diego, CA USA.--Chmouel




Re: [Cooker] new install

2000-04-24 Thread Chmouel Boudjnah

Christopher Molnar [EMAIL PROTECTED] writes:

 No, I mean I deleted the lilo.conf file on my server (accidently, you'd
 laugh to hard if I told you what I did) and didn't have a backup.

 (Hell, I had created a new server from another machine and copied all of
 /etc/*.conf from my origional machine to the new one. Well, there went the
 lilo.conf)

i don't think there is any way. (backup guy !!)

-- 
MandrakeSoft Inchttp://www.mandrakesoft.com
San-Diego, CA USA.--Chmouel




Re: [Cooker] new install

2000-04-24 Thread Pixel

Christopher Molnar [EMAIL PROTECTED] writes:

 No, I mean I deleted the lilo.conf file on my server (accidently, you'd
 laugh to hard if I told you what I did) and didn't have a backup.

no way to recover it from the mbr.

you have to reconfig it. maybe drakboot can help!




Re: [Cooker] new install

2000-04-24 Thread Robert L Martin

i think by definition the dev kernel is  not going to be in
a distro install. closest you can get is maybe
the hackkernel. but doing the dev kernel from a source
download isn't to bad route is
1 install the distros kernel source rpm (for RH or L-M type
distros) when you fix the deps
you get the toolsets
2 go to www.kernel.org or one of the mirrors and get the
archive (all 12 megs)
3 unpack the archive and rename the tree (will be linux) to
the version number (currently as of this mailing 2.3.99pre5
for the BETA)
4 move the tree to /usr/src/ and symlink to linux in the
same directory (remove the existing symlink)
5 straight out of the retail manual for L-M in a terminal
type
cd usr/src/linux/
make xconfig  make dep  make clean  make bzImage 
make modules  make modules_install
6 {bad singing} A HACKING WE WILL GO , A HACKING WE WILL GO
... {/bad singing}




Re: [Cooker] New Install of Oxygen - Few things....

2000-01-02 Thread Pixel

Scott Haug [EMAIL PROTECTED] writes:

 On Sat, Jan 01, 2000 at 09:59:09PM -0500, Heath Doane wrote:
  Greetings,
3) "Normal" user is unable to run X successfully.   Root has no problems,
  but when a regular user starts X, the server loads, the screen goes blue
  with an "X" cursor, but the KDE desktop never appears (some drive activity,
  but no desktop)
  
 
 I had this problem when I installed a fresh oxygen while retaining my previous
 /home partition.  I created new users using the same name as the previous users
 (thus reusing the old user's dirs), but the install gave them new uid's.  So
 when I tried to log in to my old account, I had no permissions to write to my
 account, which I believe is necessary when starting kde.  

this is quite strange. DrakX has special code to handle this situation. And as
far as i just retested, it works!



Re: [Cooker] New Install of Oxygen - Few things....

2000-01-02 Thread Pixel

Pixel [EMAIL PROTECTED] writes:

 Scott Haug [EMAIL PROTECTED] writes:
 
  On Sat, Jan 01, 2000 at 09:59:09PM -0500, Heath Doane wrote:
   Greetings,
 3) "Normal" user is unable to run X successfully.   Root has no problems,
   but when a regular user starts X, the server loads, the screen goes blue
   with an "X" cursor, but the KDE desktop never appears (some drive activity,
   but no desktop)
   
  
  I had this problem when I installed a fresh oxygen while retaining my previous
  /home partition.  I created new users using the same name as the previous users
  (thus reusing the old user's dirs), but the install gave them new uid's.  So
  when I tried to log in to my old account, I had no permissions to write to my
  account, which I believe is necessary when starting kde.  
 
 this is quite strange. DrakX has special code to handle this situation. And as
 far as i just retested, it works!

silly me, it doesn't works as it should, fixing it grmrmrmbbll...



Re: [Cooker] New Install of Oxygen - Few things....

2000-01-02 Thread Pixel

Heath Doane [EMAIL PROTECTED] writes:

 At 04:15 AM 1/2/00 +0100, you wrote:
 Heath Doane [EMAIL PROTECTED] writes:
 
1) When Installing, if it detects existing Linux partitions, it would not
  let me create new/more.
 
 diskdrake or lilo ?
 
 That would be in Diskdrake.  I chose the "Custom" then "Normal" install
 options when starting the install, as well.
 

you must have system commander. give readonly=0 at install boot prompt
(this is changed in last version)



Re: [Cooker] New Install of Oxygen - Few things....

2000-01-02 Thread Pixel

Pixel [EMAIL PROTECTED] writes:

   
   I had this problem when I installed a fresh oxygen while retaining my previous
   /home partition.  I created new users using the same name as the previous users
   (thus reusing the old user's dirs), but the install gave them new uid's.  So
   when I tried to log in to my old account, I had no permissions to write to my
   account, which I believe is necessary when starting kde.  
  
  this is quite strange. DrakX has special code to handle this situation. And as
  far as i just retested, it works!
 
 silly me, it doesn't works as it should, fixing it grmrmrmbbll...

yeah, a stupid line was not where it should... fixed!



Re: [Cooker] New Install of Oxygen - Few things....

2000-01-02 Thread Wayne Gabler

I'm new but... did you delete the partitions allready there first
because when i installed i could change almost at will..strange about
the 245m swap file though

Heath Doane wrote:
 
 At 04:15 AM 1/2/00 +0100, you wrote:
 Heath Doane [EMAIL PROTECTED] writes:
 
1) When Installing, if it detects existing Linux partitions, it would not
  let me create new/more.
 
 diskdrake or lilo ?
 
 That would be in Diskdrake.  I chose the "Custom" then "Normal" install
 options when starting the install, as well.
 
3) "Normal" user is unable to run X successfully.   Root has no problems,
  but when a regular user starts X, the server loads, the screen goes blue
  with an "X" cursor, but the KDE desktop never appears (some drive activity,
  but no desktop)
 
 what security level, what your .xsession-errors say ?
 
 
 Soon as I boot the Linux PC, I'll let you know..  :)
 
   Thanks
 
  Heath
 
 "For a moment, nothing happened.  Then, after a second or so,
 nothing continued to happen."
 --Douglas Adams



Re: [Cooker] New Install of Oxygen - Few things....

2000-01-02 Thread Sanjay Sheth

At 10:03 AM 1/2/00 , you wrote:
I'm new but... did you delete the partitions allready there first
because when i installed i could change almost at will..strange about
the 245m swap file though

How about adjusting the code to set the max. auto-selected swap file size 
to amount of physical
memory present (fairly good thumbrule i believe).

---
Sanjay Sheth
[EMAIL PROTECTED]



Re: [Cooker] New Install of Oxygen - Few things....

2000-01-02 Thread Pixel

Sanjay Sheth [EMAIL PROTECTED] writes:

 At 10:03 AM 1/2/00 , you wrote:
 I'm new but... did you delete the partitions allready there first
 because when i installed i could change almost at will..strange about
 the 245m swap file though
 
 How about adjusting the code to set the max. auto-selected swap file size 
 to amount of physical
 memory present (fairly good thumbrule i believe).

as for me i've never understood this rule!



Re: [Cooker] New Install of Oxygen - Few things....

2000-01-02 Thread stephen

On Sun, 2 Jan 2000, Axalon Bloodstone wrote:

 Let me clarify i guess. I wouldn't have less than 128megs. 386 or 1gig of
 real ram. At current prices 254 megs of hd cost like 2$us. I personaly
 can't recommend any less than 128 with todays uses.
 
not unfortunately in the UK, 110 for 15Gb
or is my maths screwed

srp




Re: [Cooker] New Install of Oxygen - Few things....

2000-01-02 Thread Axalon Bloodstone

On Sun, 2 Jan 2000, stephen wrote:

 On Sun, 2 Jan 2000, Axalon Bloodstone wrote:
 
  Let me clarify i guess. I wouldn't have less than 128megs. 386 or 1gig of
  real ram. At current prices 254 megs of hd cost like 2$us. I personaly
  can't recommend any less than 128 with todays uses.
  
 not unfortunately in the UK, 110 for 15Gb
 or is my maths screwed
 
 srp

Oh yeah i hate that (and always forget), so whats the current conversion
rate. The prices really are generaly comparable unless of course you live
in one of those places where satalite telephones are a must.

anyways, so like if the difference is greater than  1 to 1.5
shipping maybe cheeper than buying localy and paying taxes.



Re: [Cooker] new install

1999-11-29 Thread webmedic

It was trying to use my modem for the network. I think. I set up the
modem during install.



Pixel wrote:
 
 root [EMAIL PROTECTED] writes:
 
 [...]
 
 
  3) The modem install didn't work quite so nice this time and the crypto
  packages could not be downloaded during install. I just created an
  rc.serial and rebooted wich fixed the modem. It used to find it
  automaticaly though.
 
 francois?
 
 
  4) hwiz or whatever didn't install so I just installed the package
  myself wich fixed the hwiz errors.
 
 
 it will be in kdebase Requires
 
  5) For some reason sndconfig didn't install either.
 
 
 uh!
 
 [...]
 
 
  7) I like the new crypto download option maybe it will work better as
  soon as i get a cable modem.
 
 in fact, it shouldn't ask you about crypto stuff if there is no network
 available.



Re: [Cooker] new install

1999-11-29 Thread Sergio Korlowsky

Well most of the same ;-)

It also got stucked at cryptografic,

"choose a mirror from which to get packages from...

and the same, it couldn't find the modem... which it did before,

if I hit -cancel- skips the option to go to the next, but after setting the

time, it comes back to the same option "choose a mirror..."

also I get the same error, KFM Warning, could not execute program /usr/bin/hwiz

uhh it too early here, all night awaken ;-)

its about time to go to bed,

I like the packages pre-selection "choose the size of installation and add

more packages... neat!

Sergio Korlowsky

---
   M A N D R A K E
* The Friendliest of ALL Linux Distros *
   * Time is in our side *





Re: [Cooker] new install

1999-11-15 Thread Sergio Korlowsky

webmedic wrote:

 Its looking real good. I did an install from cdrom.

 it boots up with kdm now instead of gdm but maybe thats because I opted not to
 install gnome although it is still their using icewm as the windowmanager.

 Kfm segfaults if I try to go to the linux mandrake website. Even if i use the
 News link on the desktop.

 Netscape still segfaults, so i still using the nightly builds of mozilla for
 now. It'll be nice when they get the bugs worked out.

 I noticed that there are new fiiles on the mirror right now so I'll try a
 reinstall in the morning.

Great... just what I was waiting for...
I'll download again and burn a cd in the morning...
Thanks

sk