similar to: Intel SSD

I always tell vendors I'm using RHEL, even though we're using CentOS. If you say CentOS, some vendors immediately throw up their hands and say "unsupported" and then won't even give you the time of day. A couple tricks for fooling tools into thinking they are on an actual RHEL system: 1. Modify /etc/redhat-release to say RedHat Enterprise Linux or whatever the actual RHEL

Michael Hennebry wrote: > On Wed, 18 Nov 2015, Birta Levente wrote: > >> I have a supermicro server, motherboard is with C612 chipset and beside that with LSI3108 raid controller integrated.Two Intel SSD DC S3710 200GB. OS: Centos 7.1 up to date. >> >> My problem is that the Intel SSD Data Center Tool (ISDCT) does not recognize the SSD drives when they connected to the

On 18/11/2015 16:37, Eero Volotinen wrote: > What is Intel SSD Data Center Tool (ISDCT) ? " This tool provides a command line interface for interacting with and issuning commands to Intel SSD Data Center devices. It is intended to configure and check the state of Intel PCIe SSDs and SATA SSDs for a production environment. " > Does Linux kernel detect disk on sata ports? >

On 11/18/2015 09:51 AM, Eero Volotinen wrote: > strace -f -e open software_binary might help, but I have noticed that > Centos is not really 100% binary compatible in some cases. CentOS Linux is not 100% bit for bit compatible with RHEL in ANY cases :) CentOS and RHEL are built from mostly the same source code (we remove RH trademarks and take out RHN update pieces). But RHEL source code

What is Intel SSD Data Center Tool (ISDCT) ? Does Linux kernel detect disk on sata ports? Supported usually means that they have tested it and they can say that it works.. Many of hardware still works as linux kernel support lots of drivers -- even they are not officially supported by vendor. -- Eero 2015-11-18 16:25 GMT+02:00 Birta Levente <blevi.linux at gmail.com>: > Hi > > I

On 11/19/2015 12:54 AM, Birta Levente wrote: > I tried today morning on RHEL too ... > The ISDCT tool does not work on supported OS neither I think everyone focused on your problem with the vendor, who didn't support your OS, and ignored the fact that the tool worked when the drives were connected to a secondary controller. The OS never caused a problem for the tool, only for the

On Wed, 18 Nov 2015, Birta Levente wrote: > I have a supermicro server, motherboard is with C612 chipset and beside that > with LSI3108 raid controller integrated. > Two Intel SSD DC S3710 200GB. > OS: Centos 7.1 up to date. > > My problem is that the Intel SSD Data Center Tool (ISDCT) does not recognize > the SSD drives when they connected to the standard S-ATA ports on

strace -f -e open software_binary might help, but I have noticed that Centos is not really 100% binary compatible in some cases. -- Eero 2015-11-18 17:42 GMT+02:00 Matt Garman <matthew.garman at gmail.com>: > I always tell vendors I'm using RHEL, even though we're using CentOS. > If you say CentOS, some vendors immediately throw up their hands and > say

Hi There is a Centos 7 up-to-date box with 2 interfaces, let's say 192.168.1.12 - enp2s0, 192.168.1.13 on enp3s0. Default gateway on enp2s0. The gateway is pfsense, IP is 192.168.1.1 with 2 WAN connections On the gateway the outgoing traffic is routed by source ip to different WAN, 192.168.1.12 to WAN1 and 192.168.1.13 to WAN2 On the centos box are set all the route and routing rules:

Hi all Can someone explain me this: ifcfg-eth0-range1: ONBOOT="yes" IPADDR_START="192.168.1.48" IPADDR_END="192.168.1.55" CLONENUM_START="1" Why Bcast is 192.168.1.51 and why Mask is 255.255.255.252 ? OS: Centos 6.3/64bit Thanks Levi # ifconfig eth0:1 Link encap:Ethernet HWaddr 00:9C:02:99:FA:00 inet addr:192.168.1.48

On 09/08/2016 20:01, Gordon Messmer wrote: > On 08/08/2016 04:05 AM, Levente Birta wrote: >> Can I add this in any config files (ex: route-enp2s0)? > > > Yes. Add a route file for each interface, and set up rules to send > packets out the corresponding physical interface: > > https://blogs.oracle.com/networking/entry/advance_routing_for_multi_homed > Yes, but no

Hi list, I tried to build rpm based on dovecot-2.2.2-2.fc20.src.rpm on Centos 6.4 rpmbuild --define 'rhel 64' -ba dovecot-2.2.spec I get this error: checking for C compiler default output file name... configure: error: in `/home/builder/rpmbuild/BUILD/dovecot-2.2.2': configure: error: C compiler cannot create executables See `config.log' for more details. (config.log

On 09/08/2016 06:56, Anthony K wrote: > On 08/08/16 21:05, Levente Birta wrote: >> >> But how can I add achieve this only with ip route command ... without >> route? >> Can I add this in any config files (ex: route-enp2s0)? >> > Hi Levente. > > The iproute2 man page for each command is rather well documented on > CentOS 7. For instance, to view the

On 08/09/2016 12:03 PM, John R Pierce wrote: > those are both the same network, and the default gateway is a global > thing. packets forwarded to 192.168.1.1 could use either 192.168.1.12 > or .13, as they are all the same. in reality, they will use the first > match they find. Generally, but not necessarily. What Birta is trying to accomplish is called

Hi How can I convert all virtual mailboxes from maildir to mdbox? Manually, one by one, working, but I have a lot ... Virtual users and domains stored in sql database. Thats what I want: mail_location = maildir:/var/vmail/%d/%n/Maildir to mail_location = mdbox:/var/vmail/%d/%n/mdbox Thanks Levi -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s

I assume you are using one of the boards described here? http://www.intel.com/support/services/smartconnect/sb/CS-033108.htm On 11/19/2015 10:43 AM, Birta Levente wrote: > It is in AHCI, never was changed > > On 19:26, Thu, Nov 19, 2015 Gordon Messmer <gordon.messmer at gmail.com> wrote: > >> On 11/19/2015 12:54 AM, Birta Levente wrote: >>> I tried today morning

On 09/08/2016 15:47, Jonathan Billings wrote: > On Tue, Aug 09, 2016 at 10:58:40AM +0300, Levente Birta wrote: >> What I don't understand why the route command allow to add a second default >> gateway with different interface, but the ip route command doesn't? > You can only have one default gateway. > > It sounds to me like you want to use both interfaces, which

On Wed, Aug 10, 2016 at 09:29:15AM +0300, Levente Birta wrote: > I read the document again ... and this talk about accessing this multi-homed > host from the internet... > I have all this configured and working! You say this is working because of the output here? # ip route show default via 192.168.1.1 dev enp3s0 default via

On 10/08/16 16:29, Levente Birta wrote: > And as I said this problem is resolved too ... I asked for another way > to achieve this When you add a default gateway with: route add default gw 192.168.1.1 dev enp3s0 you'll note that you now have 2 routes with the same metric of 0 (use route -n to see the metric field - couldn't get ip route to show me the metric). When using ip

It is in AHCI, never was changed On 19:26, Thu, Nov 19, 2015 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 11/19/2015 12:54 AM, Birta Levente wrote: > > I tried today morning on RHEL too ... > > The ISDCT tool does not work on supported OS neither > > I think everyone focused on your problem with the vendor, who didn't > support your OS, and ignored