Re: [Cooker] drakboot chosing the wrong system for upgrade
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...
Re: [Cooker] drakboot chosing the wrong system for upgrade
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 are repeadedly having testing on a mandrake beta system, > > and have a stable 9.1 running, the upgrade is also more likely to be > > done on the new beta system. > > drakboot? > > you mean installation defaults to the oldest installed distro? yes, when choosing which MDK system out of several to upgrade, installation chose the oldest system. keld
Re: [Cooker] drakboot chosing the wrong system for upgrade
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, > and have a stable 9.1 running, the upgrade is also more likely to be > done on the new beta system. drakboot? you mean installation defaults to the oldest installed distro?
[Cooker] drakboot chosing the wrong system for upgrade
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 likely to be done on the new beta system. best regards Keld
[Cooker] [drakboot] doesn't apply settings
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. http://qa.mandrakesoft.com/show_bug.cgi?id=2091 Olivier Blin
Re: [Cooker] drakboot ...
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 that autologin was also group writable in my system. pkg versions autologin-1.0.0-6mdk drakxtools-9.1-0.30mdk drakboot has a graphical layout problem in my station, updated to the last cooker. Hence, I cannot see precisly what I have done, but via logdrake, I see that drakboot tries to configure the autologin. -- Adrien
[Cooker] drakboot ...
Hi, drakboot should check the presence of mdkkdm, if autologin is selected. I did not find this test via logdrak. -- Adrien
[Cooker] Drakboot and display manager setting patch
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 the Display Manager between XDM, GDM, KDM, and KDE (for
mdkkdm).
Thanks
50d49
< my $auto_mode_dm = get_display_manager();
85,87d83
< my $display_manager_combo = new Gtk2::Combo;
< $display_manager_combo->set_popdown_strings(get_dm());
< $display_manager_combo->entry->set_text($auto_mode_dm) if $auto_mode_dm;
339,348d334
< ),
<
< gtkadd(new Gtk2::Frame(N("Display Manager")),
< gtkpack__(new Gtk2::VBox(0, 5),
< gtkpack__(new Gtk2::HBox(0, 10),
< gtkpack__(new Gtk2::VBox(0, 10),
< $display_manager_combo
< )
< )
< )
351c337
< gtksignal_connect(new Gtk2::Button(N("OK")), clicked => sub { Xconfig::various::runlevel($x_mode ? 5 : 3); updateAutologin(); updateAurora(); updateDisplayManager(); $::isEmbedded ? kill('USR1',$::CCPID) : Gtk2->exit(0) }),
---
> gtksignal_connect(new Gtk2::Button(N("OK")), clicked => sub { Xconfig::various::runlevel($x_mode ? 5 : 3); updateAutologin(); updateAurora(); $::isEmbedded ? kill('USR1',$::CCPID) : Gtk2->exit(0) }),
355d340
<
439,470d423
<
< #
< # Display Manager functions
< #
<
< sub get_dm {
< @winm = ["KDM", "KDE", "GNOME"];
< }
<
< sub get_display_manager {
< my %l = getVarsFromSh("$::prefix/etc/sysyconfig/desktop");
< if ($l{DISPLAYMANAGER} eq "gdm") {$l{DISPLAYMANAGER} = "GDM";}
< if ($l{DISPLAYMANAGER} eq "GNOME") {$l{DISPLAYMANAGER} = "GDM";}
< if ($l{DISPLAYMANAGER} eq "Gnome") {$l{DISPLAYMANAGER} = "GDM";}
< if ($l{DISPLAYMANAGER} eq "gnome") {$l{DISPLAYMANAGER} = "GDM";}
<
< if ($l{DISPLAYMANAGER} eq "kde") {$l{DISPLAYMANAGER} = "KDE";}
<
< if ($l{DISPLAYMANAGER} eq "xdm") {$l{DISPLAYMANAGER} = "XDM";}
<
< return $l{DISPLAYMANAGER};
< }
<
< sub updateDisplayManager {
< my $display_manager = $display_manager_combo->entry->get_text();
<
< my %l = getVarsFromSh("$::prefix/etc/sysconfig/desktop");
< $l{DISPLAYMANAGER} = $display_manager;
< setVarsInSh("$::prefix/etc/sysconfig/desktop", \%l);
< }
<
<
[Cooker] drakboot fails on startup
[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 != NULL' failed. gtkcreate_png: missing png file /usr/share/bootsplash/themes/Mandrake/images/bootsplash-normal.jpg at /usr/lib/libDrakX/ugtk.pm line 757. Compilation failed in require at /usr/sbin/drakboot line 27 Using drakxtools-newt-1.1.9-35mdk Narfi.
Re: [Cooker] drakboot text mode bug in beta 3
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!
[Cooker] drakboot text mode bug in beta 3
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 there, there is no text in the button itself. I can provide a screen shot if needed. drakboot from drakxtools-newt-1.1.9-12mdk H
[Cooker] drakboot - why have I to Modify boot entry to be able to Remove it?
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.
[Cooker] drakboot - error messages
It runs, but EMBED XID : 67109065 CCPID : 1799 Use of uninitialized value in subroutine entry at /usr/X11R6/bin/drakconf.real line 185, 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 /usr/lib/libDrakX/bootlook.pm line 86. [root@cooker root]# rpm -q drakfloppy drakfloppy-0.43-6mdk -andrej
Re: [Cooker] drakboot/cofigure bootloader failure
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 bientot chef de projet
[Cooker] drakboot/cofigure bootloader failure
EMBED XID : 67109265 CCPID : 4252 Use of uninitialized value in subroutine entry at /usr/X11R6/bin/drakconf.real line 185, 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 /usr/lib/libDrakX/bootlook.pm line 86. No such pseudo-hash field "hds" at /usr/lib/libDrakX/any.pm line 92. Compilation failed in require at /usr/sbin/drakboot line 25. [root@cooker RPMS2]# rpm -q drakconf drakxtools drakconf-0.70-5mdk drakxtools-1.1.7-6mdk -andrej
Re: [Cooker] Drakboot
"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 pseudo-hash field "hds" at /usr/lib/libDrakX/any.pm line 92. > Compilation failed in require at /usr/sbin/drakboot line 25. yep, aware thx -- Yves Duret [EMAIL PROTECTED] P|-|34R |)4 R4|<137
[Cooker] Drakboot
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 line 92. Compilation failed in require at /usr/sbin/drakboot line 25. Cheers, Atha
[Cooker] drakboot - launch X vs. runlevel selection
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 level. Currently it shows me run-level 5 on the start even when I have default 3). And it should visually disable/enable X when corresponding level is (un-)selected. Or it should add X startup to whatever level is chosen by user if "launch X on startup" is selected. -andrej
Re: [Cooker] drakboot/lilo problems with patch
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 /boot/lilo-graphic/message by the traditionnal message due to to some symlink to symlink to file ... yves -- Yves Duret [EMAIL PROTECTED] il pinge via RFC 1149. #linuxfr
Re: [Cooker] drakboot/lilo problems with patch
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. drakboot expects files /boot/boot-menu.b,
> /boot/boo-graphic.b, /boot/message-graphic.
>
> Instead, current lilo has directories /boot/lilo-{text,menu,graphic}
>
> 2. If you switch from graphic to text-menu, drakboot will reuse old
> graphic message with very funny effects. It happens because drakboot first
> reads old configuration, and as part it reads current message file. It
> then simply puts this file back when creating configuration.
>
> The atached patch is just a proof of concept. It assumes, that we have
[..]
yep there were some changes in lilo package.
thanx for the patch i will take care of it asap.
yves
--
Yves Duret
[EMAIL PROTECTED]
il pinge via RFC 1149.
#linuxfr
[Cooker] drakboot/lilo problems with patch
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. drakboot expects files /boot/boot-menu.b,
/boot/boo-graphic.b, /boot/message-graphic.
Instead, current lilo has directories /boot/lilo-{text,menu,graphic}
2. If you switch from graphic to text-menu, drakboot will reuse old
graphic message with very funny effects. It happens because drakboot first
reads old configuration, and as part it reads current message file. It
then simply puts this file back when creating configuration.
The atached patch is just a proof of concept. It assumes, that we have
/boot/boo.b -> lilo/boot
/boot/message -> lilo/message
and
lilo -> lilo-{menu,text,graphic} (that is controlled by drakboot). It
needs new lilo RPM which include correct link for /boot/message
The patch just tests if /boot/lilo/message exists and is using default
text if not. So, it will never reuse old one. If it is accepted it could
be optimized a bit more. It works here (after I've created message link).
-andrej
--- any.pm.org Wed Apr 25 16:36:37 2001
+++ any.pm Sat May 5 22:56:33 2001
@@ -127,13 +127,13 @@
my %bootloaders = (if_(exists $b->{methods}{silo},
__("SILO") => sub {
$b->{methods}{silo} = 1 }),
if_(exists $b->{methods}{lilo},
- __("LILO with text menu") => sub {
$b->{methods}{lilo} = "boot-menu.b" },
- __("LILO with graphical menu") => sub {
$b->{methods}{lilo} = "boot-graphic.b" }),
+ __("LILO with text menu") => sub {
+$b->{methods}{lilo} = "lilo-menu" },
+ __("LILO with graphical menu") => sub {
+$b->{methods}{lilo} = "lilo-graphic" }),
if_(exists $b->{methods}{grub},
#- put lilo if grub is chosen, so that /etc/lilo.conf
is generated
__("Grub") => sub {
$b->{methods}{grub} = 1;
exists
$b->{methods}{lilo}
-and
$b->{methods}{lilo} = "boot-menu.b" }),
+and
+$b->{methods}{lilo} = "lilo-menu" }),
if_(exists $b->{methods}{loadlin},
__("Boot from DOS/Windows (loadlin)") => sub {
$b->{methods}{loadlin} = 1 }),
if_(exists $b->{methods}{yaboot},
--- bootloader.pm.org Wed Apr 25 16:36:37 2001
+++ bootloader.pm Sat May 5 23:30:34 2001
@@ -380,8 +380,8 @@
);
unless ($lilo->{methods}) {
$lilo->{methods} ||= { map { $_ => 1 } grep { $l{$_} } keys %l };
- if ($lilo->{methods}{lilo} && -e "$prefix/boot/boot-graphic.b") {
- $lilo->{methods}{lilo} = "boot-graphic.b";
+ if ($lilo->{methods}{lilo} && -e "$prefix/boot/lilo-graphic") {
+ $lilo->{methods}{lilo} = "lilo-graphic";
exists $lilo->{methods}{grub} and $lilo->{methods}{grub} = undef;
}
}
@@ -590,9 +590,24 @@
my ($prefix, $lilo, $fstab, $hds) = @_;
$lilo->{prompt} = $lilo->{timeout};
-if ($lilo->{message}) {
+#- try to use a specific stage2 if defined and present.
+-d "$prefix/boot/$lilo->{methods}{lilo}" and symlinkf $lilo->{methods}{lilo},
+"$prefix/boot/lilo";
+log::l("stage2 of lilo used is " . readlink "$prefix/boot/lilo");
+if (! -e "$prefix/boot/lilo/message") {
+ my $msg_en =
+#-PO: these messages will be displayed at boot time in the BIOS, use only ASCII
+(7bit)
+__("Welcome to %s the operating system chooser!
+
+Choose an operating system in the list above or
+wait %d seconds for default boot.
+
+");
+ my $msg = translate($msg_en);
+ #- use the english version if more than 20% of 8bits chars
+ $msg = $msg_en if int(grep { $_ & 0x80 } unpack "c*", $msg) / length($msg) >
+0.2;
+ $msg = sprintf $msg, arch() =~ /sparc/ ? "SILO" : "LILO", $lilo->{timeout};
local *F;
- open F, ">$prefix/boot/message" and print F $lilo->{message} or
$lilo->{message} = 0;
+ open F, ">$prefix/boot/message" and print F $msg;
}
{
local *F;
@@ -616,13 +631,7 @@
print F "disk=/dev/$dev bios=0x80";
}
- if ($lilo->{message}) {
- if (-e "$prefix/boot/$lilo->{methods}{lilo}" && $lilo->{methods}{lilo} eq
"boot-graphic.b") {
- print F "message=/boot/message-graphic";
- } else {
- print F "message=/boot/message";
- }
- }
+ print F "message=/boot/message";
print F "menu-
Re: [Cooker] drakboot 1.1.5-73 (bootlook.pm) broken
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 -- Yves Duret [EMAIL PROTECTED] "C'est vers l'intérieur que va le chemin mystérieux" Novalis
[Cooker] drakboot 1.1.5-73 (bootlook.pm) broken
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: my @usernames;
...
Christian
--
Things that make you go "Hmmm":
"If a train station is where the train stops, what is a workstation?"
Re: [Cooker] drakboot does not work
[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). > > bor@localhost ~ $ rpm -q drakxtools > drakxtools-1.1.5-39mdk yes, I saw that too. I'll try to fix that. -- dam's
[Cooker] drakboot does not work
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 drakxtools-1.1.5-39mdk -andrej
