Slacko Puppy 5.3.1

[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

[James C]

Didn't know this was up for a vote but +1 for legacy Grub.

[nubc]

keep Legacy Grub

[Lobster]

No bugs to report

5.3.1 just works
m m m . . . I may have to do something more demanding . . .

Some of the non-bugs. Fast boot and audio, including recording - working.

Just reporting day to day solidity

[don570]

new version of mtpaint works well
with Wacom Bamboo tablet and Slacko

http://www.murga-linux.com/puppy/viewto ... 13&t=71332

_____________________________________

[mave]

[obsolet...]

[jim3630]

+1 for Grub4dos.

it was the first I learned to use when new to linux
and so simple to use never needed to learn
another.
legacy grub maybe just as easy for all I know.

[Aitch]

Oh no....grub wars!

Well, I'll see your grub and grub4dos, and raise a Win Installer
That's REALLY for neophytes and noobies who have heard that grub breaks your hard drive

ha!

personally, I'll try anything as long as the dang thing boots
I was rather sad to see the grub splashscreen by catdude, die away

remember this?



I liked the graphical menu, choice of boots, plus visible boot path/options

Perhaps it could revive legacy grub....grub4dos just reminds me of M$...

But, oh, to be free of the fear of wrecking harddrives for noobies

Aitch

[James C]

I've pretty much had nothing but trouble with Grub4dos when trying to boot anything other than Puppy and Windows...generally the default legacy Grub menu.lst will work ootb. Novel idea...just keep both.

[gcmartin]

In 2011, we saw a marked expansion in Puppy being able to co-exist, equally, on a LAN with devices, games, Windows and Macs as well as expansion of subsystems, features and services across the board.

Shinobar, in a distro he created couple years ago, produced a working model in his "QuickPET" distro (Sept 2010). It was far-reaching then, and several distro and PET contributors followed with similars. I have found his work in that area compelling where for a Live media use, I "could" modify the boot config for many additions. In fact, PuppyLuvr created a "MultiPUP" PET (also used by JameBond in "Netboot" where a Boot menu is presented to the booting PC for option selection(s).

I can see where this type of GRUB4DOS on a booting CD/DVD can be extremely useful to distro producers.

There is ONE MAJOR drawback to me. Because of its flexibility, many users could present a daunting list of support requests. This is the ONLY drawback I could find.

But, for it to get any mass appeal in Puppy, it will require distro developers to take on something that many do not understand, today. This is, using a boot processor other than what they have traditionally used. Old habits are hard to break!

Hope this helps
P.S. I AM AWARE, that this is, probably, NOT the best place for this discussion. And, my post should be moved if a moderator chooses.

[shinobar]

I've pretty much had nothing but trouble with Grub4dos when trying to boot anything other than Puppy and Windows...

What distro you failed to boot?
Do you have trouble with the recent versions of the grub4dosconfig?
If so, visit the topic on the grub4dosconfig and help me to polish it up:
http://www.murga-linux.com/puppy/viewtopic.php?t=51697