Light-Debian-Core-Live-CD-Wheezy + Porteus-Wheezy

[fredx181]

Hi Toni

Uploaded here:
http://www.smokey01.com/saintless/Light ... wheezy.deb
Here I will start upload and move special reinstall DebianDog - Porteus-Wheezy packages;
http://www.smokey01.com/saintless/Light ... -Packages/
I will create another folder for universal debian packages and Fredx181 folder will stay for working mixed and testing packages and files.

Do you agree or suggest something else?

That should be ok but on the other hand a little confusing to have two different packages on the site.
Other suggestion:
When it's a deb package and needs root access add something like this on top of script:

Code: Select all

[ "`whoami`" != "root" ] && exec xterm -geometry 25x3 -e "su - root -c ${0}"

I believe it's simular as you had already before ( with e.g. synaptic-start)
This way it works on every occasion.
AFAIK frisbee is the only package with this issue for now.

Fred

[sklimkin]

Hi All !

Less than a day laid me distribution downloaded 14 times.
In forums where posted message already asking questions and make comments.
So to our discussion (for the distribution) have an interest in Russia.
Mounting disks offer done (from user) using ymount.

Toni: thanks for XDM !

Sergey.

[fredx181]

Hi Sergey

If such a placement for any reason do not like developers Debian-Dog (especially Toni and Fred), then report it - I am ready to cancel it.

On the contrary!
Nice to see you made both in one iso.
For looking at the thread, is it this one?:
http://linuxforum.ru/viewtopic.php?pid=399785
Or any other also?
Btw when I looked at it I noticed about copying folder unioncp in initrd.xz and /bin/chroot symlink.
In latest Porteus-Wheezy I deleted these lines in linuxrc:

Code: Select all

echo $i"Copying files from original debian initrd..."
echo ...
cp -a /unioncp/. /union/.

And removed unioncp folder, works without it.
Also I think symlink /bin/chroot is not needed but I am not sure (did not try).
Change:

Code: Select all

exec bin/chroot . /mnt/live/bin/init "$@" <dev/console >dev/console 2>&1

to

Code: Select all

exec usr/sbin/chroot . /mnt/live/bin/init "$@" <dev/console >dev/console 2>&1

Regards
Fred

[saintless]

Code: Select all

[ "`whoami`" != "root" ] && exec xterm -geometry 25x3 -e "su - root -c ${0}"

I believe it's simular as you had already before ( with e.g. synaptic-start)
This way it works on every occasion.
AFAIK frisbee is the only package with this issue for now.

Hi, Fred.
Maybe this will be the best solution to have working packages on any debian system. It is easy now with your redeb to edit the debs we have if we need. I will start checking them one by one later.

Sergey, I see comments asking about Russian language and locales. If you like you can make separate module using RemasterCow script with Russian locales (02-Russian-Locales.squashfs). I will clean it up, add update dpkg information script and upload it on the site in Light-Wheezy and Porteus-Wheezy folders for Russian users.

Toni

[sklimkin]

Hi Fred!

Yes it is one of my posts (on three different sites).

Features of development, I stated:
The main features of this development :
1. debian (wheezy) as a base system
2 . minimalism (as far as it is possible for a system with Xorg graphics add-in )
3 . possible for the user to extend the system (via apt-get or Synaptic)
4 . the ability to connect with the programs ready modules as *. squashfs and *. pet (puppy) and modified *. deb
5 . possible for the user to create ready-made modules with programs in the form *. deb and *. squashfs (*. sfs) of the downloaded and installed in source *. tar.gz or more *. deb with the possibility of minimizing
6. inclusion into the unique features of the puppy-linux , while maintaining the system as a real Debian
7. system (both versions ) is a FRUGAL and remains LIVE,
this can be seen : http://puppylinux.org/wikka/FrugalOrFullInstallation
8. work with debian repositories should always start with the team in teminale : sudo apt-get update

I finished my message with these words:
Variations on "Debian & Ubuntu" infinitely many .
Debian-Dog can be seen as a constructor for those who are willing and able to experiment. The modularity of the system and included in it modularity tools allow you to change and modify its widening (or narrowing ) the functional and retain their different versions of the system .
However , nothing prevents to set it as shown here on a flash card and to have a " Go Bag " option Linux system .

