The problem was apparently related to the Proxy settings, somehow. The ftp to
the 'repository' kept being routed through our local network proxy. I finally
had to disable it altogether, reboot, and now things seem to be working better.
Stay tuned,
Dave
Dave Stuart
Prin. Info. Systems
>>> On 1/6/2011 at 06:23 PM, David Stuart wrote:
> I'm wondering if our local proxy is getting in the way. Need to talk to the
> Security folks...
If, from your Linux system, you execute "env | grep -i proxy" and anything
shows up, that is possible. If you do need those proxy values set, th
Mark,
I don't understand what's going on. My SLES 11 SP1 system is successfully
logging on to the FTP Server, and then it issues the following commands:
(60) 1/6/2011 15:17:17 PM - galileo (157.145.216.103)> 230 Logged on
(60) 1/6/2011 15:17:17 PM - galileo (157.145.216.103)> CWD //co
Mark,
galileo:/ # zypper in yast2-qt
File '/content' not found on medium 'ftp://gali...@157.145.12.236/%2f'
Abort, retry, ignore? [a/r/i/?] (a):
I don't understand why it's giving me this error. There is a 'content' file in
the '/' directory on the FTP Server.
The 'source' is on my Win/XP
>>> On 1/6/2011 at 05:21 PM, David Stuart wrote:
> Mark,
>
> rpm -q yast2-qt
>
> says not installed. And I don't find it on the yast2 software list in
> Software -> Management.
Try "zypper in yast2-qt" and see what happens.
Mark Post
>>> On 1/5/2011 at 06:41 PM, "Smith, Ann (ISD, IT)"
wrote:
> Any ideas how important /dev/disk/by-name is and how to get it back?
I wouldn't think it's terribly important unless someone went out of their way
to use by-name for something. I would suggest running zfcp_disk_configure for
all the
Mark,
rpm -q yast2-qt
says not installed. And I don't find it on the yast2 software list in Software
-> Management.
Hmm...
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org>>> "Mark Post" 1/6/2011 2:03 PM >>>
>>> On
Eric,
>From what I can tell, at least some of the X11 libraries are there.
When I search for packages with X11 in the name, in Software Manager, I believe
it's showing that they're all installed.
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-673
>>> On 1/6/2011 at 03:37 PM, David Stuart wrote:
> Mark,
>
> I'll send it privately, if that's ok with you.
Dave,
Do you have the yast2-qt rpm installed? /sbin/yast2 is looking for the plugin
it provides and isn't finding it:
+ '[' -e /usr/lib64/YaST2/plugin/libpy2qt.so.2 ']'
+ return 1
That's Mark,
That worked perfectly.
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org>>> "Mark Post" 1/6/2011 11:32 AM >>>
snip.
It looks like you actually named the LV home-vg, not home. A simple "lvs"
command will sh
On Thu, 06 Jan 2011 16:10:36 -0500 (EST), Richard Troth wrote:
>
> The "problem" is that one cannot boot from an unpartitioned CKD disk
> (LDL) even though one can boot from an unpartitioned FBA disk.
> Partition tables are not required for other disks and bootstraps. Why
> should they be required
>>> On 1/6/2011 at 04:04 PM, Stephen Powell wrote:
-snip-
> Where I live is a moot point because I don't drink. But thanks for
> the offer.
Not even water, or soda? I didn't say it had to be alcohol. :)
-snip-
> However...
>
> Only the first combination supports more than one partition
> p
On 01/06/2011 01:22 PM, Stephen Powell wrote:
I have recently completed work on enhancements
to GNU parted to support all combinations of DASD type (CKD and FBA)
DASD format (cdl, ldl, CMS non-reserved, and CMS reserved) and DASD
driver (ECKD, FBA, and DIAG) supported by the Linux kernel;
Excell
The "problem" is that one cannot boot from an unpartitioned CKD disk
(LDL) even though one can boot from an unpartitioned FBA disk.
Partition tables are not required for other disks and bootstraps. Why
should they be required for mainframe disks and bootstraps?
Anyway ... I am hopeful that Boebli
On Thu, 06 Jan 2011 14:40:23 -0500 (EST), Mark Post wrote:
> On 1/6/2011 at 02:22 PM, Stephen Powell wrote:
>> I have recently completed work on enhancements
>> to GNU parted to support all combinations of DASD type (CKD and FBA)
>> DASD format (cdl, ldl, CMS non-reserved, and CMS reserved) and DA
Mark,
I'll send it privately, if that's ok with you.
Dave
>>> "Mark Post" 1/6/2011 12:23 PM >>>
>>> On 1/6/2011 at 03:02 PM, David Stuart wrote:
> I ran the command, and the output is attached.
Dave,
Attachments to this list get removed by the list server.
Mark Post
--
>>> On 1/6/2011 at 03:02 PM, David Stuart wrote:
> I ran the command, and the output is attached.
Dave,
Attachments to this list get removed by the list server.
Mark Post
--
For LINUX-390 subscribe / signoff / archive acces
Mark,
I ran the command, and the output is attached.
And as I said previously, the YaST GUI worked during, and for a while after,
the initial install. But when I went back to do some other things, it's not
working any longer.
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
C
David:
You shouldn't ever need to start up runlevel 5 on a virtual server. In
fact, without a graphic capable console, it won't even work.
What you do need to do is investigate why X forwarding isn't working for
you.
First, are you logging in as root or as a non-root account? That'll
make a di
Eric,
To quote an instructor from many, many years ago "There are no dumb questions
in this class. The only dumb questions is the one that doesn't get asked."
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org>>> "Eric Chev
>>> On 1/6/2011 at 02:39 PM, Eric Chevalier wrote:
> Also, permit me a
> dumb question: when you installed SLES11, did you install the X runtime
> libraries that your apps are going to require?
Based on the fact that he gets DISPLAY set properly when using ssh -X, I would
guess "yes." Now, the
Eric,
I'll have to look at the installed software. I didn't explicitly install the X
runtime. And I don't remember removing it.
And no, xfs isn't started at any run-level.
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.
Mike,
# lvextend -l +586 /dev/system_vg/home-vg
worked. I could wear I tried that, and received an error. Bit when I just
tried it again, it worked just fine.
Very puzzling.
Thanks, the /home lv has been extended, which is what I was after.
Dave
Dave Stuart
Prin. Info. Systems
Mark and Scott,
Well I apparently did call it home-vg. That's what the 'lvs' command shows.
Although, I'm pretty sure I didn't do it intentionally.
I'll have to try Mark's rename process.
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
dav
>>> On 1/6/2011 at 02:22 PM, Stephen Powell wrote:
> I have recently completed work on enhancements
> to GNU parted to support all combinations of DASD type (CKD and FBA)
> DASD format (cdl, ldl, CMS non-reserved, and CMS reserved) and DASD
> driver (ECKD, FBA, and DIAG) supported by the Linux ke
On 1/6/2011 12:59 PM, David Stuart wrote:
All,
I just saw something in the cookbook. I'll bet my 'problem' is the difference
between running with run level 3 and run level 5...
Thanks anyway, for all your ideas
Dave
P.S. Yes, I can call myself that.
Dave,
Don't be so hard on yoursel
>>> On 1/6/2011 at 02:32 PM, Scott Rohling wrote:
> looks like you called it 'home--vg' ?
Almost. Various commands (though not all commands) that display the LV names
double up on hyphens in the name. Not sure why, but I'm not involved in
writing the code.
Mark Post
--
Dave,
You can do a "ls /dev/system_vg" to see what logical volumes are there.
I would guess that this will work:
# lvextend -l +586 /dev/system_vg/home--vg
"Mike MacIsaac"(845) 433-7061
--
For LINUX-390 subscribe / sig
looks like you called it 'home--vg' ?
Scott Rohling
On Thu, Jan 6, 2011 at 12:23 PM, David Stuart wrote:
> Morning again,
>
> New linux admin here.
>
> I've added a new volume to the Volume group, and now I am trying to extend
> a logical volume.
>
> I'm following section 11.3 of the SLES 11 SP
>>> On 1/6/2011 at 02:23 PM, David Stuart wrote:
> Morning again,
>
> New linux admin here.
>
> I've added a new volume to the Volume group, and now I am trying to extend a
> logical volume.
>
> I'm following section 11.3 of the SLES 11 SP 1 Virtualization Cookbook, page
> 199.
>
> A
>>> On 1/6/2011 at 12:36 PM, David Stuart wrote:
> Hi Pedro,
>
> Win/XP with cygwin Xserver. I do a ssh -X user @ip, and run YaST2, but it
> never starts.
You might get some hints as to why by wading through /var/log/YaST2/y2log.
YaST is extremely verbose in its logging (which helps me o
Mark,
So that's where it is. Silly me, I figured it would be in with the DASD
stuff...
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org>>> "Mark Post" 1/6/2011 11:24 AM >>>
>>> On 1/6/2011 at 11:49 AM, David Stuart wrot
>>> On 1/6/2011 at 11:49 AM, David Stuart wrote:
> Morning all,
>
> New user here.
>
> I followed parts of the Virtualization Cookbook for SLES 11 SP1 when I
> installed the System (LPAR, no z/VM, so I skipped those). Now I need to add
> additional DASD to the LVM group. But all I can ge
Morning again,
New linux admin here.
I've added a new volume to the Volume group, and now I am trying to extend a
logical volume.
I'm following section 11.3 of the SLES 11 SP 1 Virtualization Cookbook, page
199.
A df -h /home (which is the 'volume' I want to extend) shows:
galileo:~ #
On Thu, 06 Jan 2011 09:03:46 -0500 (EST), Richard Troth wrote:
> ...
> The problem with mainframe labelling (the req for an IBM volser) is
> that it panders to the bad behaviour of a certain other mainframe op
> sys. Also, we're mixing labelling with partitioning. They are not
> the same thing, t
All,
I just saw something in the cookbook. I'll bet my 'problem' is the difference
between running with run level 3 and run level 5...
Thanks anyway, for all your ideas
Dave
P.S. Yes, I can call myself that.
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
On Thursday, January 06, 2011 01:24:39 pm you wrote:
> The "echo $DISPLAY" shows localhost:10.0.
>
> Whatever that means
I think that's correct; it's what SSH sets it to for me.
The X-Windows DISPLAY specification consists of three parts,
"hostname:display.screen". This refers to the pseudo-X-di
To be honest, I've never had YAST2 work either, it's always ncurses, but the
ssh -Y works for other x apps where I need root access.
On Thu, Jan 6, 2011 at 1:26 PM, David Stuart wrote:
> Mark,
>
> No joy. I tried the SSH -Y, and it immediate 'fell back' to Ncurses.
>
> I'll have to look into the
Mark,
No joy. I tried the SSH -Y, and it immediate 'fell back' to Ncurses.
I'll have to look into the command line...
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org>>> "Mark Pace" 1/6/2011 9:46
AM >>>
Sometimes I ha
The "echo $DISPLAY" shows localhost:10.0.
Whatever that means
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org>>> "Edmund R. MacKenty"
1/6/2011 9:42 AM >>>
On Thursday, January 06, 2011 12:36:35 pm you wrote:
> Win/XP wit
Sometimes I have a problem with ssh-X when connecting with one ID but then
running an X program as root. Try using ssh -Y
On Thu, Jan 6, 2011 at 12:42 PM, Edmund R. MacKenty <
ed.macke...@rocketsoftware.com> wrote:
> On Thursday, January 06, 2011 12:36:35 pm you wrote:
> > Win/XP with cygwin Xse
On Thursday, January 06, 2011 12:36:35 pm you wrote:
> Win/XP with cygwin Xserver. I do a ssh -X user @ip, and run YaST2, but it
> never starts.
Maybe your DISPLAY variable is not set in your environment? If it isn't, YaST
will use the ncurses interface instead of X. Once logged in, do "echo
$D
Hi Pedro,
Win/XP with cygwin Xserver. I do a ssh -X user @ip, and run YaST2, but it
never starts.
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org>>> "Pedro Principeza" 1/6/2011
9:29 AM >>>
If your client workstation i
If your client workstation is Linux, you may start the SSH with # ssx -X
u...@ip and, by the time you run YaST2, you'll be able to start the
graphic version of it.
Regards,
Pedro
From: David Stuart
To: LINUX-390@vm.marist.edu
Date: 06/01/2011 15:20
Subject:Re: SLES 11 SP 1 - Nc
Thanks Mike,
I'll take a look.
What's frustrating is that when I performed the initial install, I used SSH,
and received the graphical displayed like in your cookbook. Now, I don't. And
more importantly, I don't know why, or what changed.
Dave
Dave Stuart
Prin. Info. Systems Sup
Dave,
> I followed parts of the Virtualization Cookbook for SLES 11 SP1 when I
installed the System (LPAR, no z/VM, so I skipped those).
> Now I need to add additional DASD to the LVM group.
> But all I can get is the Ncurses version of YaST, and I can't figure out
how to get to the Expert Partiti
Morning all,
New user here.
I followed parts of the Virtualization Cookbook for SLES 11 SP1 when I
installed the System (LPAR, no z/VM, so I skipped those). Now I need to add
additional DASD to the LVM group. But all I can get is the Ncurses version of
YaST, and I can't figure out how to
> In theory, we could mangle the IPL code into the first
> 512 bytes of a filesystem which is reserved on x86 as "partition boot
> record", ...
You should thusly mangle the IPL code. :-)
It doesn't break anything else to do so.
> a) the disk would not be "labled" as observed by other mainf
48 matches
Mail list logo
