You are not logged in.
MiyoLinux wrote:I may be wrong, but I don't remember being advised to change jessie repositories over to deb.devuan.org. I thought they were supposed to stay as auto.mirror.devuan.org. Seems like deb.devuan.org was introduced with ASCII.
I just looked at the Devuan website, and it's still showing jessie as using auto.mirror.devuan.org.
auto.mirror.devuan.org is still the default repository because there has never been a point release for jessie and that is the repository used on the isos.
This note is also on the website (in several places):
IMPORTANT NOTE: auto.mirror is now deprecated and will be decommissioned. Please make sure you have the latest devuan-keyring package with apt-get install devuan-keyring and then point your /etc/apt/sources.list to deb.devuan.org.
Oh.
I may be wrong, but I don't remember being advised to change jessie repositories over to deb.devuan.org. I thought they were supposed to stay as auto.mirror.devuan.org. Seems like deb.devuan.org was introduced with ASCII.
I just looked at the Devuan website, and it's still showing jessie as using auto.mirror.devuan.org.
I'm not sure how this correlates with and affects Devuan, but Debian made some changes to their Jessie repositories...
^ Sorry Miyo, it was the first link in the startpage search for the song.
No apologies needed! I was just having a bit of fun with you. Good song!
Since the YouTuber (who posted the video that you linked to) discriminates against USAians, here's a link for USAers...
Looking Glass: Brandy (You're a Fine Girl)
MiyoLinux wrote:
I also change the number of minutes that elapse between update checks, but that's voluntary on my part.Can it be configured to only check about 1 minute after boot up? (Each boot up, that is.)
Hi Ron. To be honest, I don't know. I would imagine that it could, but I don't know how. I'm sorry.
In fact, I'm no longer using that notifier...I'm using a version of it that I modified. See this thread starting at this link...
https://dev1galaxy.org/viewtopic.php?pid=14058#p14058
...but that still doesn't answer your question.
No apology needed HoaS. I appreciate your help greatly.
While the delay during the live session certainly isn't ideal, the installed system doesn't have the delay. I think that those who asked for the builds understand the issue and are okay with it.
Thanks again!
Which method are you using to build the images?
I'm sorry, my last response showed up before I saw your last response...if that makes sense. To answer your question...
1. I start with a netinstall and only install the base system.
2. After installation of the base system, I reboot and install only the packages that I want for the system that I'm creating.
3. After creating the system, I use refractasnapshot to create the .iso.
Let me add...
I'm very thankful for the help, and I hope my kidding around wasn't taken the wrong way.
The "Debian Testing" versions are made by request and aren't part of my normal releases. I only made them to try and help users. While the delay during the boot process isn't ideal, it isn't a deal-breaker on my end. I let that situation be known to those who have requested it. Luckily, the delay isn't a problem after installation.
Thank you HoaS...for trying to help figure this out. I most certainly appreciate your time and knowledge.
Well...I was temporarily upgrading to sid/ceres to get synaptic in testing/beowulf. That's my analysis, and I'm stickin' to it!
You guys and your solutions! I'm just barely able to type stuff'n such...let alone do all that fancy-shmancy stuff!
Here it is...
miyo@miyolinux:~$ su
Password:
root@miyolinux:/home/miyo# journalctl -u live-config
-- Logs begin at Sat 2019-04-20 18:53:49 UTC, end at Sat 2019-04-20 19:00:19 UTC. --
Apr 20 18:53:50 miyolinux systemd[1]: Starting live-config contains the components that configure a live system during the boot process (late userspace)....
Apr 20 18:56:53 miyolinux sudo[451]: root : TTY=unknown ; PWD=/ ; USER=miyo ; COMMAND=/usr/bin/sh -c umask 0077 && mkdir -p /home/miyo/.kde/share/config && cat > /home/miyo/.kde/share/config/kdesurc
Apr 20 18:56:53 miyolinux sudo[451]: pam_unix(sudo:session): session opened for user miyo by (uid=0)
Apr 20 18:56:53 miyolinux sudo[451]: pam_unix(sudo:session): session closed for user miyo
Apr 20 18:56:57 miyolinux live-config[373]: live-config: debconf hostname user-setup sudo locales tzdata
Apr 20 18:56:57 miyolinux live-config[373]: Current default time zone: 'Etc/UTC'
Apr 20 18:56:57 miyolinux live-config[373]: Local time is now: Sat Apr 20 18:56:57 UTC 2019.
Apr 20 18:56:57 miyolinux live-config[373]: Universal Time is now: Sat Apr 20 18:56:57 UTC 2019.
Apr 20 18:56:58 miyolinux live-config[373]: slim keyboard-configuration policykit util-linux login xserver-xorg xfce4-panel.
Apr 20 18:56:58 miyolinux systemd[1]: Started live-config contains the components that configure a live system during the boot process (late userspace)..
root@miyolinux:/home/miyo#
Can you post it here then?
Ewww...I'll try. Miyo doesn't come with a browser. I'll try copying the output to a text file and transferring that to another partition.
LOLOL!!!
I think...
MiyoLinux wrote:By commenting out that line, the start job still ran in the live session; however, its time was cut in half...about 2-3 minutes before booting into the desktop...as opposed to 5-7 minutes.
Was the error message the same for both images?
Check the output of my journalctl command for both.
I'm a bit busy at the moment but try a rebuild again later.
Hi HoaS.
Unfortunately, I can't check both. I did run your listed command in the live session, but nothing stood out to me.
I haven't uploaded the 32 bit version yet, so it's not available for observation...it may be a day or two before I upload it.
I don't consider these Debian Testing builds as official MiyoLinux releases...they were built at the request of single users, and in my attempt to help folks, I've ventured beyond my comfort zone.
It's probably something that I'm doing wrong. LOL!!!
MiyoLinux wrote:A start job is running ...blah...blah...blah... no time limit
That appears to be caused by /lib/live/config/0040-sudo, specifically this line:
sudo -u "${LIVE_USERNAME}" sh -c "echo 'SU_TO_ROOT_SU=sudo' >> /home/${LIVE_USERNAME}/.su-to-rootrc"
I just tried unpacking your ISO, commenting the line then repacking the image and it then boots without error (in QEMU).
No idea why it causes the problem but the systemd journal helped me find it
For the record:
journalctl -u live-config
LOLOLOL!
WHEW! Okay...where to begin?
Since the release of the Miyo-Modern Debian Testing version (which I made for one individual), I was asked to make a 32 bit version of Miyo-Modern Debian Testing. Oy!
Taking HoaS's advice into account, I built the .iso twice...once without commenting out that line, and once with the line commented out.
By commenting out that line, the start job still ran in the live session; however, its time was cut in half...about 2-3 minutes before booting into the desktop...as opposed to 5-7 minutes.
To fsmithred (if this is helpful to you),
In order to get the GUI for the locale, keyboard layout, etc., I also had to add libgtk3-perl...libgtk2-perl wasn't enough for some reason.
I can confirm that Synaptic is back in Debian Buster/Testing...not that I would have first-hand knowledge or anything like that.
Rock on HoaS!!!
Might've posted this before; if so, stinkin' listen to it again! It's worth it!
Eric Johnson: Cliffs of Dover
I very rarely post anything by accident. Yeah, let me know if it works. I've never tried it.
(I do occasionally leave stuff out.)
LOL!
Hey...it stinkin' worked! I'm writing this from it now.
Background info...
Host Computer:
2006 Sony Vaio 32 bit
Basic inxi info about the host computer:
CPU~Dual core Intel T2060 (-MCP-)
speed/max~1067/1600 MHz
Mem~995.3MB
The USB used:
8GB Sandisk Cruiser USB-2.0
Installed system:
MiyoLinux (codenamed Addy) i686
Refracta Tools:
refractainstaller-base: 9.4.2
refractainstaller-gui: 9.4.2
refractasnapshot-base: 10.1.1
What I did...
1. Booted from the USB and chose the load to RAM option.
2. Left the USB inserted.
3. When it reached the desktop, I opened gparted and...
a) deleted the .iso from the USB and applied it.
b) created a Partition Table (msdos) on the USB and applied it.
c) created an ext4 file system on the entire USB and applied it.
4. During installation, I allowed the installer to create a swap file.
Worked like a charm! Thanks fsr!
ALL HAIL FSR!!!
Miyo, if you really want to live on the edge, boot to ram and install to the same usb you booted from. Then there's no confusion about which one is the target.
Hey...never thought about trying that!
You mentioned that on purpose, didn't you...because you know I'm going to have to try it now.
Thanks HoaS!
I knew part of the "blah, blah, blah" in the start job line had to do with live-config, but just to be honest, I don't know enough about systemd to even know to look at journald.
Hi Tobyb1906! Thank you so much for the kind words here and on Sourceforge; I truly appreciate it!
Regarding the Debian Testing version. That was made at the request of a user and probably a one-time build. When you say that it gets stuck at loading the wireless, are you speaking about this message during the boot process?
IPv6 ...blah...blah...blah... enp3so: link is not ready
Which is immediately followed by...
A start job is running ...blah...blah...blah... no time limit
If that is what you're referring to, just be patient, and it will eventually boot into the desktop. You may not have seen it, but I left a note on the download page to warn people to expect a +/- 5 minute delay while that start job is running. During one of my test installs on one computer, it took almost 7 minutes. But, it eventually got there. LOLOL!!!
That's just during the live session...it boots normally after installation.
Those start jobs are one of the "benefits" of systemd. LOLOLOL!!!
Thanks again!
Great job Miyo, just finished watching your intro to the Arch Annihilator, Gentoo jinxer
Always enjoy the tunes, I thought you were going to put on a green hat at the end LOL. Keep up the great work!
Ooh, future video request, Devuan/Miyo and music recording/production.
Aw man...wish I'd thought of the green hat! You better know I'd have worn it! LOL!
As for my obvious above-average expertise in the production of high-quality music recordings in my videos, it's pretty in-depth stuff...
1. A kid's plastic toy guitar.
2. A homemade guitar pick made from the lid of a Chlorox Disinfecting Wipes container.
3. A cheap Logitech Webcam/Microphone combo (used for recording sound) connected via USB port.
4. Make a video and hope everything is working.
5. Edit it with Openshot.
...and there you have it!
Thanks ChuangTzu!