Re: No font package for CJK Unified Ideographs Extension B?
在 2019-03-06三的 09:02 +0800，積丹尼 Dan Jacobson写道： > I still see two empty squares on the first line, seven on the second > line, etc. > That's weird. I can see all of them and the creators of Hanazono claim so [1]. [1] http://fonts.jp/hanazono/
Re: No font package for CJK Unified Ideographs Extension B?
k> I recommend the Hanazono fonts (packaged as 'fonts-hanazono'), which k> supports all of them! Thanks, but on https://www.fileformat.info/info/unicode/block/cjk_unified_ideographs_extension_b/utf8test.htm I still see two empty squares on the first line, seven on the second line, etc.
Re: Laptop still extremely slow after replacing msata ssd and putting old one back
hdv@gmail wrote: On 05/03/2019 04.28, Paul Ezvan wrote: Le 04/03/2019 à 13:32, deloptes a écrit : double check - I had similar observation when trying to setup USB stick boot for a notebook - it's a company property, so not supposed to do that ;-) Well turned out that I had to modify few bios settings to see the usb working at acceptable speed. First I was thinking the one stick was a problem, but after observing the same with a second one I looked at the bios and it did it. regards What does "top" show when your menu takes a long time to load? What is the CPU temp? Maybe you accidentaly touched the cooling system while replacing the SSD? What I forgot to mention (sloppy, sorry for that) is that the slowness already happens at "grub" time. I presume that rules out trouble with my DE (KDE/Plasma) or systemd or something like that. I am thinking hardware trouble too. Not only because the trouble start before the kernel and DE gets loaded, but also because it happens with two different SSDs. It happens with the new one with a freshly installed system, and with the old one that I never had any trouble with before this and that hasn't been changed (by me that is). In both cases the slowness begins immediately after boot. Possibly after the BIOS has run, but definitely before the kernel gets loaded or otherwise during the earliest stages of loading it. Thanks for the pointer to the cooling. I will check that. Grx HdV Is the bios still showing all the installed ram, are there any test you can run from the bios... -- Jimmy Johnson Slackware64 14.2 - KDE 4.14.32 - AMD A8-7600 - EXT4 at sda9 Registered Linux User #380263
Re: Re: No font package for CJK Unified Ideographs Extension B?
Hi, > Now I even see about half of > https://www.fileformat.info/info/unicode/block/cjk_unified_ideographs_extension_b/utf8test.htm > too! I recommend the Hanazono fonts (packaged as 'fonts-hanazono'), which supports all of them!
Re: Fdw Fstab Questions
Stephen P. Molnar wrote: > Finally, if the answer(s), to either or both, is/are 'no' - what should > the fstab entries be in order to allow users to Read/Write? Read/Write depends more or less on what permissions you grant to the directories, where those users are allowed to read and write. The fstab file handles the mounting with default permissions on the device-to-mount-point ... but under the mount point it is all permissions that are not exactly handled by the fstab options. If you want users to be able to u/mount partitions and get default (for example no execution of files) fstab is good. The rest is permissions on the directories below the mount point.
Re: Fdw Fstab Questions
> Here is my durectiry stucture: > > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:0 0 465.8G 0 disk > ??sda1 8:1 0 457.9G 0 part / > ??sda2 8:2 0 1K 0 part > ??sda5 8:5 0 7.9G 0 part [SWAP] > sdb 8:16 0 1.8T 0 disk > ??sdb1 8:17 0 1.8T 0 part /media/comp/900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 > ??sdb2 8:18 0 1K 0 part > ??sdb5 8:21 0 7.9G 0 part > sdc 8:32 0 465.8G 0 disk > ??sdc1 8:33 0 465.8G 0 part > /media/comp/1f363165-2c59-4236-850d-36d1e807099e > sr0 11:0 1 1024M 0 rom > > Here is what I have the installed fstab: > > # /etc/fstab: static file system information. > # > # Use 'blkid' to print the universally unique identifier for a > # device; this may be used with UUID= as a more robust way to name devices > # that works even if disks are added and removed. See fstab(5). > # > # > # / was on /dev/sda1 during installation > UUID=4dc278b7-1792-4e89-b67e-a517fce97d19 / ext4 errors=remount-ro 0 1 > # swap was on /dev/sda5 during installation > UUID=acfb9d26-69c6-4489-88fc-12f5c50bda97 none swap sw 0 0 > /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > > Here is what I'm proposing: > > /dev/sda1 / ext4 defaults 0 1 <== > /dev/sda5 none swap sw 0 0<== > /dev/sdb1 /hdb1 ext4 defaults 0 0 <== > /dev/sdc1 /hdc1 ext4 defaults 0 0 <== It's always recommended to use UUID instead of /dev/sdxN. First line I think should be: /dev/sda1 / ext4 errors=remount-ro 0 1 And the last two: /dev/sdb1 /hdb1 ext4 defaults 0 2 /dev/sdc1 /hdc1 ext4 defaults 0 2 > There are two key questions: > > 1. Will the boot proceed to completion? If you use UUID it should (in fact, the first line, the one for the root partition, should stay the same). Check the mount points for sdb1 and sdc1. Test if you can mount the partitions there before modifying fstab and reboot. > 2. Will users have read/write permission? The 'defaults' option implies that. "defaults - default mount settings (equivalent to rw,suid,dev,exec,auto,nouser,async)." For a better understanding of this you should read [1] and maybe [2]. > Finally, if the answer(s), to either or both, is/are 'no' - what should > the fstab entries be in order to allow users to Read/Write? I think it's appropriate to insist in the use of UUID. > Thanks in advance. You're welcome. Hope everything works fine. [1] https://wiki.debian.org/fstab [2] https://en.wikipedia.org/wiki/Fstab
Fdw Fstab Questions
P;ease see correction, below: Original Message Subject:Fstab Questions Date: Tue, 05 Mar 2019 14:14:55 -0500 From: Stephen P. Molnar To: COLUG I have just reinstalled Debian Stretch and have soee questions about the fstab. I have installed a new hdc. Here is my durectiry stucture: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ??sda1 8:1 0 457.9G 0 part / ??sda2 8:2 0 1K 0 part ??sda5 8:5 0 7.9G 0 part [SWAP] sdb 8:16 0 1.8T 0 disk ??sdb1 8:17 0 1.8T 0 part /media/comp/900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 ??sdb2 8:18 0 1K 0 part ??sdb5 8:21 0 7.9G 0 part sdc 8:32 0 465.8G 0 disk ??sdc1 8:33 0 465.8G 0 part /media/comp/1f363165-2c59-4236-850d-36d1e807099e sr0 11:0 1 1024M 0 rom Here is what I have the installed fstab: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda1 during installation UUID=4dc278b7-1792-4e89-b67e-a517fce97d19 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=acfb9d26-69c6-4489-88fc-12f5c50bda97 none swap sw 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 Here is what I'm proposing: /dev/sda1 / ext4 defaults 0 1 <== /dev/sda5 none swap sw 0 0 <== /dev/sdb1 /hdb1 ext4 defaults 0 0 <== /dev/sdc1 /hdc1 ext4 defaults 0 0 <== There are two key questions: 1. Will the boot proceed to completion? 2. Will users have read/write permission? Finally, if the answer(s), to either or both, is/are 'no' - what should the fstab entries be in order to allow users to Read/Write? Thanks in advance. -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1 -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
Re: User rw Permissions on New Hard Drive
Le 05/03/2019 à 15:17, Stephen P. Molnar a écrit : NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 457.9G 0 part / ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 7.9G 0 part [SWAP] sdb 8:16 0 1.8T 0 disk ├─sdb1 8:17 0 1.8T 0 part /media/comp/900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 ├─sdb2 8:18 0 1K 0 part └─sdb5 8:21 0 7.9G 0 part sdc 8:32 0 465.8G 0 disk └─sdc1 8:33 0 465.8G 0 part /media/comp/1f363165-2c59-4236-850d-36d1e807099e sr0 11:0 1 1024M 0 rom (...) Here is wwhat I'm proposing: /dev/hda1 / ext4 defaults 0 1 /dev/hda5 none swap sw 0 0 /dev/hdb1 /hdb1 ext4 defaults 0 0 /dev/hdc1 /hdc1 ext4 defaults 0 0 There are two key questions: 1. Will the boot proceed to completion? No. /dev/hd* do not exist. 2. Will users have read/write permission? No. At best, you will end up in emergency mode with a read-only root filesystem. Finally, if the answer(s), to either or both, is/are 'no' - what should the fstab entries be in order to allow users to Read/Write? Leave existing / and swap lines as they are. Device names /dev/sd* are not persistent and may change at each boot. Use UUID or LABEL instead of device names to identify the filesystem. Do not name mount points after supposed device names. Choose names based on contents instead. Finally, user permissions are not set in fstab. They are set in the filesystem itself, using chown/chmod if you are using standard Unix permissions or setfacl if you are going with ACLs.
Re: Docker and Container Tools Podman/Buildah/Skopeo
Hi. On Tue, Mar 05, 2019 at 05:07:00PM +0100, to...@tuxteam.de wrote: > On Tue, Mar 05, 2019 at 06:10:40PM +0300, Reco wrote: > > Hi. > > > > On Tue, Mar 05, 2019 at 02:26:24PM +0100, plataleas plataleas wrote: > > > Hi all > > > > > > RedHat announced with RHEL8 that the docker container engine is replaced > > > by > > > > s/RedHat/IBM/g > > > > fixed that for you. > > > > > > > What does the Debian community think of this move? > > > > Mixed, but I speak only for myself. > > On one hand, RedHat is known for its Not-Invented-Here syndrome. > > Endless re-implementation of known tools can hardly do anyone any good. > > Also, vendor lock-in and all that. > > You may dislike Redhat all you want (and hey, I've my beefs with them > too) but they do pay part of the bills (sometimes a significant part!) > for many things that are dear to our hearts. For example gcc, the GNU > C library and many friends (binutils, etc.) through their acquisition > of Cygnus Support (these days called Sourceware) in the 2000s; further > to the Linux kernel (through many kernel people on RH's paylist -- use > your own search engine this time ;-) and many, many more things. Indeed. For instance, RedHat in its infinite wisdom blessed us with pulseaudio (#worksinfedora), systemd (#notabug), GNOME 3 (#itsmodern), Network Manager (aka Notwork Mangler), Flatpack (#designedforshovelware) and many other Finely Designed Programs™. > Actually more than can be said about Canonical, for example (the latter > have at least given back to Debian by having Debian Developers on > payroll, so...) Canonical's famous for their NIH too. Mir, Unity, LXD - it's a long list, although RedHat has longer one. > As for the docker thingies... I get what they are supposed to do. But if > I can convince someone else to to the dirty work... Hear, hear. Reco
Re: Docker and Container Tools Podman/Buildah/Skopeo
On Tue, Mar 05, 2019 at 06:10:40PM +0300, Reco wrote: > Hi. > > On Tue, Mar 05, 2019 at 02:26:24PM +0100, plataleas plataleas wrote: > > Hi all > > > > RedHat announced with RHEL8 that the docker container engine is replaced by > > s/RedHat/IBM/g > > fixed that for you. > > > > What does the Debian community think of this move? > > Mixed, but I speak only for myself. > On one hand, RedHat is known for its Not-Invented-Here syndrome. > Endless re-implementation of known tools can hardly do anyone any good. > Also, vendor lock-in and all that. You may dislike Redhat all you want (and hey, I've my beefs with them too) but they do pay part of the bills (sometimes a significant part!) for many things that are dear to our hearts. For example gcc, the GNU C library and many friends (binutils, etc.) through their acquisition of Cygnus Support (these days called Sourceware) in the 2000s; further to the Linux kernel (through many kernel people on RH's paylist -- use your own search engine this time ;-) and many, many more things. Actually more than can be said about Canonical, for example (the latter have at least given back to Debian by having Debian Developers on payroll, so...) As for the docker thingies... I get what they are supposed to do. But if I can convince someone else to to the dirty work... Cheers [1] https://sourceware.org/news.html -- tomás signature.asc Description: Digital signature
Re: Docker and Container Tools Podman/Buildah/Skopeo
Hi. On Tue, Mar 05, 2019 at 02:26:24PM +0100, plataleas plataleas wrote: > Hi all > > RedHat announced with RHEL8 that the docker container engine is replaced by s/RedHat/IBM/g fixed that for you. > What does the Debian community think of this move? Mixed, but I speak only for myself. On one hand, RedHat is known for its Not-Invented-Here syndrome. Endless re-implementation of known tools can hardly do anyone any good. Also, vendor lock-in and all that. On the other hand, "Docker Community"/"Docker Enterprise" - [1]? That's the road that no sensible program should take. > Does it make sense to prefer podman/buildah/skopeo over the docker > engine on Debian systems as well? I'd suggest runc if you're looking for a viable alternative right now. Reco [1] https://www.docker.com/products
Re: User rw Permissions on New Hard Drive
On 03/01/2019 01:56 PM, David Wright wrote: On Fri 01 Mar 2019 at 08:46:30 (-0500), Stephen P. Molnar wrote: I am sure that you will castigate men for two things: 1. Top posting 2. Not replying to debian-users However, I wanted to keep my reply private in the hope of not starting a flame war. Please see my further comment below. Thanks for your reply. i think that we are on the same page, now. I would ask your indulgence for one more request. Here is my durectiry stucture: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 465.8G 0 disk ├─sda1 8:10 457.9G 0 part / ├─sda2 8:20 1K 0 part └─sda5 8:50 7.9G 0 part [SWAP] sdb 8:16 0 1.8T 0 disk ├─sdb1 8:17 0 1.8T 0 part /media/comp/900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 ├─sdb2 8:18 0 1K 0 part └─sdb5 8:21 0 7.9G 0 part sdc 8:32 0 465.8G 0 disk └─sdc1 8:33 0 465.8G 0 part /media/comp/1f363165-2c59-4236-850d-36d1e807099e sr0 11:01 1024M 0 rom Here is what I have asteh installed fstab: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda1 during installation UUID=4dc278b7-1792-4e89-b67e-a517fce97d19 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=acfb9d26-69c6-4489-88fc-12f5c50bda97 noneswap sw 0 0 /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 Here is wwhat I'm proposing: /dev/hda1 / ext4 defaults 0 1 /dev/hda5 none swap sw 0 0 /dev/hdb1 /hdb1 ext4 defaults 0 0 /dev/hdc1 /hdc1 ext4 defaults 0 0 There are two key questions: 1. Will the boot proceed to completion? 2. Will users have read/write permission? Finally, if the answer(s), to either or both, is/are 'no' - what should the fstab entries be in order to allow users to Read/Write? This is rather critical for my continuing good health. If I crash the system and have to reinstall the OS my wife is going to be greatly displeased. I would like to avoid this fate. Thanks in advance. Regards, Steve -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
Re: which package can remember wifi password
On Tue, Mar 05, 2019 at 05:05:34AM +, Long Wind wrote: > i need a package that can work like cell phone, > which can remember wifi passwords and auto connect to available network > which package can do the job? Thanks! The NetworkManager will do that. -- Henning Follmann | hfollm...@itcfollmann.com
Docker and Container Tools Podman/Buildah/Skopeo
Hi all RedHat announced with RHEL8 that the docker container engine is replaced by a suite of tools in the Container Tools module including podman, buildah and skopeo. https://access.redhat.com/discussions/3697371 What does the Debian community think of this move? Does it make sense to prefer podman/buildah/skopeo over the docker engine on Debian systems as well? Thanks for your thoughts! martin
Re: roundcube installer web helper problem
this was solved by user on roundcube list "In apache, having Header always set X-Frame-Options DENY Prevents roundcube from loading preview and settings." well it solves settings tabs in roundcube not working so I guess it is the same with the installer help page which I've not bothered to test as it's all working now. -- Key ID4BFEBB31
Re: No font package for CJK Unified Ideographs Extension B?
Thanks! It works! Now I even see about half of https://www.fileformat.info/info/unicode/block/cjk_unified_ideographs_extension_b/utf8test.htm too!
Re: Laptop still extremely slow after replacing msata ssd and putting old one back
On 05/03/2019 04.28, Paul Ezvan wrote: > Le 04/03/2019 à 13:32, deloptes a écrit : >> double check - I had similar observation when trying to setup USB stick boot >> for a notebook - it's a company property, so not supposed to do that ;-) >> >> Well turned out that I had to modify few bios settings to see the usb >> working at acceptable speed. First I was thinking the one stick was a >> problem, but after observing the same with a second one I looked at the >> bios and it did it. >> >> regards > > What does "top" show when your menu takes a long time to load? What is the CPU > temp? Maybe you accidentaly touched the cooling system while replacing the > SSD? What I forgot to mention (sloppy, sorry for that) is that the slowness already happens at "grub" time. I presume that rules out trouble with my DE (KDE/Plasma) or systemd or something like that. I am thinking hardware trouble too. Not only because the trouble start before the kernel and DE gets loaded, but also because it happens with two different SSDs. It happens with the new one with a freshly installed system, and with the old one that I never had any trouble with before this and that hasn't been changed (by me that is). In both cases the slowness begins immediately after boot. Possibly after the BIOS has run, but definitely before the kernel gets loaded or otherwise during the earliest stages of loading it. Thanks for the pointer to the cooling. I will check that. Grx HdV
Re: which package can remember wifi password
On 3/5/19, Long Wind wrote: > i need a package that can work like cell phone, > which can remember wifi passwords and auto connect to available network > which package can do the job? Thanks! I guess this is what you're looking for: https://wiki.debian.org/WiFi/HowToUse Regards!
