TazPuppy 5.0 rc2

Message

thinkpadfreak · #571 Post by **thinkpadfreak** » Wed 27 Jun 2018, 12:21

Hello.
I have been trying tazpup since Alpha 13.

I think tazpup sets hwclock in utc. On the other hand, windows assumes that the hardware clock is in local time.

I have some puppies installed on my PC in addition to windows, and all the puppies set hwclock in local time. The setting of tazpup affects the other puppies and windows.

As for tazpup, is it possible to choose between localtime and utc?

Regards.

mistfire · #572 Post by **mistfire** » Fri 29 Jun 2018, 02:45

@thinkpadfreak for the meantime just delete the TZ file in /etc. type unset TZ in terminal and press enter. And use hwclock -l to set the system time to local only. Im trying to fix this system time problem.

Right now I will try to prepare the first beta release of TazPup.

thinkpadfreak · #573 Post by **thinkpadfreak** » Fri 29 Jun 2018, 12:07

mistfire wrote:
> for the meantime just delete the TZ file in /etc. type unset TZ in terminal and press enter. And use hwclock -l to set the system time to local only.

Thank you for response.
I suspect that, though the procedure above makes hardware clock equal system time, ntpd or something writes utc into hardware clock. As a result, system time is different from localtime.

I think that, if we have the file /etc/localtime, system time will be corrected. But hardware clock will remain in utc.

Anyway, I am looking forward to the beta version.

s243a · #574 Post by **s243a** » Fri 29 Jun 2018, 13:54

mistfire wrote:@thinkpadfreak for the meantime just delete the TZ file in /etc. type unset TZ in terminal and press enter. And use hwclock -l to set the system time to local only. Im trying to fix this system time problem.

Right now I will try to prepare the first beta release of TazPup.

Related to time, there should be something to set lets you set time from the internet. I think that I might of done this under

Slitaz Panel -> Boot -> Manage Daemons

before. Oddly the version of TazPup that I'm running, while I post now, has this grayed out but I'm sure that I used it before. Maybe this was fixed in later versions.

Edit. So Under Tux, I set the timezone under:
Setup -> Time Zone COnfiguration

