Has anyone used the new AMD CPUs and AM4 motherboards with CentOS 6 / 7?
Any reservations or warnings?
--
Eugene Poole
Woodstock, Georgia
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
To "ken" and "hth" whomever you may have been.
>From the moderator and owner of CENTOS7, et all, in sum and in short:
- this is an improperly formatted question, first
- next, we see that CENTOS7 does NOT and will NOT support anything INTEL now
or
ever.
- With that said, you should be aware
Been using Centos and Squirrelmail since early in Centos 6 cycle. IIRC, I used
to be able to
attach more than 4 pictures to an email. Now I can't, four seems to be the
limit. Picture file
size doesn't seem to matter, they can be 50k or 5 meg each. I upped the limits
in php.ini for the
On 7 May 2017 at 16:30, Gordon Messmer wrote:
> On 05/07/2017 07:22 AM, ken wrote:
>>
>> "Note that traditional init scripts continue to function on a systemd
>> system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
>> into a service unit foobar.service
On 05/07/2017 07:22 AM, ken wrote:
"Note that traditional init scripts continue to function on a systemd
system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
into a service unit foobar.service during system initialization."
...
However, what it implies doesn't seem to work out.
Am 07.05.2017 um 16:22 schrieb ken:
"Note that traditional init scripts continue to function on a systemd
system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
into a service unit foobar.service during system initialization."
That's what it says in /etc/init.d/README.
However,
"Note that traditional init scripts continue to function on a systemd
system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
into a service unit foobar.service during system initialization."
That's what it says in /etc/init.d/README.
However, what it implies doesn't seem to work
7 matches
Mail list logo