RE: Need a README to explain items in download directory
From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Chris Brennan On 9/3/2011 7:12 PM, Adam Vande More wrote: On Sat, Sep 3, 2011 at 6:00 PM, Craig Rodrigues rodr...@crodrigues.org mailto:rodr...@crodrigues.org wrote: For this line: (1) FreeBSD-8.2-RELEASE-i386-bootonly.iso - Requires an Internet Connection Does this mean that this ISO has the minimal stuff to boot, and then do an install by downloading packages over the Internet? I really don't know, that's why I'm asking. :) What this should have said was that it is a *boot-to-installer* only ISO image, designed to be burned to optical media. A *network* connection is required (LAN/WAN depending on where you will be installing from) *or* you will have to provide a 'local source[1]' for the install to pull BASE packages from. [1] Local source can be an NFS mounted partition, local hard-drive with the base packages, etc... where-ever the BASE install files are located. While such wording may be helpful to a new user over completely absent directions, it's technically flawed. You don't need an internet connection, but rather a network connection or some other form of installation media. You are correct Adam. I was a little too basic. If such a README is to be implemented, I could find myself writing some correct descriptions ... perhaps a pr is in order? Honestly, the person who needs to read that README file isn't the person who is going to care about nitpicky details on exactly what each file is. He just wants to know which one will get him a FreeBSD system without a massive headache. A better README might look like: = FreeBSD 8.2-RELEASE Images FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz - Installer and full OS, DVD, Best Choice for Beginners FreeBSD-8.2-RELEASE-i386-disc1.iso- Installer and base OS, CD, For all people without DVD drives FreeBSD-8.2-RELEASE-i386-memstick.img - Installer and base OS, USB Memory Sticks, Advanced users FreeBSD-8.2-RELEASE-i386-bootonly.iso- Installer only, CD, For Advanced users FreeBSD-8.2-RELEASE-i386-livefs.iso - Live file system, for repairs, for Advanced users For more information, consult the FreeBSD Handbook: http://www.freebsd.org/doc/handbook/install-diff-media.html = Anybody downloading the Bootonly image should already know what they're getting into. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkg_update
Kris Kennaway wrote: On Wed, Feb 14, 2001 at 03:10:14PM +, Paul Richards wrote: Leif Neland wrote: The problem is that 'make install' in a port doesn't check dependencies properly, whereas pkg_install does. Is this really true? There are even bsd.port.mk targets you can use to obtain the list of dependencies. I've never had trouble with my ports dependancies. Heck, one of the first things I do when installing on a new desktop machine is install the Gimp port, since that will get the GTK libraries and a huge pile of graphics libraries. Usually I install apsfilter too, even if there isn't a printer attached to the system, simply because that get almost all of the common text processing utilites. -- _ __ ___ ___ __ / \/ \ | ||_ _|| _ \|___| | Jason Andresen -- [EMAIL PROTECTED] / /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those /_/\_\|_| |_| |_|\_\|___| | of the Mitre Corporation. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proper permissons on /var/mail
Garrett Wollman wrote:
On Thu, 16 Nov 2000 15:18:09 +, void [EMAIL PROTECTED] said:
I have a similar problem -- every time I make world, perms on /var/mail
get set to 775. Mutt considers my mailbox read-only until I change it
to 1777.
It is misconfigured (or perhaps just broken). 1777 mode for /var/mail
is insecure, but was necessary in the mists of ancient past, before
UNIX learned to do file locking. Unless your mail spool is shared
over NFS (don't do that), locking is reliable and .lock files should
never be used or relied upon.
Not the FreeBSD's file locking works anyway.
Here's the results from a test of the below program:
escaflowne/p6 (81 ~/bin/src): uname -a
FreeBSD escaflowne.el.hazard 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Sat
Oct 14 18:59:16 EDT 2000
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ESCAFLOWNE i386
escaflowne/p6 (82 ~/bin/src): ./testflock
flock(2) is implemented, but not functional.
And another test:
%kenshin (1 ~): uname -a
IRIX kenshin 6.5 01221642 IP20
%kenshin (2 ~): ./testflock
flock(2) is fully functional.
I hope I'm doing something wrong here, and that flock really does work
on FreeBSD.
#include sys/file.h
#include sys/wait.h
#include sys/types.h
#include stdlib.h
#include unistd.h
#include strings.h
#define TMPFILENAME "/tmp/testflock.out"
#define MESSLEN 8
#define CHILDSTR "Child \n"
#define PARENTSTR "Parent\n"
int main( int argc, char** argv)
{
char message[MESSLEN];
int pid;
int fd;
int foo;
fd = open(TMPFILENAME, O_WRONLY | O_CREAT, 0644);
pid = fork();
if ( pid == 0 )
{
strcpy(message, CHILDSTR);
sleep(1);
}
else
strcpy(message, PARENTSTR);
flock(fd, LOCK_EX);
lseek(fd, 0, SEEK_END);
write(fd, message, MESSLEN - 1);
sleep(2);
lseek(fd, 0, SEEK_END);
write(fd, message, MESSLEN - 1);
flock(fd, LOCK_UN);
close(fd);
if ( pid != 0 )
{
wait(foo);
/* Test the file, see if flock works */
fd = open(TMPFILENAME, O_RDONLY);
read(fd, (void*)message, MESSLEN - 1); /* Discard first
*/
read(fd, (void*)message, MESSLEN - 1);
if (! strcmp(message, CHILDSTR))
printf("flock(2) is implemented, but not
functional.\n");
else
printf("flock(2) is fully functional.\n");
close(fd);
}
return 0;
}
--
_ __ ___ ___ __
/ \/ \ | ||_ _|| _ \|___| | Jason Andresen -- [EMAIL PROTECTED]
/ /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those
/_/\_\|_| |_| |_|\_\|___| | of the Mitre Corporation.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
