Jim Beard
2016-10-16 16:59:10 UTC
New Workstation is assembled in its entirety, all internal SSD and HD are
connected, and the thing is working, sort of.
The monitor worked well in the brief period I was booted to W10. It goes
streaky when idle when using Mageia, but this is tolerable.
W10 boots from the EFI partition on the first ssd, and occupies about
half of the 250GB. The remaining half of this ssd is unallocated.
Mageia 5 boots from the EFI partition on the second ssd.
At the moment, when booting I have to hit DEL or F2 to get into the UEFI
BIOS, pick the ssd, dvd, or hd I want to boot from, and then hit F8 to
pick the exact source to boot from.
I think that grub2 can be set up to chainload W10, and the UEFI BIOS can
be set up to go first to the dvd and (if empty) then to the ssd grub2 is
on. This is not yet proven. I have tried to save boot order and
priority in the UEFI BIOS, but it is not doing what I expect. Further
experimenting and testing required.
With the new kernel 4.4.16-desktop-1.mga5 the new machine promptly went
to the 'Net and brought back the updates needed.
My attempt to set up nfs failed, and for a time the new workstation could
not talk to the router. This morning connectivity to the router is good.
One problem is that I set up a local network xxxxxxx:192.168.1.0/28.
xxxxxxx is the new equivalent of the old eth0 on the individual machine,
and that is put into the shorewall hosts file as "loc 192.168.1.0/28"
This allows 16 machines on the net, and with my machines, my wife's
multiple Apples, smart phone, and such the new workstation got a dynamic
ip of 20. I will have to find an unused slot on the router and assign a
static ip of 14 or less, or maybe increase the number of ip allowed on
the local net.
While looking at shorewall, I surfaced an area that gave me problems
before, and may be in error.
In my zones file, on one machine I have
loc ipv4
net ipv4
fw firewall
On another, only
net + detect
on my laptop,
fw firewall
loc ipv4
net ipv4
This cannot be right, as all should be the same. What is a "Parent"
network in shorewall speak? Does parent start with the firewall, then
the local network, and then subchild net ? I am confused, and
clarification would be appreciated.
fw is firewall, net is the net. loc is my local net, currently
192.168.1.0/28.
Cheers!
jim b.
connected, and the thing is working, sort of.
The monitor worked well in the brief period I was booted to W10. It goes
streaky when idle when using Mageia, but this is tolerable.
W10 boots from the EFI partition on the first ssd, and occupies about
half of the 250GB. The remaining half of this ssd is unallocated.
Mageia 5 boots from the EFI partition on the second ssd.
At the moment, when booting I have to hit DEL or F2 to get into the UEFI
BIOS, pick the ssd, dvd, or hd I want to boot from, and then hit F8 to
pick the exact source to boot from.
I think that grub2 can be set up to chainload W10, and the UEFI BIOS can
be set up to go first to the dvd and (if empty) then to the ssd grub2 is
on. This is not yet proven. I have tried to save boot order and
priority in the UEFI BIOS, but it is not doing what I expect. Further
experimenting and testing required.
With the new kernel 4.4.16-desktop-1.mga5 the new machine promptly went
to the 'Net and brought back the updates needed.
My attempt to set up nfs failed, and for a time the new workstation could
not talk to the router. This morning connectivity to the router is good.
One problem is that I set up a local network xxxxxxx:192.168.1.0/28.
xxxxxxx is the new equivalent of the old eth0 on the individual machine,
and that is put into the shorewall hosts file as "loc 192.168.1.0/28"
This allows 16 machines on the net, and with my machines, my wife's
multiple Apples, smart phone, and such the new workstation got a dynamic
ip of 20. I will have to find an unused slot on the router and assign a
static ip of 14 or less, or maybe increase the number of ip allowed on
the local net.
While looking at shorewall, I surfaced an area that gave me problems
before, and may be in error.
In my zones file, on one machine I have
loc ipv4
net ipv4
fw firewall
On another, only
net + detect
on my laptop,
fw firewall
loc ipv4
net ipv4
This cannot be right, as all should be the same. What is a "Parent"
network in shorewall speak? Does parent start with the firewall, then
the local network, and then subchild net ? I am confused, and
clarification would be appreciated.
fw is firewall, net is the net. loc is my local net, currently
192.168.1.0/28.
Cheers!
jim b.
--
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.