Slacko Puppy 5.3.1

[zigbert]

shinobar
Thank you for the fix


Sigmund

[01micko]

GrubConfig is not found in the menu. If this is intentional (to only offer Grub4Dos), there is a message in the universal installer mentioning GrubConfig.


Sigmund

Are your eyes painted on? Or is there paint in your eyes? (yes, pathetic art humour! I know you've been busy at the canvas )

I knew it was there as I did test for Sage, it's in the announcement thread.

[zigbert]

Truly, my eyes are covered by dark oil painting.

But why is Grub4Dos placed in 2 dfferent menus, while Legacy Grub only in System menu? Please give me a logic answer

[Jasper]

Hi zigbert,

I assume that the placement of Grub4Dos in 2 different menus was a trivial oversight but, now you have pointed this out, I have used Pmenu to hide both entries. I can temporarily unhide them if I want to make any changes.

As regards the "green" I seem to recall 01micko commented "you'll love it or hate it". Personally, I love it.

My regards and thanks for all your Puppy programs.

[Karl Godt]

But why is Grub4Dos placed in 2 dfferent menus, while Legacy Grub only in System menu? Please give me a logic answer Twisted Evil

Puppy is confusing as always ...

Slacko-5.3.1 /usr/share/applications/Grub4DosConfig.desktop
has got two entries for the /etc/xdg/menus/hierarchy :
Categories=X-SystemMemory;X-SetupUtility

/usr/share/applications/Grub-bootloader-config.desktop
Categories=X-SystemMemory

while Racy-5.2.2 Grub4DosConfig.desktop for example
has only one entry :
Categories=X-SystemMemory
(version 1.7.1)

Grub-bootloader-config.desktop
Categories=X-SystemMemory

Applying this code to change the submenu entries to show up with 1 entry already by the argument 1 ( $1= 1 )

Code: Select all

#!/bin/sh
N="$1"
[ ! "$N" ] && N=5
[ "`echo "$N" | grep '[^0-9]'`" ] && exit 106
cd /etc/xdg/menus
#for i in * ; do echo $i; sed -i 's#inline_limit="[0-9]*"#inline_limit="5"#g' $i; done
SED1='inline_limit="[0-9]*"'
SED2='inline_limit="'$N'"'
for i in * ; do echo $i;
if [ -f "$i" ];then
if [ -w "$i" ];then
sed -i "s#${SED1}#${SED2}#g" "$i"
[ "$?" != '0' ] && exit 107
fi;fi
done
fixmenus
#[ "$?" != '0' ] && exit 108
jwm -restart
[ "$?" != '0' ] && exit 109
exit 0

both show up together . (i named the script menu-sub-changer.sh)

At both Puppies the /etc/xdg/menus/hierarchy are same :

Code: Select all

#the menu hierarchy used in official Puppy v2.14
#'X-' categories are unofficial, Puppy-specific.
#w482 changed top-level name 'Calculate' to 'Business'.

System     :Memory         X-SystemMemory
Setup      :Utility        X-SetupUtility

[01micko]

Truly, my eyes are covered by dark oil painting.

But why is Grub4Dos placed in 2 dfferent menus, while Legacy Grub only in System menu? Please give me a logic answer

Hmm.. the technical answer is that there are 2 category entries in the Grub4DosConfig.desktop file:

Code: Select all

Categories=X-SystemMemory;X-SetupUtility

Now I don't know if shinobar did this on purpose and if so why?

EDIT: Oh, I see it's corrected in 1.7.1 in Racy, Barry must have corrected this. Thanks Karl.

[Karl Godt]

EDIT: Oh, I see it's corrected in 1.7.1 in Racy, Barry must have corrected this. Thanks Karl.

værsgo udråbsord
også i formerne: værsågod, værs'god, værsgo'

Here you go

Poohæ posting such in bug section

Happens , that the many usability bug posts colored onto me once or twice too .

I think it is meant good to put several categories into the .desktop files because the SUB MENU NAMING X-SystemMemory would probably fit to snapmergepuppy but not to a bootloader installer . P-SystemBoot category still to introduce .

[Master_wrong]

is it just me or when i try to install slacko into 4gb flashdishk formatted as FAT, syslinux didnt run... so i have run sys linux from lucid 528 ???

error code :
possibly unsafe /tmp/ permissions

EDIT : slacko 5.3

EDIT 2 : this solve the problem
#chmod 1777 /tmp

[shinobar]

But why is Grub4Dos placed in 2 dfferent menus, while Legacy Grub only in System menu? Please give me a logic answer

My intention
I would like the Grub4Dos menu at the same place of the installers that is 'Setup' for convenience.
But also need at 'System' where the legacy grub is.

But i think purging the legacy grub is better solution because it makes confuse for the users.
Nowadays Grub4Dos covers most of all the function what the legacy grub does.
I know some linux power users love the legacy. In that case, they can get it from the PPM.
Other case is he already has the legacy grub installed as the boot loader and want to rewrite only the menu.lst. In this case, he can do it manually using a text editor. Anyway he must do so even if the legacy grub config is available, isn't it?

(I have ever tried adding a function for the Grub4Dos config to generate legacy compatible menu.lst. But i found it is difficult to do it automatically. The user must correct the number of (hd0,0) or something manually.)

[Karl Godt]

(I have ever tried adding a function for the Grub4Dos config to generate legacy compatible menu.lst. But i found it is difficult to do it automatically. The user must correct the number of (hd0,0) or something manually.)

I have done it in two ways >

Code: Select all

echo "Enter the rootdrive ie '/dev/sda1' :
"
read ROOTPART

PARTNUMBER=`echo $ROOTPART | grep -o -e '[0-9]*$'`
echo ROOTPART=$ROOTPART PARTNUMBER=$PARTNUMBER
GRUBPART=$((PARTNUMBER-1))
echo GRUBPART=$GRUBPART
PARTCHAR=`echo $ROOTPART | sed 's#[0-9]##g' | rev | cut -c 1 |rev`
echo PARTCHAR=$PARTCHAR
case $PARTCHAR in
a)GRUBDRIVE=0;;
b)GRUBDRIVE=1;;
c)GRUBDRIVE=2;;
d)GRUBDRIVE=3;;
e)GRUBDRIVE=4;;
f)GRUBDRIVE=5;;
g)GRUBDRIVE=6;;
h)GRUBDRIVE=7;;
i)GRUBDRIVE=8;;
esac
echo GRUBDRIVE=$GRUBDRIVE

