Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Getting started with fixing bugs for Linux Post 302998470 by sreyan32 on Friday 2nd of June 2017 09:55:26 AM
Old 06-02-2017
Bug Getting started with fixing bugs for Linux

Okay I want to try my luck at fixing bugs for the Fedora OS, but I guess this question deals with any Linux distro or any open source OS for that matter.

I want to know how I can start fixing bugs on the OS level. For example the particular bug that I want to target is this logout bug

I mean how do I start with debugging something like this. These may involve OS modules that are already running in the OS, I can get the source, but how do I deploy and test it ?

MOST IMPORTANTLY-:
Can it be done in a VM like VirtualBox or KVM ?
Maybe I can test my "patched" OS there ?

Not sure about how approach this problem. Any of you who does Linux OS bug fixing could really help me out.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Is it a bugs for find command? :(

Hi! When i am trying to use find command to seacrh files in current directory, it help me to search for it sub-directory also. Is there anyway to avoid it? I am using unix operating system. My friend told me that only linux did handle this, is it true? (4 Replies)
Discussion started by: AkumaTay
4 Replies

2. UNIX for Dummies Questions & Answers

Just started linux any advice??

well i just got into this and really dont know anything so if anyone has any reccomendations like books/sites/forums/or just general advice or if anyone wants to help me get started i would really appreciate it thank you very much (6 Replies)
Discussion started by: Necrons
6 Replies

3. Solaris

Bugs with clock()

Hi there!!! Need your help in solving some tricky problems. Since clock() as such is buggy on SUN OS 5 we have started using gettimeofday() in our RTOS applications based on Solaris 9. The problems we actually encountered previously were - the applications kind of freeze/hang eternally on... (1 Reply)
Discussion started by: smanu
1 Replies

4. Linux

fixing with sed

I am trying to replace the value of $f3 but its not working . I don't know what I am missing here . cat dim_copy.20080516.sql | grep -i "create view" | grep -v OPSDM002 | while read f1 f2 f3 f4 f5 f6 f7 f8 f9 do echo " $f3 " sed -e... (13 Replies)
Discussion started by: capri_drm
13 Replies

5. UNIX for Beginners Questions & Answers

Bugs in my new Ubuntu installation

I recently bought a new HP Spectre x360 laptop and installed Linux (Ubuntu 16.04 LTS 64 bit) for the first time. I am seeing various bugs. I don't know if the problems are due to: (a) Hardware problems with the new laptop. (b) Software issues, i.e. Ubuntu not working with the other... (7 Replies)
Discussion started by: twelth_hour
7 Replies

6. Red Hat

What are Linux configuration changes required after a cloned VM Server is started?

Dear Expert Users, VMware Admin Tool is used to create a "clone" of an existing VM RHEL Server. Now, I have a Project where a cloned VM Server image is started for run . Please share what are all configuration changes required to ensure this runs fine ? I will be grateful for quick and... (2 Replies)
Discussion started by: schandrakar1
2 Replies
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)
All times are GMT -4. The time now is 03:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy