Hi Israel,
[inline]
Best regards
Nio
Den 2016-05-03 kl. 21:21, skrev Israel:
Hi Nio,
(inlines)
On 05/03/2016 07:28 AM, Nio Wiklund wrote:
Hi Israel,
[inline]
Best regards
Nio
Den 2016-05-03 kl. 01:51, skrev Israel:
...
hmmm... can I have the log please?
I'm sorry, but I think they are long gone. I have rebooted several
times.
It should be there even when you reboot!
The newer version has a date in the name of the log.
I thought this would be nice to have in the log title.
I will check, what I can find.
Probably the only task that really might need chroot is installing
the
bootloader, and that task might not cause this damage. Now you have
the same [grub] system in the live session and the tarball, so you
probably you do not even need chroot for that task. I don't use
chroot
in my original One Button Installer, but it was introduced in 9w,
where I run a Debian system to install from Ubuntu tarballs.
No. the entire user configuration happens in the chroot (setting the
language/timezone/username/password/installing pae etc...)
Those do not seem to have effected everything poorly.
But, my killing of dbus might. please send the log, this will make
things more clear.
I don't understand what you are using dbus for, and how you are using
it. Or is it activated automatically by the Debian Jessie system?
I am not sure what starts dbus either. It may be started by one of the
install processes. I assumed it was because the menus were updated...
It may be due to something else...
....
yes, you tested installing ToriOS on 2 partitions and Yakkety Yak
(don't
talk back :D) on a 3rd.
This is probably not common.
But I think the log file will be very helpful to me finding the issue
I don't think it makes much difference what previous operating system
there are. Maybe it makes a greater difference if it is an internal
drive or a USB drive.
I can try that (and save the log files), probably later today.
So do you mean that the time you installed on external it made
everything slow in booting?
Please clarify this a bit more.
It is confusing for me (too). I cannot clarify yet, but I suspect that
there is something fishy going on when you run things with chroot.
I tested with the target drive connected via USB 3. I had an HDD and
after that an SSD in the akasa external box. The problems affected
both drives.
I will test with the target drive connected internally via SATA. I
don't know yet, if it will make any difference concerning slowness
(the 1 min 30 s delay). I know it makes a difference concerning the
grub menu: It seems that sudo update-grub finds previous operating
systems in the internal drive (but not in a drive connected via USB 3.
I could test in another computer too, but this one (the Toshiba) is
the fastest, so the most convenient for testing. And it works well
with Lubuntu and the other official Ubuntu flavours as well as with
Debian Jessie.
