Having a boot splash screen would also provide a complete desktop
experience.
On 2020-03-21 05:14 PM, Stefano Trevisani wrote:
> On my notebook Clear Linux takes from 2 to 5 seconds to boot, I don't
> think
> that's such a big deal... Though having a boot screen would be cool.
>
> Il sab 21 mar 2020, 05:51 Mayuresh Kathe <mayuresh(a)kathe.in> ha
> scritto:
>
>> I think the existing boot process is slow anyways and during that
>> period
>> we have to see all the ugliness of the boot messages.
>> Would Auk Kok please reconsider (a previously closed) request #805 by
>> a
>> certain "xRiot" to include Plymouth for displaying a splash screen?
>> I agree that Plymouth might slow down the boot process a bit more, but
>> from a desktop Linux perspective, it would be a huge deal to not force
>> users to see boot messages unless they want to.
>>
>> ~Mayuresh
>> _______________________________________________
>> Dev mailing list -- dev(a)lists.clearlinux.org
>> To unsubscribe send an email to dev-leave(a)lists.clearlinux.org
>>
> _______________________________________________
> Dev mailing list -- dev(a)lists.clearlinux.org
> To unsubscribe send an email to dev-leave(a)lists.clearlinux.org
* William Douglas:
> That looks a little suspicious to me but I am not sure what is mounted
> where.
Your comment made me wonder if I had made a mistake when mounting the
partitions. I ran through the process again, and was finally able to
boot the resulting Clear Linux server. Thank you for helping me get to
this point.
One thing that stands out for me is that /etc is almost empty. It looks
like this system is as "barebone" as it gets, and that I am missing
some basic packages and configuration files (sshd_config among them).
-Ralph
Hi CL Dev team
For some reason (maybe oversight or regulatory) the AWS Clear Linux AMI
is not available for ap-east-1 (Hong Kong).
The thing is, I really needing to get a server up ASAP for a client.
After googling and trying different things, I'm afraid to admit being
out of options now :(
Having standardized on CL and AWS will take any workaround or solution
at this point
Thanks for any help
Chris
Hi, I am currently developing a video analytics project that uses RTSP protocol as a communication method. I am using the protocol to retrieve ip camera feeds over the network. I am also using OpenVINO as my video analytics toolkit.
Before using clearlinux, I have tested my setup on Ubuntu 18.04 Xenial Beaver using either of the following two methods, both of them work just fine:
1. accessing video stream using a precompiled VLC
2. using a python script with OpenCV VideoCapture function.
Based on public reviews, clearlinux OS works faster that other Linux variants. I wanted to try to develop my same project in Ubuntu and transfer to ClearLinux. I have tried the two methods using VLC and python scripts without changing any of my codes, but it didnt work.
So I searched in the the clearlinux forum for any solutions. The first solution I found was by compiling and configuring ffmpeg settings that enables H264 encoding videos to play on firefox. https://community.clearlinux.org/t/how-to-h264-etc-support-for-firefox-incl… . It didnt work with my IP camera streaming, but it did work in playing local video files encoded in H264 format.
Next, I edited my code & tried using streaming via ffplay and also precompiled gstreamer method. Both of them still can't access the IP camera feeds on the network.
In one of my posts I got a reply from the forum saying clearlinux have their own packaging and guidelines and some things are not possible due to license copyright and other reasons. I do realize that H264 is a proprietary format but I do believe the issue is not related to the H264 codec itself, but possibly the RTSP protocol or some other issues in the OS. I do not know how to remedy this issue, and would like to ask for assistance on how to find resolution.
* William Douglas:
> I'd do your normal partition and setup (is this efi btw?)
Here's what "parted -l" shows me after I finished creating partitions.
I selected these types and sizes based on a working Clear Linux server
installation I have made in VirtualBox.
Model: QEMU QEMU HARDDISK (scsi)
Disk /dev/sda: 20.5GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 150MB 149MB fat32 EFI boot, legacy_boot, esp
2 150MB 418MB 268MB linux-swap(v1) linux-swap
3 418MB 20.5GB 20.1GB ext4 /
The legacy_boot flag was an addition I made after an error message shown
by "swupd repair"; see below.
> try and use https://github.com/clearlinux/mixer-tools/blob/master/swupd-extract/main.go
> as a standalone tool for setting up the chroot.
I cloned mixer-tools master branch, installed the "golang" package in
the Debian 10 rescue system, then executed
go run main.go -state /mnt/sda3/state -output /mnt/sda3/output \
https://cdn.download.clearlinux.org/update/32730/ os-core \
os-core-update kernel-native systemd-networkd-autostart
That created a tree of directories in /mnt/sda3/output which looked OK
to me.
> Once that is installed in the chroot you should chroot into it and run
> a swupd repair-os and probably a clr-boot-manager update just to be on
> the safe side.
I (re)mounted a couple of devices, as I would for a Gentoo installation,
and entered the new environment:
mount --types proc /proc /mnt/sda3/output/proc
mount --rbind /sys /mnt/sda3/output/sys
mount --make-rslave /mnt/sda3/output/sys
mount --rbind /dev /mnt/sda3/output/dev
mount --make-rslave /mnt/sda3/output/dev
chroot /mnt/sda3/output /bin/bash
Running "swupd repair" resulted in the following:
-----8<----- snip -----8<----- snip -----8<-----
Diagnosing version 32730
Downloading missing manifests...
Checking for corrupt files
[100%]
[100%]
[100%]
Adding any missing files
[100%]
Repairing corrupt files
[100%]
Removing extraneous files
[100%]
Inspected 17948 files
Calling post-update helper scripts
External command: none
External command: [ERROR] cbm (../src/bootman/bootman.c:L740): Failed to parse given uname release: 4.19.101
External command: [WARNING] cbm (../src/bootman/bootman.c:L90): Unable to parse the currently running kernel: 4.19.101
External command: [ERROR] cbm (../src/bootloaders/syslinux-common.c:L288): No boot partition found, you need to mark the boot partition with "legacy_boot" flag.
External command: [FATAL] cbm (../src/bootman/bootman.c:L163): Cannot initialise bootloader syslinux
External command: Running in chroot, ignoring request: daemon-reload
External command: Running in chroot, ignoring request: restart
Repair successful
-----8<----- snip -----8<----- snip -----8<-----
I then ran "clr-boot-manager update" which was also partially unsuccessful
-----8<----- snip -----8<----- snip -----8<-----
[ERROR] cbm (../src/bootman/bootman.c:L740): Failed to parse given uname release: 4.19.101
[WARNING] cbm (../src/bootman/bootman.c:L90): Unable to parse the currently running kernel: 4.19.101
[ERROR] cbm (../src/bootman/update.c:L189): Cannot determine the currently running kernel
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
-----8<----- snip -----8<----- snip -----8<-----
I did not expect to be able to boot, but tried anyway. That leaves me
with the messages
Booting fomr Hard Disk...
SYSLINUX 6.03 EDD Copyright (C) 1994-2014 H. Peter Anvin et al
WARNING: No configuration file found
boot: _
At the "boot:" prompt I can enter whatever I want, without discernible
effect. I don't even know if this message is related to Clear Linux or
just something caused by the Hoster's VM bootstrapping being unable to
find anything to boot.
I am not sure how to proceed from here.
-Ralph
Currently we have the kernel-lts2019 bundle, so
let's update the kernel-lts to use this bundle.
resolves https://github.com/clearlinux/distribution/issues/1857
---
bundles/kernel-lts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bundles/kernel-lts b/bundles/kernel-lts
index 8db618ce..afc00304 100644
--- a/bundles/kernel-lts
+++ b/bundles/kernel-lts
@@ -6,4 +6,4 @@
# [MAINTAINER]: Bernal Marin, Miguel <miguel.bernal.marin(a)linux.intel.com>
# This is a meta-bundle which include the latest longterm native kernel
-include(kernel-lts2018)
+include(kernel-lts2019)
--
2.25.1
Hello,
I am currently running Ubuntu 18.04 off my 16GB Optane disk (of which only 14GB is being shown in the GNOME-Disks utility).
I have done a full-desktop GNOME install (including Plymouth) and run Firefox as the only additional graphical application along with my required tools; binutils and Vim. All that this configuration takes up is 6GB of disk space.
I had a discussion with someone from the core team at Intel (don't remember his name at all) and he mentioned that the reason I cannot install "Clear Linux OS Desktop" to my Optane disk is because there is some kind of 3 layer filter which prevents installation to targets less than 20GB to avoid dealing with problems and issues arising out of disk overuse.
What I don't understand is, why should a sleek distribution like "Clear Linux OS" mandate that 20GB limit, even in it's desktop configuration, when even a blown-up distribution like Ubuntu does manage to happily install and work painlessly on my 16GB Optane while utilizing less than 50% of disk space.
Can the core team not think about making the installation process more flexible by granting the end-user choice about what to install over-and-above the base system at first-install? For that matter, why does the installer need to even consider installing anything over-and-above the base system when the rest can be installed post first-boot?
I believe someone mentioned that Intel is targeting the "Clear Linux OS Desktop" system towards kernel developers; aren't kernel developers capable enough of using "swupd" at the Terminal CLI or even working with the graphical Software Installation tool?
Something seems to be terribly wrong in the way things are being thought-out regarding this distribution.
Maybe there's confusion about the target audience, maybe something else, but one of the basic principles of "user interface design" mandate that users be granted choices as early and as often as possible.
Do consider.
~Mayuresh
Hello list,
while the documentation's "Deploy in the cloud" section [1] addresses
various providers, I am having a hard time finding information on how to
install Clear Linux on Hetzner CX cloud servers [2].
[1] https://docs.01.org/clearlinux/latest/get-started/index.html#deploy-to-the-…
[2] https://www.hetzner.de/cloud
Hetzner does not support uploading installation images. When I want to
install a Linux distribution for which Hetzner does not provide an ISO
image, e.g. Gentoo Linux, I rely on booting Hetzner's rescue system
(Debian) to partition disks, download the stage3 archive, chroot into
the Gentoo environment, build a kernel, and so forth.
I have searched the C.L. docs, mailing list archive, Hetzner knowledge
base and the Net in general, but have not found what I am looking for.
Does somebody here know how to install Clear Linux on a CX11 server?
Your help is appreciated.
-Ralph
github.com/GNOME is a mirror of the canonical git repositories, which are at
gitlab.gnome.org.
---
autospec/tarball.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/autospec/tarball.py b/autospec/tarball.py
index e8c8506..3149e8b 100644
--- a/autospec/tarball.py
+++ b/autospec/tarball.py
@@ -369,7 +369,7 @@ def name_and_version(name_arg, version_arg, filemanager, config):
# construct github giturl from gnome projects
if not giturl and "download.gnome.org" in url:
- giturl = "https://github.com/GNOME/{}.git".format(name)
+ giturl = "https://gitlab.gnome.org/GNOME/{}.git".format(name)
if "mirrors.kernel.org" in url:
m = re.search(r".*/sourceware/(.*?)/releases/(.*?).tgz", url)
--
2.26.0
Hello,
I accept that I exhibited rude behavior and turned quite vitriolic toward one of the members of this list.
I should have controlled my frustration and instead of spewing venom should have behaved more professionally by helping the core team identify the source of problems exhibited by my hardware while running "Clear Linux OS Desktop", that would have been more productive overall and for myself.
I assure you all that I will never behave in that manner again and no such incident from my end will ever recur.
I apologize.
Best Regards,
~Mayuresh
