That depends on the file system you're running on. The Ext2,Mimix,Ext filesystems on 32bit platform can store files up to 2Gb. On 64bit platforms (Alpha, UltraSparcs) Jakub Jelinek has provided patch to allow files greater that 2Gb which should be in 2.2.
Function bar(). Stack. Automatic variable (a) allocated on stack. Variable (b) points to carefully crafted overflow data. Function bar() does not check that (b) will overflow (a). Call function foo() with (a) and (b) parameters. Return address to bar() on stack. foo() writes data from (b) into (a) but (a) is too small. foo() does no bounds checking -- it's a fast library function and (correctly) expects good data. Overflow (a), which is on the stack with bar()'s return address. Return address to bar() is now bogus. Carefully crafted overflow causes 'return' to end up someplace fun, including, possibly, it's own code which is part of the bogus data we just filled the stack with. Maybe something like a system('/bin/bash') call...
Check out these sites:
Try :
dig . @rs.internic.net > named.cache
dig . @198.41.0.6 > named.cache
From ln(1)
A hardlink to a file is indistinguishable from original file (for ex. it has
the same file permittions/ownership as the original file). This permits
multiple copies for a file, whithout using diskspace for multiple copies
for a file. Removing the file will not remove contents of a file until
removal of the last name of a file. Hard links may refer only to existing
file.
A symbolic link (also known as soft link) contains only the name of the file to which it is linked, and should be thought as of inderection, instead of a copy. This inderection is accomplished automatically by the system. A symbolic link permits multiple filenames for single file or directory even across different filesystems. The owner, group, permittions, modification time etc. of sym. link are taken from the directory,in which it resides. Sym. links may refer to non-existent files as well.
Here's a short comparision of sym. and hardlinks done by pointing to its advantages and disatvantages:
Hard Link
Soft Link
Try ``make bzImage'' instead.
tar files?
This question could be easily answered by just looking over man page for tar(1), but since it gets frequently asked on the list anyway, here it goes.
Basic syntaxis:
to create tar file: tar -cf filename.tar file1
file2to create tar.gz file: tar -cfz filename.tar.gz file1
file2find ... -type f ... | tar -cf
filename.tar -T -
You can use screens. Run screen and run your command then create
another screen using ^ac keys. Here write screen -d . This will
dettach the screen. you can now log out. The command will still be running.
When you want to get the control of the command back, just type screen -rand there you are.
Another way is to use nohup(1) utility.
Another way to do it is to use C code like:
close(0);
close(1);
close(2);
chdir("/");
open("lofile",O_WRONLY);
dup(0);
dup(0);
execv("yourprogram",NULL);
If you are using bash, you can put
export IGNOREEOF=100
from bash(1)
IGNOREEOF
Controls the action of the shell on receipt of an EOF character as the sole input. If set, the value is the number of consecutive EOF characters typed as the first characters on an input line before bash exits. If the variable exists but does not have a numeric value, or has no value, the default value is 10. If it does not exist, EOF signifies the end of input to the shell. This is only in effect for interactive shells.
this means if you hit Ctrl-D over 100 times in succession it will
log you out.:-)
There are generally two methods of locking files:
fcntl()can lock a specific region of a file, so other processes can continue to access other regions of the file.
Your files are probably having readonly attributes, or your filesystem might be corrupted. (or just mounted read-only, you know what to do here, right?:))
First, run
fsck -fon your filesystem. Then try using
chattr -ion both files and directory, which these files reside in. If your files are having immutable attribute set, even root can not delete nor modify them. Use somehing like
chattr -acidsu [file] ; rm [file]to fix that.
Assuming your new drive is /dev/hda1:
This question actually should go to UUCP-HOWTO, instead of this FAQ, but
since it's been asked for several times, and not only linux-admin mailing
list, I decided to put it here. All the files are to be located in uucp
configuration directory. ( /etc/uucp or
/usr/lib/uucp/taylor_config).
---/cut here/---
# This is an example of config, the main configuration file for Taylor
# UUCP. To use it, you must compile the package with
# HAVE_TAYLOR_CONFIG set to 1 in policy.h (that is the default), copy
# this file to newconfigdir as set in Makefile.in (the default is
# /usr/local/conf/uucp), and edit it as appropriate for your system.
# You need not use this file at all; all the important commands have
# defaults which will be used if this file can not be found.
# Everything after a '#' character is a comment. To uncomment any of
# the sample lines below, just delete the '#'.
# You must choose a UUCP name. If your system is going to be
# communicating with other systems outside your organization, the name
# must be unique in the entire world. The usual method is to pick a
# name, and then search the UUCP maps (in the newsgroup
# comp.mail.maps) to see whether it has already been taken. See the
# README posting in comp.mail.maps for more information. If the name
# of your system as returned by "uuname -n" or "hostname" is the name
# you want to use, you do not need to set the name in this file.
# Otherwise uncomment and edit the following line.
nodename your_node_name # The UUCP name of this system
# The default spool directory is set in policy.h (the default is
# /usr/spool/uucp). All UUCP jobs and status information are kept in
# the spool directory. If you wish to change it, use the spool
# command.
spool /usr/spool/uucp # The UUCP spool directory
# The default public directory is set in policy.h (the default is
# /usr/spool/uucppublic). Remote systems may refer to a file in this
# directory using "~/FILE". By default, the public directory is the
# only directory which remote systems may transfer files in and out
# of. If you wish to change the public directory, use the pubdir
# command.
pubdir /usr/spool/uucppublic # The UUCP public directory
# The names of the UUCP log files are set in policy.h. The default
# names depend on the logging option you have chosen. If
# HAVE_TAYLOR_LOGGING is set in policy.h, the default log file name is
# /usr/spool/uucp/Log, the default statistics file name is
# /usr/spool/uucp/Stats, and the default debugging file name is
# /usr/spool/uucp/Debug. These file names may be set by the following
# commands.
logfile /usr/spool/uucp/Log # The UUCP log file
statfile /usr/spool/uucp/Stats # The UUCP statistics file
debugfile /usr/spool/uucp/Debug # The UUCP debugging file
# uuxqt is the program which executes UUCP requests from other
# systems. Normally one is started after each run of uucico, the
# communications daemon. You may control the maximum number of uuxqt
# programs run at the same time with the following command. The
# default is to have no maximum.
max-uuxqts 1 # The maximum number of uuxqts
# There are several files that uucico uses. By default it looks for
# them in newconfigdir, as set in Makefile.in. You may name one or
# more of each type of file using the following commands.
# sysfile FILES # Default "sys"
# portfile FILES # Default "port"
# dialfile FILES # Default "dial"
# dialcodefile FILES # Default "dialcode"
# callfile FILES # Default "call"
# passwdfile FILES # Default "passwd"
# The ``timetable'' command may be used to declare timetables. These
# may then be referred to in time strings in the other files.
# timetable Day Wk0905-1655
# The ``unknown'' command is followed by any command which may appear
# in a sys file. These commands are taken together to describe what
# is permitted to a system which is not listed in any sys file. If
# the ``unknown'' command, then unknown systems are not permitted to
# connect.
# Here is an example which permits unknown systems to download files
# from /usr/spool/anonymous, and to upload them to
# /usr/spool/anonymous/upload.
#
# No commands may be executed (the list of permitted commands is empty)
# unknown commands
# The public directory is /usr/spool/anonymous
# unknown pubdir /usr/spool/anonymous
# Only files in the public directory may be sent; users may not download
# files from the upload directory
# unknown remote-send ~ !~/upload
# May only upload files into /usr/spool/anonymous/upload
# unknown remote-receive ~/upload
---/cut here/---
---/cut here/---
# This is an example of call, the call out password file for Taylor
# UUCP. To use it, you must compile the package with
# HAVE_TAYLOR_CONFIG set to 1 in policy.h (that is the default), copy
# this file to newconfigdir as set in Makefile.in (the default is
# /usr/local/conf/uucp), and edit it as appropriate for your system.
# Everything after a '#' character is a comment. To uncomment any of
# the sample lines below, just delete the '#'.
# This file is used when the ``call-login'' or ``call-password''
# commands are used in the sys file with a "*" argument (e.g.,
# ``call-login *''). The system name is looked up in this file, and
# the login name and password are used.
# The point of this is that the sys file may then be publically
# readable, while still concealing the login names and passwords used
# to connect to the remote system.
# The format is just system-name login-name password.
#uunet Uairs foobar
---/cut here/---
---/cut here/---
# This is an example of dial, the dialer configuration file for Taylor
# UUCP. To use it, you must compile the package with
# HAVE_TAYLOR_CONFIG set to 1 in policy.h (that is the default), copy
# this file to newconfigdir as set in Makefile.in (the default is
# /usr/local/conf/uucp), and edit it as appropriate for your system.
# Everything after a '#' character is a comment. To uncomment any of
# the sample lines below, just delete the '#'.
# All dialers named in the port (or sys) file must be described in the
# dial file. It is also possible to describe a dialer directly in the
# port (or sys) file.
# This is a typical Hayes modem definition.
dialer hayes
# The chat script used to dial the phone.
# This means:
# 1) expect nothing (i.e., continue with step 2)
# 2) send "ATZ", then a carriage return, then sleep for 1 to 2
# seconds. The \c means to not send a final carriage return.
# 3) wait until the modem echoes "OK"
# 4) send "ATDT", then the telephone number (after translating any
# dialcodes).
# 5) wait until the modem echoes "CONNECT"
chat "" ATZ\r\d\c OK ATDP\T CONNECT
# If we get "BUSY" or "NO CARRIER" during the dial chat script we
# abort the dial immediately.
chat-fail BUSY
chat-fail NO\sCARRIER
# When the call is over, we make sure we hangup the modem.
complete \d\d+++\d\dATH\r\c
abort \d\d+++\d\dATH\r\c
---/cut here/---
---/cut here/---
# This is an example of dialcode, the dialcode configuration file for
# Taylor UUCP. To use it, you must compile the package with
# HAVE_TAYLOR_CONFIG set to 1 in policy.h (that is the default), copy
# this file to newconfigdir as set in Makefile.in (the default is
# /usr/local/conf/uucp), and edit it as appropriate for your system.
# Everything after a '#' character is a comment. To uncomment any of
# the sample lines below, just delete the '#'.
# The dialcode file is used if \T is used in the dialer chat script
# and the telephone number begins with alphabetic characters. The
# alphabetic characters are looked up and translated in dialcode.
# Here are a couple of sample dialcodes.
MA 617
CA 415
# For example, if the phone number (from the sys file) is MA7389449,
# then the string sent to the modem will be 6177389449.
---/cut here/---
---/cut here/---
# This is an example of passwd, the call in password file for Taylor
# UUCP. To use it, you must compile the package with
# HAVE_TAYLOR_CONFIG set to 1 in policy.h (that is the default), copy
# this file to newconfigdir as set in Makefile.in (the default is
# /usr/local/conf/uucp), and edit it as appropriate for your system.
# Everything after a '#' character is a comment. To uncomment any of
# the sample lines below, just delete the '#'.
# This file is used when uucico is invoked with the -l or -e argument.
# uucico will then prompt for a login name and password. The login
# name is looked up in this file to check the password (the system
# password file, /etc/passwd, is not checked). This permits uucico to
# completely take over a port, allowing UUCP access to remote systems
# but not permitting remote users to actually log in to the system.
# The format is just login-name password.
Uairs foobar
---/cut here/---
---/cut here/---
# This is an example of port, the port configuration file for Taylor
# UUCP. To use it, you must compile the package with
# HAVE_TAYLOR_CONFIG set to 1 in policy.h (that is the default), copy
# this file to newconfigdir as set in Makefile.in (the default is
# /usr/local/conf/uucp), and edit it as appropriate for your system.
# Everything after a '#' character is a comment. To uncomment any of
# the sample lines below, just delete the '#'.
# All ports named in the sys file must be described in a port file.
# It is also possible to describe the port directly in the sys file.
# Commands that appears before the first ``port'' command are defaults
# for all ports that appear later in the file. In this case all ports
# will default to being modems (other possible types are direct, tcp
# and tli).
type modem
# Now we describe two ports.
# This is the name of the port. This name may be used in the sys file
# to select the port, or the sys file may just specify a baud rate in
# which case the first matching unlocked port will be used.
port port1
# This is the device name to open to dial out.
device /dev/ttyS0
# This is the dialer to use, as described in the dialer file.
dialer hayes
# This is the baud rate to dial out at.
speed 2400
# Here is a second port. This is like the first, except that it uses
# a different device. It also permits a range of speeds, which is
# mainly useful if the system specifies a particular baud rate.
port port2
device /dev/ttyS1
dialer hayes
speed-range 2400 9600
---/cut here/---
---/cut here/---
---/cut here/---
# This is an example of a sys file, the file(s) which describe remote
# systems for Taylor UUCP. To use it, you must compile the package
# with HAVE_TAYLOR_CONFIG set to 1 in policy.h (that is the default),
# copy this file to newconfigdir as set in Makefile.in (the default is
# /usr/local/conf/uucp), and edit it as appropriate for your system.
# If you do not use the ``unknown'' command in the config file, then
# each system that you communicate with must be listed in a sys file.
# Everything after a '#' character is a comment. To uncomment any of
# the sample lines below, just delete the '#'.
# This is a sample sys file that might be used in a leaf system. A
# leaf system is one that only contacts one other system. sys2
# provides another example.
# The name of the remote system that we call. (usually your ISP).
system foo
# The login name and password are kept in the callout password file
# (by default this is the file "call" in newconfigdir).
called-login *
called-password *
# We can send anything at any time.
time any
# During the day we only accept grade 'Z' or above; at other times
# (not mentioned here) we accept all grades. uunet queues up news
# at grade 'd', which is lower than 'Z'.
call-timegrade Z Wk0755-2305,Su1655-2305
# The phone number to call.
phone 123456
# uunet tends to be slow, so we increase the timeout
chat-timeout 120
# The port we use to dial out.
port serial
# Increase the timeout and the number of retries.
protocol-parameter g timeout 20
protocol-parameter g retries 10
# this will be able to dialup into yoru box
system test
commands rmail
called-login uutest
---/cut here/---
Hope it helps. For more info there's a uucp-howto, and a doc file at ftp://ftp.gnu.org/gnu/uucp/ available.
free
bash$ free
total used free shared buffers cached
Mem: 14800 14196 604 14920 588 3488
-/+ buffers/cache: 10120 4680
Swap: 61452 7808 53644
if in
Swap:
Device Boot Begin Start End Blocks Id System
/dev/hda1 1 1 192 1542208+ 83 Linux native
/dev/hda2 193 193 460 2152710 83 Linux native
/dev/hda3 461 461 1016 4466070 83 Linux native
/dev/hda4 1017 1017 1024 64260 82 Linux swap
mkswap [ -c ] device [size-in-blocks]
mkswap -c /dev/hda4 64260
swapon /dev/hda4
/dev/hda4 swap swap defaults 0 0
man foo | col -b > foo.txt
man -t foo > foo.ps
This means that the server, to which the domain is delegated, doesn't consider itself to be authoritative for the domain, or speaking in simple words it just isn't proper namesever for this domain.
This is basically isn't your problem, but the problem of domain owner, and there are very few things you could do about it. (the only thing is properly to contain domain maintainer and ask him to fix this bug).