date:20160422

Re: Simple DASD question

2016-04-22 Thread Tom Huegel

Mm probably not..
It's golf day no more time for work today.. Maybe I'll just grab a mod 27
on Monday.



On Fri, Apr 22, 2016 at 11:57 AM, Mark Post  wrote:

> >>> On 4/22/2016 at 11:20 AM, Tom Huegel  wrote:
> > Although when I try to reboot
> >
> >  [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46... 6s / no
> > limit) [ BUSY ] A start job is running for dev-disk-by\x2d
> > uuid-d8b46... 6s / no limit) [ BUSY ]
>
> Again, this looks like the bug in SLES12 that is fixed by later
> maintenance.  Was that applied before adding the DASD volume to the file
> system?
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Formatting DASD

2016-04-22 Thread Mark Post

>>> On 4/22/2016 at 02:10 PM, Michael Weiner  wrote: 
> I created /usr/test with 10 GB using dasd fmt and the lvmextend command. 
> 
> Now I want to add another 6 GB to /usr/test is there a problem with doing 
> this in YAST instead of the command line?

There should not be a problem.  That's why we have YaST in the first place.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Simple DASD question

2016-04-22 Thread Mark Post

>>> On 4/22/2016 at 11:20 AM, Tom Huegel  wrote: 
> Although when I try to reboot
> 
>  [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46... 6s / no
> limit) [ BUSY ] A start job is running for dev-disk-by\x2d
> uuid-d8b46... 6s / no limit) [ BUSY ] 

Again, this looks like the bug in SLES12 that is fixed by later maintenance.  
Was that applied before adding the DASD volume to the file system?


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-22 Thread Alan Altmark

On Friday, 04/22/2016 at 04:50 GMT, Offer Baruch  
wrote:
> If you make sure you have NATIVE NONE and keep track of your grants 
(just
> like PORTBASED) there is no real security concern...
> The guest is only allowed the vlans you grant it (just like PORTBASED) 
and
> he cant send any untagged frames.
> I would rather manage a USERBASED VSWITCH with trunks over managing 
ports
> with PORTBASED any day...
> It is much easier to make vlan mistakes with PORTBASED... USERBASED is 
much
> more intuitive, easy to manage and easy to view...

To that end, there is work under way to simplify the configuration of 
PORTBASED VSWITCHes.  With the proposed configuration simplification, the 
only difference between the two is the explicit v. implicit port numbering 
scheme.  I think that can be consolidated back into a single VSWITCH.

> I agree you should close all the security holes before you do that... 
but
> that seems a better solution then PORTBASED.
>
> There are pro's and con's for everything but I would recommend USERBASED
> for security reasons and management reasons (assuming you know what you 
are
> doing).

At the end of the day, it's your choice.  The problem was that USERBASED 
did not address the explicit need to put two access port vNICs on the same 
VSWITCH in different VLANs.  The PORTBASED VSWITCH solved that problem, 
but introduced others.   Let's talk again after we've made some progress 
on the VSWITCH Reconciliation Project (Do you like the name?  I just made 
it up!)

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Formatting DASD

2016-04-22 Thread Michael Weiner

Hi all

Quick question. 

If your traditional method of adding and extending  LVMs is done by command 
line and then you decide to add a volume and extend a specific logical volume 
using YAST is there any implications? 

Example

I created /usr/test with 10 GB using dasd fmt and the lvmextend command. 

Now I want to add another 6 GB to /usr/test is there a problem with doing this 
in YAST instead of the command line?

Have a good weekend!

Sent from my iPhone
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Simple DASD question

2016-04-22 Thread Harley Linker

Did you run command 'fdasd -a /dev/dasdb' to create the partition?  /dev/dasdb1 
doesn't exist unless you run the command.

Harley Linker Jr.



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Tom Huegel
Sent: Friday, April 22, 2016 9:08 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Simple DASD question

So far I have failed with my feeble attempts to add the second disk dasdb
(0251) to the btrfs filesystem.
This is what I have fresh after my re-re-re-re-install.
It seems "btrfs device add /dev/dasdb1 /" would be a good thing to do but I get 
message about dasdb1 not existing...


sles12:~ # lsdasd
Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
==
0.0.0250   active  dasda 94:0ECKD  4096   7042MB1802880
0.0.0251   active  dasdb 94:4ECKD  4096   7042MB1802880
sles12:~ # btrfs filesystem show
Label: none  uuid: d8b46146-19c1-48d8-b024-80547e728787
Total devices 1 FS bytes used 2.74GiB
devid1 size 5.71GiB used 3.53GiB path /dev/dasda3
Btrfs v3.16+20140829
sles12:~ # df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/dasda3 5.8G  3.0G  2.5G  55% /
devtmpfs439M  8.0K  439M   1% /dev
tmpfs   446M 0  446M   0% /dev/shm
tmpfs   446M  7.0M  439M   2% /run
tmpfs   446M 0  446M   0% /sys/fs/cgroup
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/tmp
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/spool
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/opt
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/log
/dev/dasda1 194M   24M  161M  13% /boot/zipl
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/pgsql
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/named
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/mailman
/dev/dasda3 5.8G  3.0G  2.5G  55% /usr/local
/dev/dasda3 5.8G  3.0G  2.5G  55% /tmp
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/crash
/dev/dasda3 5.8G  3.0G  2.5G  55% /srv
/dev/dasda3 5.8G  3.0G  2.5G  55% /opt
/dev/dasda3 5.8G  3.0G  2.5G  55% /home
/dev/dasda3 5.8G  3.0G  2.5G  55% /boot/grub2/s390x-emu
sles12:~ #


On Thu, Apr 21, 2016 at 2:37 PM, Mark Post  wrote:

> >>> On 4/21/2016 at 05:33 PM, Grzegorz Powiedziuk
> >>> 
> wrote:
> > then pvcreate, vgextend, lvextend and filesystem resize.
>
> No, we're trying to get him set up with LVM, just btrfs.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/
© 2016 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. 
The information contained in this communication is confidential, is intended 
only for the use of the recipient named above, and may be legally privileged. 
If the reader of this message is not the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this communication 
is strictly prohibited. If you have received this communication in error, 
please resend this communication to the sender and delete the original message 
or any copy of it from your computer system.

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-22 Thread Offer Baruch

So,

If you make sure you have NATIVE NONE and keep track of your grants (just
like PORTBASED) there is no real security concern...
The guest is only allowed the vlans you grant it (just like PORTBASED) and
he cant send any untagged frames.
I would rather manage a USERBASED VSWITCH with trunks over managing ports
with PORTBASED any day...
It is much easier to make vlan mistakes with PORTBASED... USERBASED is much
more intuitive, easy to manage and easy to view...

I agree you should close all the security holes before you do that... but
that seems a better solution then PORTBASED.

There are pro's and con's for everything but I would recommend USERBASED
for security reasons and management reasons (assuming you know what you are
doing).

Offer Baruch
On Apr 22, 2016 6:19 PM, "Alan Altmark"  wrote:

> On Friday, 04/22/2016 at 07:07 GMT, Offer Baruch 
> wrote:
> > Can you please explain what is the problem with linux working in trunk
> mode?
> > What security problem are you talking about?
>
> An untrusted server should not be on a trunk port.  Ever.  A trunk can
> also carry untagged frames, and those frames will be associated with the
> *native* VLAN of the switch.  I can't get people to code "VLAN AWARE
> NATIVE NONE", so they are getting "NATIVE 1".  That means untagged frames
> from a VLAN-aware guest will be placed on VLAN 1, which is the default for
> most switch vendors, and is used to carry switch management traffic.  And
> to talk to other hosts attached to the default VLAN.
>
> I'm not sure if a physical switch port can have the native VLAN ID for
> that port excluded from the allowed VLANs, or if that will raise an error.
>  NATIVE NONE causes untagged frames to be dropped on trunking vNICs.  z/VM
> 6.1 and earlier don't have that capability, so be careful.
>
> Trunks are for switches, not hosts.  From the network's point of view, ALL
> hosts are evil.  Let us say that in order to save money, you are attaching
> multiple hosts to a trunked OSA port.  There are NO OSA controls on what
> LPARs can use what VLANs, so it must be assumed that the host can attach
> itself to any VLAN authorized for the port.
>
> In a VSWITCH, we don't have that problem.  However, VLAN IDs can and do
> change.  You don't want a VLAN-aware host to be accidentally left on the
> wrong VLAN.  Network People don't expect hosts to be using trunks without
> a Really Good Reason.
>
> Alan Altmark
>
> Senior Managing z/VM and Linux Consultant
> Lab Services System z Delivery Practice
> IBM Systems & Technology Group
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com
> IBM Endicott
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Simple DASD question

2016-04-22 Thread Tom Huegel

Although when I try to reboot

 [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46... 6s / no
limit) [ BUSY ] A start job is running for dev-disk-by\x2d
uuid-d8b46... 6s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46... 7s / no limit) [ BUSY ] A start job is
 running for dev-disk-by\x2duuid-d8b46... 7s / no limit) [ BUSY ] A start
job is running for dev-disk-by\x2duuid-d8b46... 8s / no li
mit) [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46... 8s /
no limit) [ BUSY ] A start job is running for dev-disk-by
\x2duuid-d8b46... 9s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46... 9s / no limit) [ BUSY ] A start jo
b is running for dev-disk-by\x2duuid-d8b46...10s / no limit) [ BUSY ] A
start job is running for dev-disk-by\x2duuid-d8b46...10s / n
o limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46...11s / no limit) [** [0m] A start job is
running for dev
-disk-by\x2duuid-d8b46...11s / no limit) [ * [0m] A start job is
running for dev-disk-by\x2duuid-d8b46...12s / no limit) [**
 [0m] A start job is running for dev-disk-by\x2duuid-d8b46...12s / no
limit) [ BUSY ] A start job is running for dev-disk-by\x2duuid
-d8b46...13s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46...13s / no limit) [ BUSY ] A start job is run
ning for dev-disk-by\x2duuid-d8b46...14s / no limit) [ BUSY ] A start job
is running for dev-disk-by\x2duuid-d8b46...14s / no limit)
 [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46...15s / no
limit) [ BUSY ] A start job is running for dev-disk-by\x2d
uuid-d8b46...15s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46...16s / no limit) [ BUSY ] A start job is
 running for dev-disk-by\x2duuid-d8b46...16s / no limit) [ BUSY ] A start
job is running for dev-disk-by\x2duuid-d8b46...17s / no li
mit) [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46...17s /
no limit) [ BUSY ] A start job is running for dev-disk-by
\x2duuid-d8b46...18s / no limit) [** [0m] A start job is running for
dev-disk-by\x2duuid-d8b46...18s / no limit) [ * [0m] A
start job is running for dev-disk-by\x2duuid-d8b46...19s / no limit) [
** [0m] A start job is running for dev-disk-by\x2duuid-d8b
46...19s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46...20s / no limit) [ BUSY ] A start job is running
 for dev-disk-by\x2duuid-d8b46...20s / no limit) [ BUSY ] A start job is
running for dev-disk-by\x2duuid-d8b46...21s / no limit) [ B
USY ] A start job is running for dev-disk-by\x2duuid-d8b46...21s / no
limit) [ BUSY ] A start job is running for dev-disk-by\x2duuid
-d8b46...22s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46...22s / no limit) [ BUSY ] A start job is run
ning for dev-disk-by\x2duuid-d8b46...23s / no limit) [ BUSY ] A start job
is running for dev-disk-by\x2duuid-d8b46...23s / no limit)
 [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46...24s / no
limit)

















