Puppy Linux Discussion Forum

trio · Posted: Tue 25 Aug 2009, 23:51 Post subject:

Barry,

Here's another one with pfix=ram

shinobar · Joined: 28 May 2009 Posts: 2252 Location: Japan

For the main file names of remastered puppy,
the puppyinstaller allows, say 'ppa4-423ja.sfs'.
It writes '${DISTRO_FILE_PREFIX}-${NEWVER}*.sfs".

But init in initrd.gz does not allow. At line 438 and anywhere it writes
'${DISTRO_FILE_PREFIX}-${DISTRO_VERSION}.sfs'.

And bootflash at line 436, '*-[0-9][0-9][0-9].sfs'.

Skeptic · Joined: 24 Apr 2009 Posts: 6

Will Puppy 4.3 have sudo by default?
It's not safe to run as root by default.

gposil · Posted: Wed 26 Aug 2009, 05:15 Post subject:

How is it not safe to run as root on a R/O file system?

Skeptic · Joined: 24 Apr 2009 Posts: 6

I was talking about full installations.
Running as root from the live-cd is OK in my opinion.

Kenny-M · Joined: 15 May 2009 Posts: 147 Location: United States

I am torn in both directions on the root issue.

Yes running as root on an installed version can be an issue. But an issue for who? Those more technical understand this and appreciate the flexability given to them. For the joe average user perhaps a "user" account needs to be created that is restricted.

If for example you are using Puppy as a Rescue package on a live CD it is almost a necessity.

In my opinion you can go to the other exteme like Bebian which is more locked down. Sometimes it is a pain to have to do things in Debian. That is one reason I like Puppy.

So, I think leave root where it is.

ICPUG · Joined: 24 Jul 2005 Posts: 1277 Location: UK

This is a bug report thread.

'running as root' discussions should go somewhere else. It is not a bug. It is deliberate!

Suez2005 · Joined: 26 Aug 2009 Posts: 1

hello.

I'm from Brazil.

I do not speak English, so my pot can be confusing.

I've done everything to install puppy on HD, the version is the Puppy 4.3 Beta 1.

I followed all the tutorials available and I am almost giving up puppy install blessed.

If anyone can help me, the pc where I am trying to install has this configuration:

PENTIUM III 866 MHZ.

256 RAMDISK

HD of 10 GB SAMSUNG IDE.

Motherboard JETWAY 601CF.

Once I get it and send write Grub to MBR, it does everything right, then asks to save a file at reboot time, I saved in the same directory where the files are installed and when you start the message: DISK BOOT FAILURE, INSERTDISK SYSTEM AND PRESS ENTER.

If this is not the correct place to post this I apologize PÇO and guidelines for doing the right thing.

I am humbled the help of comrades who have more experience co Puppy 4.3 Beta 1.

Thank you.
> alterar

gposil · Posted: Thu 27 Aug 2009, 00:16 Post subject:

Is there any movement on the b43 front...

shinobar · Joined: 28 May 2009 Posts: 2252 Location: Japan

/usr/sbin/puppyinstaller at line 117-120

NG:

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

***edited: bug in microscope corrected, it now sees Fedora 11 correctly, and distinguishes "not present" from "is not set"***

***EDITED again: but, see my next post. b43, I now believe, should be not set, period. Don't put it in the kernel (or compile as a module) at all.***

By using the dotconfig-comparison utility which I describe in
http://www.murga-linux.com/puppy/viewtopic.php?t=45831
I see the following, with regard to B43 and B44 dotconfig switches. By looking at this screenshot you can see which distros' dotconfigs I am comparing.

(Suggestions as to most-advanced distro's whose dotconfigs I should be examining under this "12-way blink-comparator microscope" are welcome--I am not yet enough of a Linux guru to know what the 12 best are. The program runs in a DOS window under Windows 98SE. Memory limitations of this combination, mainly the upper limit on open file handles, determine that I can compare a maximum of only 12 distro's at a time.)

Not present in vanilla 2.6.29.6 nor foreirongold's,
not set in all the others:
*# CONFIG_B43LEGACY_DMA_MODE is not set
*# CONFIG_B43LEGACY_PIO_MODE is not set
*# CONFIG_B43_DEBUG is not set

