I am using an USB stick as installation media, when I get to the automatic
partitioning I am told that there is no available space
/dev/sda1 fat32 HPDOCS 7,81 GiB
/dev/sda2 7,81GiB label=boot, lba
unallocated 450,15 GiB
Skype : amontag52
Linux Fedora 23 (Workstation)
inviato da Gmail
On 12/28/2015 01:54 PM, Александр Кириллов wrote:
> By the gateway I mean a host with 2 public ips on separate interfaces
> connected to lan via the third interface. My undestanding of the OP is
> that all traffic coming to some other host in the lan through one of
> the public interfaces on the gateway must be routed back out that same
Joey said that he had a server, not a router, so I did not get the same
impression as you. However, even in the situation you describe, where a
Linux router has two WAN links and one LAN, you can use "ip rule" to
manage multi-homed routing without using iptables to mark packets based
on MAC addresses, or any other exotic solutions.
I have an old netbook that I have just installed F23 i386 XFCE
Workstation on that I want to use (as lightly loaded as possible) as a
remote webcam. Since I need to be able to reboot it and have the
network come back up with wlan0 working, it appears I have to use the
old "network" system instead of Network Manager (NM requires a login to
activate wlan0?). So I am doing this:
systemctl stop NetworkManager
systemctl disable NetworkManage
systemctl enable network
systemctl start network
but network doesn't start and doing:
systemctl status network
gives lots of lines like this:
. . . RTNETLINK answers: File exists
Googling finds this problem all over the place - especially with old
versions of Fedora - but I can't find a fix for my particular situation.
I imagine there is a simple fix but I haven't found it yet . . can
someone enlighten me?
PO Box 896
Cowra NSW 2794
Sent from my Samsung Galaxy smartphone.
-------- Original message --------
From: Robert Moskowitz <rgm(a)htt-consult.com>
Date: 2015-12-28 10:20 PM (GMT-07:00)
Subject: Re: F23 on Raspberry Pi 2
On 12/26/2015 06:50 AM, Suvayu Ali wrote:
> Hi Michael,
> On Thu, Dec 24, 2015 at 11:58:49PM +0000, M A Young wrote:
>> On Thu, 24 Dec 2015, Suvayu Ali wrote:
>>> It seems to me, the fedora kernel is not running. Any ideas how I can
>>> get it to run?
>> As far as I am aware you can't use a Fedora kernel on a Raspberry Pi 2, as
>> it needs some modifications that the Fedora Kernel doesn't have (unless it
>> has changed recently). One thing to check is that you have the
>> NetworkManager-wifi package, probably the wpa_supplicant package as well
>> as I don't think they are in the minimal image.
> Thanks for the information. I'll try to find more information. Perhaps
> it's simpler to try a distribution that is better supported on the Pi.
Or going to the fedora-arm list to ask about arm support?
users mailing list
To unsubscribe or change subscription options:
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Have a question? Ask away: http://ask.fedoraproject.org
I am trying to change my sendmail configuration to deliver all "user unknown"
emails to a specific account (baduser).
I added the DL definition to sendmail.mc and generated test.cf.
Then I tested this new config using:
echo who | sendmail -v -Ctest.cf noone
and the email was correctly delivered to the defined account.
I then renamed test.cf to sendmail.cf (in /etc/mail) and retested with:
echo what | sendmail -Csendmail.cf noone
and again the email was delivered to the baduser account.
Happy with this, I then restarted sendmail (via systemctl) and sent yet
another email to an invalid account.
Instead of the email being delivered to baduser, I received a 550 5.1.1 user
unknown reject email.
What have I missed here.
(Fedora 22 & sendmail 8.14.7/8.13.3)
Stephen Davies Consulting P/L Phone: 08-8177 1595
Adelaide, South Australia. Mobile:040 304 0583
I've been running a Windows 7 KVM virtual machine for
a while with a Fedora 22 host, and I found lots of
conflicting info on the web about the possibility
of installing the Windows 10 upgrade in a KVM.
After taking great care to preserve the original
Windows 7 image file, I gave the upgrade a whirl
and it seems to have worked OK for me.
Full story at:
Now it won't constantly badger me about upgrading :-).
My system is supposed to be in English, but all the commands at the console
level give feedback in Spanish.
How can I troubleshoot this?
[root@bloody ~]# export
declare -x HISTCONTROL="ignoredups"
declare -x HISTSIZE="1000"
declare -x HOME="/root"
declare -x HOSTNAME="bloody.localdomain"
declare -x KDEDIRS="/usr"
declare -x KDE_IS_PRELINKED="1"
declare -x LANG="en_US.UTF-8"
declare -x LANGUAGE="en_US:es"
declare -x LC_COLLATE="en_US.UTF-8"
declare -x LC_MEASUREMENT="en_US.UTF-8"
declare -x LC_MONETARY="en_US.UTF-8"
declare -x LC_NUMERIC="en_US.UTF-8"
[root@bloody ~]# dnf update
Última comprobación de caducidad de metadatos hecha hace 1:21:53, el Sun
Dec 27 10:55:20 2015.
Nada por hacer.
This is weird!
|O O| pepebuho(a)gmail.com
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
I am interested to see if it is possible to boot on an existing disk -
say /dev/sda ("A") - and then manually create everything required on a
second disk - /dev/sdb ("B") eg:
- create the partition table and partitions on B
- dd the existing boot track(s) from A to a file and then dd that to B -
or create it from scratch somehow?
- rsync the the first level directories into the appropriate places on
the new drive and partitions (maybe by temporarily booting on a Live USB
so we are not copying from a running system?)
If this is possible, what else would need to be done on B so that when
drive A is removed, the remaining B (the new "A") drive will be able to
boot and run normally?
PO Box 896
Cowra NSW 2794
> Date: Sun, 27 Dec 2015 10:36:36 +0100
> From: Timothy Murphy <gayleard(a)eircom.net>
> To: users(a)lists.fedoraproject.org
> Subject: Re: An Exercise: Manually creating a new boot disk from an
> existing one
> Message-ID: <n5obf4$4st$1(a)ger.gmane.org>
> Content-Type: text/plain; charset="ISO-8859-1"
> Philip Rhoades wrote:
>> I am interested to see if it is possible to boot on an existing disk -
>> say /dev/sda ("A") - and then manually create everything required on a
>> second disk - /dev/sdb ("B") eg:
>> - create the partition table and partitions on B
>> - dd the existing boot track(s) from A to a file and then dd that to B
>> or create it from scratch somehow?
>> - rsync the the first level directories into the appropriate places on
>> the new drive and partitions (maybe by temporarily booting on a Live
>> so we are not copying from a running system?)
>> If this is possible, what else would need to be done on B so that when
>> drive A is removed, the remaining B (the new "A") drive will be able
>> boot and run normally?
> Presumably you would have to (at least)
> 1. Correct /etc/fstab
> 2. Install grub on second disk
Ah yes, of course . . I might give it a go . .
PO Box 896
Cowra NSW 2794