From owner-freebsd-hackers@freebsd.org Wed Jan 31 12:21:44 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDBDAEC80C1 for ; Wed, 31 Jan 2018 12:21:43 +0000 (UTC) (envelope-from zareian.a.r@gmail.com) Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6619E8158F for ; Wed, 31 Jan 2018 12:21:43 +0000 (UTC) (envelope-from zareian.a.r@gmail.com) Received: by mail-yw0-x229.google.com with SMTP id v196so7318664ywc.6 for ; Wed, 31 Jan 2018 04:21:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=x5J++AgnnyaZCI6DkZPGPWxBN1BGjGOk866bpYsmVbU=; b=obBq0yrOS01AVoWTbTAv4gA97rYl5e5POuUllF81JvpRKzbrXYmvyR/gFqVDKNjcyz mbzcHeW97O5j/PkdQhBh6DvUe5wUMucQXFN5kViKknxqu4yoas5PumDrwB2D6hQiyKF0 Skk1pSeYT0vZpNJNLoBOccvFDrKWj8+NFU/GpFzAfV7hod/vMgV3F9zjmqnezRCZfu2T 61ge4xEJ67CLMkJVBg8fPHftZpBAZOMe0MRMdj52pMwvkRMGOUTnLHUcY9jpYykH3tjm LPwPoBfMBmN//3NXa+k45SXudc0aJ5MCs+Dqy9B0hSgHHqe/u+sZJ1dHBIW9uqJhxWhz 1PJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=x5J++AgnnyaZCI6DkZPGPWxBN1BGjGOk866bpYsmVbU=; b=cNGVzUjAcE4RFcCIHEbRdWuMcTSSonVAMZy323oL5PcJNzYwl3Vg/711F2qVisPLzq h6BM1AGUc2EcFiU7/K4uj2kZ3IVQCxcYRBnnuWudGD0OilXunNFstdnpbRTQg1ruFopZ ZNLy7J1tftP4qFQzWd8OCRhePAvQ1I7Bolglt8qi+FLpA0wxeABPZwkcs//Q29AAwUPN PAQJ4ODXmpaE9uqzC/rEi1OpHoX59bqLC1UqnvfCtSwlICKCZxqL3fL1wnm2LpNWuQdh Qmy8WfY3x2C/eb76fuaO39gygDMl57k78xTzAg3dQsAanEgA8gAX9RcK+BVWVXWpFli3 cjbg== X-Gm-Message-State: AKwxytcbOgNJ1qAESnuNTk29AxaBeVWvVZV/fWQEjSFPZO0JPGeH2OB5 mHVZaHYphwPxCwuOvZKu8UvMaNLeezVkI+K8HTLrRg== X-Google-Smtp-Source: AH8x226StQsjAS4GF5P2yP9BuWg2pGm4T+iQ/F/BH2jdaCM9Jiv83GaTv89fRN6O7eBGj6mimrQyQ96Dsf2Y+IY3O+0= X-Received: by 10.129.49.136 with SMTP id x130mr20886434ywx.468.1517401302242; Wed, 31 Jan 2018 04:21:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.16.212 with HTTP; Wed, 31 Jan 2018 04:21:41 -0800 (PST) From: ali reza zareian Date: Wed, 31 Jan 2018 15:51:41 +0330 Message-ID: Subject: Trouble running sudo or (less ) after After making serial settings To: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Wed, 31 Jan 2018 12:38:10 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 12:21:44 -0000 hello After making serial settings and boot using serial via putty, it is not possible to run sudo command.when i run this command without any parameters it should be print help but it is waiting for a key of the keyboard. if i send ctrl+c then output strings are printed. Code: settings : boot.config =>-S115200 -D ---------------------------------------------- /etc/ttys =>ttyu0 "/usr/libexec/getty std.115200" vt100 onifconsole secure ---------------------------------------------- echo $TERM => vt100 ---------------------------------------------- kern.vty=vt ---------------------------------------------- ssty -a => speed 115200 baud; 0 rows; 0 columns; lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk brkint -inpck -ignpar -parmrk oflags: opost onlcr -ocrnl tab3 -onocr -onlret cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; eol2 = ; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; --------------------------------------------------- From owner-freebsd-hackers@freebsd.org Wed Jan 31 13:52:25 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D71DBECCB2E for ; Wed, 31 Jan 2018 13:52:25 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 560A484DE7 for ; Wed, 31 Jan 2018 13:52:25 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w0VDqH8i087473 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 31 Jan 2018 14:52:18 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: zareian.a.r@gmail.com Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w0VDqE7d050062 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 31 Jan 2018 20:52:14 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Trouble running sudo or (less ) after After making serial settings To: ali reza zareian , freebsd-hackers@freebsd.org References: From: Eugene Grosbein Message-ID: <5A71CA0A.1030101@grosbein.net> Date: Wed, 31 Jan 2018 20:52:10 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 13:52:26 -0000 31.01.2018 19:21, ali reza zareian пишет: > hello > After making serial settings and boot using serial via putty, it is not > possible to run sudo command.when i run this command without any parameters > it should be print help but it is waiting for a key of the keyboard. > if i send ctrl+c then output strings are printed. You may be having flow control problem with /dev/console mentioned in default /etc/syslog.conf as target to auth.notice messages generated by sudo. Try to comment that line out and do "killall -1 syslogd". From owner-freebsd-hackers@freebsd.org Wed Jan 31 16:03:34 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D177ED3824 for ; Wed, 31 Jan 2018 16:03:34 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2AABF6B1D4 for ; Wed, 31 Jan 2018 16:03:33 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 3d30477b-06a0-11e8-b951-f99fef315fd9 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 3d30477b-06a0-11e8-b951-f99fef315fd9; Wed, 31 Jan 2018 16:03:13 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0VG3KlC001467; Wed, 31 Jan 2018 09:03:21 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1517414600.1517.57.camel@freebsd.org> Subject: Re: Trouble running sudo or (less ) after After making serial settings From: Ian Lepore To: ali reza zareian , freebsd-hackers@freebsd.org Date: Wed, 31 Jan 2018 09:03:20 -0700 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 16:03:34 -0000 On Wed, 2018-01-31 at 15:51 +0330, ali reza zareian wrote: >  hello > After making serial settings and boot using serial via putty, it is > not > possible to run sudo command.when i run this command without any > parameters > it should be print help but it is waiting for a key of the keyboard. > if i send ctrl+c then output strings are printed. > > Code: > > settings : > boot.config =>-S115200 -D > ---------------------------------------------- > /etc/ttys =>ttyu0   "/usr/libexec/getty std.115200" > vt100   onifconsole secure Try changing std.115200 to 3wire.115200 to disable flow-control.  I have no idea whether that's the problem, but it's a quick easy thing to try. -- Ian > ---------------------------------------------- > echo $TERM => vt100 > ---------------------------------------------- > kern.vty=vt > ---------------------------------------------- > ssty -a => > speed 115200 baud; 0 rows; 0 columns; > lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl >         -echoprt -altwerase -noflsh -tostop -flusho -pendin > -nokerninfo >         -extproc > iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk >         brkint -inpck -ignpar -parmrk > oflags: opost onlcr -ocrnl tab3 -onocr -onlret > cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts > -dsrflow >         -dtrflow -mdmbuf > cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; >         eol2 = ; erase = ^?; erase2 = ^H; intr = ^C; kill = > ^U; >         lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; >         status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; > --------------------------------------------------- > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd > .org" From owner-freebsd-hackers@freebsd.org Wed Jan 31 16:07:36 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B90BED3BE7 for ; Wed, 31 Jan 2018 16:07:36 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EFA8B6B473 for ; Wed, 31 Jan 2018 16:07:35 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: d37e6f08-06a0-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id d37e6f08-06a0-11e8-91c6-33ffc249f3e8; Wed, 31 Jan 2018 16:07:26 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0VG7Oqm001485; Wed, 31 Jan 2018 09:07:24 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1517414844.1517.59.camel@freebsd.org> Subject: Re: Trouble running sudo or (less ) after After making serial settings From: Ian Lepore To: ali reza zareian , freebsd-hackers@freebsd.org Date: Wed, 31 Jan 2018 09:07:24 -0700 In-Reply-To: <1517414600.1517.57.camel@freebsd.org> References: <1517414600.1517.57.camel@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 16:07:36 -0000 On Wed, 2018-01-31 at 09:03 -0700, Ian Lepore wrote: > On Wed, 2018-01-31 at 15:51 +0330, ali reza zareian wrote: > > > >  hello > > After making serial settings and boot using serial via putty, it is > > not > > possible to run sudo command.when i run this command without any > > parameters > > it should be print help but it is waiting for a key of the > > keyboard. > > if i send ctrl+c then output strings are printed. > > > > Code: > > > > settings : > > boot.config =>-S115200 -D > > ---------------------------------------------- > > /etc/ttys =>ttyu0   "/usr/libexec/getty std.115200" > > vt100   onifconsole secure > Try changing std.115200 to 3wire.115200 to disable flow-control.  I > have no idea whether that's the problem, but it's a quick easy thing > to > try. > > -- Ian Hrm, on second thought... you mention the trouble is with running sudo and less... both things that want to do some terminal-control (blank password, scrolling, etc).  Make sure putty is configured to emulate a vt100 properly.  Maybe try some other kind of terminal emulation. -- Ian From owner-freebsd-hackers@freebsd.org Thu Feb 1 06:15:56 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC9B5F12E05 for ; Thu, 1 Feb 2018 06:15:55 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6CF7B74DB5 for ; Thu, 1 Feb 2018 06:15:55 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: by mail-yw0-x22a.google.com with SMTP id x62so9584294ywg.11 for ; Wed, 31 Jan 2018 22:15:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=bD1uj4pArAejGvvRydxWBWt9VpEWegmxW0I7J+zRg0A=; b=pGt2KJelwmvcADygWzFN27LrfVHtCA6bsffV2zlbPmV64pyFXrQjPpjxXpTD72FGMG 1ycGHCiJs/3GioheWyjrrdFG868QXqYzB1y7g6fbRx8RidKX39293t7yq3NuGN/T1+ox pl1wa2w7n3r5/a8MHMwx1kUpKaE+U3Xz3/f/7QdfqYfLZwzBbmRNqEat3EmNgVQgXgNO gciqWOvcrCn2Pm0xnTxGPop+lqXNuO4aDRh6rGMfWhyqCqFsh4q/tPUmkOEbVHNqSsfl mdzY/U6BZsPD4kF1xb+sKTM/n0caOsRMl7GOZ89jbkpt+jmy4khuTSmS9aXpJCp4AVL2 MWCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=bD1uj4pArAejGvvRydxWBWt9VpEWegmxW0I7J+zRg0A=; b=h9sEBoYpf/5Xgj0YTm9Gf1jx6ebSZiS4N17qL6V6+RcyLmkX4oT1uqJAvtxzcbPUnq NnSZfqP9VGlI9BjYLRKOMU6M8X8VfhTz/zj2iw9u7kyGkXCphWYaZkTMaxkrYRwqDMYj LTu/T7rwshByX89iw5MftUmfRYH2+5AzT33XLeGOtyFbijqzR0i4QIezQedhh8NeCuXL ccnMlFpz7AoRv/vVxv7a7tJ+bubF32HsE91gdeGbIILZmunfCqOxz6+CkpWyC4OueHD8 5biBXOnLxvV7MTauBCCJMWSaWkGPE86ASwZT7q+0ZbDZ8Db1am1J5F9pgzImxU0KBV17 jhAA== X-Gm-Message-State: AKwxytc+kzmNsoXj23VlmPu9FAD/1i0w7is1IT1tymrJ2JEHW+g+5Y+B D6xorD/v0sEaFVVPnyBS5Grhu1aBpditW/Objr5WUQ== X-Google-Smtp-Source: AH8x225DVvzCYf49mSdSQMjaEBsHH5GCfROW0X3OE37Wo6NBoopYvGvt7tPFQOldI6gStxVs8NSCWpcQNj0TQqYCfD8= X-Received: by 10.129.124.67 with SMTP id x64mr24938189ywc.418.1517465754644; Wed, 31 Jan 2018 22:15:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.94.214 with HTTP; Wed, 31 Jan 2018 22:15:34 -0800 (PST) From: Farhan Khan Date: Thu, 1 Feb 2018 01:15:34 -0500 Message-ID: Subject: Printing UTF-8 characters To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 06:15:56 -0000 Hi everyone, Is there a standard way to render historically non-printable UTF-8 characters that will work across all terminals? I am trying to modify a standard FreeBSD utility that may occasionally work with characters in other languages. On some terminals, specifically FreeBSD running in VirtualBox, I see question-marks rather than the expected character. I wonder if this is the proper way to display such non-printable characters or no? I am not the most versed in encoding standards, so pardon any mistakes I might have made. Thanks, -- Farhan Khan PGP Fingerprint: B28D 2726 E2BC A97E 3854 5ABE 9A9F 00BC D525 16EE From owner-freebsd-hackers@freebsd.org Thu Feb 1 07:28:39 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39810EC8C0A for ; Thu, 1 Feb 2018 07:28:39 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (mail.dpedia.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA51C7C64C for ; Thu, 1 Feb 2018 07:28:38 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [89.204.130.116] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1eh9IS-0005XZ-3Y for freebsd-hackers@freebsd.org; Thu, 01 Feb 2018 08:28:36 +0100 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id w117SWhn002311 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 1 Feb 2018 08:28:32 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id w117SWjn002310 for freebsd-hackers@freebsd.org; Thu, 1 Feb 2018 08:28:32 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Thu, 1 Feb 2018 08:28:31 +0100 From: Matthias Apitz To: freebsd-hackers@freebsd.org Subject: Re: Printing UTF-8 characters Message-ID: <20180201072831.GA2239@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-hackers@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.130.116 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 07:28:39 -0000 El d=C3=ADa jueves, febrero 01, 2018 a las 01:15:34a. m. -0500, Farhan Khan= escribi=C3=B3: > Hi everyone, >=20 > Is there a standard way to render historically non-printable UTF-8 > characters that will work across all terminals? I am trying to modify a > standard FreeBSD utility that may occasionally work with characters in > other languages. On some terminals, specifically FreeBSD running in > VirtualBox, I see question-marks rather than the expected character. I > wonder if this is the proper way to display such non-printable characters > or no? Not sure what you mean with 'historically non-printable UTF-8'. UTF-8 is an encoding form (one of more) to present Unicode Codepoints in bytes. If you want to "print" them to paper or PDF there are ways to write them with Postscript and with the correct font-support to bring them into human readable form. If you want to "display" these UTF-8 bytes you need a terminal-software with UTF-8 support, for example from the ports x11/rxvt= -unicode and the fonts for the Codepoint areas you want to display. Btw: Can you display my signature line correctly? There is an UTF-8 encoded Codepoint for a mobile telephone :-) matthias --=20 Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea.d= e/ =F0=9F=93=B1 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub From owner-freebsd-hackers@freebsd.org Thu Feb 1 15:42:58 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC64EED8D69 for ; Thu, 1 Feb 2018 15:42:57 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84A0272643 for ; Thu, 1 Feb 2018 15:42:57 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: by mail-yw0-x22b.google.com with SMTP id t201so10754189ywf.1 for ; Thu, 01 Feb 2018 07:42:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=TZSWrsdBJetofYRj0Qj96tpnKNCCkUXuApOjoT8h54s=; b=JcdrVfHzybSwfTZ0DqogKH9nVcGQq+r4vIEJaUnyXDrS3FXDGPNHr6f2MrCDERd7MS pn/K/o0gL1wIqL3x8jtiww8WS75G8GLNZ9ugfHpLHNESiSHBMJ9RR3h6MrbxFV71PsH5 /2gdwf60B/3xlgr2Om3vYcSuBUBFELL6cjgKJnpKplQOo3NDMr6Mi4Cnu4XHxxnJzOxM eWdonJFmYMVy9Exev8qI/2IEmk9HXVcTONZcTN5uFzjcPvhKGP0ZXK2adY/yqvERlN8O +Jb+kpOTV7NSmVlrHvm+cbb3N/UqeHomo32vWyg2EmyGZOltvcu/nPOAMK40xStCwTtD YuTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=TZSWrsdBJetofYRj0Qj96tpnKNCCkUXuApOjoT8h54s=; b=YKNzYLzpiD3NBzX61k4FVRQ/VbE95ptpO+pWLle3FE4ZU2B2sCaG8e/1gjsSVbBbGf /FLATeMXfh7dCaMp6qyuaPrZQs0oJQVVG+aEwrDIhvgsAS9HsT4TrPFfjuzTeJZ8h7oz Z0elTLiO365bXBLyWhTyEIfv9PDj/iSAd5GWlj84FNylvTEocytbusLlFenNGlRIOG6i Yj1G1HqQ1fZND5cg1UdgGlEnLdGXgviO5GuzNcjmHtuWvGBadRpuDvgAQYGoAH8d70XE 1yAlomBJ1Hcym9V4E1/Yj3lDoNL9nRL41oaCW+Ot5Xn2EHXRhFB+0rGo+VFPRSaPLIuf vaFw== X-Gm-Message-State: AKwxytfca4Q4MVZ5uWXfCfxRL3K2aVUABHwT6SfAOggn75BUzaYZ/v+6 FQsvz2zQa7dQZm3PaELSCv+7LSR3DlRX5lBKyj8TQytw X-Google-Smtp-Source: AH8x227YEx/06yAulcSeR5iAuoq1rbwAD/gXAW27oBqzffpyYLAUe+3uISrZKQA0aauFz/ncMe4OJ9rKHVDpV7l/Ipw= X-Received: by 10.129.83.3 with SMTP id h3mr24958786ywb.268.1517499776809; Thu, 01 Feb 2018 07:42:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.94.214 with HTTP; Thu, 1 Feb 2018 07:42:36 -0800 (PST) In-Reply-To: <20180201072831.GA2239@c720-r314251> References: <20180201072831.GA2239@c720-r314251> From: Farhan Khan Date: Thu, 1 Feb 2018 10:42:36 -0500 Message-ID: Subject: Re: Printing UTF-8 characters To: Matthias Apitz , freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 15:42:58 -0000 On Thu, Feb 1, 2018 at 2:28 AM, Matthias Apitz wrote: > > El d=C3=ADa jueves, febrero 01, 2018 a las 01:15:34a. m. -0500, Farhan Kh= an escribi=C3=B3: > > > Hi everyone, > > > > Is there a standard way to render historically non-printable UTF-8 > > characters that will work across all terminals? I am trying to modify a > > standard FreeBSD utility that may occasionally work with characters in > > other languages. On some terminals, specifically FreeBSD running in > > VirtualBox, I see question-marks rather than the expected character. I > > wonder if this is the proper way to display such non-printable characte= rs > > or no? > > Not sure what you mean with 'historically non-printable UTF-8'. UTF-8 is > an encoding form (one of more) to present Unicode Codepoints in bytes. If > you want to "print" them to paper or PDF there are ways to write them > with Postscript and with the correct font-support to bring them into > human readable form. If you want to "display" these UTF-8 bytes you need > a terminal-software with UTF-8 support, for example from the ports x11/rx= vt-unicode > and the fonts for the Codepoint areas you want to display. > > Btw: Can you display my signature line correctly? There is an UTF-8 encod= ed > Codepoint for a mobile telephone :-) > > matthias > -- > Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea= .de/ =F0=9F=93=B1 +49-176-38902045 > Public GnuPG key: http://www.unixarea.de/key.pub > Sorry, that was a poorly phrased question on my part. Let me try again. I am trying to make text align in columns in a terminal. My understanding is that characters above 0x7E are 3 bytes in length. A modern terminal will render that as either a single question-mark or the character itself, making terminal column alignment easy. But how would an older terminal display a 3-byte character? I am worried that would render as 3 question marks and throw off column alignment. If so, is there a proper way to perform alignment for both newer and older terminals? I am reading this email on Gmail's, so those characters properly render for me :) Thanks, -- Farhan Khan PGP Fingerprint: B28D 2726 E2BC A97E 3854 5ABE 9A9F 00BC D525 16EE From owner-freebsd-hackers@freebsd.org Thu Feb 1 20:18:19 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CC18EC3B90 for ; Thu, 1 Feb 2018 20:18:19 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f43.google.com (mail-it0-f43.google.com [209.85.214.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9BEC8836CE for ; Thu, 1 Feb 2018 20:18:18 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f43.google.com with SMTP id k131so5773927ith.4 for ; Thu, 01 Feb 2018 12:18:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=ZpJHkkhl0Z5V4oBEJTtCtWJCXnrsrJ6LmEITJwhrZPc=; b=fPd9dSmG+/0Lrpf+CvW1taYp/C+qpV5FVjIeihK3/YliG5qOU0a5sMjRbiNkumQT6D XoeyZv6xCVmdEKMkI+BWnK4naYWBLpi2GBnbeJUrezKWYhsBon1A62i5a/z8wLor+68l z9gPgkLAfREnsYLOwinCqQJ7EiNHHkm9qedxNxp7x5OLatGkUANzfuAomsqYhmrbVkHF ipYrtsSJJN4vTgvebvo+ur+6h20H0mUnRyizEUGuY02xAFyOqXWX5sXlqI0i/5JEtGrZ gZ9HI8U9pdvNJrFC+54XtlOAUlixSJEKSGNbV5lBt9Y1RMkgWWLPcadAeCcBCX74Rr+O SLzQ== X-Gm-Message-State: AKwxytdDo1RpvGSwP0FVtfxeqNkAgCnYjulA7hyCN7Z3M51IzCzWc9BZ CoYbpn3OEzaa+Oc4DKbQDLwSxWIm X-Google-Smtp-Source: AH8x2257vc7gnz4QppDrCwMow0XBNchg+uFXVqHYDNutQxekoCgga1m54boBcdwYwDjkR+e13L4tzA== X-Received: by 10.36.215.134 with SMTP id y128mr42325826itg.114.1517516291801; Thu, 01 Feb 2018 12:18:11 -0800 (PST) Received: from mail-io0-f170.google.com (mail-io0-f170.google.com. [209.85.223.170]) by smtp.gmail.com with ESMTPSA id u64sm203683iod.15.2018.02.01.12.18.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 12:18:11 -0800 (PST) Received: by mail-io0-f170.google.com with SMTP id z6so20544454iob.11 for ; Thu, 01 Feb 2018 12:18:11 -0800 (PST) X-Received: by 10.107.131.210 with SMTP id n79mr38673789ioi.215.1517516290882; Thu, 01 Feb 2018 12:18:10 -0800 (PST) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.2.95.152 with HTTP; Thu, 1 Feb 2018 12:18:10 -0800 (PST) In-Reply-To: References: <20180201072831.GA2239@c720-r314251> From: Conrad Meyer Date: Thu, 1 Feb 2018 12:18:10 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Printing UTF-8 characters To: Farhan Khan Cc: Matthias Apitz , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 20:18:19 -0000 You've said a number of things about UTF-8 that appear to be mistaken. Start here: https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-= every-software-developer-absolutely-positively-must-know-about-unicode-and-= character-sets-no-excuses/ On Thu, Feb 1, 2018 at 7:42 AM, Farhan Khan wrote: > On Thu, Feb 1, 2018 at 2:28 AM, Matthias Apitz wrote: >> >> El d=C3=ADa jueves, febrero 01, 2018 a las 01:15:34a. m. -0500, Farhan K= han escribi=C3=B3: >> >> > Hi everyone, >> > >> > Is there a standard way to render historically non-printable UTF-8 >> > characters that will work across all terminals? I am trying to modify = a >> > standard FreeBSD utility that may occasionally work with characters in >> > other languages. On some terminals, specifically FreeBSD running in >> > VirtualBox, I see question-marks rather than the expected character. I >> > wonder if this is the proper way to display such non-printable charact= ers >> > or no? >> >> Not sure what you mean with 'historically non-printable UTF-8'. UTF-8 is >> an encoding form (one of more) to present Unicode Codepoints in bytes. I= f >> you want to "print" them to paper or PDF there are ways to write them >> with Postscript and with the correct font-support to bring them into >> human readable form. If you want to "display" these UTF-8 bytes you need >> a terminal-software with UTF-8 support, for example from the ports x11/r= xvt-unicode >> and the fonts for the Codepoint areas you want to display. >> >> Btw: Can you display my signature line correctly? There is an UTF-8 enco= ded >> Codepoint for a mobile telephone :-) >> >> matthias >> -- >> Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixare= a.de/ =F0=9F=93=B1 +49-176-38902045 >> Public GnuPG key: http://www.unixarea.de/key.pub >> > > Sorry, that was a poorly phrased question on my part. Let me try again. > I am trying to make text align in columns in a terminal. My > understanding is that characters above 0x7E are 3 bytes in length. A > modern terminal will render that as either a single question-mark or > the character itself, making terminal column alignment easy. But how > would an older terminal display a 3-byte character? I am worried that > would render as 3 question marks and throw off column alignment. If > so, is there a proper way to perform alignment for both newer and > older terminals? > > I am reading this email on Gmail's, so those characters properly > render for me :) > > Thanks, > > -- > Farhan Khan > PGP Fingerprint: B28D 2726 E2BC A97E 3854 5ABE 9A9F 00BC D525 16EE > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " From owner-freebsd-hackers@freebsd.org Thu Feb 1 20:24:33 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4A7DEC6483 for ; Thu, 1 Feb 2018 20:24:33 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (mail.dpedia.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7630D83E5C; Thu, 1 Feb 2018 20:24:32 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [93.209.224.150] (helo=[192.168.2.109]) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1ehLPL-0006uR-6D; Thu, 01 Feb 2018 21:24:31 +0100 From: Matthias Apitz To: Conrad Meyer Cc: Farhan Khan , Subject: Re: Printing UTF-8 characters Date: Thu, 01 Feb 2018 21:24:30 +0100 User-Agent: Dekko/0.6.20; Qt/5.4.1; ubuntumirclient; Linux; MIME-Version: 1.0 Message-ID: <33fec4eb-b73a-4f99-97d5-335850c3620e@unixarea.de> In-Reply-To: References: <20180201072831.GA2239@c720-r314251> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 93.209.224.150 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 20:24:34 -0000 On Thursday, 1 February 2018 21:18:10 CET, Conrad Meyer =20 wrote: > You've said a number of things about UTF-8 that appear to be mistaken. > Start here:=20 > ... You are top posting, which is messing up things, and you are not very clear=20= about who said something wrong. matthias --=20 Sent from my Ubuntu phone http://www.unixarea.de/ From owner-freebsd-hackers@freebsd.org Fri Feb 2 03:59:46 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C273EE1FCD for ; Fri, 2 Feb 2018 03:59:46 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (ns1.bitblocks.com [173.228.5.8]) by mx1.freebsd.org (Postfix) with ESMTP id 1A1DF77EF2 for ; Fri, 2 Feb 2018 03:59:45 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id C51F8156E80B; Thu, 1 Feb 2018 19:51:15 -0800 (PST) From: Bakul Shah To: Farhan Khan cc: freebsd-hackers@freebsd.org Subject: Re: Printing UTF-8 characters In-reply-to: Your message of "Thu, 01 Feb 2018 10:42:36 -0500." References: <20180201072831.GA2239@c720-r314251> Comments: In-reply-to Farhan Khan message dated "Thu, 01 Feb 2018 10:42:36 -0500." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <87366.1517543475.1@bitblocks.com> Date: Thu, 01 Feb 2018 19:51:15 -0800 Message-Id: <20180202035130.C51F8156E80B@mail.bitblocks.com> X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 03:59:46 -0000 On Thu, 01 Feb 2018 10:42:36 -0500 Farhan Khan wrote: > Sorry, that was a poorly phrased question on my part. Let me try again. > I am trying to make text align in columns in a terminal. My > understanding is that characters above 0x7E are 3 bytes in length. A > modern terminal will render that as either a single question-mark or > the character itself, making terminal column alignment easy. But how > would an older terminal display a 3-byte character? I am worried that > would render as 3 question marks and throw off column alignment. If > so, is there a proper way to perform alignment for both newer and > older terminals? UTF-8 can use upto 4 bytes to encode a unicode point, depending on the script. For what you want, you can use openoffice like programs that understand unicode and can do complex text layout. Normal terminal programs typically use monospace (fixed width) fonts are simply not capable of what you want. The assumption that one char means one rectangular cell on the screen is too deeply woven in them. Particularly for Indic languages this just doesn't work, You may have N unicode points, each of which require 3 bytes, all together map to a one single glyph. From owner-freebsd-hackers@freebsd.org Sat Feb 3 10:03:21 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F96DED4D06 for ; Sat, 3 Feb 2018 10:03:21 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BCB677F7FE for ; Sat, 3 Feb 2018 10:03:20 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: by mail-wr0-x22d.google.com with SMTP id g21so24864461wrb.13 for ; Sat, 03 Feb 2018 02:03:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=ZMxm7u67Kgp4XJb9rZI7P36Z0iC3HmrOyVN9FQapn+M=; b=cdoPKTa0WSSzf6XshcHGbfms1DvJdPakFzEx3j7ecLW1k1D/AIZfv+G25N3ETKHTFy NXfng0vyAi5Bsu5NgFMrMAcK7FB52zilj2Mvhs9ACOpFwh4fNYYwoi/SQr4h5v7dRY8e N06RupF34t0QC5lrOW4x13Fv/llc4exi3HXqGSbZ8hg9VJOzyUhQEulVjrwtn2z478qk L0Jo2/95RhlEyLYk8mwOlJ/ntljXOdUEgJmuqdJ4aXXWAG2YohV+k0baKjBqxLU4O91M hmpKDyKExLz4m3A66JZk4nvk9gwkNVW5wadXpFGwAfzg52ipi2bMCIxcJNERhJQgS+/X 9RCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=ZMxm7u67Kgp4XJb9rZI7P36Z0iC3HmrOyVN9FQapn+M=; b=DLBMNXeK9U/xlXjYRDJV43iqRxO7VDcJ6GNoU/NAjseKSnM8ci0lxszVbjAQFxnJFZ grtKa6jqkKDLbl8r128wBti9iQyjTPRD5DRuzoSI2ob8jTCH5htRZYOZ4mOgP41BWbmM BUj3jtQ78m2yWbJjyinLKy09MlKQyGgoCb5BGgc7HHibN4twOdkxmDdUtKLBtaj0y5nW XS5/1epUsMiOwcw6Y64DZKViigOURYMRkeDfsUogeR2w7e+d6OPFNQ+qY5N+BvOQEs89 VG8kXpg9S05bmsOpoynDSTvP9cKsw0jAwx+a0og25Z6V1zfiwJPiH6IxJxLDpU4cRPGd +zFQ== X-Gm-Message-State: AKwxytcwGSL6GxnXwmRJeHQTtt4Fd+hsovtYPJv0q9D8zKj/1h5Ha+Gh n4/AV6wMkfNl2esd78JacAv6aQ== X-Google-Smtp-Source: AH8x227FTZms61/CQy2XEXCWqze60GZnxiLQld4+ZjSMg52GAtHYxjpHLmJxyThYNj+XFCU5yhdYBA== X-Received: by 10.223.133.70 with SMTP id 64mr4648889wrh.219.1517652199217; Sat, 03 Feb 2018 02:03:19 -0800 (PST) Received: from azdaja.softwarehood.com (cable-94-189-253-147.dynamic.sbb.rs. [94.189.253.147]) by smtp.gmail.com with ESMTPSA id 188sm4785622wmg.29.2018.02.03.02.03.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Feb 2018 02:03:18 -0800 (PST) To: freebsd-hackers@FreeBSD.org From: Ivan Radovanovic Subject: Setting native resolution for FreeBSD 11.1 Message-ID: <20d9c541-e779-0134-9509-db1c7d00509a@gmail.com> Date: Sat, 3 Feb 2018 11:03:16 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 10:03:21 -0000 Hi guys, I have trouble setting native resolution when booting FreeBSD 11.1 (and I have to do it there because I have to use scfb as X driver since intel doesn't seem to work). What I want to execute is gop set 2 When I put it in loader.rc.local it seems to blink to proper resolution but it is like beastie somehow changes it back to "gop set 0". If I put it directly in loader.rc above beastie-start then beastie again turn it off, if I put it after beastie-start then it works properly when I choose to go to loader prompt, but not if I choose default boot option in menu. It would be really nice if somebody can point me in right direction :-) Kind regards, Ivan From owner-freebsd-hackers@freebsd.org Sat Feb 3 10:54:21 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 736BCEDA664 for ; Sat, 3 Feb 2018 10:54:21 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD82581A20 for ; Sat, 3 Feb 2018 10:54:20 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: by mail-wr0-x22c.google.com with SMTP id a43so17394301wrc.4 for ; Sat, 03 Feb 2018 02:54:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:from:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=THg5abgdmW9pSvvTJjtaJMDeYuTWAcmexwYM5ab5a/g=; b=VPCV9szmZCbBtYxihQL/6nIknLojtXS+waWp8uUyo09kCyjLPgd0cQiXoD0OaTc87p 23ohPIVnKN2M2cVUUthWE+JpbAyX6ZU/I23vMGuu98wAgIsgdbWhaU474kNt+hUNx09z k/0DKyqDpYlg8ZughJjP8rdqn5HkgH9LaYUREeXxh787VxJO3nrjzintsmzIzZBMW2EO 2cPNFOK6A6Bp3PoKqRjPIA79aQPOqdr0K3pcXO1Vi6WRrnQGucQCoB6+gz5tuxoLiKqH lit03GfmZesq7D7Xf8Q1wl5PySd5tIu6pW/P6cwiiK1bDxJg0wi00l/vxs9vmvU+nX7x un6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=THg5abgdmW9pSvvTJjtaJMDeYuTWAcmexwYM5ab5a/g=; b=IZdsDRyMgW79yvuj6DxtSc/2dCsPpRbujPgi8c4W/ASsw4YzRzDx+1Z52rCrhin0ZX emRFtJ6aIXR9jm0xgBp+6/kFCeoUhjIs3ok7JWoVd7qJtDu4/AmrOB5HF94TNaxfzoI7 fEyFdECdRHFOtCjhBU5Cf2U+cMhROGEucEV/Sn1zko9EwgP4gZuNi9t4icSfWUNYN7ld wM1kZGkkknY6yp6X2NIeExB3b59rH1BKhbJ5v47LuYQPvdSY5pBeZkNWMNSLWJd8qCe7 BK8rwHvS+IIcw7CmS6DwdL8oCSyk6Y3hpmfE7GSP2wOJ+UXcZ2ST/PQVqa99RWUoQ7Ei Ue7g== X-Gm-Message-State: AKwxytc94n6531FUQzV543KGSnMl3gPJFgEZfru+Z6Bc/b8ZreMCcjJt 22Cf6Y1xJC3sVLliau6qng6n0A== X-Google-Smtp-Source: AH8x224FYaY0AItkE9GPwIfvAEESrBAEHRRSJFPXbreTT38YdPCDnYt/R2feXzrIOrNFqHA6l6ZKgQ== X-Received: by 10.223.132.103 with SMTP id 94mr2852128wrf.115.1517655259709; Sat, 03 Feb 2018 02:54:19 -0800 (PST) Received: from azdaja.softwarehood.com (cable-94-189-253-147.dynamic.sbb.rs. [94.189.253.147]) by smtp.gmail.com with ESMTPSA id i4sm1832567wmf.3.2018.02.03.02.54.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Feb 2018 02:54:19 -0800 (PST) Subject: Re: Setting native resolution for FreeBSD 11.1 From: Ivan Radovanovic To: freebsd-hackers@FreeBSD.org References: <20d9c541-e779-0134-9509-db1c7d00509a@gmail.com> Message-ID: <4d1294d1-d8fe-1ec4-4575-7aeeebd1b763@gmail.com> Date: Sat, 3 Feb 2018 11:54:14 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20d9c541-e779-0134-9509-db1c7d00509a@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 10:54:21 -0000 On 03/02/2018 11:03, Ivan Radovanovic wrote: > I have trouble setting native resolution when booting FreeBSD 11.1 (and > I have to do it there because I have to use scfb as X driver since intel > doesn't seem to work). > > What I want to execute is > gop set 2 > > When I put it in loader.rc.local it seems to blink to proper resolution > but it is like beastie somehow changes it back to "gop set 0". If I put > it directly in loader.rc above beastie-start then beastie again turn it > off, if I put it after beastie-start then it works properly when I > choose to go to loader prompt, but not if I choose default boot option > in menu. > Solution was to put mode 3 in loader.rc.local (I was trying mode 2, assuming that numbers should be identical, but they are not)