similar to: console-sanity tool in klibc?

Displaying 20 results from an estimated 3000 matches similar to: "console-sanity tool in klibc?"

2008 Jun 16
0
latest fixes
hello hpa, nothing too exciting, again syncing latest Debian upload and subsequent patch emails. plus wanting to get the ext4dev in line for the Lenny release. :) please review. thanks -- maks please pull git pull git://git.debian.org/~maks/klibc.git maks for the changes: Arthur Loiret (1): Makefile (ARCH): Support sh4 as sh. David H?rdeman (1): [klibc] mount: allow multiple fs
2019 Jan 25
0
[klibc:update-dash] input: Remove HETIO
Commit-ID: e1eb3db72782a1a27bdaa64f8af53450986914c2 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=e1eb3db72782a1a27bdaa64f8af53450986914c2 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 5 Jan 2015 22:20:45 +1100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] input: Remove HETIO
2020 Mar 28
0
[klibc:update-dash] dash: input: Remove HETIO
Commit-ID: e14ba93ad4c4ab9fa8851316d317a4c32d9745eb Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=e14ba93ad4c4ab9fa8851316d317a4c32d9745eb Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 5 Jan 2015 22:20:45 +1100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: input: Remove
2008 Jun 08
0
klibc: Fix breakage with multiple fs specification in mount
Hi, I've already submitted the attached patch to the Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480994 Basically it fixes the argument parsing when running something like "mount -t ext3,ext2...". If that is fixed, I assume that "-t auto" could also be faked by replacing auto with a long list of fs types (or running "fstype" in the
2006 Sep 13
0
[patch] add iso9660 detection to fstype
The attached patch adds iso9660 detection support to fstype. Signed-off-by: David H?rdeman <david at hardeman.nu> -- fstype.c | 17 +++++++++++++++++ iso9660_sb.h | 24 ++++++++++++++++++++++++ 2 files changed, 41 insertions(+) -------------- next part -------------- diff -Nru klibc/usr/kinit/fstype/fstype.c klibc-hack/usr/kinit/fstype/fstype.c ---
2001 Mar 30
4
linux tcsetattr failed
does anyone else see this on linux: localhost sshd[14418]: Accepted password for stevesk from 15.126.45.158 port 49594 localhost sshd[14418]: Setting tty modes failed: Invalid argument redhat with kernel 2.2.17. ttymodes.c: /* Set the new modes for the terminal. */ if (tcsetattr(fd, TCSANOW, &tio) < 0) log("Setting tty modes failed: %.100s", strerror(errno)); return;
2017 Apr 03
0
[PATCH supermin] init: Don't perform ioctl (TIOCSCTTY).
Doing this breaks bash in virt-rescue with the error: bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell Also ^C etc does not work. Removing this ioctl call fixes this. I noticed the problem because supermin's init compiled with dietlibc worked, since the dietlibc header files don't define TIOCSCTTY and hence the ioctl
2003 Apr 02
0
TIOCSCTTY problem/fix
Perhaps this is a known problem, but I only found one instance of someone describing it on the net with no follow-up. I just installed openssh (3.6p1) on a linux system (running an old 2.0.34 kernel) with privilege separation disabled and get the following messages in /var/log/messages: Apr 2 15:48:34 ernestine sshd[6153]: error: ioctl(TIOCSCTTY): Operation not permitted Apr 2 15:48:34
2001 Oct 18
0
Patch for hanging ssh-add under Solaris CDE
One of my users found that the new ssh-add, from the portable OpenSSH CVS as of October 12, was hanging in his .profile while trying to start up CDE (Common Desktop Environment) on Solaris 2.6. The previous one, which was from OpenSSH 2.9p2, did not hang. It turns out that CDE, at least on Solaris 2.6, 7 and 8, runs the user's .profile with a special startup shell that allocates a pseudo-tty
2006 Apr 18
0
[patch] fstype fix ext3 <-> lvm2 detection
From: David H?rdeman <david@2gen.com> if a partition has been used as lvm2 and has not been cleared with pvremove, fstype would recognise the ext3 partition as lvm2. workaround that by detection lvm2 after ext3. Bonuspoint remove long fs list as this one just generates conflicts. Signed-off-by: David H?rdeman <david@2gen.com> Signed-off-by: maximilian attems
2005 Oct 10
2
[Bug 1101] terminal allocation hangs ssh at a blocking tcsetattr (-t option)
http://bugzilla.mindrot.org/show_bug.cgi?id=1101 Summary: terminal allocation hangs ssh at a blocking tcsetattr (- t option) Product: Portable OpenSSH Version: 4.2p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket
2020 Jun 01
0
[PATCH nbdkit 1/3] server: Disallow password=- from non-tty and fix error message (RHBZ#1842440).
This command fails with an incorrect error message: $ nbdkit ssh host=localhost /nosuchfile password=- --run 'qemu-img info $nbd' </dev/null password: nbdkit: error: could not read password from stdin: Inappropriate ioctl for device The error (ENOTTY Inappropriate ioctl for device) is actually a leftover errno from the previous isatty call. This happens because getline(3) can
2002 May 22
1
error: ioctl(TIOCSCTTY)
Hi there I've just upgraded to openssh-3.2.2p1 from openssh-1.2.3 and am having some difficulties. On one of the platforms I'm using (linux kernel 2.2.19 with glibc 2.1.1) it works fine, but on another (linux kernel 2.2.20 with glibc 2.0.7) I get this in the syslog every time I log in: sshd[12277]: Accepted publickey for root from 212.38.67.158 port 2397 ssh2 PAM_pwdb[12277]: (sshd)
1997 Sep 27
0
x-kernel@vger.rutgers.edu Subject: Re: tty chowning Newsgroups: mail.linux.kernel In-Reply-To: <199709261901.PAA04763@dcl.MIT.EDU> Organization: Cc: Bcc: "Theodore Y. Ts''o" <tytso@MIT.EDU> writes: > David Holland <dholland@eecs.harvard.edu> writes: > } Why not build chowning into this process? On TIOCSCTTY, the tty would > } chown itself to the
2006 Nov 01
0
No subject
<Snip> debug1: server_input_channel_req: channel 0 request x11-req reply 0^M debug1: session_by_channel: session 0 channel 0^M debug1: session_input_channel_req: session 0 req x11-req^M debug1: bind port 6010: Can't assign requested address^M debug1: fd 11 setting O_NONBLOCK^M debug2: fd 11 is O_NONBLOCK^M debug1: channel 1: new [X11 inet listener]^M debug1: server_input_channel_req:
2006 Nov 04
0
arrayfields-3.6.0
URLS: - http://raa.ruby-lang.org/project/arrayfields/ - http://www.codeforpeople.com/lib/ruby/arrayfields/ - http://rubyforge.org/projects/arrayfields/ SYNOPSIS: allow keyword access to arrays: require ''arrayfields'' fields = ''name'', ''age'' row = [ ''bob'', 30 ] row.fields = fields row[
2006 Feb 05
1
Add swap support to fstype, second version
This patch adds support for swap detection to fstype (to be applied on top of the previous luks patch). The patch is now against klibc's git tree instead of klibc-1.2. Signed-off-by: David H?rdeman <david@2gen.com> -- fstype.c | 42 ++++++++++++++++++++++++++++++------------ swap_fs.h | 18 ++++++++++++++++++ 2 files changed, 48 insertions(+), 12 deletions(-) --------------
1997 Sep 26
1
tty chowning
About a year ago I outlined a scheme for arranging chowning of the tty end of ptys without needing root privileges. Since then, I haven''t had time to actually implement it. I was thinking about the problem again today, and, having learned a bit about sessions and controlling ttys and stuff, was able to come up with a simpler mechanism. First, observe that the POSIX session mechanism, if
2008 May 26
4
xvm-gate: arrow keys broken in pygrub
One of my test domUs is a opensuse 10.3 PV domain, and it has a /boot/grub/menu.lst file. pygrub is used as bootloader. With xVM 3.1.4, the arrow keys can be used in the pygrub screen. With xVM 3.3-unstable, the arrow keys don''t work for me any more. What I''ve found out so far is that: - gnome-terminal, xterm or dtterm are running with "vt100 application key
2004 Nov 22
1
patch to fix non-echo tty on scp SIGINT
A long-time missing feature (or bug, depending on how you look at it) is that a Ctrl-C at the password prompt in scp does not restore the terminal settings, thus dropping you to the command prompt without any keyboard echo. (A "reset" command will fix it.) This is a pretty regular occurance for me, and some others I've talked to - usually when you realize that the scp command you