Porting NetBSD to the AMD x86-64: a case study in OS portability Seriously, I have no big words to say, other than just recommending this laptop to FOSS enthusiasts :) So here it is, my new laptop, a Google Pixelbook. something rather big for a tablet, but it is useful actually), a Wacom touchscreen that supports a pen, mostly reasonable hardware (Intel Wi-Fi), and that famous coreboot support (Chromebooks\u2019 stock firmware is coreboot + depthcharge). Thin aluminum design, a 3:2 HiDPI screen, rubber palm rests (why isn\u2019t every laptop ever doing that?!), the \u201cconvertibleness\u201d (flip the screen around to turn it into. Other than the big huge large bezels around the screen, I liked everything about it. I want something more efficient, not less!Īnd then I discovered the Pixelbook. But going back in processor generations just doesn\u2019t feel great. I was considering a ThinkPad X1 Carbon from an old generation - the one from the same year as the X230 is corebootable, so that\u2019s fun. how about something with open source firmware, that would be fun.supported by FreeBSD of course (\u201csome development required\u201d is okay but I\u2019m not going to write big drivers).assembled with screws and not glue (I don\u2019t necessarily need expansion and stuff in a laptop all that much, but being able to replace the battery without dealing with a glued chassis is good).without a dGPU, especially without an NVIDIA GPU.with a HiDPI display (and ideally with a good size for exact 2x scaling instead of fractional).with a 3:2 display (why is Lenovo making these Serious Work\u2122 laptops 16:9 in the first place? 16:9 is awful in below-13-inch sizes especially).lighter and thinner (ha, turns out this is actually important, I got tired of carrying a T H I C C laptop - Apple was right all along).But this summer I\u2019ve decided that it was time for something newer. Unlike most people in the ThinkPad crowd, I actually liked the clickpad and didn\u2019t use the trackpoint much. FreeBSD and custom firmware on the Google Pixelbookīack in 2015, I jumped on the ThinkPad bandwagon by getting an X240 to run FreeBSD on.xsessionrc, but it's part of the session startup script some display managers including GDM (the GNOME display manager) and lightdm, but not others such as xdm and kdm.Headlines FreeBSD and custom firmware on the Google Pixelbook xsessionrc is a Debian feature and distributions that are not based on Debian don't have it unless they've implemented something similar. xsession are historical features of the X11 Window system so they should be available and have a similar behavior on all Unix systems. It doesn't have any official documentation that I know of, you have to dig into the source to see what works. It typically sets variables that can be used by later startup scripts. It's executed relatively early, after loading resources but before starting any program such as a key agent, a D-Bus daemon, etc. xinitrc, because in that case startx falls back on the same session startup scripts that are used for GUI login. It's also executed from startx if the user doesn't have a. ~/.xsessionrc is executed on Debian (and derivatives such as Ubuntu, Linux Mint, etc.) by the X startup scripts on a GUI login, for all session types and (I think) from all display managers. xsession to run.) Its role is both to set login-time parameters (such as environment variables) and to start the GUI session. xsession is always executed, but with modern display managers that give the user a choice of session type, you usually need to pick “custom” for. (With the historical display manager xdm. ~/.xsession is executed when you log in in graphical mode (on a display manager) and the display manager invokes the “custom” session type. xinitrc is to start the GUI part of the session, typically by setting some GUI-related settings such as key bindings (with xmodmap or xkbcomp), X resources (with xrdb), etc., and to launch a session manager or a window manager (possibly as part of a desktop environment). This program is executed after logging in: first you log in on a text console, then you start the GUI with startx.
~/.xinitrc is executed by xinit, which is usually invoked via startx.
0 kommentar(er)
