I installed Centos 6.2/i386 on a machine last night with a 1920x1080 monitor.
The installer ran in graphical mode and looked fine. After the install was
finished I rebooted and ran through the "firstboot" stuff (set up user, etc)
with no problem and, again, it looked good.
After that, when I should have seen the gdm login screen, all I got was the
blue background but not the box with the usernames in it, so there is no way to
log in.
"telinit 3", login to the text console, no problem. Type "startx", back to the
same empty blue screen that gdm shows me.
[root@ws194 log]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain ws194 ws194.ltsp
::1 localhost localhost.localdomain ws194 ws194.ltsp
[root@ws194 log]# uname -a
Linux ws194.ltsp 2.6.32-220.2.1.el6.i686 #1 SMP Thu Dec 22 18:50:52 GMT 2011
i686 i686 i386 GNU/Linux [root@ws194 log]#
I rsynced /etc/skel to /home/myusername before running startx but that made no
difference. Still got the blank blue screen.
I tried disabling the Composite extension as directed here:
http://www.linuxquestions.org/questions/slackware-14/unable-to-startx-after…
Nothing changed.
I don't see anything in /var/log/Xorg.0.log that looks too interesting; it
appears that X figures it's running fine.
This was working fine with a smaller monitor on Centos 5.7. Plus the Centos 6
installer looked fine, and the blue screen also looks nice and crisp,
--
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.comwww.creekfm.com - FIFTY THOUSAND WATTS of POW WOW POWER!
My provider is getting ready to switch my DSL router to bridging mode
and I supply the router (so I can get no only IPv4 addresses but also
IPv6 addresses!).
Here are his 'instructions' to me:
"Basically you start pppoe, I give you the username and password for it,
and then I set the router to passthrough modem mode, and you initiate
the PPPoE session directly with my LNS back here. You'll get a dynamic
IP on the dsl side (which is normal) and then you just set up your
static routes in the linux box as normal. My LNS automatically routes
your traffic to the IP it randomly assigns to the DSL link. Once we
verify that IP6CP is up, I can assign you a /48 and you can rock out
with that however you want."
Currently I have a /26 IPv4 assignment which will continue.
So do I change the alias in modprobe.conf from eth0 to ppp0? Or is just
listing interface eth0 in hte pppoe.conf file enough?
From my ISP's comments, the pppoe negotiation will provide the address
for eth0. I already know my /26 allocation. I need to set up static
routes on eth1 for these IPv4 addresses (different subnets to different
internal firewalls). What tool do I use to set these?
And then I get to work with IPv6!
Pointers to Howtos are greatly appreciated.
On Sun, Jan 11, 2009, Marko Vojinovic wrote:
>On Saturday 10 January 2009 23:03, John R Pierce wrote:
>> Marko Vojinovic wrote:
>> > I have a WinXP machine that is to be unattended for a period of 3 years
>> > (yes, I know, it sounds ridiculous, but still...). What I need is remote
>> > access to it to perform regular system maintenance, virus cleanups,
>> > occasional software installations, reboots, config changes, etc.
>> >
>> > Of course, rdesktop would do it, or vnc server or something else. The
>> > problem is that this machine is behind a NAT, and I cannot access it
>> > remotely from outside (and I need access from whereever on the planet I
>> > may happen to be).
>>
>> if this remote XP machine is behind a NAT server that you can log onto
>> with SSH, then, from your local machine...
>>
>> ssh -L 3390:private-ip-of-remote-XP-machine:3389
>> username@ip-or-hostname-of-remote-NAT-server
>
>Well, first, private-ip-of-remote-XP-machine is dynamic, given by my ISP's
>dhcp server, so I cannot have 100% guarantee that it will always be the same.
>And I have no easy way of finding it out if it does change.
We handle this with our *nix clients that are on dynamic IP
addresses by assigning them a hostname with proper DNS that
resolves to their latest dynamic IP address, then having them
check in every fifteen minutes with a cron job that hits a web
URL here with this hostname as an argument. On this end, it
looks at their real IP, compares that to the one in DNS, and
sends a notice of there's a change. It also sends a reply to the
http(s) request indicating a change that can be acted up on their
end (actually it's an xmlrpc call and the cron job a python
script -- which is probably fairly easy to implement using python
on the Microsoft Virus, Windows).
Using OpenVPN from the dynamic end, it would be pretty easy to
have it make sure that there's a current connection after a
change is made. We generally use unique /24 subnets in the
private 10.0.0.0/8 space for each client machine so the *nix side
can route through the appropriate OpenVPN tunnel.
>Second, and more serious, I have no access to the NAT server, the ISP controls
>it. I may try using my username/password combination, but I am not sure what
>structure the ISP has. I mean, they may well have a NAT inside a NAT inside a
>NAT... However, I'll try it out to see if this kind of port-forwarding works
>in my case. :-)
That should not be a problem with OpenVPN connections initiated
from the Windows machines.
The real issue is how one would script this on the Windows side
as the OpenVPN client I've seen for Windows assumes GUI control.
Bill
--
INTERNET: bill(a)celestial.com Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way
Voice: (206) 236-1676 Mercer Island, WA 98040-0820
Fax: (206) 232-9186
Rights is a fictional abstraction. No one has ``Rights'', neither
machines nor flesh-and-blood. Persons... have opportunities, not rights,
which they use or do not use.
-- Lazarus Long
I have a Windows Server 2003 system I'm trying to back up to a Linux host.
when I access the share with smbclient, I can "see" the files (`ls` returns a
list of files, etc)
smbclient -U shareuser //server/sharename password
But, when I try to actually mount the drive, I get "permission denied" errors
trying to access the drive. (EG: using `df`) Running the following command
takes about 10 seconds:
smbmount //server/sharename /mnt/servername -o \
credentials=/path/to/credentials,ro
I've also tried an alternate format:
mount -t smbfs -o username=USERNAME //server/sharename /mnt/servername
Same results both ways. I found a CentOS forum where somebody had problems
with the RPM package, but retrograding to the package(s) he recommends didn't
change anything.
http://www.centos.org/modules/newbb/viewtopic.php?topic_id=2307
I'm running the latest samba-client & samba-common on CentOS 4.2. SELinux is
in warn mode. Here's the /var/log/messages when I mount:
Feb 2 19:42:16 sol kernel: SELinux: initialized (dev smbfs, type smbfs), uses
genfs_contexts
Feb 2 19:42:16 sol kernel: smb_retry: no connection process
Feb 2 19:42:46 sol kernel: smb_add_request: request [c554bee0, mid=0] timed
out!
Feb 2 19:42:46 sol kernel: smb_delete_inode: could not close inode 2
Feb 2 19:42:46 sol kernel: SELinux: initialized (dev smbfs, type smbfs), uses
genfs_contexts
Feb 2 19:42:46 sol mount.smbfs[21755]: [2006/02/02 19:42:46, 0]
client/smbmount.c:send_fs_socket(410)
Feb 2 19:42:46 sol mount.smbfs[21755]: mount.smbfs: entering daemon mode
for service \\heliodorite.sunset.net\iissites, pid=21755
Running with debug=8 didn't provide much that was helpful. Any ideas where to
go from here?
-Ben
--
"The best way to predict the future is to invent it."
- XEROX PARC slogan, circa 1978
On Tue, Sep 14, 2010, Timothy Murphy wrote:
>
>Is there a document with instructions for this?
>I've had smartd warnings that a hard disk in my server is sick,
>so I am installing a new drive (in addition to the old).
>
>I was thinking of copying the old root partition with
> sudo cp -a -P /* /mnt/hd
>(after mounting the prospective new root partition).
>Then I'd have to modify the new /etc/fstab .
>
>Is that a sensible approach?
IHMO, the most sensible approach is to do a fresh install on a
new HD. After the install is complete, install and mount the old
HD read-only to allow you to copy things over.
I just went through this process about 10 days ago when a fan
went Tango Uniform on our mail e-mail/file server which had been
up 1,390 days before the crash. The old system had two
partitions, one for ``/'', the other on ``/home'' making it easy
to copy the old ``/home'' to the new one using any of a number of
tools. I prefer ``cd /oldhome; find . | cpio -pdum /home'' as it
takes care of everything (of course it's important to add the
appropriate users and groups before doing this).
Using ``rsync'' would also work, but given that the initial copy
is not likely to have anything to update, I prefer ``cpio''.
Things get a bit more complicated when the old and new systems
are different distributions as user/group ids may differ. In my
recent case, the old machine was running SuSE Linux Enterprise 10
while the new one is CentOS 5.current. This required a bit of
``chown -R username: ~username'' work after the ``/home'' copy to
get things the way CentOS prefers.
In this case transferring user accounts was complicated a bit as
SuSE used different encryption in the ``/etc/shadow'' file so
simply copying the relevant part of the files was not sufficient,
but the passwords had to be reset so CentOS recognized them.
In our case, we didn't have to worry about things that were
installed under /usr/bin as we use the OpenPKG portable package
management system for pretty much everything including vendor
systems like openssh and postfix, and they are installed under
the ``/home'' file system.
Installing non-distribution software under /usr/local with that
either in its own file system or symlinked to a non-root file system
avoids having to sort out what belongs to the distribution, and
what has been added from other sources. With most open source
software this simply requires using a simple option when building
``./configure --prefix=/usr/local ...''
This was standard practice with open source software long before
Linux came around, and is probably my main gripe with Linux
standards (the other is changing APIs without considering how
the change breaks installed systems).
Bill
--
INTERNET: bill(a)celestial.com Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way
Voice: (206) 236-1676 Mercer Island, WA 98040-0820
Fax: (206) 232-9186 Skype: jwccsllc (206) 855-5792
Just because you do not take an interest in politics doesn't mean politics
won't take an interest in you. -- Pericles
On Mon, February 2, 2015 5:34 pm, Always Learning wrote:
>
> On Mon, 2015-02-02 at 16:30 -0600, Valeri Galtsev wrote:
>
>> RedHat doesn't like poorly administered machined with RHEL linux get
>> hacked, then many voices saying saying in the internet: RHEL Linux is
>> not secure, RHEL Linux machines are getting hacked. Even though the
>> reason is not what it sounds like.
>
> What is the reason RHEL machines are being hacked ?
>
I assume, you may have your own list but once you asked I'll mention off
the top of my head what I've seen (no, these are not happened on machine I
administer - knocking on wood ):
1. machine compromised elsewhere, user password (via keylogger or
malicious ssh client) or secret key gets stolen; cyber criminal connects
to my server with credentials on my user
2. after he is in: elevation of privileges through some local exploit. As
I tend to have nothing to be exploited on multi-user machines (and run
them under assumption bad guy is already in), this normally doesn't happen
to me, but I help sometimes to sweep up mess and do forensics when that
happened to someone
3. Independent on the above: just blunder when you are doing
administration. I have seen admin helping a user (who was on the phone)
change his password. And he accidentally in
passwd username
stuck enter between the above two words (!). Which ended up in changing
root password on machine to very weak one he passed that person over the
phone. When that didn't work (good hint that that was not that user's
password that was changed!), he just changed it again. Then intruder just
walked as root through open door (that weak password was one of the top
four in cracker's dictionary).
4. Not updating the system, or having vulnerable services - I have seen
these as well
5. Weak root password should be on the list, but practically only the ones
on the top of password cracking dictionary are... Anyway, I do (or I like
to think that I do) have strong root passwords. Nevertheless, I always
have measures to thwart dictionary attacks from the network (as some of my
users may have weak passwords, not the ones on the top of dictionary
though I bet)
... This list goes on, someone can continue. Most of what I see (like the
list above) I would classify as poor system administration. The last has
nothing to do with how well RedHat puts together and patches their system.
So I can understand them being less than willing to have RHEL hacked due
to that. However, to think that you can force one to maintain his system
well is utopia. So, even though I understand their reasons, I am sceptical
they will find panacea.
Valeri
++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247
++++++++++++++++++++++++++++++++++++++++
> While I do not normally recommend using statically compiled binaries or
> installing programs that are not RPMS, in this case there is no real
> choice, other than breaking your system by upgrading qt ... which I
> would never recommend.
>
> I can not make a "Redistributable" RPM, as Skype is not GPL ... so
> please don't ask :D
>
> But, what you can do is download the Linux "Static" version:
>
> http://www.skype.com/go/getskype-linux-static
>
> You can put it in any directory initially (you will want to save it, I
> personally put all non-RPM installed software in a directory under
> /root/ so that I know what is installed ... Then you need to untar the
> file like this (you need to be root to do this):
>
> ====================================
> COMMANDS
> ====================================
> tar -xvjf skype_static-<version>.tar.bz2
>
> cd skype_static-<version>
>
> mkdir /usr/share/skype
>
> cp -a * /usr/share/skype/
>
> cd /usr/share/skype/
>
> mv skype /usr/bin/
>
> mv skype.conf /etc/dbus-1/system.d/
>
> chown <your-username>.<your-group> skype.desktop
>
> mv skype.desktop ~<your-username>/Desktop
>
> ====================================
> END COMMANDS
> ====================================
>
> You should now see skype on your desktop, and you can right click the
> launcher and change the icon (pictures in /usr/share/skype/icons) now.
>
> Thanks,
> Johnny Hughes
>
Thanks Johnny,
I'll try installing skype the way you suggest - and thanks to others
who've sent helpful replies. One question though - don't want to appear
stupid, but what exactly is qt - I don't think it's the kernel (is it)
but it's obviously a major part of the OS? By the way, are these
deficiencies resolved in CentOS 5, which I have on my laptop (CentOS 4.4
is on my PC)?
Actually, I've just tried that and the launcher's now on my desktop - but how do I launch skype? When I (right) click on it nothing happens or try to launch from the command line, I get these errors:
skype: error while loading shared libraries: libsigc-2.0.so.0: cannot open shared object file: No such file or directory
Again thanks,
Andy
> _______________________________________________
> CentOS mailing list
> CentOS(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos
good morning jtj.
thank you for replying.
On 07/21/16 06:56, Jose Maria Terry Jimenez wrote:
> El 21/7/16 a las 8:53, geo.inbox.ignore escribió:
>
>> greetings to all.
>>
>> centos = 6.8 current
>> system = toshiba l455d-s5976 laptop
>>
>> a new problem has developed after 1st updating of 6.8.
>>
>> regular user is not able to open kde desktop, can open
>> gnome desktop.
>>
>> root user can open either kde or gnome desktop.
>>
>> as a user, when i try to open kde, after entering password,
>> screen goes to a solid blue, then shows a quick full screen
>> view of command line text, too quick to read, then screen
>> changes back to login prompt.
>>
>> logged in as root, i created a second user, still have same
>> results as above.
>>
>> searching thru 2+ years of local archives revealed nothing,
>> nor does web searching.
>>
>> any advise, recommendation, suggestion appreciated.
>>
>> tia.
>>
> Hello
>
> If it works for root and not for users, it seems a permissions problem
>
> I'd try:
>
> chown -R username.username /home/username
>
> Hope it helps
>
--->
first checking was owner and permissions.
from /home, user owns and mod is 'drwx------'. users 'home' has both
'drwx------' and 'drwxrwxr-x' with files of both '-rwx------' and
'-rwxr--r--'.
--
peace out.
-+-
Tired of having your microsoft os hacked?
Change to Linux os, used by microsoft hackers.
-+-
in a world with out fences, who needs gates.
-+-
CentOS GNU/Linux 6.8
tc,hago.
g
.
On 08/01/2012 09:13 AM, Andreas Rogge wrote:
> Am 01.08.2012 09:39, schrieb Paul R. Ganci:
>> anybody have a clue as to why %u is not evaluating to the linux username
>> snichols and is getting treated simply as the string %u?
> You have to use %U instead of %u - this is not a security issue as
> having the wrong UNC path should (and probably will) be caught using ACLs.
Well last night I implemented this change and indeed this fixed the Win
XP problem. The domain users on the client Win XP box can indeed find
their roaming profiles and properly sync them at logon/logoff time.
However when I went to add a domain user to the first Win 7 Professional
box added to the domain, that user only gets a local profile (i.e. a
C:\Users\username instead of C:\Users\username.domainame) despite the
fact the domain user has a roaming profile. I am sure this is a Win 7
client setup issue.
The best I have been able to do is copy a local profile from the Win 7
box for the domain user back to the Samba PDC. I then delete the domain
user's local profile and could get the Win 7 client to read the profile
from the Samba PDC on the domain user's next logon. Basically I can get
the Win 7 client to create a new local profile from the profile found on
the Samba PDC but on logoff the Win 7 client will not sync that profile
with the Samba PDC and on subsequent logons only uses the local stored
profile on the Win 7 box. It is like the Win 7 client policy is to use
local profiles only and it uses the Samba PDC profile only as a default
if the local profile doesn't exist. There is no subsequent profile
synchronization at logon/logoff after the Win 7 local profile gets created.
Any suggestions to registry/policy settings to get roaming profiles to
act as roaming profiles on a Win 7 Professional SP 1 box? I thought I
ask here first as I am already on this list. Admittedly this might
better belong on a Samba forum but I am guessing somebody out there has
already run into this issue. Everything on the web says this should work
but alas...
--
Paul (ganci(a)nurdog.com)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
About a week ago I was forced to migrate my main (production) email server from RH9 to
Centos4.1. The installation has dovecot-0.99.11 + postfix-2.1.5 and >600 mbox accessed email
accounts.
Number 1. Some users accessing thru squirremail (installed in my webserver) can read their
INBOX at /var/spool/mail directory but when trying to delete a message they receive the
following error message from squirrelmail:
ERROR: Could not complete request.
Consulta: COPY 1279 "mail/Trash"
Reason Given: Internal error occured. Error report written to server log. [2005-09-16 15:08:04]
and the error logged is the following:
Sep 16 15:09:27 mail imap(username): mkdir_parents(/home/username//mail/.imap/Trash) failed:
Permission denied
I never stated that .imap/Trash when configuring dovecot and the strangest thing is that my
account, as most of others, can delete messages moving from /var/spool/mail/my_name to
/home/my_name/mail/Trash
Number 2. Randomly, some users connecting from Mozilla Thunderbird via IMAP get an error
message telling that there has been an error connecting to INBOX. Watching the maillog I
found the following:
Sep 16 13:07:43 mail imap(otheruser): File isn't in mbox format: /var/spool/mail/otheruser
I accessed the user's inbox file with vi and found that there was a "--604" at the beginning
of the file. In other case I found that the file was beginning with a truncated email message.
Trying to "walk on the safer side", I changed the mbox_lock setting from "fcntl" to
"dotlock" in the /etc/dovecot.conf file.
Any suggestions and comments about his will be highly appreciated. Forgive me about my
English, it is not my native lanaguage.
Regards,
- --
Francisco Neira B.
Administrador de Red
Defensoria del Pueblo
Lima, Peru, -05:00 UTC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDKyxz6PLP4IwWB7QRAiMKAJ482XebJMAE7WReJ+z/5DtIsqOgXACdFBx9
VhoveuSay6KBFcaNNinXa+A=
=XUV0
-----END PGP SIGNATURE-----