linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault-vYW+cPY1g1pg9hUCZPvPmw@public.gmane.org>
To: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [ANNOUNCE] util-linux v2.23-rc1
Date: Fri, 22 Mar 2013 14:41:47 +0100	[thread overview]
Message-ID: <20130322134147.GA6125@type.bordeaux.inria.fr> (raw)
In-Reply-To: <20130322125621.GA6278-s5vVilr7EKH/9pzu0YdTqQ@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 304 bytes --]

Hello,

Karel Zak, le Fri 22 Mar 2013 13:56:21 +0100, a écrit :
> The util-linux release v2.23-rc1 is available at
>  
>    ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.23
>     
> Feedback and bug reports, as always, are welcomed.

Here is a couple of obvious fixes for non-linux systems.

Samuel

[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 651 bytes --]

diff --git a/login-utils/sulogin.c b/login-utils/sulogin.c
index db5f41e..621df1e 100644
--- a/login-utils/sulogin.c
+++ b/login-utils/sulogin.c
@@ -118,7 +118,9 @@ static void tcinit(struct console *con)
 		cfsetispeed(tio, ispeed);
 		cfsetospeed(tio, ospeed);
 
+#ifdef HAVE_STRUCT_TERMIOS_C_LINE
 		tio->c_line         = 0;
+#endif
 		tio->c_cc[VTIME]    = 0;
 		tio->c_cc[VMIN]     = 1;
 
@@ -198,7 +200,7 @@ static void tcfinal(struct console *con)
 	tio->c_cc[VEOF]     = CEOF;
 #ifdef VSWTC
 	tio->c_cc[VSWTC]    = _POSIX_VDISABLE;
-#else
+#elif defined(VSWTCH)
 	tio->c_cc[VSWTCH]   = _POSIX_VDISABLE;
 #endif
 	tio->c_cc[VSTART]   = CSTART;

      parent reply	other threads:[~2013-03-22 13:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 12:56 [ANNOUNCE] util-linux v2.23-rc1 Karel Zak
     [not found] ` <20130322125621.GA6278-s5vVilr7EKH/9pzu0YdTqQ@public.gmane.org>
2013-03-22 13:41   ` Samuel Thibault [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130322134147.GA6125@type.bordeaux.inria.fr \
    --to=samuel.thibault-vyw+cpy1g1pg9huczpvpmw@public.gmane.org \
    --cc=kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).