OR

Code: Select all

func10(){
if [ "$rootpart" ];then
echo rootpart=$rootpart
#ie sda1
partition=`echo $rootpart | sed 's#[[:alpha:]]##g'`
echo partition=$partition
#ie 1
grubpartition=$((partition-1))
echo grubpartition=$grubpartition
#ie 0

rootdrive=${rootpart:2:1} #first char 0 one char
echo rootdrive=$rootdrive
#ie a
c=0
for i in {a..z};do
if [ "$i" = "$rootdrive" ];then
grubdrive=$c
break
fi
c=$((c+1))
done
return 0
else
echo "WARN : code could not filter the drive"
return 141
fi
}
wd="`pwd`"
if [ "`echo "$wd" |grep '/mnt/'`" ];then
rootpart=`echo "$wd" | grep -o -e '/[shmflr]d.[0-9]/' | tr -d '/'`
func10 || exit 142
else
rootpart=`rdev |grep -o -e '/[shmflr]d.[0-9]' |tr -d '/'`
func10 || exit 143
fi

AND write something like this >

Code: Select all

for k in $kernels ;do
kernel=${k##*/}
echo $kernel
kernelpattern=`echo "$kernel" |sed 's/\([[:punct:]]\)/\\\\\1/g'`
echo "$kernelpattern"
if [ ! "`grep "$kernelpattern" ./grub/menu.lst`" ];then
echo "
title kernel $kernel on $rootpart
root (hd${grubdrive},${grubpartition})
kernel /boot/$kernel root=/dev/$rootpart ro $kernelline
" >> ./grub/menu.lst
fi
done

[Karl Godt]

is it just me or when i try to install slacko into 4gb flashdishk formatted as FAT, syslinux didnt run... so i have run sys linux from lucid 528 ???

error code :
possibly unsafe /tmp/ permissions

EDIT : slacko 5.3

EDIT 2 : this solve the problem
#chmod 1777 /tmp

This would be a woof bug for /usr/sbin/bootflash

short manual diff :

Code: Select all

#gather the files together...
rm -rf /tmp/makebootfat 2>/dev/null
mkdir /tmp/makebootfat
+ chmod 1777 /tmp
cd /tmp/makebootfat
cp -a /usr/lib/syslinux/ldlinux.bss ./
cp -a /usr/lib/syslinux/mbrfat.bin ./
cp -a /usr/lib/syslinux/mbr.bin ./
cp -a /usr/lib/syslinux/ldlinux.sys ./
mkdir tempdir

Don't know if it would need a chmod −R, −−recursive

[shinobar]

Tnx Karl, but the sky is not always blue.

One case is when you boot up from the USB drives.
Some case, the PC with some kernel has both sd? and hd?.
Another case is the boot loader is installed on the second drive.
You can directly boot the second drive swaping the order by the BIOS setting.
Or you can boot up the first drive and chain to the second by the boot loader on the first.

How the grub4dos solves these situation?
The function of 'find --set-root' or 'uuid' does, which the legacy cannot.

Conclusion: The legacy grub is not for beginners. Use the legacy for experts who love to manage it manually.

[01micko]

But i think purging the legacy grub is better solution because it makes confuse for the users.
Nowadays Grub4Dos covers most of all the function what the legacy grub does.

Hmm... I might just do that

As you say shino, power user can easily get legacy grub from PPM or even LILO if they desire. (in slackware repo).

[Sylvander]

Slacko-5.3.1-scsi-main

1. Booting a "live" CD-RW, with slackosave on an internal HDD, BUT...
I edited the ISO's isolinux.cfg file to add pmedia=ataflash, so the slackosave is being treated as though it's on a Flash Drive.
And...

2. Changed "Save interval = 0", so there is no auto-save during the session.
But...

3. PROBLEM:
Clicking the "Save" icon has no effect.
Hence...
The %CPU usage shows no increase, as would be normal during a save.
So...

4. I'm forced to instead...
Choose to save the session at shut-down.
[I made the necessary change to be given the option "to save or not to save"]

[Karl Godt]

Some case, the PC with some kernel has both sd? and hd?.

Ihave such today running a self configured kernel with everything of IDE , P/SATA , SCSI inside :

rdev
/dev/hdb3 /

grep -i 'mounted root' /tmp/bootkernel.log
[ 8.666738] VFS: Mounted root (ext4 filesystem) readonly on device 259:786432

ls /sys/block

loop0 loop3 loop6 ram0 ram11 ram14 ram3 ram6 ram9 sr0
loop1 loop4 loop7 ram1 ram12 ram15 ram4 ram7 sda sr1
loop2 loop5 md0 ram10 ram13 ram2 ram5 ram8 sdb

The HDD is SATA but i have a /proc/ide directory ....

Grub sees it's DISK it sits in the mbr of
always as hd0 as the few times i could observe it
in opposite to the BIOS or Kernel who would see the disk hdc as Master on controller 1 OR /dev/hdc on IDE boards with IDE kernel and i think it is the same with SATA boards .
An array of
CDROM MASTER CON 0,
HDD SLAVE CON 0 ,
HDD MASTER CON 1 ,
HDD SLAVE CON 1
and grub to mbr of HDD MASTER CON 1
would read hd0=/dev/hdc hd1=/dev/hdb hd2=/dev/hdd

Conclusion: The legacy grub is not for beginners. Use the legacy for experts who love to manage it manually.

I started with lilo and when grub 1 came out i was not able to handle it .. i think iirc it started run some kind of debug fstest displaymem or whatever automatically by debian sarge installer which polluted the screen with many output but no menu.lst .

Now i can handle grub 1 and it is OK for me . I actually have compiled it some days ago in racy which turns out to be a quite good compile environment , at least for non gui source ( hdparm,sdparm ) .

One tiny thing though , shinobar : cp /boot/vmlinuz to /boot/vmlinuz-1 , -2 , -3 and run grub4dosconfig ... Not too bad menu.lst , but ...

Nevertheless ...
I actually like the possibility of your grub4dosconfig to write a large menu.lst to include frugals .

[shinobar]

One tiny thing though , shinobar : cp /boot/vmlinuz to /boot/vmlinuz-1 , -2 , -3 and run grub4dosconfig ...

The problem occurs if the /boot/vmlinuz does not exist.
I will investigate the issue.

Tnx Karl. I like debugging even it is tiny.

EDIT(2012-01-15)
v1.7.2: fix was mmc card(ex. mmcblk0p1) failed(thanks to jemimah), which vmlinuz and initrd should be taken(thanks to Karl)
Topic on the grub4dosconfig:
http://www.murga-linux.com/puppy/viewtopic.php?t=51697

[Sage]

But i think purging the legacy grub is better solution because it makes confuse for the users.
Nowadays Grub4Dos covers most of all the function what the legacy grub does.


Hmm... I might just do that

Go ahead! Live dangerously! You'll win no friends, be sure of that. Legacy 0.9 is a pillar that the silent majority will not relinquish. Take a look at the postbag of other distros...

[Jasper]

Sage,

As 01micko said; but, cluelessly and either carelessly or selectively, you did not:

"As you say shino, power user can easily get legacy grub from PPM or even LILO if they desire. (in slackware repo)."

My regards

[Sage]

Who is this smart*ass always trying to score points. As usual, you are utterly wrong; you don't understand regular users. Go away.
So-called 'power users' will always know where and how to get all the files they need and how to use them. Puppy's greatest appeal is to neophytes and incomers who need the very simplest methods to get up-&-running.

[bigpup]

As a normal user, I have not used Grub since I discovered Grub4dos.
The last time I used Grub was back in the Puppy version 3 days.
+1 for Grub4dos