Re: Access request to Salsa d-i and installation-guide repo
Hi, Am Donnerstag, 20. Dezember 2018 schrieb Javier Fernández-Sanguino Peña: > Dear colleagues, > > Could some admin of the Salsa repo's add my user (jfs) to both the d-i and > the installation-guide projects in Salsa? Done. Cheers Holger -- Sent from my Jolla phone http://www.jolla.com/
Access request to Salsa d-i and installation-guide repo
Dear colleagues, Could some admin of the Salsa repo's add my user (jfs) to both the d-i and the installation-guide projects in Salsa? I used to have access previously in Alioth but my user was not moved to the new project. I did not needed the access before, but would need it in the coming months to update the translation into Spanish. Thanks! Javier signature.asc Description: PGP signature
Bug#910227: installation-reports: installation on DELL XPS 13 9370
Hello, Just to confirm that alpha4 does not have the tiny font issue any more. Samuel
Elliott Erwitt, Personae, uno dei fotografi più importanti e celebrati del Novecento.
Se non visualizzi correttamente questo messaggio, clicca qui: http://www.mailant.it/nl.aspx?idp=14715&idn=101689&cvp=0E2FA94E582CE1334891A9A307CD9E07B21F6098&idu=22&cvup=526C5E306750B237BD3C52BBF1A0A3E80DF04F81
Re: Bug#833116: fgetty: Incorrect keystroke interpretation
Dear all,
I have tested Anton's suggestions with the following results.
Please, see below for more information.
Steps made:
; su - -c 'adduser testbash'
...
; cat /etc/passwd | grep testbash
testbash:x:1002:1002:Test Bash,,,:/home/testbash:/bin/bash
; cat /etc/inittab | grep /sbin/getty | grep -v '^#'
1:2345:respawn:/sbin/getty --noclear 38400 tty1
2:23:respawn:/sbin/getty --login-program /lib/fgetty/login1 38400 tty2
Following steps, see below.
Thank you!
Ricardo Peliquero
Anton Zinoviev
Wed, 5 Dec 2018 21:29:10 +0200:
> On Wed, Dec 05, 2018 at 08:56:16AM +, Dmitry Bogatov wrote:
> Suppose that we have a working bash shell with UTF-8 console where ñ
> displays properly. Then try this:
>
> LANG=C bash # run a subshell in a non-UTF8 locale
>
> If you press ñ, you will see (arg: 1). The programs (including a
> subshell) also work incorrectly because the locale is not UTF8.
>
Reproduced with expected result (within both login and login1 ttys).
> Now execute this:
>
> LANG=. (some UTF-8 locale)
>
> Now, if you press ñ, you will see (arg: 1) like before. The programs
> (including a subshell), however, will work correctly.
>
Within login1:
typing ñ echoes (arg: 1)
$ LANG=es_AR.UTF-8 bash
typing ñ echoes ñ
> Now execute this:
>
> export LANG
>
> Now also ñ works correctly.
typing ñ echoes ñ
$ exit
typing ñ echoes (arg: 1)
> If you are sure that the problem does not come from the locale,
> another thing to check is to compare the output of
>
> bind -v
> bind -p
>
> in bash where ñ works properly and in bash where ñ leads to (arg: 1).
; diff bind_-v_testbash_login.txt bind_-v_testbash_login1.txt
8c8
< set convert-meta off
---
> set convert-meta on
; diff bind_-p_login.txt bind_-p_login1.txt > \
diff_bind-p_login_login1.txt # (attached)
> Also make sure there are no files ~/.inutrc and the variable INPUTRC
> is unset.
; env # within both ttys
; diff env_login.txt env_login1.txt # (both attached)
2,3c2,4
< LANG=es_AR.UTF-8
< HUSHLOGIN=FALSE
---
> drop_caps=
> INIT_VERSION=sysvinit-
> CONSOLE=/dev/console
5a7
> PREVLEVEL=N
7c9,12
< MAIL=/var/mail/testbash
---
> UID=1002
> init=/sbin/init
> BOOT_IMAGE=Linux
> edd=off
10,11c15,17
< SHLVL=1
< LANGUAGE=es_AR:es
---
> rootmnt=/root
> RUNLEVEL=2
> SHLVL=2
13a20
> AUTOBOOT=YES
; set # within both ttys
; diff set_login.txt set_login1.txt
0a1
> AUTOBOOT=YES
10a12
> BOOT_IMAGE=Linux
11a14
> CONSOLE=/dev/console
22d24
< HUSHLOGIN=FALSE
24,25c26
< LANG=es_AR.UTF-8
< LANGUAGE=es_AR:es
---
> INIT_VERSION=sysvinit-
30d30
< MAIL=/var/mail/testbash
37c37,38
< PPID=2702
---
> PPID=1
> PREVLEVEL=N
41a43
> RUNLEVEL=2
44c46
< SHLVL=1
---
> SHLVL=2
48c50,54
< _=set
---
> _=env
> drop_caps=
> edd=off
> init=/sbin/init
> rootmnt=/root
4c4
< "\e\C-g": abort
---
> "\M-\C-g": abort
11,12c11,12
< "\eOD": backward-char
< "\e[D": backward-char
---
> "\M-OD": backward-char
> "\M-[D": backward-char
16,22c16,22
< "\e\C-h": backward-kill-word
< "\e\C-?": backward-kill-word
< "\e\e[D": backward-word
< "\e[1;5D": backward-word
< "\e[5D": backward-word
< "\eb": backward-word
< "\e<": beginning-of-history
---
> "\M-\C-h": backward-kill-word
> "\M-\C-?": backward-kill-word
> "\M-\M-[D": backward-word
> "\M-[1;5D": backward-word
> "\M-[5D": backward-word
> "\M-b": backward-word
> "\M-<": beginning-of-history
24,27c24,27
< "\eOH": beginning-of-line
< "\e[1~": beginning-of-line
< "\e[H": beginning-of-line
< "\e[200~": bracketed-paste-begin
---
> "\M-OH": beginning-of-line
> "\M-[1~": beginning-of-line
> "\M-[H": beginning-of-line
> "\M-[200~": bracketed-paste-begin
29c29
< "\ec": capitalize-word
---
> "\M-c": capitalize-word
31c31
< "\e\C-]": character-search-backward
---
> "\M-\C-]": character-search-backward
34,40c34,40
< "\e\e": complete
< "\e!": complete-command
< "\e/": complete-filename
< "\e@": complete-hostname
< "\e{": complete-into-braces
< "\e~": complete-username
< "\e$": complete-variable
---
> "\M-\M-": complete
> "\M-!": complete-command
> "\M-/": complete-filename
> "\M-@": complete-hostname
> "\M-{": complete-into-braces
> "\M-~": complete-username
> "\M-$": complete-variable
46c46
< "\e[3~": delete-char
---
> "\M-[3~": delete-char
48,59c48,59
< "\e\\": delete-horizontal-space
< "\e-": digit-argument
< "\e0": digit-argument
< "\e1": digit-argument
< "\e2": digit-argument
< "\e3": digit-argument
< "\e4": digit-argument
< "\e5": digit-argument
< "\e6": digit-argument
< "\e7": digit-argument
< "\e8": digit-argument
< "\e9": digit-argument
---
> "\M-\\": delete-horizontal-space
> "\M--": digit-argument
> "\M-0": digit-argument
> "\M-1": digit-argument
> "\M-2": digit-argument
> "\M-3": digit-argument
> "\M-4": digit-argument
> "\M-5": digit-argument
> "\M-6": digit-argument
> "\M-7": digit-argument
> "\M-8": digit-argument
> "\M-9": digit-argument
87,112c87,112
< "\eA": do-lowercase-version
< "\eB": do-lowercase-version
< "\eC": do-lowercase-version
< "\eD": do-lowercase-version
< "\eE": do-lowercase-version
< "\eF": do-lowercase-version
Bug#916843: installation-report: Buster testing on Dell DX0D thin-client without non-free section
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.69
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
- -- Package-specific info:
Boot method: USB
Image version:
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso,
2018-12-17 Date:
2018-12-19, 10-12 h
Machine: Dell DX0D
Partitions:
> root@detst:/home/user# df -Tl
> Filesystem Type 1K-blocksUsed Available Use% Mounted on
> udev devtmpfs801760 0801760 0% /dev
> tmpfs tmpfs 1630362672160364 2% /run
> /dev/sdb2 btrfs 6347776 1151684 4642012 20% /
> tmpfs tmpfs 815180 0815180 0% /dev/shm
> tmpfs tmpfs 5120 0 5120 0% /run/lock
> tmpfs tmpfs 815180 0815180 0% /sys/fs/cgroup
> /dev/sdb1 ext4 4739200 61312 4417436 2% /boot
> tmpfs tmpfs 163036 0163036 0% /run/user/1000
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [o]
Detect network card:[o]
Configure network: [o]
Detect CD: [o]
Load installer modules: [o]
Clock/timezone setup: [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives: [o]
Install base system:[o]
Install tasks: [o]
Install boot loader:[o]
Overall install:[o ]
Comments/Problems:
My initial problem with this thin-client was the BIOS-password, so I took the
box apart and removed the RTC-battery in order to reset it, but this was not
workable. The password seems to be hardcoded, not secret thought, but
generally known as "Fireport". One can clearly spare the effort, trying to
reset this. Installation was good although without non-free packages only.
Trying to set up non-free firmware throws the following error:
> root@detst:/home/user# aptitude install firmware-linux-nonfree
> firmware-amd-graphics The following NEW packages will be installed:
> amd64-microcode{a} firmware-amd-graphics firmware-linux-nonfree
> firmware-misc-nonfree{a} intel-microcode{a} iucode-tool{a}
> 0 packages upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
> Need to get 6,803 kB of archives. After unpacking 34.4 MB will be used.
> Do you want to continue? [Y/n/?]
> Get: 1 http://ftp2.de.debian.org/debian buster/non-free amd64
> amd64-microcode amd64 3.20180524.1 [34.4 kB] Get: 2
> http://ftp2.de.debian.org/debian buster/non-free amd64
> firmware-amd-graphics all 20180825+dfsg-1 [2,328 kB] Get: 3
> http://ftp2.de.debian.org/debian buster/non-free amd64
> firmware-misc-nonfree all 20180825+dfsg-1 [3,056 kB] Get: 4
> http://ftp2.de.debian.org/debian buster/non-free amd64
> firmware-linux-nonfree all 20180825+dfsg-1 [16.8 kB] Get: 5
> http://ftp2.de.debian.org/debian buster/contrib amd64 iucode-tool amd64
> 2.3.1-1 [62.4 kB] Get: 6 http://ftp2.de.debian.org/debian buster/non-free
> amd64 intel-microcode amd64 3.20180807a.2 [1,306 kB] Fetched 6,803 kB in 1s
> (8,422 kB/s) dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable Note:
> root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin E:
> Sub-process /usr/bin/dpkg returned an error code (2) dpkg: warning:
> 'ldconfig' not found in PATH or not executable dpkg: warning:
> 'start-stop-daemon' not found in PATH or not executable dpkg: error: 2
> expected programs not found in PATH or not executable Note: root's PATH
> should usually contain /usr/local/sbin, /usr/sbin and /sbin
There is only the base-system set up now, without non-free packages xserver
will probably not work, you have to go without proper graphics, at least
graphics are not accelerated.
This box was not supposed to be used as a desktop-system anyway, but in fact
I had in mind to use it as new NAS, degrade the old VIA-based NAS to a
dedicated backup-server and to build a new 2TB-NAS based on the dell-client.
The debian BTRFS-NAS worked so well with asymmetric RAID1, that I would do it
again, fit one slim disk inside, and attach the second one externally via USB.
The internal flash-module with the original OS is fitted into a combined SATA-
and power-jack similarly to HP-t555. Slim disks are 7mm thick, so one could
have up to 2 TB currently.
FreeNAS distribution requires at least 8 GB RAM, which is off limits for this
small box.
- --
Please make sure that the hardware-summary log file, and any other
installation lo