For more information about the development of the system under the name Debian-Dog , see the topic ( if English is not an obstacle )
murga-linux.com/puppy/viewtopic.php? t = 90660

Sorry if something is forgotten.

Maybe it makes sense to "freshen up" DebianDog-PorteusDog-test.iso especially given the significant additions in the past month?

De facto, you Fred and Toni is a leading developer Debian-Dog and I do not consider myself the right to issue such an update (so my knowledge is not enough for this).

Sergey.

[sklimkin]

Hi Toni !

I love my native Russian language.
I believe that for mass localization should be complete.
But I also consider myself a realist and so I think that we should accept the fact that English has become a tool of exchange between people from different countries (eg you , Fred and I - Bulgaria , the Netherlands and Russia).
Therefore, in the areas of research participants need a minimum English proficiency.
So in this particular case: wishing to explore the Debian-Dog obliged, at least read the menu in English.
Besides, we all understand that localization modules weigh a prohibitively long for ideas "LIGHT".
Let possibility of localization and appears to Southeast Asia and India and to the Slavs and for Arab and Semitic languages​​, but only after the release of version 1.0, IMHO.

Sergey.

[saintless]

Maybe it makes sense to "freshen up" DebianDog-PorteusDog-test.iso especially given the significant additions in the past month?

Hi, Sergey.
Yes, we have too many changes and I think in the next 2-3 weeks I will make new DebianDog-PorteusDog.iso.
It is OK for us to work with single testing module but the iso is really too old from what we have now.

Toni

[fredx181]

Hi Toni
Do you have any idea how to get PATH right when logged in as user puppy and su root?
On Porteus-Wheezy:

Code: Select all

puppy@debian:~$ echo $PATH
/opt/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
puppy@debian:~$ su root
Password: 
root@debian:/home/puppy# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

On DebianDog it's ok
I have same in /etc/profile as in DebianDog
:

Code: Select all

#if [ "`id -u`" -eq 0 ]; then
 # PATH="/opt/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
#else
  #PATH="/opt/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games"
#fi
PATH="/opt/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
[ "`id -u`" -eq 0 ]&& PATH="$PATH:/usr/local/sbin:/usr/sbin:/sbin"
export PATH

Other Q:
Do you have white background with desktop_drive_icons (on DebianDog)?
When I restart X it's ok

Fred

[saintless]

Do you have any idea how to get PATH right when logged in as user puppy and su root?
On Porteus-Wheezy:

Code: Select all

puppy@debian:~$ echo $PATH
/opt/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
puppy@debian:~$ su root
Password: 
root@debian:/home/puppy# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Hi, Fred. Check out /etc/sudors file I have there:

Code: Select all

Defaults	secure_path="/opt/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

Also after installing XDM /ets/profile path stops working. I have this in /etc/environment instead:

Code: Select all

PATH=/opt/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/local/sbin:/usr/sbin:/sbin

Do you have white background with desktop_drive_icons (on DebianDog)?
When I restart X it's ok

Not now but I remember I had something like this with IceWM if there is no wallpaper set for IceWM in preferences. I will check this more careful on the last testing module.

Toni

[fredx181]

Hi Toni

I have this in /etc/environment instead:
Code:
PATH=/opt/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/local/sbin:/usr/sbin:/sbin

Just putting it in /etc/environment worked, Thanks

Quote:
Do you have white background with desktop_drive_icons (on DebianDog)?
When I restart X it's ok

Not now but I remember I had something like this with IceWM if there is no wallpaper set for IceWM in preferences. I will check this more careful on the last testing module.

I have it with JWM as default booting with savefile.
It's with the JWM version included in your latest squashfs.

Fred

[mcewanw]

Hi Toni
Do you have any idea how to get PATH right when logged in as user puppy and su root?

I expect you know this, but thought I'd mention that normal practice is to type a '-' after the su command if you want the su to take the normal environment of the changed user. That is:

