Sponsored Content
Full Discussion: Creating a bootable CD
Operating Systems BSD Creating a bootable CD Post 302072688 by avatar1349 on Friday 5th of May 2006 06:46:07 AM
Old 05-05-2006
first of all do a make LINT in /usr/src/sys/i386/conf
In LINT you'll find all the possible vars for your kernel
put in /etc/make.conf KERNCONF="YOURKERNELNAME"

then in /usr/src make buildkernel && make installkernel

avatar1349
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Bootable CD

Hi, I need to be able to make a back bootable CD for Solaris 7 + software on the system. As stated the CD needs to be a bootable one, I know it will more then likely have to be more then 1 CD and I don't mind. What would be a good program to do this? Also the best way to go about doing it.... (1 Reply)
Discussion started by: merlin
1 Replies

2. SuSE

CD Bootable OS

Hi, I want to create a CD that is bootable containing a working Linux OS ie OS runs from CD and not harddrive. Will probably install Linux to a 650GB partition , including all the bits I need. How would I then use this partition to create a working CD? Ideas and Web sites with info very... (5 Replies)
Discussion started by: markdr011
5 Replies

3. Filesystems, Disks and Memory

Make non-bootable scsi drive, bootable

In our HP/Unix system, our master scsi drive was bootable and our mirrored drive was non-bootable. Are any of these alternatives possible: 1) Make the non-bootable scsi drive bootable? How? 2) Create a bootable scsi drive, then copy the mirrored data to the newly created scsi drive? I seek... (1 Reply)
Discussion started by: bfisk
1 Replies

4. HP-UX

Creating a bootable disk in 9.10

I am trying to copy a HP-UX disk. Both the OS and H/W are quite old HP-UX hpeval3 B.09.10 A 9000/382 080009789a46 I have a 1.5Gb disk and a new 2Gb disk. I have been using the following method to create the copy, which must be a bootable disk. #mediainit /dev/rdsk/cEd1s0 (2Gb disk) cEd0s0... (9 Replies)
Discussion started by: malcqv
9 Replies

5. Red Hat

Looking for help with creating bootable USB key

I am currently trying to create a bootable USB key that I can use to boot a couple different X86 single slot processors. Creating a basic key is as easy as can be but I am looking to customize this boot image to meet two important criteria: 1. The system must boot in text only mode as my only... (4 Replies)
Discussion started by: kingfish1760
4 Replies

6. Linux

Creating a bootable dvd/cd disk

Hi all, thanks for so many helps in many problems! Can anyone guide, how to create a bootable cd/dvd from downloaded iso images of CentOS 5? I have collected all the iso in a dvd but it is not booting the system. Any response will be appreciable... (2 Replies)
Discussion started by: naw_deepak
2 Replies

7. Shell Programming and Scripting

help needed with creating challenging bash script with creating directories

Hi, Can someone help me with creating a bash shell script. I need to create a script that gets a positive number n as an argument. The script must create n directories in the current directory with names like map_1, map_2 etcetera. Each directory must be contained within its predecessor. So... (7 Replies)
Discussion started by: I-1
7 Replies

8. Homework & Coursework Questions

Creating a .profile, displaying system variables, and creating an alias

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: Here is what I am supposed to do, word for word from my assignment page: 1. Create/modify and print a... (2 Replies)
Discussion started by: Jagst3r21
2 Replies

9. Red Hat

Trouble creating RHEL 6.5 bootable image with custom kickstart file

Hi everyone, I have a custom kickstart file from a software vendor and I'm trying to package that with a RHEL 6.5 and then attach it to a VM and install RHEL with the settings in the kickstarter file. I'm doing this from a windows PC using an app called InfraRecorder. I've extracted the... (0 Replies)
Discussion started by: 911Eric
0 Replies
LINT(1) 						      General Commands Manual							   LINT(1)

NAME
lint - a C program verifier SYNOPSIS
lint [ -abchnpuvx ] file ... DESCRIPTION
Lint attempts to detect features of the C program files which are likely to be bugs, or non-portable, or wasteful. It also checks the type usage of the program more strictly than the compilers. Among the things which are currently found are unreachable statements, loops not entered at the top, automatic variables declared and not used, and logical expressions whose value is constant. Moreover, the usage of functions is checked to find functions which return values in some places and not in others, functions called with varying numbers of argu- ments, and functions whose values are not used. By default, it is assumed that all the files are to be loaded together; they are checked for mutual compatibility. Function definitions for certain libraries are available to lint; these libraries are referred to by a conventional name, such as `-lm', in the style of ld(1). Any number of the options in the following list may be used. The -D, -U, and -I options of cc(1) are also recognized as separate argu- ments. p Attempt to check portability to the IBM and GCOS dialects of C. h Apply a number of heuristic tests to attempt to intuit bugs, improve style, and reduce waste. b Report break statements that cannot be reached. (This is not the default because, unfortunately, most lex and many yacc outputs produce dozens of such comments.) v Suppress complaints about unused arguments in functions. x Report variables referred to by extern declarations, but never used. a Report assignments of long values to int variables. c Complain about casts which have questionable portability. u Do not complain about functions and variables used and not defined, or defined and not used (this is suitable for running lint on a subset of files out of a larger program). n Do not check compatibility against the standard library. Exit(2) and other functions which do not return are not understood; this causes various lies. Certain conventional comments in the C source will change the behavior of lint: /*NOTREACHED*/ at appropriate points stops comments about unreachable code. /*VARARGSn*/ suppresses the usual checking for variable numbers of arguments in the following function declaration. The data types of the first n arguments are checked; a missing n is taken to be 0. /*NOSTRICT*/ shuts off strict type checking in the next expression. /*ARGSUSED*/ turns on the -v option for the next function. /*LINTLIBRARY*/ at the beginning of a file shuts off complaints about unused functions in this file. FILES
/usr/lib/lint[12] programs /usr/lib/llib-lc declarations for standard functions /usr/lib/llib-port declarations for portable functions SEE ALSO
cc(1) S. C. Johnson, Lint, a C Program Checker LINT(1)
All times are GMT -4. The time now is 07:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy