Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - VastOne

Pages: [1] 2 3 ... 29
1
  • Updated VSIDO to latest Debian SID kernel – 4.19.0-5-amd64 #1 SMP Debian 4.19.37-1 (2019-05-05)
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

________________________________


The x64 is installing flawlessly (though still a delay during the bootloader installation)
The x64_uEFI installer is not seeing the
Code: [Select]
/lib/live/mount/medium/live/filesystem.squashfs
even though it is clearly there

2
Hardware Help & Support / ceni changes
« on: March 28, 2019, 03:07:33 AM »
ceni is in Debian repos and when ported there the name was changed to Ceni which caused headaches... 

For those who want it here is  fix for Ceni / ceni so that you won't have to change any menus... Run the following to create a ceni symlink

Code: [Select]
sudo ln -s /usr/sbin/Ceni /usr/local/bin/ceni
Keep in mind you must know roots PW in order to run ceni.. In VSIDO default you must change the root PW to know it by running:

Code: [Select]
sudo passwd root

3
  • Updated VSIDO to latest Debian SID kernel – 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15)
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

________________________________


After nearly a year, I have made some changes..

There is only the x64 and x64_uEFI versions now and forevermore

We are up to kernel 4.19 and I anticipate going to 5 in the next month

The only known issues I am aware of is that grub stalls during the install with the following message

Code: [Select]
WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000000 microseconds
I think it is an installer issue related to what @filip fixed in locating the drives, I think the grub part of the installer also cannot find the drives but does the install fine anyway

I also have a new machine now, a uEFII machine donated to VSIDO by Luke / lwfitz so I can do all real time testing now onto HW

I also want to thank jedi, whose friendship and patience are one of the rocks behind VSIDO

Enjoy and please let me know of any issues

4
General Support / uEFI and grub2
« on: March 22, 2019, 12:15:32 AM »
Back story is simple, I have been away for a while and caught up with almost everything regarding the VSIDO build but there seems to be a big change in what ever grub uEFI uses (i know it is grub-efi-amd64) but something is completely different

Before (and still with legacy x64 VSIDO) to make sure eth0 was the correct name of the network interface all we had to do was make sure net.ifnames=0 is on the GRUB_CMDLINE_LINUX_DEFAULT= line in /etc/default/grub file

That has not changed, and as a matter of fact the line is there on a liveCD but what appears to have changed is grub-efi-amd no longer reads /etc/default/grub

The proof is this.. When you boot to the test uEFI ISO that is now available and tab to edit the grub line and add net.ifnames=0 to  the Linux (kernel) line it does in fact boot correctly with eth0 as the network interface name

So the question is simple

When you do add that parameter on a liveCD boot, what exactly is it being written to?

This all works as it should on Legacy x64 VSIDO which is also in that directory suggesting that it is definitely a uefi grub issue only

5
Hello all.. I wanted to share with everyone a discussion in chat I had with Zephyr.. This is it

Hello  Zephyr..! I am well and thank you for asking.. I am working nearly 7 days a week and although it is good to be working again it exhausts me.. I am doing more physical work now than I have ever done.. I am all right but it takes just about all my time..

The real issue with VSIDO is not so much lack of time or effort, it is/was with Debian
About 6 months ago I lost a HD that basically took me out for about a week.. No big deal, I just let VSIDO builds get away from me.. that week turned into a month and when I did try to start with the rebuilds Debian had so much crap that they were including (GCC 5,6,7,8) it caused the ISO to balloon to 400 MB more than when I was up to date.. It pissed me off, but I have started from ground zero before and was happy to do that.. that is about the time that my work started 6-7 days a week plus all my responsibilities here taking care of my invalid mother..

Needless to say I have not had the time, I do want to and will get back to rebuilding VSIDO again but I need some time to do that.. when I do get that time, rest assured, VSIDO will rock once again

Apologies to all in not talking about this sooner but in some ways I actually did need a break

Thanks for understanding

Cheers!


6
  • Updated VSIDO to latest Debian SID kernel – 4.15.0-3-amd64 #1 SMP Debian 4.15.17-1 (2018-04-19)
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

7
General Support / 10 gig log files
« on: April 19, 2018, 01:57:39 AM »
My syslog and daemon.log both grew to 10 gig a piece and basically froze me out of a log in due to the file system running out of space.. after I cleared the logs I could get back in.. Both were too big to open with any editor (TWSS) so I have no idea what caused it.. This is a new install (reinstall) of the build system that had only been up for a day.. I am going to log back in and see if they begin to grow again, but so far they have not and I am at a loss.. never have I seen anything remotely close to this one.. On searches for solutions on google, there have been many instances of the syslog and kernel.log growing and on most there seemed to be an SSD involved which is what I am installed on