Code: Select all

su - root

Then root should get their normal login environvent including PATH. I'm on a different system at the moment, but I presume that is what happens in DebianDog and Porteus-Wheezy anyway.

[saintless]

Hi, William.
The PATH problem with DebianDog is not only for puppy user but for root also. After installing XDM root account does not have /opt/bin in the path anymore. Stopping XDM and reboot fixes the PATH. After starting XDM the PATH is not working again.
Exporting PATH in /etc/environment fixed this. Some advices point export path to be icluded in $HOME/.xsession but it didn't work for me.

Toni

[fredx181]

Hi William

I expect you know this, but thought I'd mention that normal practice is to type a '-' after the su command if you want the su to take the normal environment of the changed user. That is:

Code:
su - root

You're right.
Thanks, in fact I knew there's a difference but didn't know about the PATH env.

Fred

[fredx181]

Hi Toni William
I was wondering where the PATH is read when doing su root.
Found here some useful info:
http://stackoverflow.com/questions/7257 ... ble-change
It seems like /etc/login.defs is the one, but as we know already /etc/environment works also to change PATH.

Fred

[saintless]

It seems like /etc/login.defs is the one, but as we know already /etc/environment works also to change PATH.

I think to keep the PATH in /etc/environment, Fred.
It is the only working fix I found for XDM path change issue. If you include XDM in Porteus-Wheezy I guess the same problem will appear.

Toni

[fredx181]

Hi Toni
Sorry, I've found another ownership problem:
/usr/lib//dbus-1.0/dbus-daemon-launch-helper
Group ownership should be messagebus instead of root.

Found this when trying to get slim working on porteus-wheezy.
Didn't work first but by reinstalling dbus I've got working slim now

Maybe works with JWM then also , would be nice.

Fred

[sunburnt]

# Q: What`s with the link /live-rw-backing that points to the boot partition.?
# Shouldn`t it point to the live-rw partition.?
( All this because Debian found a new way to hide crap from us...)

# Which brings up a good point, DebianDog needs a PUPSTATE file.?
# Or I think better yet, have "env" variables instead of a sourced file.
The boot and live partitions are useful info., and many other system settings.


Toni; Tried a Debian menu converter script. Wow they really made it difficult.!
I`ll look at writing one in BaCon, it does not have Bash`s quoting problems.


Here`s Desktop File Editor. It works, but I`m not sure it`s better than using Geany.
Easy to browse... I should probably use an EditBox in place of the EntryBoxes.
I didn`t like the one I found and as always, Python. Like Java, not many apps.

To test... Click [New] and fill in some variables and the file name. [Apply]
To edit an existing desktop file, make a BackUp copy first.
It prints the output if run from a VTerm. ### Suggestions.?

[saintless]

Hi Toni
Sorry, I've found another ownership problem:
/usr/lib//dbus-1.0/dbus-daemon-launch-helper
Group ownership should be messagebus instead of root.

Found this when trying to get slim working on porteus-wheezy.
Didn't work first but by reinstalling dbus I've got working slim now

Maybe works with JWM then also , would be nice.

Fred

Thank you, Fred
No need to sorry. It is very good you have one more fix for DebianDog. I guess this file is missing in Debian Live Standard. I will check this out.

I still have doubts about SLiM. It does not explain why it creates the same problems after a while for Sergey. He uses chroot builded Debian system with all ownerships right.
Antix also has (or had) the same problems with SLiM. I read in Other Distros the login stops work in time. I gues Antix found proper fix in the latest versions but this still does not explain the problems since the ownership problem does not exist there. I will stick with XDM for DebianDog but I will test LightDM after your fix.

BTW tiny XDM seems to be much better than I thought. I can change the colors and messages in the login box and I have wonderful small DebianDog color desktop screenshot on the right side of the login box. You will see it in the next testing module.
I read for other possible solution to load more than one WM from the login box.

Toni

[saintless]

Hi, Terry.

# Q: What`s with the link /live-rw-backing that points to the boot partition.?

