On Tue, Aug 26, 2003 at 02:51:29AM +0200, Pixel wrote:
Keld Jørn Simonsen [EMAIL PROTECTED] writes:
Current cooker drakboot choses the oldest Mandrake system for
upgrading. I think it is more relevant to chose the newest.
The older systems may just be som test systems.
Anyway if you
Keld Jørn Simonsen [EMAIL PROTECTED] writes:
yes, when choosing which MDK system out of several to upgrade,
installation chose the oldest system.
well, i'll fix this later...
Keld Jørn Simonsen [EMAIL PROTECTED] writes:
Current cooker drakboot choses the oldest Mandrake system for
upgrading. I think it is more relevant to chose the newest.
The older systems may just be som test systems.
Anyway if you are repeadedly having testing on a mandrake beta system
Current cooker drakboot choses the oldest Mandrake system for
upgrading. I think it is more relevant to chose the newest.
The older systems may just be som test systems.
Anyway if you are repeadedly having testing on a mandrake beta system,
and have a stable 9.1 running, the upgrade is also more
Hi
When I change my settings with drakboot and then clic ok to save, the settings are not
applied (I can see it in /etc/sysconfig/autologin for instance).
This bug has already been reported one week ago, I report it again because I think it
has to be corrected before final 9.1 release.
Le Samedi 15 Février 2003 21:57, Adrien Guichard a écrit :
Hi,
drakboot should check the presence of mdkkdm, if autologin is selected. I
did not find this test via logdrak.
I cannot set autologin via drakboot, I think this is due to missing S30dm
script in /etc/rc5.d.
another problem was
Hi,
drakboot should check the presence of mdkkdm, if autologin is selected. I did
not find this test via logdrak.
--
Adrien
Hi all,
I am trying to include the Display Manager configuration in drakboot.
I am not a perl and gtk guru and I just look at what have already be done. The
layout of the widget is not very good but if you are interrested here is a
patch for /usr/lib/libDrakX/bootlook.pm
It allow you to choose
[root@c-115082 root]# drakboot
Thu Sep 5 17:12:02 2002 Gtk-LOG **: file gtkcombo.c: line 849
(gtk_combo_set_popdown_strings): assertion `strings != NULL' failed. at
/usr/lib/libDrakX/bootlook.pm line 141.
** CRITICAL **: file gdk-pixbuf.c: line 79 (gdk_pixbuf_unref): assertion
`pixbuf !=
Hello,
While running drakboot in text mode, there is a bug on the screen where you are given
the options to modify add done the lilo entries.
The bug is that there is no text on the two buttons at the bottom of the screen. I
know they are meant to be OK and CANCEL, but while the buttons are
Hamster [EMAIL PROTECTED] writes:
The bug is that there is no text on the two buttons at the bottom of the
screen. I know they are meant to be OK and CANCEL, but while the buttons are
there, there is no text in the button itself.
booh, my bug. fixing
thanks!
I would expect Add/Modify/Remove/Done menu. Currently we have
Add/Modiy/Done and I have to enter Modify to remove entry. Sounds weird.
It runs, but
EMBED
XID : 67109065
CCPID : 1799
Use of uninitialized value in subroutine entry at
/usr/X11R6/bin/drakconf.real line 185, VERS line 1.
Fri Aug 24 20:52:47 2001 Gtk-LOG **: file gtkcombo.c: line 849
(gtk_combo_set_popdown_strings): assertion `strings != NULL' failed. at
EMBED
XID : 67109265
CCPID : 4252
Use of uninitialized value in subroutine entry at
/usr/X11R6/bin/drakconf.real line 185, VERS line 1.
Thu Aug 23 19:59:12 2001 Gtk-LOG **: file gtkcombo.c: line 849
(gtk_combo_set_popdown_strings): assertion `strings != NULL' failed. at
Borsenkow Andrej [EMAIL PROTECTED] writes:
[root@cooker RPMS2]# rpm -q drakconf drakxtools
drakconf-0.70-5mdk
drakxtools-1.1.7-6mdk
already fixed in drakxtools-1.1.7-7mdk
please upgrade
thx
--
Yves Duret
[EMAIL PROTECTED]
comment ca dadou a dit ca ? - mais c'est moi dadou !
(c) dadou
Atha Kouroussis [EMAIL PROTECTED] writes:
Hi,
after launching drakconf and invoking the boot config, clicking on the
configure button for lilo/grub does nothing.
Launching drakconf from the console the following errors are seen after
clicking on the configure button:
No such
Hi,
after launching drakconf and invoking the boot config, clicking on the
configure button for lilo/grub does nothing.
Launching drakconf from the console the following errors are seen after
clicking on the configure button:
No such pseudo-hash field hds at /usr/lib/libDrakX/any.pm
Newer drakboot allows you to select run-level. But selecting launch X
means actually setting run-level 5 (unselecting means run-level 3).
drakboot should at least reflect this - i.e. it should visually select
run-level 5 when launch X is selected (well, it should generally show
current default
On Sat, May 05, 2001 at 11:49:24PM +0400, Andrej Borsenkow wrote:
Current drakboot and lilo do no work together. there are several problems.
bor@localhost% rpm -q lilo
lilo-0.21.7-11mdk
bor@localhost% rpm -q drakxtools-1.1.5-101mdk
drakxtools-1.1.5-101mdk
1. lilo layout has changed.
On Mon, May 07, 2001 at 10:43:27AM +0200, Yves Duret wrote:
yep there were some changes in lilo package.
thanx for the patch i will take care of it asap.
yves
fixed in drakxtools-1.1.5-102mdk and drakxtools-newt-1.1.5-102mdk
i needed to change some of your stuff because it overwritte
current issue:
Unrecognized file test: -h at /usr/lib/libDrakX/bootlook.pm line 57.
Compilation failed in require at /usr/sbin/drakboot line 25.
...
54: my $in = interactive-vnew('su');
55: local $_ = join '', @ARGV;
56:
57: /-h/ and die _("no help implemented yet.\n");
58:
59: my @winm;
60:
On Thu, Apr 05, 2001 at 12:42:35PM +0200, Christian Bricart wrote:
current issue:
Unrecognized file test: -h at /usr/lib/libDrakX/bootlook.pm line 57.
Compilation failed in require at /usr/sbin/drakboot line 25.
fixed. i will upload a new drakxtools asap
(come from a bad patch...)
yves
--
started under drakconf it trashes disk by continously spawning
lilo; started as standalone I get
bor@localhost ~ $ /usr/sbin/drakboot
kdesu (kdelibs): [process.cpp:279] Echo mode still on.
and that is all (it requested root password before).
bor@localhost ~ $ rpm -q drakxtools
[EMAIL PROTECTED] (Andrej Borsenkow) writes:
started under drakconf it trashes disk by continously spawning
lilo; started as standalone I get
bor@localhost ~ $ /usr/sbin/drakboot
kdesu (kdelibs): [process.cpp:279] Echo mode still on.
and that is all (it requested root password before).
24 matches
Mail list logo