Any ideas?

8
  • Corrected an issue with the installer with the help of Filip. Removed dependencies on Debian-MultiMedia repo
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

9
VSIDO Discussions / Debian Bullshit
« on: March 21, 2018, 01:55:54 AM »
So I filed this bug report today

Straight forward, an update killed the ability to run any kind of apt-get update, dist-upgrade or install of any kind.. apt was broken

The response and closing of the bug makes it pretty clear where Debian is still stuck up their own asses

Quote
That's because you use packages from Debian Multimedia (dmo), which
breaks the dependency/file replacement resolution process of apt by
unnecessarily increasing the version number (1:1.12 > 1.14).

I resolved it by pretty much eliminating the multimedia repos and reinstalled the gstreamer stuff from SID

It did not sit well with me today... I never have understood the need to place blame on the end user when reporting an obvious bug

10
I've Got a Life / Aging and things...
« on: February 28, 2018, 02:11:30 AM »
I'll be 58 tomorrow...

Played 36 holes of golf today and played better than I ever have.. Pro level stuff

Hopefully it stays consistent all year.. Golf is a strange game.. The minute you think you have it all figured out it disappears like a fart in the wind

11
General Support / Be wary of NPM update
« on: February 23, 2018, 04:32:17 AM »
A bug in npm (Node Package Manager), the most widely used JavaScript package manager (something I have never heard of),  will change ownership of crucial Linux system folders, such as /etc, /usr, /boot

Guess we're lucky the crazy ass developer of VSIDO has never heard of it either...  ???

12
VSIDO Discussions / Testdisk Photorec and recovering deleted files
« on: February 22, 2018, 01:30:30 AM »
I want to relate a little story that will detail a gotcha, an OH FUCK, and some new info I have gleaned on recovering deleted files

1 - What happened

As most of you know I use grsync, a gui front end for rsync.. I swear by it.. I don't use it that often anymore (use ftp just as easily between systems and smart phone).. lately though I had been building up a nice supply of mp3's from one system using Pithos Fly (standard on VSIDO)

So I setup grsync to transfer a shit ton of new mp3's to this my main multimedia server.. I simply created a new one and this is what it looks like


 

See that one little area that says  Delete on destination?  When I reversed this and created it new, by default this is set to ON (checked) .. Why? Idiotic IMO to have something setup so dangerous that does not say 'ARE YOU SURE YOU WANT THIS?'.. But I missed it.. and you can guess what happens

Anyway, enough bitching about grsync, I still love it but the point of the above is.. be careful... When I set the reverse (this server and my main mp3 loacation) once I executed it started deleting files.. I noticed it right away and killed it but within 3 seconds 2000 files had been deleted

That's the gotcha and OH FUCK moment...

2 - Recovery .. I did some research and found out about testdisk which includes the app photorec.. I booted the VSIDO LiveCD.. installed test disk, and mounted a recovery location (Very important because you don't have enough room with the 1 gig in the liveCD session)

I basically followed the instructions from this site, selected mp3 as the targeted files and restored 4500 of them to the designated mounted recovery location (another partition).. I then used Puddletag to re-tag the files (the files are restored in a numeric naming convention based on the file structure they are found on)...

Did I get back the exact same thing? No.. but I did learn some new things, and did locate the files and restore them.. just not in the same directory structure..

It was an interesting learning experience.. and this bastardized How To just might help some folks down the road

Enjoy..  ???

13
  • Updated VSIDO to latest Debian SID kernel – 4.15.0-1-amd64 #1 SMP Debian 4.15.4-1 (2018-02-18)
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

14
  • Switched to the LXDM display manager, created a VSIDO theme and removed lightdm
  • Added http://www.deb-multimedia.org sid main non-free to sources
  • Installed the gstreamer files that allow for complete multimedia listening and creation
  • Brought back Pithos Fly, set up to record songs as they are played
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

15
I need new eyes on this please to help me spot what is happening

Attached to this are two files.. the journalctl -b of both Stock and New VSIDO ISO.. 1.txt is from the original Stock and 2.txt is from the New VSIDO

This is a journalctl -b section of the Stock ISO that is taking 12 minutes and 27 seconds to run


Code: [Select]
Feb 03 18:12:10 vsido ntpdate[626]: step time server 137.190.2.4 offset 1.628547 sec
Feb 03 18:16:30 vsido groupadd[655]: group added to /etc/group: name=vsido, GID=1000
Feb 03 18:16:30 vsido groupadd[655]: group added to /etc/gshadow: name=vsido
Feb 03 18:16:30 vsido groupadd[655]: new group: name=vsido, GID=1000
Feb 03 18:18:01 vsido useradd[659]: new user: name=vsido, UID=1000, GID=1000, home=/home/vsido, shell=/bin/bash
Feb 03 18:21:01 vsido usermod[668]: change user 'vsido' password
Feb 03 18:21:02 vsido chfn[673]: changed user 'vsido' information
Feb 03 18:21:02 vsido usermod[679]: change user 'vsido' password
Feb 03 18:21:02 vsido gpasswd[685]: user vsido added by root to group audio
Feb 03 18:21:02 vsido gpasswd[690]: user vsido added by root to group cdrom
Feb 03 18:21:02 vsido gpasswd[695]: user vsido added by root to group dip
Feb 03 18:21:02 vsido gpasswd[700]: user vsido added by root to group floppy
Feb 03 18:21:02 vsido gpasswd[705]: user vsido added by root to group video
Feb 03 18:21:02 vsido gpasswd[710]: user vsido added by root to group plugdev
Feb 03 18:21:02 vsido gpasswd[715]: user vsido added by root to group netdev
Feb 03 18:22:32 vsido gpasswd[722]: user vsido added by root to group scanner
Feb 03 18:22:32 vsido gpasswd[727]: user vsido added by root to group bluetooth
Feb 03 18:24:03 vsido sudo[736]:     root : TTY=unknown ; PWD=/ ; USER=vsido ; COMMAND=/bin/sh -c echo 'SU_TO_ROOT_SU=sudo' >> /home/vsido/.su-to-rootrc
Feb 03 18:24:03 vsido sudo[736]: pam_unix(sudo:session): session opened for user vsido by (uid=0)
Feb 03 18:24:03 vsido sudo[736]: pam_unix(sudo:session): session closed for user vsido
Feb 03 18:24:03 vsido sudo[738]:     root : TTY=unknown ; PWD=/ ; USER=vsido ; COMMAND=/usr/bin/gconftool-2 -s -t bool /apps/gksu/sudo-mode true
Feb 03 18:24:03 vsido sudo[738]: pam_unix(sudo:session): session opened for user vsido by (uid=0)
Feb 03 18:24:03 vsido sudo[738]: pam_unix(sudo:session): session closed for user vsido
Feb 03 18:24:03 vsido sudo[740]:     root : TTY=unknown ; PWD=/ ; USER=vsido ; COMMAND=/usr/bin/gconftool-2 -s -t bool /apps/gksu/display-no-pass-info false
Feb 03 18:24:03 vsido sudo[740]: pam_unix(sudo:session): session opened for user vsido by (uid=0)
Feb 03 18:24:03 vsido sudo[740]: pam_unix(sudo:session): session closed for user vsido
Feb 03 18:24:03 vsido sudo[742]:     root : TTY=unknown ; PWD=/ ; USER=vsido ; COMMAND=/bin/sh -c umask 0077 && mkdir -p /home/vsido/.kde/share/config && cat > /home/vsido/.kde/share/config/kdesurc
Feb 03 18:24:03 vsido sudo[742]: pam_unix(sudo:session): session opened for user vsido by (uid=0)
Feb 03 18:24:03 vsido sudo[742]: pam_unix(sudo:session): session closed for user vsido
Feb 03 18:24:04 vsido live-config[369]: live-config: debconf hostname user-setup sudo locales tzdata
Feb 03 18:24:04 vsido live-config[369]: Current default time zone: 'Etc/UTC'
Feb 03 18:24:04 vsido live-config[369]: Local time is now:      Sat Feb  3 18:24:04 UTC 2018.
Feb 03 18:24:04 vsido live-config[369]: Universal Time is now:  Sat Feb  3 18:24:04 UTC 2018.
Feb 03 18:24:04 vsido live-config[369]:  lightdm lxdm keyboard-configuration policykit anacron util-linux login xserver-xorg xscreensaver linstallerdefaultConfiguration file /etc/linstaller/trios doesn't exist. Breaking here.
Feb 03 18:24:04 vsido live-config[369]:  linstallersession.
Feb 03 18:24:04 vsido systemd[1]: Started live-config contains the components that configure a live system during the boot process (late userspace)..
Feb 03 18:24:04 vsido systemd[1]: Reached target Basic System.
Feb 03 18:24:04 vsido systemd[1]: Starting Modem Manager...
Feb 03 18:24:04 vsido systemd[1]: Started Regular background program processing daemon.
Feb 03 18:24:04 vsido systemd[1]: Started Deferred execution scheduler.
Feb 03 18:24:04 vsido systemd[1]: Starting Login Service...
Feb 03 18:24:04 vsido systemd[1]: Starting Initialize hardware monitoring sensors...
Feb 03 18:24:04 vsido systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Feb 03 18:24:04 vsido systemd[1]: Starting Save/Restore Sound Card State...
Feb 03 18:24:04 vsido systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Feb 03 18:24:04 vsido systemd[1]: Started Run anacron jobs.
Feb 03 18:24:04 vsido systemd[1]: Starting Disk Manager...
Feb 03 18:24:04 vsido systemd[1]: Started D-Bus System Message Bus.
Feb 03 18:24:04 vsido cron[845]: (CRON) INFO (pidfile fd = 3)
Feb 03 18:24:05 vsido systemd-logind[847]: Watching system buttons on /dev/input/event1 (Power Button)
Feb 03 18:24:05 vsido systemd-logind[847]: Watching system buttons on /dev/input/event2 (Sleep Button)
Feb 03 18:24:05 vsido systemd-logind[847]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard)
Feb 03 18:24:05 vsido systemd-logind[847]: New seat seat0.
Feb 03 18:24:05 vsido avahi-daemon[851]: Found user 'avahi' (UID 108) and group 'avahi' (GID 115).
Feb 03 18:24:05 vsido avahi-daemon[851]: Successfully dropped root privileges.
Feb 03 18:24:05 vsido avahi-daemon[851]: avahi-daemon 0.7 starting up.
Feb 03 18:24:05 vsido sensors[848]: No sensors found!
Feb 03 18:24:05 vsido sensors[848]: Make sure you loaded all the kernel drivers you need.
Feb 03 18:24:05 vsido sensors[848]: Try sensors-detect to find out which these are.
Feb 03 18:24:05 vsido ModemManager[844]: <info>  ModemManager (version 1.6.8) starting in system bus...
Feb 03 18:24:05 vsido cron[845]: (CRON) INFO (Running @reboot jobs)
Feb 03 18:24:05 vsido udisksd[853]: udisks daemon version 2.7.5 starting
Feb 03 18:24:05 vsido systemd[1]: Started Login Service.
Feb 03 18:24:05 vsido avahi-daemon[851]: Successfully called chroot().
Feb 03 18:24:05 vsido systemd[1]: Starting LSB: Starts and stops Wicd...
Feb 03 18:24:05 vsido avahi-daemon[851]: Successfully dropped remaining capabilities.
Feb 03 18:24:05 vsido avahi-daemon[851]: Loading service file /services/udisks.service.
Feb 03 18:24:05 vsido avahi-daemon[851]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::a00:27ff:fee7:3dae.
Feb 03 18:24:05 vsido avahi-daemon[851]: New relevant interface eth0.IPv6 for mDNS.
Feb 03 18:24:05 vsido avahi-daemon[851]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.1.107.
Feb 03 18:24:05 vsido avahi-daemon[851]: New relevant interface eth0.IPv4 for mDNS.
Feb 03 18:24:05 vsido avahi-daemon[851]: Network interface enumeration completed.
Feb 03 18:24:05 vsido avahi-daemon[851]: Registering new address record for fe80::a00:27ff:fee7:3dae on eth0.*.
Feb 03 18:24:05 vsido avahi-daemon[851]: Registering new address record for 10.0.1.107 on eth0.IPv4.
Feb 03 18:24:05 vsido systemd[1]: Starting WPA supplicant...
Feb 03 18:24:05 vsido rtkit-daemon[849]: Successfully called chroot.
Feb 03 18:24:05 vsido rtkit-daemon[849]: Successfully dropped privileges.
Feb 03 18:24:05 vsido rtkit-daemon[849]: Successfully limited resources.
Feb 03 18:24:05 vsido rtkit-daemon[849]: Running.
Feb 03 18:24:05 vsido dbus-daemon[854]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.4' (uid=0 pid=844 comm="/usr/sbin/ModemManager ")
Feb 03 18:24:05 vsido systemd[1]: Started irqbalance daemon.
Feb 03 18:24:05 vsido rtkit-daemon[849]: Watchdog thread running.
Feb 03 18:24:05 vsido rtkit-daemon[849]: Canary thread running.
Feb 03 18:24:05 vsido systemd[1]: Starting System Logging Service...
Feb 03 18:24:05 vsido systemd[1]: Starting LSB: NFS support files common to client and server...
Feb 03 18:24:05 vsido systemd[1]: Started ACPI event daemon.
Feb 03 18:24:05 vsido systemd[1]: Starting LSB: Set up packet writing devices...
Feb 03 18:24:05 vsido systemd[1]: Started Save/Restore Sound Card State.
Feb 03 18:24:05 vsido systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Feb 03 18:24:05 vsido systemd[1]: Started RealtimeKit Scheduling Policy Service.
Feb 03 18:24:05 vsido sensors[872]: No sensors found!
Feb 03 18:24:05 vsido sensors[872]: Make sure you loaded all the kernel drivers you need.
Feb 03 18:24:05 vsido sensors[872]: Try sensors-detect to find out which these are.
Feb 03 18:24:06 vsido systemd[1]: Started Initialize hardware monitoring sensors.
Feb 03 18:24:06 vsido udftools[871]: Not starting udftools packet writing, no devices listed in /etc/default/udftools.
Feb 03 18:24:06 vsido systemd[1]: Started LSB: Set up packet writing devices.
Feb 03 18:24:06 vsido acpid[870]: starting up with netlink and the input layer
Feb 03 18:24:06 vsido systemd[1]: Started LSB: NFS support files common to client and server.
Feb 03 18:24:06 vsido systemd[1]: Starting Authorization Manager...
Feb 03 18:24:06 vsido systemd[1]: Started Run anacron jobs.
Feb 03 18:24:06 vsido wpa_supplicant[863]: Successfully initialized wpa_supplicant
Feb 03 18:24:06 vsido systemd[1]: Started WPA supplicant.
Feb 03 18:24:06 vsido systemd[1]: Reached target Network.
Feb 03 18:24:06 vsido systemd[1]: Reached target Network is Online.
Feb 03 18:24:06 vsido systemd[1]: Starting LSB: disk temperature monitoring daemon...
Feb 03 18:24:06 vsido systemd[1]: Starting LSB: RPC portmapper replacement...
Feb 03 18:24:06 vsido systemd[1]: Starting LSB: exim Mail Transport Agent...
Feb 03 18:24:06 vsido systemd[1]: Starting Permit User Sessions...
Feb 03 18:24:06 vsido avahi-daemon[851]: Server startup complete. Host name is vsido.local. Local service cookie is 1006096771.
Feb 03 18:24:06 vsido systemd[1]: Starting Network Time Service...
Feb 03 18:24:06 vsido systemd[1]: Starting /etc/rc.local Compatibility...
Feb 03 18:24:06 vsido systemd[1]: Started LSB: RPC portmapper replacement.
Feb 03 18:24:06 vsido systemd[1]: Started /etc/rc.local Compatibility.
Feb 03 18:24:06 vsido systemd[1]: Started Permit User Sessions.
Feb 03 18:24:06 vsido systemd[1]: Starting LXDE Display Manager...
Feb 03 18:24:06 vsido systemd[1]: Started Getty on tty1.
Feb 03 18:24:06 vsido systemd[1]: Reached target Login Prompts.
Feb 03 18:24:06 vsido rsyslogd[868]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.32.0]
Feb 03 18:24:06 vsido systemd[1]: Started System Logging Service.
Feb 03 18:24:06 vsido rsyslogd[868]:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="868" x-info="http://www.rsyslog.com"] start
Feb 03 18:24:06 vsido systemd[1]: Started LXDE Display Manager.
Feb 03 18:24:06 vsido acpid[870]: 27 rules loaded
Feb 03 18:24:06 vsido acpid[870]: waiting for events: event logging is off
Feb 03 18:24:07 vsido hddtemp[889]: Starting disk temperature monitoring daemon: hddtemp: no disks with monitoring capability were found..
Feb 03 18:24:07 vsido systemd[1]: Started LSB: disk temperature monitoring daemon.
Feb 03 18:24:07 vsido avahi-daemon[851]: Service "vsido" (/services/udisks.service) successfully established.
Feb 03 18:24:07 vsido ntpd[916]: ntpd 4.2.8p10@1.3728-o (1): Starting
Feb 03 18:24:07 vsido polkitd[886]: started daemon version 0.105 using authority implementation `local' version `0.105'
Feb 03 18:24:07 vsido dbus-daemon[854]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 03 18:24:07 vsido systemd[1]: Started Authorization Manager.
Feb 03 18:24:07 vsido ntpd[916]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 111:120
Feb 03 18:24:07 vsido ntpd[970]: proto: precision = 1.396 usec (-19)
Feb 03 18:24:07 vsido systemd[1]: Started Network Time Service.
Feb 03 18:24:07 vsido ntpd[970]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
Feb 03 18:24:07 vsido ntpd[970]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2018-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
Feb 03 18:24:07 vsido ntpd[970]: Listen and drop on 0 v6wildcard [::]:123
Feb 03 18:24:07 vsido ntpd[970]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Feb 03 18:24:07 vsido ntpd[970]: Listen normally on 2 lo 127.0.0.1:123
Feb 03 18:24:07 vsido ntpd[970]: Listen normally on 3 eth0 10.0.1.107:123
Feb 03 18:24:07 vsido ntpd[970]: Listen normally on 4 lo [::1]:123
Feb 03 18:24:07 vsido ntpd[970]: Listen normally on 5 eth0 [fe80::a00:27ff:fee7:3dae%2]:123
Feb 03 18:24:07 vsido ntpd[970]: Listening on routing socket on fd #22 for interface updates
Feb 03 18:24:07 vsido systemd[1]: Started Disk Manager.
Feb 03 18:24:07 vsido udisksd[853]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 03 18:24:08 vsido systemd[1]: Started Modem Manager.
Feb 03 18:24:08 vsido ntpd[970]: Soliciting pool server 162.210.111.4
Feb 03 18:24:09 vsido ntpd[970]: Soliciting pool server 74.120.81.219
Feb 03 18:24:09 vsido ntpd[970]: Soliciting pool server 129.250.35.251
Feb 03 18:24:09 vsido exim4[891]: Starting MTA: exim4.
Feb 03 18:24:09 vsido systemd[1]: Started LSB: exim Mail Transport Agent.
Feb 03 18:24:10 vsido ntpd[970]: Soliciting pool server 198.58.110.84
Feb 03 18:24:10 vsido ntpd[970]: Soliciting pool server 108.61.56.35
Feb 03 18:24:10 vsido ntpd[970]: Soliciting pool server 107.161.30.25
Feb 03 18:24:10 vsido ModemManager[844]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:03.0': not supported by any plugin
Feb 03 18:24:11 vsido ntpd[970]: Soliciting pool server 173.230.144.109
Feb 03 18:24:11 vsido ntpd[970]: Soliciting pool server 208.88.126.235
Feb 03 18:24:11 vsido ntpd[970]: Soliciting pool server 45.127.113.2
Feb 03 18:24:11 vsido ntpd[970]: Soliciting pool server 96.126.105.86
Feb 03 18:24:11 vsido wicd[861]: Starting Network connection manager: wicd.
Feb 03 18:24:11 vsido systemd[1]: Started LSB: Starts and stops Wicd.
Feb 03 18:24:11 vsido systemd[1]: Reached target Multi-User System.
Feb 03 18:24:11 vsido systemd[1]: Reached target Graphical Interface.
Feb 03 18:24:12 vsido systemd[1]: Starting Update UTMP about System Runlevel Changes...
Feb 03 18:24:12 vsido systemd[1]: Started Update UTMP about System Runlevel Changes.
Feb 03 18:24:12 vsido systemd[1]: Startup finished in 6.651s (kernel) + 12min 20.520s (userspace) = 12min 27.171s

This is the same section of the New Build ISO's to compare .. This one takes 17.5 seconds to run

Code: [Select]
Feb 03 19:41:21 vsido groupadd[532]: group added to /etc/group: name=vsido, GID=1000
Feb 03 19:41:21 vsido groupadd[532]: group added to /etc/gshadow: name=vsido
Feb 03 19:41:21 vsido groupadd[532]: new group: name=vsido, GID=1000
Feb 03 19:41:21 vsido useradd[536]: new user: name=vsido, UID=1000, GID=1000, home=/home/vsido, shell=/bin/bash
Feb 03 19:41:21 vsido usermod[544]: change user 'vsido' password
Feb 03 19:41:22 vsido chfn[549]: changed user 'vsido' information
Feb 03 19:41:22 vsido usermod[555]: change user 'vsido' password
Feb 03 19:41:22 vsido gpasswd[561]: user vsido added by root to group audio
Feb 03 19:41:22 vsido gpasswd[566]: user vsido added by root to group cdrom
Feb 03 19:41:22 vsido gpasswd[571]: user vsido added by root to group dip
Feb 03 19:41:22 vsido gpasswd[576]: user vsido added by root to group floppy
Feb 03 19:41:22 vsido gpasswd[581]: user vsido added by root to group video
Feb 03 19:41:22 vsido gpasswd[586]: user vsido added by root to group plugdev
Feb 03 19:41:22 vsido gpasswd[591]: user vsido added by root to group netdev
Feb 03 19:41:22 vsido gpasswd[598]: user vsido added by root to group bluetooth
Feb 03 19:41:23 vsido sudo[607]:     root : TTY=unknown ; PWD=/ ; USER=vsido ; COMMAND=/bin/sh -c echo 'SU_TO_ROOT_SU=sudo' >> /home/vsido/.su-to-rootrc
Feb 03 19:41:23 vsido sudo[607]: pam_unix(sudo:session): session opened for user vsido by (uid=0)
Feb 03 19:41:23 vsido sudo[607]: pam_unix(sudo:session): session closed for user vsido
Feb 03 19:41:23 vsido sudo[609]:     root : TTY=unknown ; PWD=/ ; USER=vsido ; COMMAND=/usr/bin/gconftool-2 -s -t bool /apps/gksu/sudo-mode true
Feb 03 19:41:23 vsido sudo[609]: pam_unix(sudo:session): session opened for user vsido by (uid=0)
Feb 03 19:41:23 vsido sudo[609]: pam_unix(sudo:session): session closed for user vsido
Feb 03 19:41:23 vsido sudo[611]:     root : TTY=unknown ; PWD=/ ; USER=vsido ; COMMAND=/usr/bin/gconftool-2 -s -t bool /apps/gksu/display-no-pass-info false
Feb 03 19:41:23 vsido sudo[611]: pam_unix(sudo:session): session opened for user vsido by (uid=0)
Feb 03 19:41:23 vsido sudo[611]: pam_unix(sudo:session): session closed for user vsido
Feb 03 19:41:23 vsido sudo[613]:     root : TTY=unknown ; PWD=/ ; USER=vsido ; COMMAND=/bin/sh -c umask 0077 && mkdir -p /home/vsido/.kde/share/config && cat > /home/vsido/.kde/share/config/kdesurc
Feb 03 19:41:23 vsido sudo[613]: pam_unix(sudo:session): session opened for user vsido by (uid=0)
Feb 03 19:41:23 vsido sudo[613]: pam_unix(sudo:session): session closed for user vsido
Feb 03 19:41:24 vsido live-config[331]: live-config: debconf hostname user-setup sudo locales tzdata
Feb 03 19:41:24 vsido live-config[331]: Current default time zone: 'Etc/UTC'
Feb 03 19:41:24 vsido live-config[331]: Local time is now:      Sat Feb  3 19:41:24 UTC 2018.
Feb 03 19:41:24 vsido live-config[331]: Universal Time is now:  Sat Feb  3 19:41:24 UTC 2018.
Feb 03 19:41:24 vsido live-config[331]:  lxdm keyboard-configuration policykit util-linux login xserver-xorg linstallerdefaultConfiguration file /etc/linstaller/trios doesn't exist. Breaking here.
Feb 03 19:41:24 vsido live-config[331]:  linstallersession.
Feb 03 19:41:24 vsido systemd[1]: Started live-config contains the components that configure a live system during the boot process (late userspace)..
Feb 03 19:41:24 vsido systemd[1]: Reached target Basic System.
Feb 03 19:41:24 vsido systemd[1]: Starting Modem Manager...
Feb 03 19:41:24 vsido systemd[1]: Starting Initialize hardware monitoring sensors...
Feb 03 19:41:24 vsido systemd[1]: Started Regular background program processing daemon.
Feb 03 19:41:24 vsido systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
Feb 03 19:41:24 vsido systemd[1]: Starting System Logging Service...
Feb 03 19:41:24 vsido systemd[1]: Started D-Bus System Message Bus.
Feb 03 19:41:24 vsido cron[709]: (CRON) INFO (pidfile fd = 3)
Feb 03 19:41:25 vsido sensors[708]: No sensors found!
Feb 03 19:41:25 vsido sensors[708]: Make sure you loaded all the kernel drivers you need.
Feb 03 19:41:25 vsido sensors[708]: Try sensors-detect to find out which these are.
Feb 03 19:41:25 vsido cron[709]: (CRON) INFO (Running @reboot jobs)
Feb 03 19:41:25 vsido systemd[1]: Starting LSB: Starts and stops Wicd...
Feb 03 19:41:25 vsido systemd[1]: Starting Login Service...
Feb 03 19:41:25 vsido systemd[1]: Starting WPA supplicant...
Feb 03 19:41:25 vsido systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
Feb 03 19:41:25 vsido sensors[717]: No sensors found!
Feb 03 19:41:25 vsido sensors[717]: Make sure you loaded all the kernel drivers you need.
Feb 03 19:41:25 vsido sensors[717]: Try sensors-detect to find out which these are.
Feb 03 19:41:25 vsido systemd[1]: Started LSB: Starts and stops Wicd.
Feb 03 19:41:25 vsido systemd[1]: Started Initialize hardware monitoring sensors.
Feb 03 19:41:25 vsido ModemManager[707]: <info>  ModemManager (version 1.6.8) starting in system bus...
Feb 03 19:41:25 vsido dbus-daemon[712]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.1' (uid=0 pid=707 comm="/usr/sbin/ModemManager ")
Feb 03 19:41:25 vsido systemd-logind[715]: Watching system buttons on /dev/input/event1 (Power Button)
Feb 03 19:41:25 vsido systemd-logind[715]: Watching system buttons on /dev/input/event2 (Sleep Button)
Feb 03 19:41:25 vsido systemd[1]: Starting Authorization Manager...
Feb 03 19:41:25 vsido rsyslogd[711]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.32.0]
Feb 03 19:41:25 vsido systemd[1]: Started System Logging Service.
Feb 03 19:41:25 vsido rsyslogd[711]:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="711" x-info="http://www.rsyslog.com"] start
Feb 03 19:41:25 vsido systemd-logind[715]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard)
Feb 03 19:41:25 vsido systemd-logind[715]: New seat seat0.
Feb 03 19:41:25 vsido systemd[1]: Started Login Service.
Feb 03 19:41:25 vsido polkitd[722]: started daemon version 0.105 using authority implementation `local' version `0.105'
Feb 03 19:41:25 vsido systemd[1]: Started WPA supplicant.
Feb 03 19:41:25 vsido systemd[1]: Reached target Network.
Feb 03 19:41:25 vsido systemd[1]: Reached target Network is Online.
Feb 03 19:41:25 vsido systemd[1]: Starting LSB: disk temperature monitoring daemon...
Feb 03 19:41:25 vsido systemd[1]: Starting Permit User Sessions...
Feb 03 19:41:25 vsido dbus-daemon[712]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 03 19:41:25 vsido systemd[1]: Started Authorization Manager.
Feb 03 19:41:25 vsido wpa_supplicant[716]: Successfully initialized wpa_supplicant
Feb 03 19:41:25 vsido systemd[1]: Started Permit User Sessions.
Feb 03 19:41:25 vsido systemd[1]: Started Getty on tty1.
Feb 03 19:41:25 vsido systemd[1]: Reached target Login Prompts.
Feb 03 19:41:25 vsido systemd[1]: Starting LXDE Display Manager...
Feb 03 19:41:25 vsido systemd[1]: Started LXDE Display Manager.
Feb 03 19:41:25 vsido systemd[1]: Started LSB: disk temperature monitoring daemon.
Feb 03 19:41:25 vsido systemd[1]: Started Modem Manager.
Feb 03 19:41:25 vsido systemd[1]: Reached target Multi-User System.
Feb 03 19:41:25 vsido systemd[1]: Reached target Graphical Interface.
Feb 03 19:41:25 vsido systemd[1]: Starting Update UTMP about System Runlevel Changes...
Feb 03 19:41:25 vsido systemd[1]: Started Update UTMP about System Runlevel Changes.
Feb 03 19:41:25 vsido systemd[1]: Startup finished in 5.993s (kernel) + 11.599s (userspace) = 17.592s.


Pages: [1] 2 3 ... 29