It is a fix for Desktop-drive-icons. If we do not have this /live-rw-backing link to the partition containing live-rw save file you can not mount the boot partition from desktop-drive-icons with Rox. It gives error live-rw-backing not found. It works with XFE without /live-rw-backing but it is better to have it working for Rox also.
This issue comes again from using downgraded initrd.img. Wheezy live-boot v3.x system expects to mount all drives in /lib/live/mount/(medium, modules etc.). and creates mount points for live-rw and all squashfs modules included in /live folder. You can see some warnings on boot there is no mount point for 01----.squashfs.
With downgraded kernel DebianDog try to create same mount points in / and it can't. This way we get the warnings. I can easy remove the warnings but this means to edit boot configuration file which will be needed if DebianDog boots with original initrd.img. I prefer to keep it untouched.

# Which brings up a good point, DebianDog needs a PUPSTATE file.?
# Or I think better yet, have "env" variables instead of a sourced file.
The boot and live partitions are useful info., and many other system settings.

Not sure what exactly it does for puppy. Any suggestion you have is welcome.

Here`s Desktop File Editor. It works, but I`m not sure it`s better than using Geany.

Thank you, I will test it today.

Toni

[saintless]

Hi Toni
Sorry, I've found another ownership problem:
/usr/lib//dbus-1.0/dbus-daemon-launch-helper
Group ownership should be messagebus instead of root.

Hi, Fred.
Thought to save you some more surprises

Code: Select all

chown user:tty /dev/tty6
chown user:tty /dev/tty5
chown user:tty /dev/tty4
chown user:tty /dev/tty3
chown user:tty /dev/tty2
chown root:tty /dev/tty1
chown root:kmem /dev/mem
chown root:kmem /dev/port
chown root:dialout /dev/ttyS0
chown root:dialout /dev/ttyS3
chown root:dialout /dev/ttyS2
chown root:dialout /dev/ttyS1
chown root:video /dev/agpgart
chown root:tty /dev/pts/0
chown root:disk /dev/sda1
chown root:cdrom /dev/sr0
chown root:disk /dev/sda
chown root:cdrom /dev/sg1
chown root:disk /dev/loop7
chown root:disk /dev/loop6
chown root:disk /dev/loop5
chown root:disk /dev/loop4
chown root:disk /dev/loop3
chown root:disk /dev/loop2
chown root:disk /dev/loop1
chown root:disk /dev/loop0
chown root:audio /dev/snd/timer
chown root:adm /dev/xconsole
chown root:lp /dev/parport0
chown root:lp /dev/lp0
chown root:video /dev/dri/card0
chown root:messagebus /usr/lib/dbus-1.0/dbus-daemon-launch-helper
chown root:staff /usr/local
chown root:staff /usr/local/bin
chown root:staff /usr/local/etc
chown root:staff /usr/local/games
chown root:staff /usr/local/include
chown root:staff /usr/local/lib
chown root:staff /usr/local/lib/python2.6
chown root:staff /usr/local/lib/python2.6/dist-packages
chown root:staff /usr/local/lib/python2.6/site-packages
chown root:staff /usr/local/lib/python2.7
chown root:staff /usr/local/lib/python2.7/dist-packages
chown root:staff /usr/local/lib/python2.7/site-packages
chown root:staff /usr/local/man
chown root:staff /usr/local/sbin
chown root:staff /usr/local/share
chown root:staff /usr/local/share/ca-certificates
chown root:staff /usr/local/share/fonts
chown root:staff /usr/local/share/man
chown root:staff /usr/local/share/sgml
chown root:staff /usr/local/share/sgml/declaration
chown root:staff /usr/local/share/sgml/dtd
chown root:staff /usr/local/share/sgml/entities
chown root:staff /usr/local/share/sgml/misc
chown root:staff /usr/local/share/sgml/stylesheet
chown root:staff /usr/local/share/xml
chown root:staff /usr/local/share/xml/declaration
chown root:staff /usr/local/share/xml/entities
chown root:staff /usr/local/share/xml/misc
chown root:staff /usr/local/share/xml/schema
chown root:staff /usr/local/src
chown root:tty /usr/bin/wall
chown root:ssh /usr/bin/ssh-agent
chown root:mail /usr/bin/procmail
chown root:mail /usr/bin/mutt_dotlock
chown root:mlocate /usr/bin/mlocate
chown root:lpadmin /usr/bin/lppasswd
chown root:mail /usr/bin/lockfile
chown root:shadow /usr/bin/expiry
chown root:mail /usr/bin/dotlockfile
chown root:crontab /usr/bin/crontab
chown root:shadow /usr/bin/chage
chown root:tty /usr/bin/bsd-write
chown daemon:daemon /usr/bin/at
chown root:lpadmin /usr/share/ppd/custom
chown libuuid:libuuid /usr/sbin/uuidd
chown root:utempter /usr/lib/utempter
chown root:utmp /usr/lib/utempter/utempter
chown root:mail /var/mail
chown root:staff /var/local
chown daemon:daemon /var/spool/cron/atspool
chown root:crontab /var/spool/cron/crontabs
chown Debian-exim:Debian-exim /var/spool/exim4
chown Debian-exim:Debian-exim /var/spool/exim4/db
chown Debian-exim:Debian-exim /var/spool/exim4/input
chown Debian-exim:Debian-exim /var/spool/exim4/msglog
chown daemon:daemon /var/spool/cron/atjobs
chown daemon:daemon /var/spool/cron/atjobs/.SEQ
chown root:lp /var/spool/cups
chown root:lp /var/spool/cups/tmp
chown root:lp /var/cache/cups
chown root:lp /var/cache/cups/rss
chown root:mlocate /var/lib/mlocate/mlocate.db
chown libuuid:libuuid /var/lib/libuuid
chown avahi-autoipd:avahi-autoipd /var/lib/avahi-autoipd
chown colord:colord /var/lib/colord
chown root:Debian-exim /var/lib/exim4/config.autogenerated
chown statd:nogroup /var/lib/nfs/sm
chown statd:nogroup /var/lib/nfs/sm.bak
chown statd:nogroup /var/lib/nfs
chown root:adm /var/log/samba
chown root:adm /var/log/fsck/checkfs
chown root:adm /var/log/fsck/checkroot
chown root:utmp /var/log/btmp
chown root:root /var/log/apt
chown root:adm /var/log/apt/term.log
chown Debian-exim:adm /var/log/exim4
chown Debian-exim:adm /var/log/exim4/mainlog
chown root:adm /var/log/cups/access_log
chown root:adm /var/log/cups/error_log
chown root:adm /var/log/cups/page_log
chown root:adm /var/log/news/news.crit
chown root:adm /var/log/news/news.err
chown root:adm /var/log/news/news.notice
chown root:adm /var/log/debug
chown root:adm /var/log/messages
chown root:utmp /var/log/lastlog
chown root:adm /var/log/auth.log
chown root:adm /var/log/dmesg.0
chown root:adm /var/log/dmesg
chown root:adm /var/log/syslog
chown root:adm /var/log/daemon.log
chown root:adm /var/log/kern.log
chown root:adm /var/log/lpr.log
chown root:adm /var/log/mail.log
chown root:adm /var/log/user.log
chown root:adm /var/log/mail.info
chown root:adm /var/log/mail.warn
chown root:adm /var/log/mail.err
chown root:utmp /var/log/wtmp
chown root:ssl-cert /etc/ssl/private
chown root:ssl-cert /etc/ssl/private/ssl-cert-snakeoil.key
chown root:Debian-exim /etc/exim4/passwd.client
chown root:daemon /etc/at.deny
chown root:lp /etc/cups
chown root:lp /etc/cups/ppd
chown root:lp /etc/cups/ssl
chown root:shadow /etc/gshadow
chown root:shadow /etc/shadow

Many of them are removed from Debian-Live-Standard but it is a good list to check out.

About /dev/tty ownership may be there is a reason debian Live keeps /dev full populated. I do not know if we can change ownership in /dev since RemasterDog leaves it empty. Need to test more about this.

Edit: Fred, all seems OK in new populated /dev so we do not have problem keeping /dev empty.

Toni