- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Dec 15 2018
I like this much better; hopefully the performance tests will show that it is an improvement.
Sorry, a tiny tinsy bit more.
Overcome by D18449
Could you try to fix the build with clang7? What is the error you get?
Don't run mount twice
Fixed whitespace issues (tab vs space) and added informational messages
In D18546#395727, @sobomax wrote:This is not quite what I am talking about here. We want the value returned by the DHCP server to have an effect when system boots, but we don't want dhclient to continuously restore the state back in case it has been changed by the administrator. My point is that dhclient does not do this periodic "check-up/fix-up" for any other part of configuration that it makes (e.g. ip address, netmask, default gateway, dns server), so there is no reason for an administrator to expect MTU to be in a different bucket. I believe "leave interface alone unless there are some changes on the DHCP side" is the proper approach.
Don't use DESTDIR in tools/boot/install-root.sh: it causes bad stuff to happen
since it's that file is now sourced into other scripts. For example,
"make vm-release" installs files to / !
Rebasing.