Set in all, except is not set in vanilla 2.6.29.6 and foreirongold's:
*CONFIG_B43=m
*CONFIG_B43LEGACY=m
*CONFIG_B44=m

Set in all, except is not present in vanilla 2.6.29.6 and foreirongold's:
*CONFIG_B43LEGACY_DMA=y
*CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
*CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
*CONFIG_B43LEGACY_PCI_AUTOSELECT=y
*CONFIG_B43LEGACY_PIO=y
*CONFIG_B43_PCICORE_AUTOSELECT=y
*CONFIG_B43_PCI_AUTOSELECT=y
*CONFIG_B44_PCI=y
*CONFIG_B44_PCICORE_AUTOSELECT=y
*CONFIG_B44_PCI_AUTOSELECT=y

Set in Ubuntu 9.04 and CrunchBang Linux (Ubuntu 9.04.1 with Openbox),
not present in vanilla 2.6.29.6 and foreirongold's,
is not set in any of the others:
*CONFIG_B43LEGACY_DEBUG=y

Set in the Pup(pie)s and Fedora 11 but not set in Ubuntu 9.04 and CrunchBang;
not present in vanilla 2.6.29.6 and foreirongold's:
*CONFIG_B43_PCMCIA=y

Set in Fedora 11, not present in vanilla 2.6.29.6, Ubuntu 9.04,
Crunchbang, Puppy 4.12-k2.6.25.16 nor foreirongold's,
set in all other Pup(pie)s:
*CONFIG_B43_PIO=y

Set in all except not present in vanilla 2.6.29.6, Puppy 4.12 2.6.25.16, MU's config-2.6.29.1MU-based-on2.6.28.5, and foreirongold's:
*CONFIG_B43LEGACY_RFKILL=y
*CONFIG_B43_RFKILL=y

Set in all, except is not present in unpatched vanilla 2.6.29.6, Puppy 4.12 2.6.25.16, and foreirongold's:
*CONFIG_B43LEGACY_LEDS is set =y
*CONFIG_B43_LEDS=y

Sorry for the messup in the previous version. There was a fencepost error in the parser, such that the first finding of a present-and-set switch when stepping through the distro's (as often as not, this was in Fedora) was not being recorded. Alles in ordnung now.

jaddison · Posted: Thu 27 Aug 2009, 20:11 Post subject:

First boot on lenovo r61 and MSI Wind:

No wireless on either. MSI not a surprise; had to add 8187 pet with 4.21. Lenovo a little surprising--on 4.21 no wireless when I run the "connect" wizard, but if I use the Pwireless app to scan for a connection and then manually connect I usually have no problem. No dice either way with this version.

4.3 gives me sound on the MSI machine--never could get that to work with 4.21.

capoverde · Posted: Fri 28 Aug 2009, 01:00 Post subject: Wine on Puppy 4.3B1

No problems found up to now after one week with Puppy 4.3Beta1 (single-proc), real fine.

After reading Barry's blog post about Wine I downloaded wine-1.1.28-i486.pet and installed it, then ran the Win$ version of a music notation program - MuseScore, mscore-0.9.4.exe - which runs perfectly and way faster than the Linux version (actually MuseScore 0.9.3 on Puppy 4.1)!

It sees all fonts by putting a symlink to the fonts directory, which is in another ext3 partition, into Wine's "Windows-> Fonts" directory -- this 6-7yr-old PC has no Win$.
Laughing

How funny, it's just the opposite of what one needs to do in order to have TrueType fonts in Puppy with Win$ boxes! I'm quite amazed, Wine's performance is far better than I expected.

paulh177 · Joined: 22 Aug 2006 Posts: 870 Location: ST862228

frugal install

I tried a .pup conversion only to find the following :

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

I have now *actually read* tempestuous's thread from last November, "Extra drivers for Puppy 4.1 with 2.6.25.16 kernel" --his message with a hybrid Broadcom wifi driver PET attached on page 5...and, followed up by *actually looking at* what Broadcom themselves say, at
http://www.broadcom.com/docs/linux_sta/README.txt
Broadcom recommends you use their hybrid driver. This readme.txt paragraph seems particularly relevant: