).
So my question relates to when I should update my USB stick's /boot
directory.
I'm assuming that the /boot directory should be owned by the kernel and
could be updated by a make installkernel (which is what I do after
building the world but before my reboot into single user to install the
world
On Tue, 6 Jul 2010 17:02:54 -0700 (PDT)
Bill Tillman btillma...@yahoo.com wrote:
Doesn't that seem odd that the default partition size for root
(512M) isn't quite big enough?
It's not that odd: nobody has bothered to update the default partition
sizes in sysinstall for a good few years, I
On Wed, 7 Jul 2010 11:13:21 +0100
Bruce Cran br...@cran.org.uk articulated:
I'd consider that bad advice: the defaults sysinstall chooses are
currently just wrong, and you should indeed be setting / to at least
1GB so you don't run out of space. The 'solution' of deleting
kernel.old or not
On Wed, 7 Jul 2010 07:18:18 -0400
Jerry freebsd.u...@seibercom.net wrote:
I also ran out of space. I decided that a minimum of 2GB was the
safest choice. It would be nice if the authors changed the default
settings in the soon to be released 8.1 version so as to nullify this
phenomena.
I've
On Wed, Jul 7, 2010 at 7:47 AM, Bruce Cran br...@cran.org.uk wrote:
On Wed, 7 Jul 2010 07:18:18 -0400
Jerry freebsd.u...@seibercom.net wrote:
I also ran out of space. I decided that a minimum of 2GB was the
safest choice. It would be nice if the authors changed the default
settings in the
On Tue, Jul 06, 2010 at 05:02:54PM -0700, Bill Tillman wrote:
Thanks guys.
:-)
Doesn't that seem odd that the default partition size for root
(512M) isn't quite big enough?
Things change slowly.
I think only a short while ago the default was 256 MB or even 128 MB.
Should I make the
Jerry McAllister writes:
Things change slowly.
I think only a short while ago the default was 256 MB or even 128
MB.
I haven't checked the logs, but I think it would have been more
than a short while.
Consider:
huff@ du -s /boot/kernel
225008 /boot/kernel
huff@ du -s
Thanks guys.
:-)
Doesn't that seem odd that the default partition size for root
(512M) isn't quite big enough?
Should I make the partition size slightly larger (on future installs)
to eliminate this problem?
Ed
--
I had the same problem and since my drives are
On Fri, 02 Jul 2010 16:28:29 +0100
Arthur Chance free...@qeng-ho.org wrote:
I suspect whoever you were talking to probably has more of a clue
than I do. As a quick data point, I just ran portsnap fetch update
while another process did a df /var; sleep 1 loop and /var
increased by about 30MB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/07/2010 22:29:54, Ed Flecko wrote:
Henrik,
When I FIRST installed 8.0, I did create a separate /home partition.
When I installed the kernel and starting running out of space in / , I
thought O.K...I'll let FreeBSD make the partition sizes IT
On 02.07.2010 09:33, Matthew Seaman wrote:
On 01/07/2010 22:29:54, Ed Flecko wrote:
Henrik,
When I FIRST installed 8.0, I did create a separate /home partition.
When I installed the kernel and starting running out of space in / , I
thought O.K...I'll let FreeBSD make the partition sizes IT
On 2 July 2010 08:33, Matthew Seaman m.sea...@infracaninophile.co.ukwrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/07/2010 22:29:54, Ed Flecko wrote:
Henrik,
When I FIRST installed 8.0, I did create a separate /home partition.
When I installed the kernel and starting running
krad writes:
all i can say is your a brave boy 8) A 1 TB+ / slice would take
ages to fsck.
For ages being less than ten (fifteen ?) minutes on a modern
system with reasonable memory ...
... which should be necessary very rarely. Even on my test
system, time between
On Fri, 02 Jul 2010 08:33:45 +0100
Matthew Seaman m.sea...@infracaninophile.co.uk wrote:
Is it time for me to start advocating one big partition again?
This may not be the consensus view, but I have found that for a quiet
life and general lack of botheration it helps to create *only two*
On Thu, Jul 01, 2010 at 02:29:54PM -0700, Ed Flecko wrote:
Henrik,
When I FIRST installed 8.0, I did create a separate /home partition.
When I installed the kernel and starting running out of space in / , I
thought O.K...I'll let FreeBSD make the partition sizes IT wants to
and see if I have
On 07/02/10 13:13, Bruce Cran wrote:
I have a task on my TODO list to increase the sizes of the partitions in
sysinstall: for example / goes to 1GB, /var to 4GB. I hope to commit
the code in the next couple of weeks.
As a matter of idle curiosity with a bit of education thrown in, why 4GB
for
Arthur Chance writes:
As a matter of idle curiosity with a bit of education thrown in,
why 4GB for /var? The last time I installed a new machine I made
/ 1GB as I'd found out from a previous install that 512MB wasn't
really enough, and then decided to make /var bigger than the
Handbook
On Fri, 02 Jul 2010 15:04:10 +0100
Arthur Chance free...@qeng-ho.org wrote:
As a matter of idle curiosity with a bit of education thrown in, why
4GB for /var? The last time I installed a new machine I made / 1GB as
I'd found out from a previous install that 512MB wasn't really
enough, and
On 07/02/10 15:38, Bruce Cran wrote:
On Fri, 02 Jul 2010 15:04:10 +0100
Arthur Chancefree...@qeng-ho.org wrote:
As a matter of idle curiosity with a bit of education thrown in, why
4GB for /var? The last time I installed a new machine I made / 1GB as
I'd found out from a previous install that
-supfile
# cd /usr/src
# make buildworld
# make buildkernel
# make installkernel
After the make installkernel command, the / partition shows 106%
capacity (and it started as 500M).
Here's my before and after running make installkernel
Before:
Filesystem SizeUsed Avail Capacity Mounted
the following steps:
# csup -4 /etc/stable-supfile
# cd /usr/src
# make buildworld
# make buildkernel
# make installkernel
After the make installkernel command, the / partition shows 106%
capacity (and it started as 500M).
Here's my before and after running make installkernel
Before
Thanks guys.
:-)
Doesn't that seem odd that the default partition size for root
(512M) isn't quite big enough?
Should I make the partition size slightly larger (on future installs)
to eliminate this problem?
Ed
___
freebsd-questions@freebsd.org
Chip Camden sterl...@camdensoftware.com writes:
I've experienced the same thing on amd64 -- the default partition size
for root is too small. Rather than going to the trouble of correcting
it, I just 'rm -r /boot/kernel.old' when it fails and then redo 'make
installkernel', and all seems OK
Chip,
That sounds like a smart thing to do; can you tell me more about how
to do that (or point me to a www resource; I'm happy to read more
about that).
:-)
Ed
___
freebsd-questions@freebsd.org mailing list
running make installkernel on FreeBSD 8.0
Hi folks,
I'm running FreeBSD 8.0, and I'm trying to simple stay current with
all security patches. It's a clean install of FreeBSD 8.0 on a 50G
drive, and I let sysinstall select the default partition configuration
when I did the install.
I've taken
and then redo 'make
installkernel', and all seems OK.
That's a little dangerous, because you're deleting your last known-good
kernel. I'd feel better about recommending just removing the
unnecessary kernel modules (which for a lot of people, is all of them
On Jul 01 12:07, Ed Flecko wrote:
Thanks guys.
:-)
Doesn't that seem odd that the default partition size for root
(512M) isn't quite big enough?
Should I make the partition size slightly larger (on future installs)
to eliminate this problem?
Ed
'rm -r /boot/kernel.old' when it fails and then redo 'make
installkernel', and all seems OK.
That's a little dangerous, because you're deleting your last known-good
kernel. I'd feel better about recommending just removing the
unnecessary kernel modules (which for a lot of people, is all
Chip Camden sterl...@camdensoftware.com writes:
On Jul 01 12:07, Ed Flecko wrote:
Thanks guys.
:-)
Doesn't that seem odd that the default partition size for root
(512M) isn't quite big enough?
Should I make the partition size slightly larger (on future installs)
to eliminate this
A healthy fear, indeed.
For one thing, I'd certainly rather have someone
do rm /boot/kernel.old/*.ko than rm -r /boot/kernel.old.
Being even more selective is an obvious extension...
Why not move the old useless kernel to another drive. Sure if the system
kernel fails and you need the old
Since it would be smart to have at least one known, good kernel, why
not make the / partition maybe 1G?
I know the smaller the / partition, the better the performance (since
it's the first partition of the drive), but I can't imagine a slightly
larger / partition would impact performance that
On 1 July 2010 21:12, Ed Flecko edfle...@gmail.com wrote:
Since it would be smart to have at least one known, good kernel, why
not make the / partition maybe 1G?
I know the smaller the / partition, the better the performance (since
it's the first partition of the drive), but I can't imagine
On Thu, 01 Jul 2010, Lowell Gilbert wrote:
Chip Camden sterl...@camdensoftware.com writes:
On Jul 01 12:07, Ed Flecko wrote:
Thanks guys.
:-)
Doesn't that seem odd that the default partition size for root
(512M) isn't quite big enough?
Should I make the partition size
the install.
I've taken the following steps:
# csup -4 /etc/stable-supfile
# cd /usr/src
# make buildworld
# make buildkernel
# make installkernel
After the make installkernel command, the / partition shows 106%
capacity (and it started as 500M).
Here's my before and after running make
On Thu, Jul 01, 2010 at 12:07:50PM -0700, Ed Flecko wrote:
Thanks guys.
:-)
Doesn't that seem odd that the default partition size for root
(512M) isn't quite big enough?
Should I make the partition size slightly larger (on future installs)
to eliminate this problem?
Many people find
Henrik,
When I FIRST installed 8.0, I did create a separate /home partition.
When I installed the kernel and starting running out of space in / , I
thought O.K...I'll let FreeBSD make the partition sizes IT wants to
and see if I have the same problem, and I did.
Apparently, 512M is just, not,
Henrik Hudson writes:
Or just make one large partition. Not on a server, but I don't
see much reason for using multiple partitions on a laptop.
Multiple partitions still isn't a bad idea if you ever have to
fsck and even on a desktop / laptop I usually mount /tmp as
noexec.
On Jul 01 12:29, Chip Camden wrote:
On Jul 01 12:07, Ed Flecko wrote:
Thanks guys.
:-)
Doesn't that seem odd that the default partition size for root
(512M) isn't quite big enough?
Should I make the partition size slightly larger (on future installs)
to eliminate this
Hello freebsd-questions,
It says that there is no libbsm
--
--
Best regards,
Anton= ;[1]mailto:an...@sng.by
Administrator
Feel free to contact me
via ICQ 363780596
via Skype dobryak47
via phone +375 29 3320987
References
On Wed, 22 Jul 2009 19:11:14 +0300, Anton an...@sng.by wrote:
Hello freebsd-questions,
It says that there is no libbsm
Check that all your sorces are complete and of the same version.
The libbsm is part of openbsm - /usr/src/contrib/openbsm/.
--
Polytropon
From Magdeburg, Germany
Just making sure I'm not brewing a disaster...
Is it 'safe' to install a kernel (i.e. 'make installkernel') on a
system while in multi-user mode?
Thanks!
-Modulok-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
Modulok wrote:
Just making sure I'm not brewing a disaster...
Is it 'safe' to install a kernel (i.e. 'make installkernel') on a
system while in multi-user mode?
Thanks!
-Modulok-
Yes. But you should schedule a reboot shortly afterwards
Modulok wrote:
Just making sure I'm not brewing a disaster...
Is it 'safe' to install a kernel (i.e. 'make installkernel') on a
system while in multi-user mode?
Thanks!
-Modulok-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org
On Wednesday 06 May 2009 22:52:12 Modulok wrote:
Just making sure I'm not brewing a disaster...
Is it 'safe' to install a kernel (i.e. 'make installkernel') on a
system while in multi-user mode?
It's the best and prefered way. Dropping to single user for installkernel has
very little
application
at a time commandiered the
window manager or something. I lost the Gnome Applications Places System
window and it got
replaced with whatever app's menu system was File .. I tried make
installkernel which I guess was
stupid because the other make failed. makeinstallkernel.log
Hello List!
I have the following trouble:
# cat /etc/make.conf | grep PORTS_MODULES
PORTS_MODULES= x11/nvidia-driver emulators/kqemu-kmod
running:
# cd /usr/src
# make buildkernel
# make installkernel
goes fine for installation of kernel and nvidia-driver, but making kqemu-mod
fails
Hello,
I'm having a problem getting make to understand the current working
directory.
For example, I have a directory structure where /usr/src and /usr/obj
are symbolic links to another location. When I type: make
installkernel, make thinks I'm in the directory /mnt/src, instead of
/usr/src
/umounts fine. The
problem is with make installkernel. I cd /usr/src and type:
# make installkernel KERNCONF=FIREWALL
--
Installing kernel
--
cd /usr/obj/mnt/src/sys/FIREWALL
I don't have physical access to the server at the moment to try the
loader prompt but...
I tried
mv /boot/kernel /root/
mv /boot/kernel.old /root/
make installkernel
the folder and its files reappear in /boot but a reboot still shows
the custom config.
I also tried shutting down
Nope
%grep ident /usr/src/sys/amd64/conf/GENERIC
ident GENERIC
and its more than that. After reinstalling the kernel I still have SMP
support.
- Original Message -
From: [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Sent: Sunday, March 12, 2006 11:53 PM
Subject: Re: make
/kernel.
Assuming it's there, what happens if you stop the boot at the loader
prompt and manually load the kernel you want?
-Glenn
- Original Message -
From: [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Sent: Sunday, March 12, 2006 11:53 PM
Subject: Re: make installkernel doesn't
I don't get it. I'm trying to switch from a custom kernel named SERVER to a
generic kernel.
%uname -imrs
FreeBSD 6.0-RELEASE-p4 amd64 SERVER
cd /usr/src
make clean
rm -rf /usr/obj
make buildkernel
make installkernel
reboot
%sysctl kern.ident
kern.ident: SERVER
Why isn't the GENERIC kernel
On Mar 12, 2006, at 8:55 PM, Cstdenis wrote:
I don't get it. I'm trying to switch from a custom kernel named
SERVER to a
generic kernel.
%uname -imrs
FreeBSD 6.0-RELEASE-p4 amd64 SERVER
cd /usr/src
make clean
rm -rf /usr/obj
make buildkernel
make installkernel
reboot
%sysctl kern.ident
]
To: freebsd-questions@freebsd.org
Sent: Sunday, March 12, 2006 9:38 PM
Subject: Re: make installkernel doesn't work?
On Mar 12, 2006, at 8:55 PM, Cstdenis wrote:
I don't get it. I'm trying to switch from a custom kernel named
SERVER to a
generic kernel.
%uname -imrs
FreeBSD 6.0-RELEASE-p4
Maybe you set your ident to something else:
$ grep ident /usr/src/sys/i386/conf/GENERIC
or whatever your arch is.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
A and enter ...
make installkernel KERNCONF=config. for machine A
... the install fails.
From what I can see, the program /usr/bin/install core
dumps with exit status 4. Looking at the man page for
install(1) it seems that there is an issue with
fchflags(2) over NFS.
The questions
--
make installkernel KERNCONF=config. for machine A
... the install fails.
From what I can see, the program /usr/bin/install
core
dumps with exit status 4. Looking at the man page
for
install(1) it seems that there is an issue with
fchflags(2) over NFS.
The questions
In an effort to get the simplest of compiled c++ programs (compiled with g++)
to actually run without a segfault on my box I'm trying to update everything.
So I cvsup'd src-all and ports-all. Then I did:
make -j4 buildworld (which worked)
make -DALWAYS_CHECK MAKE buildkernel (which also
Keyser wrote:
In an effort to get the simplest of compiled c++ programs (compiled with g++)
to actually run without a segfault on my box I'm trying to update everything.
So I cvsup'd src-all and ports-all. Then I did:
make -j4 buildworld (which worked)
make -DALWAYS_CHECK MAKE buildkernel
Cut and pasted from /usr/src/Makefile
- - - CUT - - -
# Make sure we have an up-to-date make(1). Only world and buildworld
# should do this as those are the initial targets used for upgrades.
# The user can define ALWAYS_CHECK_MAKE to have this check performed
# for all targets.
#
- - - CUT - - -
On 6/11/05, Keyser [EMAIL PROTECTED] wrote:
Cut and pasted from /usr/src/Makefile
- - - CUT - - -
# Make sure we have an up-to-date make(1). Only world and buildworld
# should do this as those are the initial targets used for upgrades.
# The user can define ALWAYS_CHECK_MAKE to have this
=== usr.bin/bluetooth
=== usr.bin/bluetooth/bthost
install -s -o root -g wheel -m 555 bthost /usr/bin
install -o root -g wheel -m 444 bthost.1.gz /usr/share/man/man1
=== usr.bin/bluetooth/btsockstat
install -s -o root -g kmem -m 2555 btsockstat /usr/bin
install: kmem: Invalid argument
***
in /usr/src.
TB-14R
doh i did make install kernel instead of make installkernel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Bizarro...
After having another search of the archives and seeing someone suggest
they were having make problems in X:
(http://lists.freebsd.org/mailman/htdig/freebsd-questions/2004-September/058300.html)
... I ran the make installkernel outside of X (i.e. in a console) and it
works fine.
Try
On 2004-09-22 11:19, Phil Payne [EMAIL PROTECTED] wrote:
After having another search of the archives and seeing someone suggest
they were having make problems in X:
(http://lists.freebsd.org/mailman/htdig/freebsd-questions/2004-September/058300.html)
... I ran the make installkernel outside
/058300.html)
... I ran the make installkernel outside of X (i.e. in a console) and it
works fine.
Try to run it in aterm or xterm and you get the can't shift that many
error.
I cannot pretend to know anything about why this is the case.
This error seems to be caused by some sort
On 2004-09-22 11:43, Phil Payne [EMAIL PROTECTED] wrote:
On Wed, 2004-09-22 at 11:38, Giorgos Keramidas wrote:
On 2004-09-22 11:19, Phil Payne [EMAIL PROTECTED] wrote:
... I ran the make installkernel outside of X (i.e. in a console)
and it works fine. Try to run it in aterm or xterm
On Wed, 2004-09-22 at 13:15, Giorgos Keramidas wrote:
On 2004-09-22 11:43, Phil Payne [EMAIL PROTECTED] wrote:
On Wed, 2004-09-22 at 11:38, Giorgos Keramidas wrote:
On 2004-09-22 11:19, Phil Payne [EMAIL PROTECTED] wrote:
... I ran the make installkernel outside of X (i.e. in a console
On 2004-09-22 13:44, Phil Payne [EMAIL PROTECTED] wrote:
On Wed, 2004-09-22 at 13:15, Giorgos Keramidas wrote:
Weird. Everything seems ok but you seem to be bumping on a problem
related to the shell in use :-/
Weirder... installed Eterm... and I can installkernel install ports
fine. So
On Wed, 2004-09-22 at 15:18, Giorgos Keramidas wrote:
On 2004-09-22 13:44, Phil Payne [EMAIL PROTECTED] wrote:
On Wed, 2004-09-22 at 13:15, Giorgos Keramidas wrote:
Weird. Everything seems ok but you seem to be bumping on a problem
related to the shell in use :-/
Weirder... installed
Phil Payne wrote:
On Wed, 2004-09-22 at 15:18, Giorgos Keramidas wrote:
On 2004-09-22 13:44, Phil Payne [EMAIL PROTECTED] wrote:
On Wed, 2004-09-22 at 13:15, Giorgos Keramidas wrote:
Weird. Everything seems ok but you seem to be bumping on a problem
related to the shell in use :-/
On Wed, 2004-09-22 at 16:33, Kevin D. Kinsey, DaleCo, S.P. wrote:
Phil Payne wrote:
On Wed, 2004-09-22 at 15:18, Giorgos Keramidas wrote:
On 2004-09-22 13:44, Phil Payne [EMAIL PROTECTED] wrote:
On Wed, 2004-09-22 at 13:15, Giorgos Keramidas wrote:
Weird. Everything
result.
Thanks,
Phil.
--
Kernel build for PP completed on Mon Sep 20 15:40:31 BST 2004
--
gw# make installkernel KERNCONF=PP
.
--
Kernel build for PP completed on Mon Sep 20 15:40:31 BST 2004
--
gw# make installkernel KERNCONF=PP
--
Making hierarchy
Freshly cvsupped two machines, one built and installed world/kernel
fine, the second builds world and kernel OK then gives the following
error for make installkernel:
su-2.05b# make installkernel
cd /usr/obj/usr/src/sys/GENERIC; MAKEOBJDIRPREFIX=/usr/obj
MACHINE_ARCH=i386 MACHINE=i386
issues after cvsup to releng_5_2.
I now get the following:
dawn# make installkernel kernconf=GENERIC
cd /usr/obj/usr/src/sys/GENERIC; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386
MACHINE=i386 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/i386/legacy/usr/bin
GROFF_FONT_PATH=/usr/obj/usr/src/i386
On Wednesday 18 February 2004 04:34 pm, James Brasil wrote:
hello,
I'm still very new to freebsd and have run into a glitch upgrading from:
dawn# uname -a
FreeBSD dawn.brasil 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #0: Sun Sep 28
08:00:09 EDT 2003 [EMAIL
77 matches
Mail list logo
