Google Chrome OS is an open source Google project and will be available to use at no cost in 2010, initially be targeted at netbooks. In 2009, Google will open-source Chrome OS code.
The software architecture is Google Chrome running within a new window manager on top of the Linux kernel. ... (20 Replies)
I know that Google Chrome came out with the Android under a Unix based system, but did it come out yet for Windows Mobile? I have Windows Mobile 6 on my device. (0 Replies)
Discussion started by: Anna Hussie
0 Replies
5. Post Here to Contact Site Administrators and Moderators
For some reason Google Chrome sees unix.com as dangerous and has start to block it. I need to select advanced and continue on own risk.
Can you make an effort to remove unix.com form the list of dangerous site from Google.
IE has not this problem. (5 Replies)
Hi All,
My chrome browser was working correctly on my Debian Lenny 5 PC..Today i downloaded the version from google and tried to install the deb from command line as follows:
dpkg -i <latest-chrome-package>
The installation failed but now my existing old chrome browser is not starting.
... (2 Replies)
Hi Dears
i use UBUNTU 16.04 LTS. I download google chrome .deb package and install it but not work. i remove and purge it and install again but not work. i remove .confi too.
what kind of details you need?
Can help me? (7 Replies)
Discussion started by: alii
7 Replies
LEARN ABOUT CENTOS
ksc
KSC(1) User Commands KSC(1)NAME
ksc - Linux kernel module source checker
SYNOPSIS
ksc [ -d | --directory ] DIRECTORY
ksc [ -k | --ko ] FILE
OPTIONS
KSC accepts command-line arguments, and has both a long and short form usage. You can use either style or combine them to specify
options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules, it
checks for the specific architecture for which the binary was built.
Valid RHEL whitelist releases are rhel6.0, rhel6.1, rhel6.2, rhel6.3, rhel6.4
-h, --help
show this help message and exit
-c CONFIG, --config=CONFIG
path to the local ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from
/etc/ksc.conf
-d DIRECTORY, --directory=DIRECTORY
path to the directory
-i, --internal
to create text files to be used internally.
-k KO, --ko=KO
path to the ko file. You should either use -d or -k to run the KSC tool, but not both. If both -d and -k option is used at the
same time then only -d is used and the -k option is discarded.
-n RELEASENAME, --name=RELEASENAME
Red Hat release against which the bug is to be filed. Default value is 6.5
-p PREVIOUS, --previous=PREVIOUS
path to the previous resultset file and submit it as a bug to Red Hat Bugzilla.
-r RELEASE, --release=RELEASE
RHEL whitelist release used for comparison
-s, --submit
Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com). The credentials need to be in the /etc/ksc.conf file. The
tool will prompt for bugzilla password.
The configuration file looks like below:
[bugzilla]
user=user@redhat.com
partner=partner-name
partnergroup=partner-group
server=https://bugzilla.redhat.com/xmlrpc.cgi
-v, --version
Prints KSC version number
ksc - Version 0.9.11 Feb 2014 KSC(1)