Stephen Powell wrote:
> On Mon, 07 Sep 2015 11:47:56 -0400 (EDT), Sven Hartge wrote:
>> Looks fine, from a cursory glance.
>>
>> Maybe you can add a section about using
>>
>>"systemctl cat serial-getty@ttyS0.service"
>>
>> to verfiy that the override.conf has been
On Mon, 07 Sep 2015 18:08:05 -0400 (EDT), Bob Bernstein wrote:
>
> What a great contribution!
>
> My null-modem cable ought to still be around here somewhere!
>
> :-)
I try to focus on the latest technology.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
Hello,
Thanks for all the clarification. I now find myself in need of doing this
again on another server running Jessie, and I just want to make sure I'm
clear on what the best procedure is. As I understand it, I should
copy /lib/systemd/system/serial-getty@.service to
Stephen Powell wrote:
> Sven and Michael, please review this also and correct me if I made a
> mistake. I do not want to publish bad advice.
Looks fine, from a cursory glance.
Maybe you can add a section about using "systemctl cat
serial-getty@ttyS0.service" to verfiy
On Mon, 07 Sep 2015 09:56:12 -0400 (EDT), David Parker wrote:
>
> Thanks for all the clarification. I now find myself in need of doing this
> again on another server running Jessie, and I just want to make sure I'm
> clear on what the best procedure is.
> ...
I just finished updating my web
On Mon, 7 Sep 2015, Stephen Powell wrote:
I just finished updating my web page to reflect the new
information. Once again, go to
http://users.wowway.com/~zlinuxman/serial.htm
What a great contribution!
My null-modem cable ought to still be around here somewhere!
:-)
--
Bob Bernstein
On Mon, 07 Sep 2015 11:47:56 -0400 (EDT), Sven Hartge wrote:
>
> Looks fine, from a cursory glance.
>
> Maybe you can add a section about using
>
>"systemctl cat serial-getty@ttyS0.service"
>
> to verfiy that the override.conf has been
> read successfully after "systemctl daemon-reload".
Am 06.09.2015 um 21:04 schrieb Stephen Powell:
>[Service]
>ExecStart=-/sbin/agetty -8 --noclear %I 38400 ibm3151
>
> But when I restart the service, I get the following error:
>
> systemd[1]: serial-getty@ttyS0.service: Service has more than one ExecStart=
> setting, which is only
Stephen Powell wrote:
> Well, Sven, that's a nice idea, but I can't get it to work for me in this
> situation. I issued
>systemctl edit serial-getty@ttyS0.service
> and placed the following two lines into the file:
>[Service]
>ExecStart=-/sbin/agetty -8
On Sun, 06 Sep 2015 16:06:35 -0400 (EDT), Michael Biebl wrote:
> Am 06.09.2015 um 21:04 schrieb Stephen Powell:
>> ...
>>[Service]
>>ExecStart=-/sbin/agetty -8 --noclear %I 38400 ibm3151
>>
>> But when I restart the service, I get the following error:
>>
>> systemd[1]:
Hello Michael,
On 09/06/2015 10:06 PM, Michael Biebl wrote:
> See also man 5 systemd.unit , "Example 2. Overriding vendor settings":
>
>>Note that for drop-in files, if one wants to remove entries from a
>> setting that is
>>parsed as a list (and is not a dependency), such as
On Wed, 02 Sep 2015 17:29:40 -0400 (EDT), Sven Hartge wrote:
>
> systemd provides a way to override or ammend parts of units. You do this
> by creating a directory structure like this:
>
> /etc/systemd/system/foo.service.d/
>
> This will contain all additional config files for the unit
>
On Thu, 03 Sep 2015 20:06:43 -0400 (EDT), Michael Biebl wrote:
>
> Am 03.09.2015 um 03:14 schrieb Stephen Powell:
>> Do you know a similar technique for overriding individual udev rules in
>> a system-provided rules file?
>
> A similar mechanism exists for udev rules file.
> See man 7 udev ->
Stephen Powell wrote:
> Do you know a similar technique for overriding individual udev rules in
> a system-provided rules file?
Ah, that part is a white spot on my (mind)map.
Maybe Michael Biebl can provide more input, as one of the DDs
maintaining systemd and udev he
Am 03.09.2015 um 03:14 schrieb Stephen Powell:
> Do you know a similar technique for overriding individual udev rules in
> a system-provided rules file?
A similar mechanism exists for udev rules file.
See man 7 udev -> "RULES FILES"
--
Why is it that all of the instruments seeking intelligent
On Wed, 02 Sep 2015 17:29:40 -0400 (EDT), Sven Hartge wrote:
> ...
>
> systemd provides a way to override or ammend parts of units.
> You do this by creating a directory structure like this:
>
> /etc/systemd/system/foo.service.d/
>
> This will contain all additional config files for the unit
David Parker wrote:
> Thanks. I actually found that site in a Google search, and it's where
> I found the tip on copying the
> /lib/systemd/system/serial-getty@.service template file to customize
> the baud rate, etc. Specifically, I found the info I needed at:
>
On Wednesday 02 September 2015 23:29:40 Sven Hartge wrote:
> Eike Lantzsch wrote:
> > On Wednesday 02 September 2015 20:58:29 Sven Hartge wrote:
> >> David Parker wrote:
> >>> Thanks. I actually found that site in a Google search, and it's where
> >>> I found
On Wednesday 02 September 2015 20:58:29 Sven Hartge wrote:
> David Parker wrote:
> > Thanks. I actually found that site in a Google search, and it's where
> > I found the tip on copying the
> > /lib/systemd/system/serial-getty@.service template file to customize
> > the baud
Eike Lantzsch wrote:
> On Wednesday 02 September 2015 20:58:29 Sven Hartge wrote:
>> David Parker wrote:
>>> Thanks. I actually found that site in a Google search, and it's where
>>> I found the tip on copying the
>>> /lib/systemd/system/serial-getty@.service
Thanks. I actually found that site in a Google search, and it's where I
found the tip on copying the /lib/systemd/system/serial-getty@.service
template file to customize the baud rate, etc. Specifically, I found the
info I needed at:
http://users.wowway.com/~zlinuxman/serial.htm#Systemd
Michael Biebl wrote:
> As for overriding the system provided service files, I usually recommend
> to use drop-ins, i.e. creating a
> /etc/systemd/system/foo.service.d/my_custom_config.conf
> This way you only need to override what you are actually interested in.
Users of
Am 01.09.2015 um 18:13 schrieb David Parker:
> And still not in the same way that they appear on Wheezy ("/sbin/getty
> 38400 tty1", etc.). If I add the line for the serial console to
> /etc/inittab and reload the init deamon, or even reboot the PC, it simply
> does nothing. No getty process
Am 01.09.2015 um 19:31 schrieb David Parker:
> Thanks, Michael! That was indeed the problem. I
> copied /lib/systemd/system/serial-getty@.service to /etc/systemd/system,
> edited it to use the correct baud rate and terminal type, and then ran
> "systsystemctl start serial-getty@ttyS0.service"
On Tue, 01 Sep 2015 12:13:56 -0400 (EDT), David Parker wrote:
>
> I have a bunch of Debian Wheezy servers set up with the console available
> via the serial port. Generally, I just add this line to /etc/inittab:
> ...
> That's all fine and good, but when I try to do this on my desktop PC
>
Hello,
I have a bunch of Debian Wheezy servers set up with the console available
via the serial port. Generally, I just add this line to /etc/inittab:
co:2345:respawn:/sbin/getty -L ttyS0 9600 vt102
And then run "kill -HUP 1" and the serial console works (I could also use
"telinit q" or
26 matches
Mail list logo