Re: [systemd-devel] Fedora on systemd-nspawn container - ML best practice
by arnaud gaboury
On Tue, Apr 28, 2015, 11:38 AM Lennart Poettering <mzerqung(a)0pointer.de>
wrote:
On Tue, 28.04.15 09:31, arnaud gaboury (arnaud.gaboury(a)gmail.com) wrote:
> I started running Fedora server on a systemd-nspawn container.
>
> I am wondering what is the best practice when an issue occurs:
> - send to Fedora user ML
> - send to systemd-devel ML
> - send both with CC
>
> I am afraid that when sending to only one list I will be told to ask
> the other one, thus wasting time between the two lists. On the other
> hand, CC to both lists can be viewed as spam.
>
> From a user point of view, best would be to post to both lists as long
> as the issue can come from systemd-nspawn functionality or Fedora.
>
> use case: after install, boot, upgrade Fedora container, network is
> down in container (when it used to work to install some new packages).
>
> Thank you for advice about ML posting.
Cross-posting is not particularly popular, so I'd avoid it.
I know.
If it's nspawn related it's probably best to keep it on the systemd
ML.
Consider using using systemd-networkd in the container and on the
host. If so the network should just work between them.
I will as systemd- networkd already manage my network on the host. Btw, as
fedora will act as a server, i will need a fix ip, get rid of ebtables and
firewalld in container (kernel is built with apparmor and grsec) etc etc.
Lot of work
Lennart
--
Lennart Poettering, Red Hat
8 years, 12 months
Serial port bug?
by Jeandet Alexis
Hi,
I found a weird behavior, I don't know if it is a bug. On my codes I
usually look into "/dev/serial/by-id/" to list available serial ports. I
discovered that when I use two FT2232(USB to dual serial port) I only
see the last connected chip not both. If look into
"/dev/serial/by-path/" I see all of them and also into
"/sys/bus/usb-serial/devices/".
Example:
[jeandet@machin opt]$ ls -al /sys/bus/usb-serial/devices/
total 0
drwxr-xr-x 2 root root 0 28 avril 10:40 .
drwxr-xr-x 4 root root 0 28 avril 10:40 ..
lrwxrwxrwx 1 root root 0 28 avril 10:35 ttyUSB0
-> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.0/ttyUSB0
lrwxrwxrwx 1 root root 0 28 avril 10:35 ttyUSB1
-> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.1/ttyUSB1
lrwxrwxrwx 1 root root 0 28 avril 10:35 ttyUSB2
-> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/ttyUSB2
lrwxrwxrwx 1 root root 0 28 avril 10:35 ttyUSB3
-> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/ttyUSB3
[jeandet@machin opt]$ ls -al /dev/serial/by-id/
total 0
drwxr-xr-x 2 root root 80 28 avril 10:32 .
drwxr-xr-x 4 root root 80 28 avril 10:32 ..
lrwxrwxrwx 1 root root 13 28 avril 10:32
usb-FTDI_Dual_RS232-HS-if00-port0 -> ../../ttyUSB2
lrwxrwxrwx 1 root root 13 28 avril 10:32
usb-FTDI_Dual_RS232-HS-if01-port0 -> ../../ttyUSB3
[jeandet@machin opt]$ ls -al /dev/serial/by-path/
total 0
drwxr-xr-x 2 root root 120 28 avril 10:32 .
drwxr-xr-x 4 root root 80 28 avril 10:32 ..
lrwxrwxrwx 1 root root 13 28 avril 10:32
pci-0000:00:14.0-usb-0:1:1.0-port0 -> ../../ttyUSB2
lrwxrwxrwx 1 root root 13 28 avril 10:32
pci-0000:00:14.0-usb-0:1:1.1-port0 -> ../../ttyUSB3
lrwxrwxrwx 1 root root 13 28 avril 10:32
pci-0000:00:14.0-usb-0:2.2:1.0-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 28 avril 10:32
pci-0000:00:14.0-usb-0:2.2:1.1-port0 -> ../../ttyUSB1
Should I consider that as a bug? If yes where should I report this
issue? Which package might be the cause, the kernel, udev?
Best regards,
Alexis.
8 years, 12 months
Fedora on systemd-nspawn container - ML best practice
by arnaud gaboury
I started running Fedora server on a systemd-nspawn container.
I am wondering what is the best practice when an issue occurs:
- send to Fedora user ML
- send to systemd-devel ML
- send both with CC
I am afraid that when sending to only one list I will be told to ask
the other one, thus wasting time between the two lists. On the other
hand, CC to both lists can be viewed as spam.
>From a user point of view, best would be to post to both lists as long
as the issue can come from systemd-nspawn functionality or Fedora.
use case: after install, boot, upgrade Fedora container, network is
down in container (when it used to work to install some new packages).
Thank you for advice about ML posting.
--
google.com/+arnaudgabourygabx
8 years, 12 months
wifi flaky since recent upgrade
by Neal Becker
lenovo carbon x1
It seems recently, every time my laptop wakes, it immediately connects to
wifi. But shortly afterwards, the wifi isn't working (can't ping anything).
Then I disconnect and reconnect, and it's fine. This happens very
repeatably.
Not quite sure if it actually works for a few seconds and then stops.
I'm fairly sure it didn't happen until some recent upgrade (f21 with all
updates).
--
Those who fail to understand recursion are doomed to repeat it
9 years
Re: WiFi restoration
by J.Witvliet＠mindef.nl
Powerline adapters are illegal in several countries as they pollute the radio spectrum.
Only good solution is cat6 or fibre and a second accesspoint.
Verstuurd vanaf mijn iPhone
> Op 25 apr. 2015 om 01:36 heeft Patrick O'Callaghan <pocallaghan(a)gmail.com> het volgende geschreven:
>
> On Sat, 2015-04-25 at 00:51 +0200, Timothy Murphy wrote:
>>> Move the wireless access point, move or improve the antenna
>> (transmitter
>>> and/or receiver), re-position the the failing client device, add
>> another
>>> access point or wireless repeater, move objects that may be in the
>> way
>>> of the wireless signal path.
>>
>> I did get a longer antenna for the Linksys WRT54GL WiFi router.
>> I also tried to set up a WiFi repeater (SilverCrest SWR 300 a1)
>> but could not get it working under Fedora or Windows.
>> I have thought of using a TP-Link which is set up on my system.
>
> I tried a wireless repeater a few years ago. Complete waste of money,
> despite being a reputable brand (Linksys). Also, repeaters reduce your
> wireless bandwidth by about 50% IIRC. A much better solution is to use a
> pair of power-line adaptors. Modern ones use the IEEE 1901 standard
> (known as Homeplug), are available from several manufacturers and have
> good performance.
>
> poc
>
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
9 years
Thunderbird filters -
by Bob Goodwin
I sortpop3mail into directories with Thunderbird which works well for
me. However when I unsubscribe from a list I often want to remove the
filter's directory is shown in the Inbox Menu at the top left. So I
right click on the directory and choose delete from the menu, it asks
for reassurance that I really mean delete it, I click on ok, the menu
closes and the directory is still there, delete does not delete it. The
list of directories grows longer with time and all I can do is rename
the directories with xx's so it sorts them to the bottom of the list!
This may be related to my saving the .thunderbird Mail file for years
mainly to keep the filters I have ... This is Thunderbird 31.5.0 in up
to date Fedora 21/22 and earlier.
Am I the only one seeing this? My efforts with Google have not been much
help.
Bob
--
http://www.qrz.com/db/w2bod
box10 Fedora-22/64bit Linux/XFCE
9 years
Hibernate: Sleep verb not supported ??
by sean darcy
F21, XFCE:
When I try to hibernate I get :
GDBus.Error:org.freedesktop.login1.SleepVerbNotSupported: Sleep verb not
supported
Any way to fix this?
sean
9 years