I logged out looged in as root and the time was correct (Maybe it would have also been correct if I logged back in under Tux.

Anyway, Under root I was able to open

Slitaz Panel -> Boot -> Manage Daemons

and the time server was running. It is called, "ntpd".

I did all this using alpha 12. I have newer versions of TazPup installed just not on the computer that I was presently typing on.

Edit 2 I logged out then back in as Tux and the time is still correct but for better or worse Tux doesn't have access to "Manage Daemons".

zagreb999 · #575 Post by **zagreb999** » Fri 29 Jun 2018, 14:02

this one works
tzclock_3.0.6-1_i386.deb

thinkpadfreak · #576 Post by **thinkpadfreak** » Sat 30 Jun 2018, 01:32

s243a wrote:
> Related to time, there should be something to set lets you set time from the internet.

Adjustment of the hardware clock by "ntpd" is OK, but the hardware clock has to be in localtime for the compatibility with Windows. Ntpd seems to set the hardware clock in utc, which causes a problem.

Edit:
In order to keep the hardware clock in localtime, one might either stop ntpd or, issue a command before shutdown such as:
# hwclock --systohc --localtime

zagreb999 wrote:
> this one works
> tzclock_3.0.6-1_i386.deb

Thank you for your advice.
However, my concern is not how to set the time zone correctly but how to set the hardware clock as we wish (localtime or utc).

mistfire · #577 Post by **mistfire** » Sat 30 Jun 2018, 02:25

Tazpup Alpha 17 released:

* Improved system clock (puppy algorithm is now applied)
* utc and localtime can now selected on configure timezone

Download: https://drive.google.com/file/d/1FdWZvr ... sp=sharing

Build kit
https://drive.google.com/file/d/1N0tuuS ... sp=sharing

thinkpadfreak · #578 Post by **thinkpadfreak** » Mon 02 Jul 2018, 08:02

I am using Alpha 17 under Japanese environment. The clock issue seems to have been mostly fixed.

One of the members in Puppy Linux Japanese Forum suggests a setting as follows:

/etc/daemons.conf
NTPD_OPTIONS="-nqp pool.ntp.org"

This way, ntpd quits after clock is set. (It does not run as a daemon) This setting seems to help prevent the hardware clock being re-written in the way we don't expect.

P.S.
urxvt does not function properly. Some commands cannot be executed, probably because it is a cut-down version.

s243a · #579 Post by **s243a** » Tue 03 Jul 2018, 02:06

thinkpadfreak wrote:I am using Alpha 17 under Japanese environment. The clock issue seems to have been mostly fixed.

One of the members in Puppy Linux Japanese Forum suggests a setting as follows:

/etc/daemons.conf
NTPD_OPTIONS="-nqp pool.ntp.org"

This way, ntpd quits after clock is set. (It does not run as a daemon) This setting seems to help prevent the hardware clock being re-written in the way we don't expect.

P.S.
urxvt does not function properly. Some commands cannot be executed, probably because it is a cut-down version.

I kind of like this approach because it means less process running

. It also should be adequate for most peoples needs.

mistfire · #580 Post by **mistfire** » Tue 03 Jul 2018, 06:04

Hello there

Can you help me about this problem.

I noticed that pristine slitaz triggers /etc/init.d/rc.shutdown when going to shutdown or reboot while in tazpup does not but it is defined in /etc/inittab in both slitaz and tazpup. Any ideas how to get it work on tazpup?

s243a · #581 Post by **s243a** » Thu 05 Jul 2018, 05:39

mistfire wrote:Tazpup Alpha 17 released:

* Improved system clock (puppy algorithm is now applied)
* utc and localtime can now selected on configure timezone

Download: https://drive.google.com/file/d/1FdWZvr ... sp=sharing

Build kit
https://drive.google.com/file/d/1N0tuuS ... sp=sharing

I'm just looking at the code and the following doesn't appear to be an error:

Ln#416 of make-tazpup.sh

Code: Select all

mksquashfs "slitaz-rootfs" "$DISTRO_PUPPYSFS" -comp xz -Xbcj x86 -b 1M -Xdict-size 100%

However, for if some reason you leave "$curdir" (due to a code modification) then it will get an error. The code might be more robust to changes if you use the following instead:

Code: Select all

mksquashfs "$curdir/slitaz-rootfs" "$DISTRO_PUPPYSFS" -comp xz -Xbcj x86 -b 1M -Xdict-size 100%

and this would be more consistent with the rest of your code.

s243a · #582 Post by **s243a** » Mon 09 Jul 2018, 04:37

So I couldn't figure out why I was deleting files and wasn't freeing up any space. After some time of incessant deleting I finally figured out all the files were being moved to:

/mnt/home/.Trash-0/files

The trick is to open /mnt/home/ as root. This option is available by right clicking the folder.

After one navigates to the above path, one must highlight all the items in the folder then in the edit menu (located on the menu bar) select "remove". This removed most files except for ldlinux.sys, basesfs.msh, blank.png, boot.msg, elp.msg, savefile.msg, startnet.msg.

s243a · #583 Post by **s243a** » Wed 18 Jul 2018, 02:58

You use to be able to right click on the desktop and select logout. This no longer work on TazPup Alpha 17. This is relevant, because sometimes when you install packages the taskbar disappears. I also noticed that if you logout by:

/etc/init.d/slim stop

that

/etc/init.d/slim start

doesn't restart the desktop. This isn't a problem to me because it makes sense to have logging in and starting the desktop as to separate functions. However, I need to know the command to start the desktop.

mistfire · #584 Post by **mistfire** » Thu 26 Jul 2018, 00:27

Hello

I sucessfully make the slitaz shuts down like a puppy by redirecting /etc/rc.d/rc.shutdown output to /dev/tty1 instead of /dev/console. However it requires some refinements and tweaks to make got it work. Also I will try to get work it on non-acpi computers.

mistfire · #585 Post by **mistfire** » Tue 31 Jul 2018, 02:24

TazPup alpha 18 released

Changes
* Overhauled shutdown (it works like puppy)
* Improved boot scripts
* Some tweaks on ntp (thanks thinkpadfreak)
* Some tweaks on shutdownconfig

Download: https://drive.google.com/file/d/1Xa0awT ... sp=sharing
Build kit: https://drive.google.com/file/d/1HBgVlP ... sp=sharing

For SliPen Developers this latest build kit is highly recommended.

mistfire · #586 Post by **mistfire** » Sat 04 Aug 2018, 08:33

TazPup has now reached BETA!

Changes:
* Some radical changes on pup_event, pmount, resizepfile.sh, and partview
* Some shutdown bugfixes

Download: https://drive.google.com/file/d/1JJ5OoU ... sp=sharing
Build kit: https://drive.google.com/file/d/1-A7vr_ ... sp=sharing

thinkpadfreak · #587 Post by **thinkpadfreak** » Sun 05 Aug 2018, 06:53

Hello.
I am trying beta 1.

First boot seems OK.
Second boot with a save file seems OK. (However, the message "sfs_load: Depmod..." appears.)
At third boot, "sfs_load: Depmod..." keeps me waiting for a while.

I would like to know if such a behavior is normal.

Regards.

peebee · #588 Post by **peebee** » Sun 05 Aug 2018, 08:39

Congrats on Beta 1 - astonishing what can be achieved in only 84MB!!

A few "improvement" things I've noticed in unstructured testing:

- the partition booted from does not show in PcManFM - [LATER] actually some sort of conflict between /mnt and /media - any partition in /mnt does not get displayed

- some menus are alphabetical ordered, some are reverse-alphabetical....would be better to be consistent

- i'd prefer single click to be the default in PcManFM but that's just a personal preference

- tazpup builder - custom-packages folder is needed for cloud based build to add in packages not in slitaz repos - e.g. pFind

Cheers
peebee

mistfire · #589 Post by **mistfire** » Mon 06 Aug 2018, 02:55

@thinkpadfreak depmod normally runs when loading custom sfs modules
@peebee I will check that

thanks for feedback

thinkpadfreak · #590 Post by **thinkpadfreak** » Mon 06 Aug 2018, 05:46

mistfire wrote:
> depmod normally runs when loading custom sfs modules

Thank you for response.

I use adrv*.sfs, which is a Japanese language pack prepared by one of the Puppy Linux Japanese Forum members.

I think adrv*.sfs is different from extra sfs modules.
But, just in case, I removed it, and booted tazpup in its original (English) environment.

As I stated before, the message "sfs_load: Depmod..." appears at every boot except first boot, though I have no extra sfs modules added.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

TazPuppy 5.0 rc2

tzclock_3.0.6-1_i386.deb