RUNNING   SCZVMLX2

On Fri, Apr 22, 2016 at 7:59 AM, Tom Huegel  wrote:

> Thank-you...
> Maybe someday I will learn how it all works... I just don't do that much
> with LINUX..
>
>
> sles12:~ # fdasd -a /dev/dasdb
> reading volume label ..: VOL1
> reading vtoc ..: ok
> auto-creating one partition for the whole disk...
> writing volume label...
> writing VTOC...
> rereading partition table...
> sles12:~ # btrfs device add /dev/dasdb1 /
> sles12:~ # btrfs filesystem show
> Label: none  uuid: d8b46146-19c1-48d8-b024-80547e728787
> Total devices 2 FS bytes used 2.74GiB
> devid1 size 5.71GiB used 3.53GiB path /dev/dasda3
> devid2 size 6.88GiB used 0.00B path /dev/dasdb1
> Btrfs v3.16+20140829
> sles12:~ # df -h
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/dasda3  13G  3.0G  9.4G  24% /
> devtmpfs439M  8.0K  439M   1% /dev
> tmpfs   446M 0  446M   0% /dev/shm
> tmpfs   446M  7.0M  439M   2% /run
> tmpfs   446M 0  446M   0% /sys/fs/cgroup
> /dev/dasda3  13G  3.0G  9.4G  24% /var/tmp
> /dev/dasda3  13G  3.0G  9.4G  24% /var/spool
> /dev/dasda3  13G  3.0G  9.4G  24% /var/opt
> /dev/dasda3  13G  3.0G  9.4G  24% /var/log
> /dev/dasda1 194M   24M  161M  13% /boot/zipl
> /dev/dasda3  13G  3.0G  9.4G  24% /var/lib/pgsql
> /dev/dasda3  13G  3.0G  9.4G  24% /var/lib/named
> /dev/dasda3  13G  3.0G  9.4G  24% /var/lib/mailman
> /dev/dasda3  13G  3.0G  9.4G  24% /usr/local
> /dev/dasda3  13G  3.0G  9.4G  24% /tmp
> /dev/dasda3  13G  3.0G  9.4G  24% /var/crash
> /dev/dasda3  13G  3.0G  9.4G  24% /srv
> /dev/dasda3  13G  3.0G  9.4G  24% /opt
> /dev/dasda3  13G  3.0G  9.4G  24% /home
> /dev/dasda3  13G  3.0G  9.4G  24% /boot/grub2/s390x-emu
> sles12:~ #
>
> On Fri, Apr 22, 2016 at 7:19 AM, Mark Post  wrote:
>
>> >>> On 4/22/2016 at 10:07 AM,

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-22 Thread Alan Altmark

On Friday, 04/22/2016 at 07:07 GMT, Offer Baruch  
wrote:
> Can you please explain what is the problem with linux working in trunk 
mode?
> What security problem are you talking about?

An untrusted server should not be on a trunk port.  Ever.  A trunk can 
also carry untagged frames, and those frames will be associated with the 
*native* VLAN of the switch.  I can't get people to code "VLAN AWARE 
NATIVE NONE", so they are getting "NATIVE 1".  That means untagged frames 
from a VLAN-aware guest will be placed on VLAN 1, which is the default for 
most switch vendors, and is used to carry switch management traffic.  And 
to talk to other hosts attached to the default VLAN.

I'm not sure if a physical switch port can have the native VLAN ID for 
that port excluded from the allowed VLANs, or if that will raise an error. 
 NATIVE NONE causes untagged frames to be dropped on trunking vNICs.  z/VM 
6.1 and earlier don't have that capability, so be careful.

Trunks are for switches, not hosts.  From the network's point of view, ALL 
hosts are evil.  Let us say that in order to save money, you are attaching 
multiple hosts to a trunked OSA port.  There are NO OSA controls on what 
LPARs can use what VLANs, so it must be assumed that the host can attach 
itself to any VLAN authorized for the port.

In a VSWITCH, we don't have that problem.  However, VLAN IDs can and do 
change.  You don't want a VLAN-aware host to be accidentally left on the 
wrong VLAN.  Network People don't expect hosts to be using trunks without 
a Really Good Reason.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Simple DASD question

2016-04-22 Thread Tom Huegel

Thank-you...
Maybe someday I will learn how it all works... I just don't do that much
with LINUX..


sles12:~ # fdasd -a /dev/dasdb
reading volume label ..: VOL1
reading vtoc ..: ok
auto-creating one partition for the whole disk...
writing volume label...
writing VTOC...
rereading partition table...
sles12:~ # btrfs device add /dev/dasdb1 /
sles12:~ # btrfs filesystem show
Label: none  uuid: d8b46146-19c1-48d8-b024-80547e728787
Total devices 2 FS bytes used 2.74GiB
devid1 size 5.71GiB used 3.53GiB path /dev/dasda3
devid2 size 6.88GiB used 0.00B path /dev/dasdb1
Btrfs v3.16+20140829
sles12:~ # df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/dasda3  13G  3.0G  9.4G  24% /
devtmpfs439M  8.0K  439M   1% /dev
tmpfs   446M 0  446M   0% /dev/shm
tmpfs   446M  7.0M  439M   2% /run
tmpfs   446M 0  446M   0% /sys/fs/cgroup
/dev/dasda3  13G  3.0G  9.4G  24% /var/tmp
/dev/dasda3  13G  3.0G  9.4G  24% /var/spool
/dev/dasda3  13G  3.0G  9.4G  24% /var/opt
/dev/dasda3  13G  3.0G  9.4G  24% /var/log
/dev/dasda1 194M   24M  161M  13% /boot/zipl
/dev/dasda3  13G  3.0G  9.4G  24% /var/lib/pgsql
/dev/dasda3  13G  3.0G  9.4G  24% /var/lib/named
/dev/dasda3  13G  3.0G  9.4G  24% /var/lib/mailman
/dev/dasda3  13G  3.0G  9.4G  24% /usr/local
/dev/dasda3  13G  3.0G  9.4G  24% /tmp
/dev/dasda3  13G  3.0G  9.4G  24% /var/crash
/dev/dasda3  13G  3.0G  9.4G  24% /srv
/dev/dasda3  13G  3.0G  9.4G  24% /opt
/dev/dasda3  13G  3.0G  9.4G  24% /home
/dev/dasda3  13G  3.0G  9.4G  24% /boot/grub2/s390x-emu
sles12:~ #

On Fri, Apr 22, 2016 at 7:19 AM, Mark Post  wrote:

> >>> On 4/22/2016 at 10:07 AM, Tom Huegel  wrote:
> > This is what I have fresh after my re-re-re-re-install.
> > It seems "btrfs device add /dev/dasdb1 /" would be a good thing to do
> but I
> > get message about dasdb1 not existing...
>
> Have you used YaST or run fdasd to create it?
> fdasd -a /dev/dasdb
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Ubuntu support for zoom

2016-04-22 Thread Michael MacIsaac

Hello lists,

I added support for Ubuntu Linux to the new zoom 1-22 release. See:
https://sourceforge.net/projects/system-zoom/files/

You will only find a .rpm, not a .deb package.  But the Ubuntu "alien"
command quickly and seemingly accurately converts RPMs to .deb format.

For reading CMS files, it would seem that cmsfscat and cmsfslst are
missing, so I modified the code to use cmsfs-fuse. I streamlined it so SLES
and RHEL also use cmsfs-fuse.  Less is more (sorry Rick :)).

There is also a new, short chapter (5) "zoom on Ubuntu" in the PDF.

This code is still very much experimental, but hopefully in keeping with
the "Release early, release often" open-source philosophy.

Enjoy if you are so inclined as to try it.  Feedback is always welcome.

-Mike MacIsaac

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Simple DASD question

2016-04-22 Thread Mark Post

>>> On 4/22/2016 at 10:07 AM, Tom Huegel  wrote: 
> This is what I have fresh after my re-re-re-re-install.
> It seems "btrfs device add /dev/dasdb1 /" would be a good thing to do but I
> get message about dasdb1 not existing...

Have you used YaST or run fdasd to create it?
fdasd -a /dev/dasdb


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Simple DASD question

2016-04-22 Thread Tom Huegel

So far I have failed with my feeble attempts to add the second disk dasdb
(0251) to the btrfs filesystem.
This is what I have fresh after my re-re-re-re-install.
It seems "btrfs device add /dev/dasdb1 /" would be a good thing to do but I
get message about dasdb1 not existing...


sles12:~ # lsdasd
Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
==
0.0.0250   active  dasda 94:0ECKD  4096   7042MB1802880
0.0.0251   active  dasdb 94:4ECKD  4096   7042MB1802880
sles12:~ # btrfs filesystem show
Label: none  uuid: d8b46146-19c1-48d8-b024-80547e728787
Total devices 1 FS bytes used 2.74GiB
devid1 size 5.71GiB used 3.53GiB path /dev/dasda3
Btrfs v3.16+20140829
sles12:~ # df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/dasda3 5.8G  3.0G  2.5G  55% /
devtmpfs439M  8.0K  439M   1% /dev
tmpfs   446M 0  446M   0% /dev/shm
tmpfs   446M  7.0M  439M   2% /run
tmpfs   446M 0  446M   0% /sys/fs/cgroup
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/tmp
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/spool
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/opt
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/log
/dev/dasda1 194M   24M  161M  13% /boot/zipl
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/pgsql
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/named
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/mailman
/dev/dasda3 5.8G  3.0G  2.5G  55% /usr/local
/dev/dasda3 5.8G  3.0G  2.5G  55% /tmp
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/crash
/dev/dasda3 5.8G  3.0G  2.5G  55% /srv
/dev/dasda3 5.8G  3.0G  2.5G  55% /opt
/dev/dasda3 5.8G  3.0G  2.5G  55% /home
/dev/dasda3 5.8G  3.0G  2.5G  55% /boot/grub2/s390x-emu
sles12:~ #


On Thu, Apr 21, 2016 at 2:37 PM, Mark Post  wrote:

> >>> On 4/21/2016 at 05:33 PM, Grzegorz Powiedziuk 
> wrote:
> > then pvcreate, vgextend, lvextend and filesystem resize.
>
> No, we're trying to get him set up with LVM, just btrfs.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Available now: Linux on z Systems publications for Ubuntu 16.04

2016-04-22 Thread Dorothea Matthaeus

The Ubuntu 16.04 distribution is now available for Linux on z Systems and
LinuxONE.
IBM provides documentation that can be used as a complement to the
documentation that is provided by the Ubuntu Documentation Project.
See:

IBM Knowledge Center:
https://www.ibm.com/support/knowledgecenter/linuxonibm/liaaf/lnz_r_ubuntu.html

developerWorks:
http://www.ibm.com/developerworks/linux/linux390/documentation_ubuntu.html


Dorothea Matthaeus
Linux on z Systems, Information Development
IBM Deutschland Research and Development GmbH

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Available now: Linux on z Systems. Kernel 4.4 and libica 2.6 documentation

2016-04-22 Thread Dorothea Matthaeus

