BFS does this as part of journal management, but not as part of block
cache synchronization (which makes sense, as flushing it then would
defeat the purpose of the drive's write cache.) No other file system
seems to touch it at all, so we should do it as part of an explicit sync.
This may help with some of the filesystem corruption issues, as it seems
that on slow disks, the drive might not have enough time to flush the cache
before it is powered off (or on some SATA/AHCI based disks, it is not flushed
before close at all), so triggering it here and, as the ioctl is supposed to be
synchronous, waiting for it also, seems to make sense.
Change-Id: I7d9992c21ca4b59c839711dcc96c973b4b8df052
Reviewed-on: https://review.haiku-os.org/530
Reviewed-by: Jérôme Duval <jerome.duval@gmail.com>
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
(cherry picked from commit 864b868b262e56dabe45bbb3881564a4ff162582)
Reviewed-on: https://review.haiku-os.org/539
* The difference is visible when control background doesn't match
panel background.
Change-Id: Ie3a034acaa52929becd6601520e0e05f32ecc8d8
Reviewed-on: https://review.haiku-os.org/537
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
(cherry picked from commit f5ac1f07e20890e92adf8f7cee03413afbc9a4db)
Reviewed-on: https://review.haiku-os.org/538
When URLs combine a base URL with a relative part, the relative part's
path component was being pre-processed. This removed any ".." from the
path and in some cases in the unit test cases, the ".." should have been
retained and then only later applied to the base URL. This changes
fixes this so that the relative part is not pre-processed and is applied
with it's path in a raw state.
Completes Fixes for #14377
Change-Id: I9cebb8599889494e11f40a3b54c87ebca3ed1a21
Reviewed-on: https://review.haiku-os.org/529
Reviewed-by: Jérôme Duval <jerome.duval@gmail.com>
(cherry picked from commit 1a5994981b4f568f04fef429ac962f78f10bfce2)
Reviewed-on: https://review.haiku-os.org/536
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
Resetting the drawing mode to B_OP_COPY was not right, since the previous mode could be anything.
Use WritePush/PopState() instead.
Change-Id: If9cba2c46bf372fd0164d951fcc49696cf72d576
Reviewed-on: https://review.haiku-os.org/534
Reviewed-by: Stefano Ceccherini <stefano.ceccherini@gmail.com>
Does not seem to work, though.
Change-Id: I309d8de79a71ab8e08f4ac2f2566080b67b84800
Reviewed-on: https://review.haiku-os.org/533
Reviewed-by: Stefano Ceccherini <stefano.ceccherini@gmail.com>
Like the AS_DRAW_PICTURE case, make a copy of the passed BPicture also for AS_CLIP_TO_PICTURE
Change-Id: Id9a0adc48d73e5ec9c0d37e2ed85e30aa48369ab
Reviewed-on: https://review.haiku-os.org/532
Reviewed-by: Stefano Ceccherini <stefano.ceccherini@gmail.com>
In the AS_CLIP_TO_PICTURE case, the "picture" variable was shadowing the outer "picture" variable.
Change-Id: I3b9de2432f93a683aaccdb899051a14ebf9b7e6e
Reviewed-on: https://review.haiku-os.org/531
Reviewed-by: Stefano Ceccherini <stefano.ceccherini@gmail.com>
Change-Id: I52ada3447b638db07622fa51746e75ce6cce7a46
Reviewed-on: https://review.haiku-os.org/518
Reviewed-by: Alexander von Gluck IV <kallisti5@unixzen.com>
Reviewed-on: https://review.haiku-os.org/522
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
This change matches hrev52316 in master. These URL's will be around
for a long time since haikudepot references them for repository
matching.
Change-Id: Ifbfbc8a69ab45f76ee0a10e05903b0b05c161d9b
Reviewed-on: https://review.haiku-os.org/519
Reviewed-by: Alexander von Gluck IV <kallisti5@unixzen.com>
* De-escalate the severety of data loss from "high risk" to "risk".
* Remove the advice to not create partitions with DriveSetup. It's been tested
and been working well since the last alpha. Do recommend making backups of
all partitions.
* Remove description how to add Haiku to Grub. It's too much detail and the
user would have to memorize the info. Add a link to our Booting guide
instead.
* Mention BootManager as an alternative to boot Haiku, refering to the
Userguide for more info.
* Alpha -> Beta
* Only give normal thanks instead of "a lot" and don't beg to like us.
Sounded a bit desperate...
Change-Id: I212513fde01287f5d1c9c5c9891827aaf0b7e1ea
Reviewed-on: https://review.haiku-os.org/502
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
When recording a BPicture, the app_server just record events and does
not draw anything. As a result, drawing code that relies on the view
state can get out of sync.
Specifically, our text drawing code relies on getting the pen position
from app_server when asked to draw at "current pen position". As a
result, the pen is never moved and when drawing multiple chunks of text,
they end up overlapping, all drawn at the same cursor position.
To avoid the problem and show that this is indeed what is happening,
this patch adds an explicit cursor move into the BPicture after drawing
a string. This also updates app_server internal pen position, so further
drawing happens at the expected place.
This is however not the right way to fix this. Either we should remove
the code that gets the pen position back from app_server, and let
app_server completely manage the cursor position, or, we should make
sure recording a BPicture also updates the pen position so the
application can rely on accessing it and getting up to date data.
Fixes #6761.
NOTE(waddlesplash): It seems to make sense to include this hack
in R1/beta1, so that printing is not totally broken. Obviously
it should stay out of master.
Change-Id: Ib8e031355032228ef29aceee5f1e1ca21565b831
Reviewed-on: https://review.haiku-os.org/498
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
As the comment says, there are a number of scenarios when this is
the case, e.g. non-interactive SSH sessions.
Change-Id: I3a10043820039f344b3f036f7861c81f6fb7ef05
Reviewed-on: https://review.haiku-os.org/499
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
(cherry picked from commit bd114eeb370ba18d65f641fcb6b78b453ffc2937)
Reviewed-on: https://review.haiku-os.org/500
* Unlink/Symlink not needed as we now use a package.
* Use correct URLs to download headers.
Fixes #14412.
Change-Id: I76dbca3d48d0b2933a27bea666551ff86d404a93
Reviewed-on: https://review.haiku-os.org/493
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
(cherry picked from commit 60eefaaad87efb6a1207f6b2d5fc469eb2c92bea)
Reviewed-on: https://review.haiku-os.org/495
This is much simpler than the prior condvar-based method and should be
functionally equivalent. It seems tsleep() cause a NULL dereference,
though (which will be fixed in the next commit), so this probably
also fixes #14355.
Change-Id: I36968de38ceb0a1c0896cae8839821f5ca383504
Reviewed-on: https://review.haiku-os.org/489
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
(cherry picked from commit 2e64054de804b4dbf471b0c1834b30e4be2c48d1)
Reviewed-on: https://review.haiku-os.org/491
Our implementation of tsleep does this. It seems very few things
actually use that, though, so the issue referenced in the previous
commit may be one of the first things to use pause/tsleep.
Change-Id: Id2edb2268b3b078b9ded5d634cfa241599f882f1
Reviewed-on: https://review.haiku-os.org/490
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
(cherry picked from commit 5e7b3530c8197a5950c34035dc33f5eb141d925a)
Reviewed-on: https://review.haiku-os.org/492
The function allocates a message because it uses lazy initialization,
however the user does not get ownership and must not delete it.
Fixes #14413.
Change-Id: I94807026c6969746a804492ee07808d621533ac3
Reviewed-on: https://review.haiku-os.org/488
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
* PRE_BETA_2 is now the default in master.
* For libbe: R1/alpha4 used internal=8, but nobody bumped master
at the same time, so now we are on internal=9.
Fix -Werror=class-memaccess pointed out by gcc8.
* Use TerminalLine::Clear() instead of memset()
* Use rgb_color::operator=() instead of memcpy()
Change-Id: I41360e245fd55c526d9c2802a2f247ba22583080
Reviewed-on: https://review.haiku-os.org/483
Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>
It is just straight up broken on most systems without this, as
the same "cast specifies signature type" appears there too.
Exactly why this fixes the problem does not appear to be any more known
than it was when this was first instated in 2012.
The latter is not just a symlink to the former, but is a small pseudo-
library that tells the linker to use the .so.1 version instead. As we
do not pass -L to this directory to the linker invocation, the linker
thus cannot find it, and so errors out.
We rightly do not want the linker doing "magic" things for us that
we don't expect, and so even if this one case is fine, we shouldn't
allow the linker to take care of this automatically for us when
it comes to libroot and other core system functionality, especially
as going forward we may indeed add a second libgcc version due to ABI
breaks. Instead, link against .so.1 directly.
Fixes the build breakage caused by the GCC 7 bump.
We now build libicns against it. It seems that it is better-maintained than
JasPer, so we should probably consider switching the JPEG2000Translator to
use it also.
ffmpeg_devel pulls in some other devel packages we don't really need,
and very few things are built against it anyway, so whoever needs it
can install it manually. Same goes for freetype and fontconfig.
