old kernels disappearing?
While dealing with the fallout from my MS heartburn, I've noticed something new. I can no longer keep old kernels in /boot/kernel/, at least not with the name kernel.* Is this new behavior or have I made a mistake in my loader.conf? -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: URGENT: Microsoft overwrites boot loader!
On 7/17/20 1:34 AM, Manish Jain wrote: On 2020-07-17 13:57, Don Wilde wrote: On 7/16/20 7:40 PM, Manish Jain wrote: On 2020-07-17 01:49, Don Wilde wrote: The [deleted] ones in Redmond have done it again. My multi-OS GRUB2 boot loader is gone, and in its place is a 500M partition called 'Windows boot loader'. The purpose is to force us to look at MS' new version of Edge. All my old boot files are gone. It's taken me much of the morning to get underneath this, since on this unit my only OS (other than Doze 10) with a WM and GUI is Ubuntu. That's the last time I will allow this, and I'm calling those [deleted]s tomorrow to give them a piece of my mind. After that I will erase every vestige of that obscene OS from my disk. If I understand correctly, it's just that your Grub boot-loader is gone. Yes, exactly. That should not be much of a problem if your system is MBR+BIOS. Unfortunately, it's GPT under EFI. I can access all my files through the F12 key on this Dell tower, be it Windows, Linux or FreeBSD, but if I allow it to boot with the Doze HDD in the system, it boots to that one. If your system is MBR+BIOS, the following should work. Boot with your FreeBSD CD/DVD/memstick, and write out boot0 to all your disks: boot0cfg -B /dev/ boot0cfg -B /dev/ boot0cfg -B /dev/ Next, boot with your Ubuntu CD/DVD/memstick, and write out Grub to your Ubuntu / partition. If Ubuntu / is /dev/sdb2 : sudo mount /dev/sdb2 /mnt sudo grub-install --force --root-directory=/mnt /dev/sdb2 Reboot. When booting Ubuntu the first time, first press 'e' at the Grub loader menu to edit the configuration, delete the complete if..fi block, check that your line beginning with 'linux' is accurate and then press F10. Once the system has booted, run 'sudo update-grub'. I appreciate the good data, Manish. I'm going to make sure I've gotten all my files off the Doze partition and then wipe it completely. FreeBSD is going to be my primary host OS and I'll keep my other drive for whatever flavors of Linux I need to work with for work. Based on what I've hseen on these threads, MS is still saddled with a number of bad legacy architectural choices as well as poor management choices, and both of those contribute to the challenges the use of their OS brings. I simply won't accept any contract that requires me to work with Windows. I've survived well enough without that skill set and I see no problem going forward. Hi Done, It is further my sincere suggestion to use MBR+BIOS. GPT+UEFI is problem-prone, with one of the problems being that you won't be able to boot FreeBSD. I've already seen that one on my 'mule' machine. This tower (a 2007 machine) will boot FreeBSD directly even in UEFI-BIOS mode; I just need to set it up so that FreeBSD also hosts the boot-loader for the other OSen. To use one of my favorite phrases, "We'll get there!" :D -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: URGENT: Microsoft overwrites boot loader!
On 7/16/20 11:53 PM, Polytropon wrote: On Thu, 16 Jul 2020 13:19:51 -0700, Don Wilde wrote: The [deleted] ones in Redmond have done it again. My multi-OS GRUB2 boot loader is gone, and in its place is a 500M partition called 'Windows boot loader'. They do this all the time. The consensus here is to install "Windows" first, always, restricted to the designated disk space, and _then_ install Linux, FreeBSD, GRUB, or anything else non-"Windows", in order to avoid the exact problem you are describing. Even older versions of "Windows" were known to destroy things like the FreeBSD boot manager when they are installed as a 2nd choice. MICROS~1 always wants you to treat it first class, with golden feet and glockenspiel. However, is my interpretation correct? Did this happen when you _installed_ "Windows" on that machine for the first time, or did it happen after you _booted_ an already installed instance of "Windows", which then did attack "foreign data" on the disk? This machine still maintains the original Windows installation, first with W7, and then (finally, bad mistake) upgraded to W10. The purpose is to force us to look at MS' new version of Edge. All my old boot files are gone. Something like that should never happen. It's absolutely normal that "Windows" installs software without user consent, and then presents it prominently in user-configured areas such as the desktop, the "Start" menu, or the bottom bar (pun absolutely intended), but it should never exceed its authority beyong the border of the "Windows" partition, which clearly means: "Hands off of Grub partition!" Yes. The bastards also screwed up my 128GB backup drive -- again without asking -- when I left it plugged in during a Doze boot. Especially with "Windows 10", the PC is no longer a PC, not a _personal_ computer belonging to the user; it's rather a system remotely controlled by MICROS~1, and having installed "Windows" and therefore agreed to the terms of usage (EULA), there is probably nothing "wrong" with it, because you have agreed that they can do whatever they want, and if something goes wrong, it's your fault. Legal business as usual. Yes, agreed. They far outstrip the robber barons of the 1800s in their greed. Even Carnegie finally discovered a heart beating inside of himself, and gave us libraries and Napoleon Hill! Many years (or let's say, decades) I had a similar problem with an OS/2 installation: It messed up the system's partition table, a system where DOS (not that DOS, the other one) was installed, and there was a data loss: Partition D: became C:, E: became D:, F: became E:, and C: along with its content seemed to be gone. But in the overall "disk space calculation" it must still have been on disk, so I used the Norton Disk Editor (DISKEDIT.EXE from Norton Utilities, a great product at that time!), a handheld calculator and pen & paper to re-calculate the correct values for the partition table, entered them, rebooted, prayed unto the holy bringer of peace, Alpha-Omega, and tadaa, C: was there again, with the correct content. I never had that wonderful luxury of being saddled with a "real" IBM machine or OS/2. One would note that they, too (along with MS, eventually), are being relegated to the dustbin of history where they belong. [snip] That's the last time I will allow this, and I'm calling those [deleted]s tomorrow to give them a piece of my mind. After that I will erase every vestige of that obscene OS from my disk. They don't mind. They already have your money. And maybe they even have your name, address, phone number, credit card number or other banking information... I have a few last resort technologies they *don't* know about, though they are not worth any more of my time or psychic energy. :D -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: URGENT: Microsoft overwrites boot loader!
On 7/16/20 7:40 PM, Manish Jain wrote: On 2020-07-17 01:49, Don Wilde wrote: The [deleted] ones in Redmond have done it again. My multi-OS GRUB2 boot loader is gone, and in its place is a 500M partition called 'Windows boot loader'. The purpose is to force us to look at MS' new version of Edge. All my old boot files are gone. It's taken me much of the morning to get underneath this, since on this unit my only OS (other than Doze 10) with a WM and GUI is Ubuntu. That's the last time I will allow this, and I'm calling those [deleted]s tomorrow to give them a piece of my mind. After that I will erase every vestige of that obscene OS from my disk. If I understand correctly, it's just that your Grub boot-loader is gone. Yes, exactly. That should not be much of a problem if your system is MBR+BIOS. Unfortunately, it's GPT under EFI. I can access all my files through the F12 key on this Dell tower, be it Windows, Linux or FreeBSD, but if I allow it to boot with the Doze HDD in the system, it boots to that one. If your system is MBR+BIOS, the following should work. Boot with your FreeBSD CD/DVD/memstick, and write out boot0 to all your disks: boot0cfg -B /dev/ boot0cfg -B /dev/ boot0cfg -B /dev/ Next, boot with your Ubuntu CD/DVD/memstick, and write out Grub to your Ubuntu / partition. If Ubuntu / is /dev/sdb2 : sudo mount /dev/sdb2 /mnt sudo grub-install --force --root-directory=/mnt /dev/sdb2 Reboot. When booting Ubuntu the first time, first press 'e' at the Grub loader menu to edit the configuration, delete the complete if..fi block, check that your line beginning with 'linux' is accurate and then press F10. Once the system has booted, run 'sudo update-grub'. I appreciate the good data, Manish. I'm going to make sure I've gotten all my files off the Doze partition and then wipe it completely. FreeBSD is going to be my primary host OS and I'll keep my other drive for whatever flavors of Linux I need to work with for work. Based on what I've hseen on these threads, MS is still saddled with a number of bad legacy architectural choices as well as poor management choices, and both of those contribute to the challenges the use of their OS brings. I simply won't accept any contract that requires me to work with Windows. I've survived well enough without that skill set and I see no problem going forward. -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: URGENT: Microsoft overwrites boot loader!
On 7/16/20 4:55 PM, Alan Somers wrote:
On Thu, Jul 16, 2020 at 5:47 PM Don Wilde <mailto:dwil...@gmail.com>> wrote:
On 7/16/20 1:28 PM, Alan Somers wrote:
On Thu, Jul 16, 2020 at 2:20 PM Don Wilde mailto:dwil...@gmail.com>> wrote:
The [deleted] ones in Redmond have done it again. My multi-OS
GRUB2 boot
loader is gone, and in its place is a 500M partition called
'Windows
boot loader'.
The purpose is to force us to look at MS' new version of
Edge. All my
old boot files are gone.
It's taken me much of the morning to get underneath this,
since on this
unit my only OS (other than Doze 10) with a WM and GUI is Ubuntu.
That's the last time I will allow this, and I'm calling those
[deleted]s
tomorrow to give them a piece of my mind. After that I will
erase every
vestige of that obscene OS from my disk.
--
Don Wilde
* What is the Internet of Things but a system *
* of systems including humans? *
Edge? I thought that was a browser. What does it have to do
with boot loaders?
-Alan
It is. They over-wrote my boot loader with a special package
touting their upgrade and its features.
AUTOEXEC.bat is no longer sufficient for them!
The only way to get out of it was to reboot to a different disk.
By installing a new copy of Ubuntu from DVD on a portion of that
drive, I was able to get to the rest of my disk through its GRUB2
(which had been trashed by MS).
I sent a really pointed message to MS "Senior Technical Advisors"
but nobody (of more than a dozen who were on-line and saw it)
responded. I hope nobody commits seppuku, but I'll bet there will
be some resignations.
MS Windows is the toxic RoundUp of the software world, and 10 is
the most egregious one yet.
Are you saying that they overwrite the bootloader in order to display
some kind of popup add before the main OS loads? That makes no sense
whatsoever. It is the crazy ravings of a madman. Except, I know Don
to be reliable. There's definitely a madman involved with this story
somehow, but I don't think it's Don.
-Alan
Thanks, Alan!
After that one, I'm not even sure. From what others have said, I
guess I've been lucky on this. Then again, I've been dodging MS bullets
since the CP/M days...
--
Don Wilde
* What is the Internet of Things but a system *
* of systems including humans? *
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: URGENT: Microsoft overwrites boot loader!
On 7/16/20 2:28 PM, Valeri Galtsev wrote: On Jul 16, 2020, at 3:28 PM, Tomasz CEDRO wrote: czw., 16 lip 2020, 22:20 użytkownik Don Wilde napisał: That's the last time I will allow this, and I'm calling those [deleted]s tomorrow to give them a piece of my mind. After that I will erase every vestige of that obscene OS from my disk. I did that long time ago :-) I have one dedicated laptop if I am really forced to use M$ crap but by all means necessary I avoid it for more than 15 years :-) Microsoft does not admit that other systems exist. So, if I have to have multi boot system, usually laptop, as many sysadmins do, I install MS Widows first (often it is even not installation, but bringing up to the drive “image” machine vendor gives for “reinstallation”). If for whatever reason MS windows is installed not the first, I just restore boot of another system (say by booting it from live DVD) after Windows installation. My current PC laptop is triple boot: UbuntuEbonite linux (my apologies it is not CentOS), FreeBSD, and, of course MS Windows ;-) Valeri Actually, Doze WAS the first on that system, straight from Dell. I never had this issue before, even with the 7 - 10 upgrade, despite adding Ubuntu 18 to it many years ago. I was playing with GRUB Customizer the other day to add another drive dedicated to FreeBSD, and that may have installed my loader in the location MS trashed. I no longer need any program on Windows. I have gotten everything, even my payware model train programs with OpenGL, to work on Wine. It will be erased from my last disk this weekend. -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: URGENT: Microsoft overwrites boot loader!
On 7/16/20 1:28 PM, Alan Somers wrote:
On Thu, Jul 16, 2020 at 2:20 PM Don Wilde <mailto:dwil...@gmail.com>> wrote:
The [deleted] ones in Redmond have done it again. My multi-OS
GRUB2 boot
loader is gone, and in its place is a 500M partition called 'Windows
boot loader'.
The purpose is to force us to look at MS' new version of Edge. All my
old boot files are gone.
It's taken me much of the morning to get underneath this, since on
this
unit my only OS (other than Doze 10) with a WM and GUI is Ubuntu.
That's the last time I will allow this, and I'm calling those
[deleted]s
tomorrow to give them a piece of my mind. After that I will erase
every
vestige of that obscene OS from my disk.
--
Don Wilde
* What is the Internet of Things but a system *
* of systems including humans? *
Edge? I thought that was a browser. What does it have to do with
boot loaders?
-Alan
It is. They over-wrote my boot loader with a special package touting
their upgrade and its features.
AUTOEXEC.bat is no longer sufficient for them!
The only way to get out of it was to reboot to a different disk. By
installing a new copy of Ubuntu from DVD on a portion of that drive, I
was able to get to the rest of my disk through its GRUB2 (which had been
trashed by MS).
I sent a really pointed message to MS "Senior Technical Advisors" but
nobody (of more than a dozen who were on-line and saw it) responded. I
hope nobody commits seppuku, but I'll bet there will be some resignations.
MS Windows is the toxic RoundUp of the software world, and 10 is the
most egregious one yet.
--
Don Wilde
* What is the Internet of Things but a system *
* of systems including humans? *
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
URGENT: Microsoft overwrites boot loader!
The [deleted] ones in Redmond have done it again. My multi-OS GRUB2 boot loader is gone, and in its place is a 500M partition called 'Windows boot loader'. The purpose is to force us to look at MS' new version of Edge. All my old boot files are gone. It's taken me much of the morning to get underneath this, since on this unit my only OS (other than Doze 10) with a WM and GUI is Ubuntu. That's the last time I will allow this, and I'm calling those [deleted]s tomorrow to give them a piece of my mind. After that I will erase every vestige of that obscene OS from my disk. -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: quirk in libpng16.{a|so}
On 7/14/20 10:10 AM, y...@freebsd.org wrote:
On 2020-07-14 09:59, Don Wilde wrote:
Hi, Yuri -- I understand that you maintain the png++ "C++ wrapper for
libpng"?
There's a game engine I'm trying to work with on my 12-stable system,
called Drag[en]gine.
https://dragondreams.ch/
It's a complicated port, and I'll end up tweaking some heavy-duty
OpenGL graphics to get it to do stuff for me. The first issue is that
our libpng16 library is missing a C++ call:
png_access_version_number(), which causes its setup program (a Python
script)to crash.
I have both png and png++ installed and both libpng16.so and
libpng16.a are present.
I'm in the process of (also) installing it on my Ubuntu 18.04.4
machine. It hasn't given me this libpng16 issue.
What do you think of this problem? Is this yours or is it the actual
libpng library itself?
Hi Don,
I used png++ on both Linux (CentOS) and FreeBSD without any problems.
I also can't find png_access_version_number() call in the png++ sources.
Okay, this must actually be a call in the actual libpng sources.
Could you please provide an example code that exhibits the problem?
Here's what happens, though there's evidently quite a bit of
construction that happens in the middle.
scons is Yet Another Super-Make, and it's plus (evidently) is that it
can also generate Android and Windows code.
I type 'scons -h', and the output is:
scons: Reading SConscript files ...
Checking for zlibVersion() in C++ library z... yes
Checking for png_access_version_number() in C++ library png16... no
KeyError: 'forceRuntimeLibs':
File "/opt/dragengine/SConstruct", line 633:
duplicate=0, exports='parent_env parent_targets parent_report' )
File
"/usr/local/lib/python3.7/site-packages/SCons/Script/SConscript.py",
line 660:
return method(*args, **kw)
File
"/usr/local/lib/python3.7/site-packages/SCons/Script/SConscript.py",
line 597:
return _SConscript(self.fs, *files, **subst_kw)
File
"/usr/local/lib/python3.7/site-packages/SCons/Script/SConscript.py",
line 286:
exec(compile(scriptdata, scriptname, 'exec'), call_stack[-1].globals)
File "/opt/dragengine/extern/libpng/SConscript", line 120:
forceRuntimeLibs.extend(parent_targets['lib_zlib']['forceRuntimeLibs'])
The SConscript files are generated from the (attached) custom.py, from
what I understand. The error happens in the construct between lines 631
- 633 of that attached SConscript file (which acts like Makefile does
for C and C++).
Don Wilde
* What is the Internet of Things but a system *
* of systems including humans? *
from SConsCommon import *
from SConsPlatformAndroid import androidUpdateEnv
# create environment
tools = ARGUMENTS.get( 'tools', '' )
if tools:
if tools == 'mingw64':
parent_env = Environment( CPPPATH='.', LIBPATH='.',
tools=['mingw'] )
compiler = 'x86_64-w64-mingw32'
if not parent_env.Detect( '{}-g++'.format( compiler ) ):
print( 'Windows 64-bit Cross-Compiler not found.' )
Return()
parent_env.Replace( CC = '{}-gcc'.format( compiler ) )
parent_env.Replace( CXX = '{}-g++'.format( compiler ) )
parent_env.Replace( LD = '{}-ld'.format( compiler ) )
parent_env.Replace( AR = '{}-ar'.format( compiler ) )
parent_env.Replace( STRIP = '{}-strip'.format( compiler ) )
#parent_env.Replace( MAKE = '{}-make'.format( compiler ) )
parent_env.Replace( RANLIB = '{}-ranlib'.format( compiler ) )
parent_env.Replace( NM = '{}-nm'.format( compiler ) )
parent_env.Replace( RC = '{}-windres'.format( compiler ) )
parent_env.Replace( DLLTOOL = '{}-dlltool'.format( compiler ) )
parent_env.Replace( SHCCFLAGS = [ '$CCFLAGS' ] ) # remove -fPIC
if included. just to silence misleading warnings
parent_env.Replace( SHLIBPREFIX = '' ) # fix prefix since the
environment is set up for unix
parent_env.Replace( SHLIBSUFFIX = '.dll' ) # fix suffix since
the environment is set up for unix
parent_env.Replace( LIBPREFIX = '' ) # fix prefix since the
environment is set up for unix
parent_env.Replace( LIBPREFIXES = [ '' ] ) # fix prefix since
the environment is set up for unix
parent_env.Replace( LIBSUFFIX = '.lib' )
parent_env.Replace( LIBSUFFIXES = [ '.lib', '.a' ] )
parent_env[ 'OS_NAME' ] = 'win32'
parent_env[ 'SYS_PLATFORM' ] = 'win32'
parent_env[ 'CROSSCOMPILE_HOST' ] = compiler
parent
quirk in libpng16.{a|so}
Hi, Yuri -- I understand that you maintain the png++ "C++ wrapper for libpng"? There's a game engine I'm trying to work with on my 12-stable system, called Drag[en]gine. https://dragondreams.ch/ It's a complicated port, and I'll end up tweaking some heavy-duty OpenGL graphics to get it to do stuff for me. The first issue is that our libpng16 library is missing a C++ call: png_access_version_number(), which causes its setup program (a Python script)to crash. I have both png and png++ installed and both libpng16.so and libpng16.a are present. I'm in the process of (also) installing it on my Ubuntu 18.04.4 machine. It hasn't given me this libpng16 issue. What do you think of this problem? Is this yours or is it the actual libpng library itself? -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: swap space issues
On 7/12/20 12:39 PM, Jonathan Chen wrote: [snip] With synth you can reduce the number of workers to just "1" (ie: Number_of_builders=1), if you just want your ports-build to complete without any stress. However, one of the reasons why I use synth is _because_ of the stress it can place on my 12-STABLE snapshots. If the system is stable and performs well when under load, I feel just that bit more assured about using it in production environments. My 2 cents. Yeah, I did that. Problem was a bad update to a port, had mismatched bracket element so blew the stack. Same thing happened with one worker, one task. Made sure I didn't use that port again... ;-) -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: swap space issues
On 7/11/20 11:28 PM, Scott Bennett via freebsd-stable wrote:
I have read this entire thread to date with growing dismay, and I
thank Donald Wilde for reporting his ongoing troubles, although they
spoil my hopes that the kernel's memory management bugs that first became
apparent in 11.2-RELEASE (and -STABLE around the same time) were not
propagated into 12.x. A recent update to stable/12 source tree made it
finally possible for me to build 12.1-STABLE under 11.4-PRERELEASE, and I
was just about to install the upgrade when this thread appeared.
Spoiler alert. Since I gave up on Synth, I haven't had a single swap
issue. It does appear to be one particular port that drove it nuts
(apparently, one of the 'Google performance' bits, with a
mismatched-brackets problem). I have rebuilt the machine several times,
but that's more for my sense of tidiness than anything.
I've got a little Crystal script that walks the installed packages and
ports and updates them with system() calls.
The machine is very slow, but it's not swapping at all.
It is quite usable now with 12-STABLE.
On Fri, 26 Jun 2020 03:55:04 -0700 : Donald Wilde
wrote:
On 6/26/20, Peter Jeremy wrote:
[snip]
I strongly suggest you don't have more than one swap device on spinning
rust - the VM system will stripe I/O across the available devices and
that will give particularly poor results when it has to seek between the
partitions.
True. The only reason I can think of to use more than one swapping/
paging area on the same device for the same OS instance is for emergencies
or highly unusual, temporary situations in which more space is needed until
those situations conclude. and even in such situations, if the space can be
found on another device, it should be placed there. Interleaving of swap
space across multiple devices is intended as a performance enhancement
akin to striping (a.k.a. RAID0), although the virtual memory isn't
necessarily always actually striped across those devices. Adding a paging
area on the same device as an existing one is an abhorrent situation, as
Peter Jeremy noted, and it should be eliminated via swapoff(8) as soon as
the extraordinary situation has passed. N.B. the GENERIC kernel sets a
limit of four swap devices, although it can be rebuilt with a different
limit.
That's good data, Scott, thanks! The only reason I got into that
situation of trying to add another swap device was that it was crashing
with OO swap messages.
My intent is to make this machine function -- getting the bear
dancing. How deftly she dances is less important than that she dances
at all. My for-real boxen will have real HP and real cores and RAM.
Also, you can't actually use 64GB swap with 4GB RAM. If you look back
through your boot messages, I expect you'll find messages like:
warning: total configured swap (524288 pages) exceeds maximum recommended
amount (498848 pages).
warning: increase kern.maxswzone or reduce amount of swap.
Also true. Unfortunately, no guidance whatsoever is provided to advise
system administrators who need more space as to how to increase the relevant
table sizes and limits. However, that is a documentation bug, not a code
bug.
I've got both my kern.max* and CCACHE set up mostly correctly.
Everything builds and runs well, although I've found that it's helpful
to only use -j3 while building, not -j4 which would be appropriate for
my HAMMER i3. I'd much rather have the bear *dancing* than running into
walls. :D
Yes, as I posted, those were part of the failure stream from the synth
program. When I had kern.maxswzone increased, it got through boot
without complaining.
or maybe:
WARNING: reducing swap size to maximum of MB per unit
The warnings were there, in the as-it-failed complaints.
The absolute limit on swap space is vm.swap_maxpages pages but the
realistic
limit is about half that. By default the realistic limit is about 4?RAM
(on
64-bit architectures), but this can be adjusted via kern.maxswzone (which
defines the #bytes of RAM to allocate to swzone structures - the actual
space allocated is vm.swzone).
As a further piece of arcana, vm.pageout_oom_seq is a count that controls
the number of passes before the pageout daemon gives up and starts killing
processes when it can't free up enough RAM. "out of swap space" messages
generally mean that this number is too low, rather than there being a
shortage of swap - particularly if your swap device is rather slow.
Thanks, Peter!
A second round of thanks to Peter Jeremy for pointing out this sysctl
variable (vm.pageout_oom_seq), although thus far I have yet to see that it is
actually effective in working around the memory management bugs. I have added
the following lines to /etc/sysctl.conf.
# Because FreeBSD 11.{2,3,4} tie up page frames unnecessarily, set value high
#vm.pageout_wakeup_thresh=14124 # Default value
vm.pageout_wakeup_thresh=112640 # 410 MB
[snip]
I do totally agree that these are
Re: Getting a new shell to work for the 'toor' user
On 7/6/20 12:13 PM, Jonathan Chen wrote: On Tue, 7 Jul 2020 at 07:10, Don Wilde wrote: All, I finally got around to -- I thought :) -- completing my inclusion of bash-static as a usable shell. It works as an available shell in 'adduser', but when I tried to use it as a recovery shell (see attached .odt), I ran into a problem. My fist pass was to add /bin/stbash to the end of the toor line in master.passwd, but that didn't change it even after a reboot. You have to use vipw(8). That worked, thanks! I'd forgotten about vipw, though I'd used it before. Doug's answer would have worked too, but since vipw calls pwd_mkdb, I didn't have to figure that one out. :) I'll polish the doc and ship it to freebsd-doc@ for comments. Appreciate the help! -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Getting a new shell to work for the 'toor' user
All, I finally got around to -- I thought :) -- completing my inclusion of bash-static as a usable shell. It works as an available shell in 'adduser', but when I tried to use it as a recovery shell (see attached .odt), I ran into a problem. My fist pass was to add /bin/stbash to the end of the toor line in master.passwd, but that didn't change it even after a reboot. Next, I discovered that logging in as toor and issuing: # chsh -s /bin/stbash, but that didn't work successfully because it changed my root shell to the static-linked bash as well. I quickly changed it back! Two other commands work as expected, and track the issue: 'echo $0' and 'echo $SHELL' I don't see where SHELL is set, or $0. Are these in one of the rc files? What did I miss? -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
sackcloth and ashes time
Dear FreeBSD friends; I recently added my gmail contacts to Linked-In, Inviting only those who were already on Linked-In, and discovered -- thanks to Bruce Cran -- that it came to STABLE. Looking in Linked-In at his profile, Mr Rotaev's public e-mail address address is clearly noted as being freebsd-sta...@freebsd.org. I have requested that Linked-In customer service address the matter, as I cannot contact him without causing more of the same spam in your mailboxes. He does not appear to be an active Linked-In user. Thank you all in advance for your understanding! :D -- -- Don Wilde Convince by Example http://www.EngineeringJobFuture.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Don Wilde wants to connect on LinkedIn
LinkedIn Don Wilde requested to add you as a connection on LinkedIn: -- Dear Valeriy, I'm merging my GMail with Liked-In so I can easily learn more about what's new in your lives. Please accept my humble invitation and feel free to personally reconnect and strengthen the connection! :D - Don Wilde Accept invitation from Don Wilde http://www.linkedin.com/e/2bA_QBNshSoW6_Mg2FRMfzNsaTwKa_DOn-2pAopq/blk/I39742775_4/1BpC5vrmRLoRZcjkkZt5YCpnlOt3RApnhMpmdzgmhxrSNBszYQnPkTdP8QdPAPiiZWd44MblxWiOYPdz8Md3sPe3wLrCBxbOYWrSlI/EML_comm_afe/ View invitation from Don Wilde http://www.linkedin.com/e/2bA_QBNshSoW6_Mg2FRMfzNsaTwKa_DOn-2pAopq/blk/I39742775_4/d5YRdPsOd3sVcQALqnpPbOYWrSlI/svi/ -- DID YOU KNOW you can be the first to know when a trusted member of your network changes jobs? With Network Updates on your LinkedIn home page, you'll be notified as members of your network change their current position. Be the first to know and reach out! http://www.linkedin.com/ -- (c) 2009, LinkedIn Corporation ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
continuing problem building -STABLE kernel
I did everything I could to clean out /usr/obj, did 'make cleandir', etc, before building, but it appears that the fix (as of yesterday's CVS) for this problem isn't there yet. I remember somebody mentioning about 2 weeks ago that work has been done in -CURRENT on this. I am running a fairly stock kernel without IPv6 on a Dell Inspiron 6000. make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=LYNX ... [snip] linking kernel udbp.o(.text+0x108): In function `udbp_detach': : undefined reference to `ng_rmnode_self' udbp.o(.text+0x11b): In function `udbp_detach': : undefined reference to `ng_unref_node' udbp.o(.text+0x487): In function `udbp_attach': : undefined reference to `ng_newtype' udbp.o(.text+0x4a4): In function `udbp_attach': : undefined reference to `ng_make_node_common' udbp.o(.text+0x4de): In function `udbp_attach': : undefined reference to `ng_name_node' udbp.o(.text+0x5bd): In function `udbp_attach': : undefined reference to `ng_unref_node' udbp.o(.text+0x621): In function `udbp_in_transfer_cb': : undefined reference to `ng_package_data' udbp.o(.text+0x637): In function `udbp_in_transfer_cb': : undefined reference to `ng_address_hook' udbp.o(.text+0x646): In function `udbp_in_transfer_cb': : undefined reference to `ng_snd_item' udbp.o(.text+0x8cd): In function `ng_udbp_rcvmsg': : undefined reference to `ng_free_item' udbp.o(.text+0x8d7): In function `ng_udbp_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' udbp.o(.text+0x90b): In function `ng_udbp_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' udbp.o(.text+0x98e): In function `ng_udbp_rcvmsg': : undefined reference to `ng_address_ID' udbp.o(.text+0x99d): In function `ng_udbp_rcvmsg': : undefined reference to `ng_snd_item' udbp.o(.text+0x9c6): In function `ng_udbp_rcvmsg': : undefined reference to `ng_free_item' udbp.o(.text+0x9f6): In function `ng_udbp_rcvdata': : undefined reference to `ng_free_item' udbp.o(.text+0xc34): In function `ng_udbp_rmnode': : undefined reference to `ng_unref_node' udbp.o(.text+0xc42): In function `ng_udbp_rmnode': : undefined reference to `ng_make_node_common' udbp.o(.text+0xc79): In function `ng_udbp_rmnode': : undefined reference to `ng_name_node' udbp.o(.text+0xce0): In function `ng_udbp_rmnode': : undefined reference to `ng_unref_node' udbp.o(.text+0xd36): In function `ng_udbp_disconnect': : undefined reference to `ng_rmnode_self' udbp.o(.rodata+0x20): undefined reference to `ng_parse_int32_type' udbp.o(.rodata+0x3c): undefined reference to `ng_parse_struct_type' udbp.o(.rodata+0x64): undefined reference to `ng_parse_int32_type' udbp.o(.rodata+0x70): undefined reference to `ng_parse_int32_type' *** Error code 1 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: continuing problem building -STABLE kernel
On 10/29/06, Ronald Klop [EMAIL PROTECTED] wrote: do you have 'options NETGRAPH' in your kernel? see 'man udbp'. Memo to self: always check GENERIC before building! Thanks, Ronald! :D ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
c-ares and IPv6
Hey, folks - I know you're all busy with release work, but can somebody point me to how to get things like gnupg to compile? curl says both c-ares and IPv6 cannot coexist, but c-ares is not installed and I've built kernels both with and without IPv6 support. Whazzup? curl does not seem to be the only seminal package that's killing me, but I've tried deleting it, reinstalling it, etc etc etc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Seg fault error this morning
On 9/19/06, Brian [EMAIL PROTECTED] wrote: I just cvsupped this morning after seeing the gzip announcement. During a buildworld, I get the below. I have replicated this a few times. buildworld from cvsup this morning (x86) worked fine for me, Brian, same time frame. Suggest you update source again, 'make clean' and try again. :D ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
cron abuse
I reinstalled my crontab (with crontab -e) after a user edited the crontab directly and nothing appears to be working now. The mails I get suggest that it's trying to find 'root' and 'operator' as programs. Would somebody kindly help me recover from this copilot error? I can't find anything in crontab(5) or cron(8). My procedure was to invoke crontab -e (getting a blank emacs editor window), split the window, opening a copy of the /etc/crontab copied the contents into the temporary crontab save and exit kill -1 1 these are the e-mails I'm getting Subject: Cron [EMAIL PROTECTED] root /usr/libexec/atrun root: not found TIA! Don Wilde ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron abuse
On 9/3/06, David Wolfskill [EMAIL PROTECTED] wrote: Formats for /etc/crontab user-specific crontabs are different; the former contains a field for the user under whose auspices the command should be run, while the latter does not (as it's implied by the owner of the crontab in question). Peace, david Thanks for taking the time to answer, David. Yes, I see that. I'm reinstalling the old /etc/crontab back into /etc/crontab. This is what's driving me nuts. Why would it be acting as though it's a user crontab? %D ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron abuse
On 9/3/06, David Wolfskill [EMAIL PROTECTED] wrote: On Sun, Sep 03, 2006 at 11:43:01AM -0500, Don Wilde wrote: ... Thanks for taking the time to answer, David. Sure thing. Yes, I see that. I'm reinstalling the old /etc/crontab back into /etc/crontab. OK. This is what's driving me nuts. Why would it be acting as though it's a user crontab? I doubt that it is -- more likely, a copy of /etc/crontab was installed as a user crontab -- go check /var/cron/tabs. Yes, it did exactly that. Will removing the /var/cron/tabs entry make everything Just Work again? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron abuse
One good thing about your problem is it reminded me I'd forgotten to MFC the anti foot shooting measure I added a while back which causes crontab to refuse to load /etc/crontab as a user crontab. It doesn't try very hard, but it does prevent the most common error. -- Brooks Which is what happened here. :) It never ceases to amaze me how rich a world FreeBSD is, and there's always more to learn. Many tanks of beer to all who added suggestions. The root crontab was indeed saved by my actions as /var/cron/tabs/root, and it was that which was complaining vociferously. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
On 7/28/06, Michael Proto [EMAIL PROTECTED] wrote: Don Wilde wrote: Okay, I've gotten it working with all encryption off (raw DHCP). All the nasty messages went away, so I'll see what's changed in the ifconfig options. ifconfig_iwi0=DHCP ssid rewired channel 11 authmode shared weptxkey 1 wepmode on wepkey 0x1234567890 Can anybody spot it off the top? By removing the hardwired 'channel 11 authmode shared' from both sides, I have been able to connect successfully with WEP authentication. Just a note (and someone please correct me if I'm wrong), but setting the channel in the client's ifconfig statement is invalid in BSS mode-- it will pull the appropriate channel from the AP during the association. -Proto It used to work that way, so somebody must have updated the coding. Thanks, Michael, for the input. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
Yes, I have. I just did another CVSup, and when I recompiled -kmod it did indeed put a bunch of .ko files in /build/modules, but a) I still get a whole bunch of Can't load firmware complaints, and b) it doesn't work. It goes through the DISCOVER process, but doesn't get any offers it recognizes. I've tried this both with an open DHCP and also with my parameters wired in. Hardware notes: Dell 6100 Inspiron with 2200G iwi. I have heard from another gent who has a 2200G pci card and is having the same problem with STABLE. This all was working two weeks ago. On 7/27/06, Mark Willson [EMAIL PROTECTED] wrote: Have you tried using the firmware from iwi-firmware-kmod, rather than iwi-firmware. I am using the former on a Thinkpad T42 and it is working ok. -mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
On 7/27/06, Max Laier [EMAIL PROTECTED] wrote: [Please don't top-post] On Thursday 27 July 2006 21:01, Don Wilde wrote: Yes, I have. I just did another CVSup, and when I recompiled -kmod it did indeed put a bunch of .ko files in /build/modules, but a) I still get a whole bunch of Can't load firmware complaints, and b) it doesn't work. It goes through the DISCOVER process, but doesn't get any offers it recognizes. I've tried this both with an open DHCP and also with my parameters wired in. Hardware notes: Dell 6100 Inspiron with 2200G iwi. I have heard from another gent who has a 2200G pci card and is having the same problem with STABLE. This all was working two weeks ago. Just to get the facts straight and assembled in one place: You are running a somewhat recent RELENG_6, have net/iwi-firmware-kmod installed and device iwi and options firmware built into your kernel? When do you get the Can't load firmware messages? What does kldstat [-v] say before and after that point? Can you try kldload iwi_bss before and see if that gets you up and running? On 7/27/06, Mark Willson [EMAIL PROTECTED] wrote: Have you tried using the firmware from iwi-firmware-kmod, rather than iwi-firmware. I am using the former on a Thinkpad T42 and it is working ok. Hi, Max - I did so, and it appears that the module is already loaded. It seems that the problems occur because my system is also trying to load the old firmware somehow. A more disturbing issue is that my rc.conf seems to be being read twice. I see the kldstat reports (with my echo commands) being printed four times instead of the two I'm requesting. Attached are my rc.conf and dmesg. rc.cnf Description: Binary data dmesg.iwi Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
On 7/27/06, Don Wilde [EMAIL PROTECTED] wrote: On 7/27/06, Max Laier [EMAIL PROTECTED] wrote: [Please don't top-post] On Thursday 27 July 2006 21:01, Don Wilde wrote: Yes, I have. I just did another CVSup, and when I recompiled -kmod it did indeed put a bunch of .ko files in /build/modules, but a) I still get a whole bunch of Can't load firmware complaints, and b) it doesn't work. It goes through the DISCOVER process, but doesn't get any offers it recognizes. I've tried this both with an open DHCP and also with my parameters wired in. Hardware notes: Dell 6100 Inspiron with 2200G iwi. I have heard from another gent who has a 2200G pci card and is having the same problem with STABLE. This all was working two weeks ago. Just to get the facts straight and assembled in one place: You are running a somewhat recent RELENG_6, have net/iwi-firmware-kmod installed and device iwi and options firmware built into your kernel? When do you get the Can't load firmware messages? What does kldstat [-v] say before and after that point? Can you try kldload iwi_bss before and see if that gets you up and running? On 7/27/06, Mark Willson [EMAIL PROTECTED] wrote: Have you tried using the firmware from iwi-firmware-kmod, rather than iwi-firmware. I am using the former on a Thinkpad T42 and it is working ok. Hi, Max - I did so, and it appears that the module is already loaded. It seems that the problems occur because my system is also trying to load the old firmware somehow. A more disturbing issue is that my rc.conf seems to be being read twice. I see the kldstat reports (with my echo commands) being printed four times instead of the two I'm requesting. Attached are my rc.conf and dmesg. Okay, I've gotten it working with all encryption off (raw DHCP). All the nasty messages went away, so I'll see what's changed in the ifconfig options. ifconfig_iwi0=DHCP ssid rewired channel 11 authmode shared weptxkey 1 wepmode on wepkey 0x1234567890 Can anybody spot it off the top? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
On 7/27/06, Don Wilde [EMAIL PROTECTED] wrote: On 7/27/06, Don Wilde [EMAIL PROTECTED] wrote: On 7/27/06, Max Laier [EMAIL PROTECTED] wrote: [Please don't top-post] On Thursday 27 July 2006 21:01, Don Wilde wrote: Yes, I have. I just did another CVSup, and when I recompiled -kmod it did indeed put a bunch of .ko files in /build/modules, but a) I still get a whole bunch of Can't load firmware complaints, and b) it doesn't work. It goes through the DISCOVER process, but doesn't get any offers it recognizes. I've tried this both with an open DHCP and also with my parameters wired in. Hardware notes: Dell 6100 Inspiron with 2200G iwi. I have heard from another gent who has a 2200G pci card and is having the same problem with STABLE. This all was working two weeks ago. Just to get the facts straight and assembled in one place: You are running a somewhat recent RELENG_6, have net/iwi-firmware-kmod installed and device iwi and options firmware built into your kernel? When do you get the Can't load firmware messages? What does kldstat [-v] say before and after that point? Can you try kldload iwi_bss before and see if that gets you up and running? On 7/27/06, Mark Willson [EMAIL PROTECTED] wrote: Have you tried using the firmware from iwi-firmware-kmod, rather than iwi-firmware. I am using the former on a Thinkpad T42 and it is working ok. Hi, Max - I did so, and it appears that the module is already loaded. It seems that the problems occur because my system is also trying to load the old firmware somehow. A more disturbing issue is that my rc.conf seems to be being read twice. I see the kldstat reports (with my echo commands) being printed four times instead of the two I'm requesting. Attached are my rc.conf and dmesg. Okay, I've gotten it working with all encryption off (raw DHCP). All the nasty messages went away, so I'll see what's changed in the ifconfig options. ifconfig_iwi0=DHCP ssid rewired channel 11 authmode shared weptxkey 1 wepmode on wepkey 0x1234567890 Can anybody spot it off the top? By removing the hardwired 'channel 11 authmode shared' from both sides, I have been able to connect successfully with WEP authentication. Thanks for all your suggestions, guys! :D ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