The following Linux on z Systems publications are now live on IBM Knowledge
Center and developerWorks.

 - Device Drivers, Features, and Commands (Kernel 4.4)
 - Device Drivers, Features, and Commands for Linux as a KVM Guest (Kernel
4.4)
 - Using the Dump Tools (Kernel 4.4)
 - Kernel Messages (Kernel 4.4)

 - libica Programmer's Reference 2.6

See:

developerWorks:
http://www.ibm.com/developerworks/linux/linux390/documentation_dev.html

IBM Knowledge Center:
http://www.ibm.com/support/knowledgecenter/linuxonibm/liaaf/lnz_r_main.html


Dorothea Matthaeus
Linux on z Systems, Information Development
IBM Deutschland Research and Development GmbH

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

2016-04-21 Linux on z Systems - Kernel 4.4 related updates on developerWorks

2016-04-22 Thread Gerhard Hiller

Please refer to 
http://www.ibm.com/developerworks/linux/linux390/whatsnew.html
for several updates to the 'Development stream':
 * description of upstream kernel 4.4 features that were
   contributed by Linux on z Systems development
 * kernel 4.4 patch for kernel message catalog
 * s390-tools 1.33.0 and s390-tools 1.34.0 delivers new functionality
   and bug fixes
 * updated documentation
   -- Device Drivers, Features, and Commands for Linux as a KVM Guest 
  (Kernel 4.4) - SC34-2754-01
   -- Device Drivers, Features, and Commands (Kernel 4.4) SC33-8411-29
   -- Using the Dump Tools (Kernel 4.4) SC33-8412-15
   -- Kernel Messages (Kernel 4.4) - SC34-2599-11
   -- libica Programmer's Reference -SC34-2602-07
* end of message


Mit freundlichen Grüßen / Kind regards








Gerhard Hiller


 














Software Management and Linux Technologies


IBM Systems








Phone:
 +49-7031-16-4388
 IBM Deutschland





 Schoenaicher Str. 220


E-Mail:
 ghil...@de.ibm.com
 71032 Boeblingen




 Germany





IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz,  Geschäftsführung: Dirk 
Wittkopp 
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, 
HRB 243294

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-22 Thread Offer Baruch

Alan,
Can you please explain what is the problem with linux working in trunk mode?
What security problem are you talking about?

Thanks
Offer Baruch
On Apr 22, 2016 8:00 AM, "Alan Altmark"  wrote:

> On Friday, 04/22/2016 at 02:41 GMT, Grzegorz Powiedziuk
>  wrote:
> >
> > 3. Less common, useful in some cases - OSA is plugged into "trunk" port
> on
> > real switch and in general same as (2). But, when you do grant, you can
> say
> > that this specific grant should act as "porttype trunk" (and you specify
> > which vlans are trunked)  so VSWITCH instead of removing the vlan tag,
> > forwards the whole thing to linux guest. So linux guest should be
> > configured to receive and send tagged frames.  As Mark mentioned, during
> > install process it might be troublesome.
>
> Please don't do this.  Instead, use a PORTBASED VSWITCH so that you can
> two vNICs, each assigned to a different VLAN on the same VSWITCH.
>
> Except for a VSWITCH sniffer, there's no longer any need for Linux to be
> VLAN-aware when running as a guest.
>
> Alan Altmark
>
> Senior Managing z/VM and Linux Consultant
> Lab Services System z Delivery Practice
> IBM Systems & Technology Group
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com
> IBM Endicott
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Simple DASD question

Re: Formatting DASD

Re: Simple DASD question

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

Formatting DASD

Re: Simple DASD question

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

Re: Simple DASD question

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

Re: Simple DASD question

Ubuntu support for zoom

Re: Simple DASD question

Re: Simple DASD question

Available now: Linux on z Systems publications for Ubuntu 16.04

Available now: Linux on z Systems. Kernel 4.4 and libica 2.6 documentation

2016-04-21 Linux on z Systems - Kernel 4.4 related updates on developerWorks

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

17 matches

Site Navigation

Mail list logo

Footer information