Porteus-v3.2rc5 bug reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Bogomips
Full of knowledge
Full of knowledge
Posts: 2562
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Porteus-v3.2rc5 bug reports

Post#181 by Bogomips » 24 Oct 2016, 11:02

^ Hardware clock set to UTC or to Local Time?
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3223
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#182 by Ed_P » 24 Oct 2016, 16:03

Local time.
Ed

Bogomips
Full of knowledge
Full of knowledge
Posts: 2562
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Porteus-v3.2rc5 bug reports

Post#183 by Bogomips » 24 Oct 2016, 18:27

Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3223
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#184 by Ed_P » 24 Oct 2016, 19:07

hmmmm
Bogomips wrote:changes
  • Time remains stuck on utc. Setting to Network Time has no effect, and

    Code: Select all

    sudo ln -sf /usr/share/zoneinfo/Europe/London  /etc/localtime
    also no effect, although works perfectly well when running without changes.
  • Fixed by setting system time from h/w clock, as noticed h/w clock on local time:

    Code: Select all

    guest@porteus:~$ sudo /sbin/hwclock
    Fri 19 Aug 2016 10:07:31 AM BST  .892266 seconds
    guest@porteus:~$ sudo /sbin/hwclock -s
    guest@porteus:~$ date
    Fri Aug 19 10:07:51 BST 2016
    
I don't understand the function of the two commands. The date/time/zone displays are the same after each one. :unknown:

While the time zone is not that important so long as the clock is right it is apparently a bug hung over from rc4. :(

Clock & time zone work ok in 3.0.1.

Image

Thanks bogomips. :)
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3223
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#185 by Ed_P » 26 Oct 2016, 04:24

Interesting.

I boot, I wait 5 minutes, I unlock the Date & Time settings, I wait 5 minute, I change the Region & City from Europe & London by dragging the time zone bar to America & Toronto, relock the settings then run my changes script:

Code: Select all

#!/bin/sh
# http://forum.porteus.org/viewtopic.php?f=81&t=3776#p27204
  
X=5
if [ ! "$1" == "" ]; then
   X=$1
fi  

find /mnt/live/memory/changes  -iname "*" -mmin -$X
read
exit
with this output:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# ./changes.sh 1
/mnt/live/memory/changes/home/guest/.cache/dconf/user
/mnt/live/memory/changes/var/lib/dhcpcd/dhcpcd-eth1-QuickMoose.lease6
/mnt/live/memory/changes/var/log/secure
/mnt/live/memory/changes/var/log/messages
/mnt/live/memory/changes/etc
/mnt/live/memory/changes/etc/localtime

root@porteus:/home/guest# cp /mnt/live/memory/changes/etc/localtime /home/guest/Backups/Time
root@porteus:/home/guest# cp /mnt/live/memory/changes/home/guest/.cache/dconf/user /home/guest/Backups/Time
root@porteus:/home/guest# 
with the plan to make the two files a module to be loaded when I boot.

5 minutes later I check the Date & Time settings and the Region & City are back to Europe & London. I have not rebooted and I'm not running with changes=.

Code: Select all

guest@porteus:~$ ./bootmode.sh
Boot device: /dev/sda5
Device format: "ntfs" 
Boot ISO: /ISOs/Porteus-CINNAMON-v3.2rc5-x86_64.iso
 Changes will not be saved.
 To save changes create a save.dat file using Porteus Savefile Manager.
Cmdline:  quiet from=/ISOs/Porteus-CINNAMON-v3.2rc5-x86_64.iso kmap=us extramod=/porteus3.2/Modules;/porteus3.2/modsavedat 
guest@porteus:~$ 
:unknown:

Code: Select all

Oct 25 21:50:09 porteus NetworkManager[985]: <info>  [1477446609.0043] device (eth1): supplicant interface state: 4-way handshake -> completed
Oct 25 21:50:09 porteus NetworkManager[985]: <info>  [1477446609.0045] device (eth1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'QuickMoose'.
Oct 25 21:50:09 porteus NetworkManager[985]: <info>  [1477446609.0047] device (eth1): state change: config -> ip-config (reason 'none') [50 70 0]
Oct 25 21:50:09 porteus NetworkManager[985]: <info>  [1477446609.0104] dhcp4 (eth1): activation: beginning transaction (timeout in 45 seconds)
Oct 25 21:50:09 porteus NetworkManager[985]: <info>  [1477446609.0522] dhcp4 (eth1): dhcpcd started with pid 1012
Oct 25 21:50:09 porteus dhcpcd[1012]: DUID 00:01:00:01:1f:a2:c8:51:60:d8:19:1a:a1:fc
Oct 25 21:50:09 porteus dhcpcd[1012]: eth1: IAID 19:1a:a1:fc
Oct 25 21:50:09 porteus dhcpcd[1012]: eth1: soliciting a DHCP lease
Oct 25 21:50:10 porteus dhcpcd[1012]: eth1: soliciting an IPv6 router
Oct 25 21:50:10 porteus ModemManager[1001]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:15.2/0000:06:00.0': not supported by any plugin 
Oct 25 21:50:10 porteus ModemManager[1001]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:15.3/0000:07:00.0': not supported by any plugin 
Oct 25 21:50:10 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 21:50:10 porteus dhcpcd[1012]: eth1: adding address 2604:6000:1010:406b:dea2:2fab:3fdf:f4cb/64
Oct 25 21:50:10 porteus dhcpcd[1012]: eth1: adding route to 2604:6000:1010:406b::/64
Oct 25 21:50:10 porteus dhcpcd[1012]: eth1: requesting DHCPv6 information
Oct 25 21:50:10 porteus NetworkManager[985]: <info>  [1477446610.8693] dhcp6 (eth1): activation: beginning transaction (timeout in 45 seconds)
Oct 25 21:50:12 porteus dhcpcd[1012]: eth1: offered 192.168.200.212 from 192.168.200.1 `ecosystem.home.cisco.com'
Oct 25 21:50:12 porteus dhcpcd[1012]: eth1: leased 192.168.200.212 for 86400 seconds
Oct 25 21:50:12 porteus dhcpcd[1012]: eth1: adding route to 192.168.200.0/24
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3697]   address 192.168.200.212
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3700]   plen 24 (255.255.255.0)
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3701]   gateway 192.168.200.1
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3707]   server identifier 192.168.200.1
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3709]   lease time 86400
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3710]   hostname 'porteus'
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3712]   nameserver '192.168.200.1'
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3713]   domain name 'rochester.rr.com'
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3714] dhcp4 (eth1): state changed unknown -> bound
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3770] device (eth1): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3876] device (eth1): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3904] device (eth1): state change: secondaries -> activated (reason 'none') [90 100 0]
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3916] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3972] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3982] policy: set 'Auto QuickMoose' (eth1) as default for IPv4 routing and DNS
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.3987] policy: set 'Auto QuickMoose' (eth1) as default for IPv6 routing and DNS
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.4039] device (eth1): Activation: successful, device activated.
Oct 25 21:50:12 porteus nm-dispatcher: req:1 'up' [eth1]: new request (0 scripts)
Oct 25 21:50:12 porteus nm-dispatcher: req:1 'up' [eth1]: completed: no scripts
Oct 25 21:50:12 porteus NetworkManager[985]: <info>  [1477446612.4167] manager: startup complete
Oct 25 21:50:12 porteus kernel: [   37.042763] [drm] Please enable CONFIG_MTRR and CONFIG_X86_PAT for better performance thanks to write-combining
Oct 25 21:50:14 porteus dbus[575]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Oct 25 21:50:15 porteus dbus[575]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Oct 25 21:50:20 porteus dbus[575]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Oct 25 21:50:21 porteus dbus[575]: [system] Successfully activated service 'org.freedesktop.UPower'
Oct 25 21:50:23 porteus kernel: [   47.626937] snd_hda_intel 0000:00:01.1: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Oct 25 21:50:25 porteus dbus[575]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
Oct 25 21:50:25 porteus udisksd[1223]: udisks daemon version 2.1.5 starting
Oct 25 21:50:25 porteus dbus[575]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Oct 25 21:50:25 porteus udisksd[1223]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Oct 25 21:50:27 porteus dbus[575]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper)
Oct 25 21:50:27 porteus dbus[575]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 25 21:50:44 porteus cinnamon-killer-daemon: Bound Cinnamon restart to <Control><Alt>Escape.
Oct 25 21:50:50 porteus dbus[575]: [system] Activating service name='org.freedesktop.Accounts' (using servicehelper)
Oct 25 21:50:50 porteus accounts-daemon[1376]: started daemon version 0.6.40
Oct 25 21:50:50 porteus dbus[575]: [system] Successfully activated service 'org.freedesktop.Accounts'
Oct 25 21:51:51 porteus dbus[575]: [system] Activating service name='org.cinnamon.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Oct 25 21:51:51 porteus dbus[575]: [system] Successfully activated service 'org.cinnamon.SettingsDaemon.DateTimeMechanism'
Oct 25 21:52:18 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 21:52:18 porteus NetworkManager[985]: <info>  [1477446738.5696] dhcp4 (eth1): state changed bound -> unknown
Oct 25 21:54:38 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 21:56:04 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 21:58:10 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 21:59:58 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:01:35 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:03:02 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:05:32 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:07:47 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:09:15 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:11:07 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:13:34 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:14:57 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:16:37 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:17:56 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:20:01 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:21:49 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:23:55 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:25:23 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:26:53 porteus dbus[575]: [system] Activating service name='org.cinnamon.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Oct 25 22:26:53 porteus dbus[575]: [system] Successfully activated service 'org.cinnamon.SettingsDaemon.DateTimeMechanism'
Oct 25 22:27:02 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:29:09 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:31:32 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:33:49 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:35:14 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:36:39 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:37:57 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:39:50 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:41:14 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:42:31 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:44:03 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:46:24 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:46:32 porteus dbus[575]: [system] Activating service name='org.cinnamon.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Oct 25 22:46:32 porteus dbus[575]: [system] Successfully activated service 'org.cinnamon.SettingsDaemon.DateTimeMechanism'
Oct 25 22:47:28 porteus dbus[575]: [system] Activating service name='org.cinnamon.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Oct 25 22:47:28 porteus dbus[575]: [system] Successfully activated service 'org.cinnamon.SettingsDaemon.DateTimeMechanism'
Oct 25 22:48:31 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:49:53 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:51:09 porteus dhcpcd[1012]: eth1: Router Advertisement from fe80::22aa:4bff:feeb:a814
Oct 25 22:51:12 porteus dbus[575]: [system] Activating service name='org.cinnamon.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Oct 25 22:51:12 porteus dbus[575]: [system] Successfully activated service 'org.cinnamon.SettingsDaemon.DateTimeMechanism'
Oct 25 22:51:53 porteus root: ACPI action lid is not defined
Oct 25 22:51:55 porteus kernel: [ 3740.084116] Non-volatile memory driver v1.3
Oct 25 22:51:56 porteus NetworkManager[985]: <info>  [1477450316.0347] manager: sleep requested (sleeping: no  enabled: yes)
Oct 25 22:51:56 porteus NetworkManager[985]: <info>  [1477450316.0347] manager: sleeping...
Oct 25 22:51:56 porteus NetworkManager[985]: <info>  [1477450316.0350] device (eth0): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Oct 25 22:51:56 porteus NetworkManager[985]: <info>  [1477450316.0534] manager: NetworkManager state is now ASLEEP
Oct 25 22:51:56 porteus NetworkManager[985]: <info>  [1477450316.0544] audit: op="sleep-control" arg="on" pid=2195 uid=0 result="success"
Oct 25 22:51:56 porteus kernel: [ 3740.933451] PM: Syncing filesystems ... done.
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5521
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v3.2rc5 bug reports

Post#186 by brokenman » 26 Oct 2016, 12:04

It would be really nice if people could become more autonomous when learning. Porteus is based on slackware. Anything outside of modularity you can read about in the slackware documentation. To me, this is noise in the bug thread.

https://docs.slackware.com/howtos:hardw ... local_time
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
francois
Contributor
Contributor
Posts: 5000
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Porteus-v3.2rc5 bug reports

Post#187 by francois » 26 Oct 2016, 12:06

Agreed! Not only finding problems, but doing some substantial work toward the solution, before asking for the solution. Google is my friend.
Voltaire: Le mieux est l'ennemi du bien.

User avatar
Ed_P
Contributor
Contributor
Posts: 3223
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#188 by Ed_P » 26 Oct 2016, 23:14

hmmmm So the new 3.2 Date & Time GUI window is going to be:
Porteus 3.2 wrote:Porteus is based on slackware. Anything outside of modularity you can read about in the slackware documentation.

https://docs.slackware.com/howtos:hardw ... local_time

Remember: Google is your friend.
Or will it only be displayed when the time zone is attempted to be changed?

Maybe it could be the standard window whenever a Help icon is clicked.

:D
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5521
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v3.2rc5 bug reports

Post#189 by brokenman » 27 Oct 2016, 00:25

How many other people have an incorrect system clock by default?
What makes you think your system clock is set to localtime? If it really is set to localtime, why?
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3223
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#190 by Ed_P » 27 Oct 2016, 05:11

brokenman wrote:What makes you think your system clock is set to localtime?
Well when I boot and press F2 and the BIOS window opens the Time value equals what's on the TV's DVR so I would say it's set to local time.
If it really is set to localtime, why?
Why!! Why would I set it to UTC time or leave it set to California time which is what new pcs appear to be set to?

To be clear, so long as the system displays the correct time and maintains the correct time with files it updates especially ones that are used across multiple systems I don't care about the time zone. I am however more than a little annoyed when I try to change a time setting in an OS and it effects the time settings in other OSs booted on the same system which is what happens with 3.2rc5.

Being the perfectionist that you are I thought you would be interested in this situation. Obviously you're not and that's ok it's your system and you are probably tired of working on it alone. I understand. I won't trouble you about this any further.

Putting some kind of warning in 3.2 that multi-booting systems will be effected by clock/time zone changes might be helpful for others that try it. But that's entirely your call. (Hopefully Francois agrees. :D )
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5521
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v3.2rc5 bug reports

Post#191 by brokenman » 28 Oct 2016, 01:22

Being the perfectionist that you are I thought you would be interested in this situation. Obviously you're not and that's ok
It has nothing to do with me being interested in it. The current setup has always been the case and will be for some time yet. The best idea for you would be to have it sync to a network time using ntpd. Then you can always be sure you are looking at the correct time.

Personally I just set my system clock to UTC which is what the majority of modern systems use (including windows) and all is well. You can do this through the Porteus settings tool. If you can do the legwork and find another distro that makes such warnings about time to it's users then I will try to emulate it. I highly recommend reading up on how the time works on a computer. It will save time and one more thread that someone thinks is a bug. I have seen this same complaint various times.

Basically if one OS thinks localtime should be the norm (and writes to the hardware clock) and another has a different idea then you are going to have problems.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2562
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Porteus-v3.2rc5 bug reports: noauto & usb partitions

Post#192 by Bogomips » 07 Nov 2016, 16:54

noauto & partitions of a usb stick

Despite noauto being specified, partitions of a usb stick are mounted:

Code: Select all

guest@porteus:~$ cat /proc/cmdline
quiet from=/dev/sda10/tmp/iso/rc5/i586/Porteus-CINNAMON-v3.2rc5-i586.iso copy2ram ramsize=30% noauto

guest@porteus:~$ mount
tmpfs on /dev/shm type tmpfs (rw)
/mnt/live/run on /run type none (rw,bind)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfsd-fuse on /home/guest/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=guest)
/dev/sdb2 on /mnt/sdb2 type ext4 (rw,noatime,nodiratime)
/dev/sdb1 on /mnt/sdb1 type ext2 (rw,noatime,nodiratime)

root@porteus:/home/guest# usm -i
++++++++++++++++++++++++++++++
usm application information

USM version:  3.2.0
DB version:  160320
Current storage: /tmp/usm
Current config: /etc/usm/usm.conf
Current platform: Porteus-v3.2rc5
Current arch: i686
Current Slackware 14.2
Current kernel 4.7.2-porteus
Diagnostic Output from Initrd:
  • Code: Select all

    quiet from=/dev/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso copy2ram ramsize=30% noauto rootcopy=/dev/sda4/cin_rcp rammod=base extramod=/dev/sda10/xzm debug
    
  • Prior to Check for copy2ram on a Removable Device

    Code: Select all

    cat /proc/self/mountstats
    device tmpfs mounted on / with fstype tmpfs
    device proc mounted on /proc with fstype proc
    device sysfs mounted on /sys with fstype sysfs
    device none mounted on /dev with fstype devtmpfs
    device /dev/sda1 mounted on /mnt/sda1 with fstype reiserfs
    device /dev/sda10 mounted on /mnt/sda10 with fstype ext2
    device /dev/sda3 mounted on /mnt/sda3 with fstype vfat
    device /dev/sda4 mounted on /mnt/sda4 with fstype reiserfs
    device /dev/sda5 mounted on /mnt/sda5 with fstype ext2
    device /dev/sda6 mounted on /mnt/sda6 with fstype ext2
    device /dev/sda8 mounted on /mnt/sda8 with fstype vfat
    device /dev/sda9 mounted on /mnt/sda9 with fstype ext2
    device /dev/loop0 mounted on /mnt/isoloop with fstype iso9660
    device tmpfs mounted on /memory/changes with fstype tmpfs
    device aufs mounted on /union with fstype aufs
    device /dev/loop1 mounted on /memory/images/000-kernel.xzm with fstype squashfs
    device /dev/loop2 mounted on /memory/images/001-core.xzm with fstype squashfs
    device /dev/loop3 mounted on /memory/images/002-xorg.xzm with fstype squashfs
    device /dev/loop4 mounted on /memory/images/003-cinnamon.xzm with fstype squashfs
    device /dev/loop5 mounted on /memory/images/flashplayer-plugin-22.0.0.209-i586-1.xzm with fstype squashfs
    device /dev/loop6 mounted on /memory/images/geany-1.25-i486-bundle.xzm with fstype squashfs
    device /dev/loop7 mounted on /memory/images/gecko-mediaplayer-1.0.9.i686-pkg-1.xzm with fstype squashfs
    device /dev/loop8 mounted on /memory/images/lt_040816.xzm with fstype squashfs
    device /dev/loop9 mounted on /memory/images/terminator-0.97-i486-1_slack.xzm with fstype squashfs
    device aufs mounted on /lib/modules with fstype aufs
    device /dev/sdb1 mounted on /mnt/sdb1 with fstype ext2
    device /dev/sdb2 mounted on /mnt/sdb2 with fstype ext4
    
  • Live system ready. About to Pivot Root:

    Code: Select all

    cat /proc/self/mountstats
    device tmpfs mounted on / with fstype tmpfs
    device proc mounted on /proc with fstype proc
    device sysfs mounted on /sys with fstype sysfs
    device none mounted on /dev with fstype devtmpfs
    device /dev/sda10 mounted on /mnt/sda10 with fstype ext2
    device tmpfs mounted on /memory/changes with fstype tmpfs
    device aufs mounted on /union with fstype aufs
    device /dev/loop1 mounted on /memory/images/000-kernel.xzm with fstype squashfs
    device /dev/loop2 mounted on /memory/images/001-core.xzm with fstype squashfs
    device /dev/loop3 mounted on /memory/images/002-xorg.xzm with fstype squashfs
    device /dev/loop4 mounted on /memory/images/003-cinnamon.xzm with fstype squashfs
    device /dev/loop5 mounted on /memory/images/flashplayer-plugin-22.0.0.209-i586-1.xzm with fstype squashfs
    device /dev/loop6 mounted on /memory/images/geany-1.25-i486-bundle.xzm with fstype squashfs
    device /dev/loop7 mounted on /memory/images/gecko-mediaplayer-1.0.9.i686-pkg-1.xzm with fstype squashfs
    device /dev/loop8 mounted on /memory/images/lt_040816.xzm with fstype squashfs
    device /dev/loop9 mounted on /memory/images/terminator-0.97-i486-1_slack.xzm with fstype squashfs
    
    ls /mnt/
    sda10
    isoloop
    
    ls /union/mnt
    live	isoloop	sda1	sda10	sda3	sda4	sda5	sda6	sda8	
    sda9              sdb1	sdb2
    
    ls /union/mnt/sda{1,4,9,10}
    ls /union/mnt/sdb{1,2}
    
seems to show exiting Initrd with clean bill of health. Suspect something to do with the udevs further down the line.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3223
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#193 by Ed_P » 07 Nov 2016, 18:18

brokenman wrote:Personally I just set my system clock to UTC which is what the majority of modern systems use (including windows) and all is well.
This past weekend the clocks got set back an hour many automatically. My wife's new Windows 10 notebook, my Windows 10 netbook booting Windows all had the correct time in the morning. My Porteus 3.0.1 system on the netbook also had the correct time and correct time zone. My Porteus 3.2rc5 system on the netbook also had the correct time though it's time zone is set for UTC.

The Windows 10 time settings window on our systems recommends the system be set to local time. I can send you a screen print if you'd like. Not sure what modern systems your seeing but I suspect they are server based rather than personal computer based. And I suspect most Porteus users are not running it on servers.
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5521
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v3.2rc5 bug reports

Post#194 by brokenman » 07 Nov 2016, 18:28

Sorry Ed_P, I retract that misinformation. Windows 10 software does indeed use local time but I think the system does not. I had changed my machine long ago to UTC and had forgotten I made the change when I verified it on my machine.

Modern MS systems will indeed move to UTC (that will be fun):
https://azure.microsoft.com/en-us/blog/ ... -time-utc/

EDIT:
These microsoft links appear to say the system uses UTC:
https://support.microsoft.com/en-us/kb/245786
https://msdn.microsoft.com/en-us/librar ... .110).aspx
https://msdn.microsoft.com/en-us/librar ... s.85).aspx

Bogomips I will have to look into this and push it through an update since I have already wrapped everything up for the final release. Thanks for the report.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3223
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#195 by Ed_P » 07 Nov 2016, 20:10

brokenman wrote:These microsoft links appear to say the system uses UTC:
https://support.microsoft.com/en-us/kb/245786
The commands shown don't appear to work with Windows 10.

Code: Select all

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>filetime
'filetime' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>systemtime
'systemtime' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>time
The current time is: 14:49:30.81
Enter the new time:

C:\WINDOWS\system32>
And Command Prompt was run as Admin.


BTW A USB drive with Porteus 2.0 and 2.1 show them also displaying the right time and EDT time zone when booted on the netbook.
Ed

Post Reply